Key personnel clauses: what they bind and how to write them

The clause that buys people

Almost everything in a federal contract is written in the language of outcomes. Deliver the software. Meet the specification. Hit the milestone. The key personnel clause is the exception. It names individuals, binds their time, and makes their departure a contractual event rather than an internal staffing matter. Teams that treat it as boilerplate discover, usually about four months into performance, that they signed away something they did not price.

There is no government-wide FAR clause for key personnel. That surprises people. Search FAR Part 52 and nothing universal comes back. The obligation is created either by an agency supplement or, far more often, by a clause the contracting officer drafts into the solicitation. Under the uniform contract format at FAR 15.204-1, Table 15-1, that clause lands in Section H, Special Contract Requirements. Section L tells you what to submit with the proposal (resumes, commitment letters, page limits on each). Section M tells you how the evaluators will score what you submitted.

Agency supplements fill some of the gap. The HHS Acquisition Regulation clause at HHSAR 352.237-75, Key Personnel, is a clean example of the standard mechanics: the contractor identifies key personnel, must notify the contracting officer in advance of any change, and cannot substitute without approval. Many defense solicitations use a locally written H-clause with almost identical language. Because those clauses are drafted locally, the terms swing widely. One contract binds two people. Another binds nine. One asks for a substitute with "equal or greater qualifications." Another requires the contracting officer's written consent before the replacement may charge a single hour to the contract. Read Section H every time. Do not assume you know it from the last bid.

Three obligations, plus one nobody reads

Designation. The clause lists the positions and the humans filling them. Once the contract is signed, that list is contract content. Moving a person off the job is a change to the contract, not a decision the program manager makes on a Friday afternoon. Firms that name eight key people because it looked impressive in the proposal have created eight separate approval gates for themselves.

Availability. Most clauses attach a level of effort to each name: full time, 50 percent, 480 hours over the base period. That number is auditable. On cost-reimbursement and labor-hour work, timecards are the evidence, and a variance between the promised percentage and the billed percentage is the easiest finding an auditor will ever write.

Substitution. The approval gate. Standard language requires advance written notice, a substitute resume, a qualification comparison, and the contracting officer's written consent before the replacement starts. Thirty days advance notice is the most common figure. Some clauses shorten it to fifteen for unplanned departures and stretch it to sixty for voluntary ones.

Notification. The obligation almost nobody reads carefully, and the one that causes the most damage. The notice clock usually starts when the contractor learns a key person is leaving, not when the person actually walks out. A two-week resignation notice combined with a thirty-day advance-notification requirement means you are already late on the day you find out. Build the internal reporting path before you need it.

Clause element	Typical language	What it actually obligates
Designation	"The following individuals are designated as key personnel..."	Locks the named list into the contract. Adding, removing, or reassigning a name is a contract action.
Availability	"shall be available at not less than a 50 percent level of effort"	Creates an auditable time commitment. Timecards, not intentions, are the proof.
Substitution	"no substitution without prior written approval of the Contracting Officer"	Gives the CO a veto. A substitute who bills before consent creates a compliance finding.
Notice period	"thirty (30) days advance written notification"	Runs from when the contractor learns of the change, which is usually earlier than expected.
Qualification standard	"of equal or greater qualifications"	Measured against the resume you submitted. An inflated resume raises your own replacement bar.
Remedy	Often silent	Silence favors the government. Consideration, fee reduction, or a management rating in the performance record.

Availability is priced, not just promised

An availability commitment is a cost claim as much as a staffing claim, and evaluators treat it that way. FAR 52.222-46, Evaluation of Compensation for Professional Employees, applies to negotiated solicitations above the simplified acquisition threshold (currently $250,000 under FAR 2.101) that will require professional employees. It requires the offeror to submit a total compensation plan, and it directs the agency to assess whether that plan is realistic enough that the proposed people will actually take the job and stay in it. A senior engineer named at a rate the market would not support is a finding waiting to be written.

Cost realism analysis under FAR 15.404-1(d) is the second checkpoint. On cost-reimbursement work, the agency may adjust your probable cost upward when the labor mix or the rates do not match the work described. Compensation reasonableness under FAR 31.205-6 is the third. Naming a principal engineer at half time, then pricing that half time at a rate that would never retain the person, is not one weakness in a proposal. It is three findings in three different volumes, and evaluators read across volumes.

One more boundary worth holding. FAR 37.104(a) defines a personal services contract as one that, by its express terms or the manner of administration, makes contractor employees look like government employees under direct supervision. Key personnel clauses drift toward that line whenever a customer starts directing named individuals instead of managing the contract. A subcontractor should not accept flow-down language that hands day-to-day supervision of its engineers to anyone outside its own management chain.

The pre-award trap: a name that goes stale

Months pass between proposal submission and award. People resign in that window. The rule that catches firms is this one: when an offeror knows that proposed key personnel have become unavailable and says nothing, the proposal contains a material misrepresentation. GAO has sustained protests on that basis for years. The agency may exclude the proposal from the competition, and a competitor who learns the facts can protest an award made in reliance on the stale name.

What makes this ground dangerous is how documentary the evidence is. A public profile update. A conference bio listing a new employer. Protest counsel find it in an afternoon.

The defense is not clever drafting. It is a short chain between the person and the proposal. Re-confirm availability in writing at submission. Re-confirm it again at any discussions or final proposal revision round. If the person has left, tell the contracting officer and offer a substitute before the agency finds out another way. A firm that self-reports a departure and proposes an equally qualified replacement is in a far better position than one that hopes the resume ages quietly.

How a substitution actually moves

Two details decide whether that sequence goes smoothly. The first is the qualification comparison. Write it as a table, line by line, against the original resume: years in the discipline, specific systems, clearances, certifications, publications where relevant. A narrative paragraph asking the contracting officer to trust you is the slowest possible path to consent.

The second is the overlap. Offering a two-week paid handoff at your own expense converts a contract problem into a goodwill deposit, and contracting officers remember which contractors absorbed the transition instead of billing it.

When a named person leaves anyway

Sometimes there is no substitute of equal qualification available, or the customer simply does not want one. The clause itself is usually silent on remedy, and that silence works in the government's favor. In practice, four things happen, in rough order of frequency.

Consideration. The most common outcome. The contractor gives something back: a fee reduction, absorbed transition labor, an added deliverable, a schedule concession. It is negotiated, documented in a modification, and closed.

Performance record. Personnel churn shows up in the Management or Staffing rating under FAR 42.1502 and 42.1503. That record is retained and used in later source selections, which means a departure handled badly follows the firm into competitions it has not yet entered. This is the cost that lands years later, on a bid nobody has connected to the original event.

Reduced scope. If the named person was the reason a task existed, the government may descope. Common on advisory and specialized-analysis work where a single expert was the deliverable.

Termination. Rare, and reserved for cases where the loss guts the contract or where the original naming looks like it was never in good faith. The government's real hold is not the termination clause. It is that every future evaluation reads the last performance record.

SBIR and STTR: stricter than any H-clause

On SBIR and STTR awards, personnel rules come from statute and the SBIR/STTR Policy Directive, not from a locally drafted clause, and they cannot be negotiated. The principal investigator on an SBIR award must be primarily employed by the small business, meaning more than one-half of the PI's time, for the duration of the project. The PI must be an employee of the firm at award, not a consultant routed through a subcontract. Any change of PI requires the agency's prior written approval.

Work-percentage floors compound the effect. Under 15 U.S.C. 638 and the Policy Directive, the small business performs at least two-thirds of the research in SBIR Phase I and at least one-half in Phase II. STTR splits differently: at least 40 percent to the small business, at least 30 percent to the research institution, and the PI may be primarily employed by either party. Small business size and ownership eligibility sit alongside these rules at 13 CFR 121.702.

The practical consequence for teaming: a prime that plans to staff an SBIR award mostly from a subcontractor's bench has a structural problem no amount of clause drafting fixes. Get the workshare and the PI employment right first, then write the personnel commitments to match.

How a sub commits named engineers without over-promising

A prime asking for named staff is asking for risk transfer. That is fine. The answer is to accept the risk you can actually carry and price the rest, rather than signing a commitment that quietly depends on nobody changing jobs for eighteen months.

• Name only people who have signed a consent to be named, before the bid goes out.
• State level of effort as a band with a floor, tied to a stated award-date window.
• Identify a qualified alternate in the same paragraph as the primary.
• Define "unavailable" in writing so the trigger is not argued later.
• Accept a substitution standard that mirrors the prime contract, never a stricter one.
• Refuse exclusivity that outlives the bid unless it is paid for.
• Match the resume format the solicitation prescribes, including any required school, degree, and year fields.
• Keep supervision of your engineers inside your own management chain.

The band matters more than it looks. "Available at 50 to 75 percent, with a floor of 50 percent, for a period of performance beginning within 180 days of the proposal due date" is a commitment a firm can keep. "Full time for the life of the program" is a sentence that will be read back to you in a cure discussion. Evaluators do not reward the second phrasing over the first; contracting officers reward the one that turns out to be true.

The award-date window is the other quiet protection. Solicitations slip. An availability promise with no time boundary asks an engineer to hold capacity for a contract that may award fourteen months late. Stating the window is standard, and no reasonable prime objects to it.

Language a subcontractor should ask the prime for

Mirror, do not multiply. The sub's key-personnel obligation should track the prime contract clause exactly. If the prime contract allows thirty days notice and a substitute of equal qualification, the subcontract should say the same. Flow-downs that add a stricter standard at each tier are common and are usually negotiable on request.

Notice runs both directions. The prime should be obligated to tell the sub about schedule slips, descopes, and stop-work actions that affect the named engineers' availability. A one-way notice obligation puts the sub in default for conditions the prime created.

Replacement right, not replacement duty. The sub should have the right to propose a qualified substitute and a reasonable period to do it, rather than an automatic breach the day a person resigns.

A definition of "key." If the subcontract names five people but the prime contract designates two, the sub is carrying three commitments the government never asked for. Ask which names are contractually key and which are proposal color.

Cost recovery for transition. If the prime wants a paid overlap during turnover, that is reasonable. Put it in the subcontract with a rate and a cap, before it is needed.

What to send us

If you are bidding a solicitation that requires named AI, ML, data, or cloud engineers, send three things to [email protected]: the solicitation number, the Section H key personnel list or the Section L instruction that describes it, and the close date. You will get a yes or no within 24 hours. If it is a yes, you get named resumes with signed consent to be named, a stated level of effort, and a one-page scope within three business days, in time to fold into your volume rather than after it.

Frequently asked questions