A key personnel clause names the people a contractor promised and limits how they can be replaced. When a named project manager resigns, the contractor owes the owner notice, an equal replacement and often a wait for approval. Most contractors have two weeks to do what the contract assumes takes a month, so the plan has to exist before the resignation.

The proposal won on a resume. Eight months into the job, the resume works for someone else. Most contractors treat that as a staffing problem, and on a contract with a key personnel clause it is also a compliance problem with a deadline attached. The owner is entitled to ask who is coming, when, and why that person is as good as the one in the proposal. Few contractors can answer on the day the question arrives.

What does a key personnel clause require of a contractor?

A key personnel clause requires the contractor to keep named individuals on the project, to tell the owner before any of them is moved or lost, and to propose a replacement of equal or better qualifications for the owner’s approval. The names come from the proposal.

Federal contracting offers the clearest public wording. The Department of Health and Human Services key personnel clause calls the named people essential to the work, asks for notice at least 30 days before a contractor voluntarily diverts one of them, and requires a written justification showing how the replacement meets or exceeds the contract’s requirements. Federal construction contracts separately require a competent superintendent on site who is satisfactory to the contracting officer. For the departing manager’s part in a clean transition, see our note on resigning mid-project. A manager who leaves during a construction claim is a witness as well as a name on the list.

Private owners write their own versions into amended standard agreements. Hospital systems, universities, data center developers and public agencies using CM-at-risk or design-build delivery nearly always name the project executive, the project manager and the superintendent. Some add the preconstruction lead and the MEP coordinator. In a qualifications-based CM-at-risk selection those names carry much of the score, so a contractor naming someone it has not yet hired should settle that proposal staffing before the interview. The stricter versions give the owner a right to interview the replacement, and a few attach a credit or a withheld fee if a named person leaves in the first year. On Gulf Coast plant work the owner knows the contractor’s industrial project manager by name, so the same exposure exists whatever the clause says.

None of that wording is exotic. What makes it bite is the calendar.

Why does a personnel clause turn a resignation into a contract event?

A resignation gives the contractor less time than the clause assumes. The contract expects weeks of warning and an approved successor. The departing project manager gives two weeks. The gap between those numbers is where the owner’s confidence, and sometimes the contractor’s fee, is lost.

Put numbers on one case. A project manager on a negotiated hospital job in Houston gives 14 days of notice. The contract asks for 30 days of warning before a change in named staff. The contractor has nobody on the bench, so it starts an outside search, and a careful search for a senior project manager is measured in months: assume 90 days before someone is in the seat.

Days available against days needed Bar chart, Days available against days needed: Notice the manager gives 14 days, Warning the clause expects 30 days, Outside search to a start 90 days. Days available against days needed A resignation gives 14 days. The clause assumes 30, and an outside replacement takes about 90. 0 days 50 days 100 days 150 days 200 days Notice the manager gives 14 days Warning the clause expects 30 days Outside search to a start 90 days Source: Worked example in this section; 30 days per 48 CFR 352.237-75
A resignation gives 14 days. The clause assumes 30, and an outside replacement takes about 90.

For most of those 90 days the project runs on an acting manager the owner did not choose. A resignation is not a voluntary diversion, so the contractor is rarely in breach on day one. It is, though, in a negotiation it did not prepare for, with an owner who now reads every late RFI and every change-order dispute as evidence that the team was oversold.

Tenure data says to expect this. The Bureau of Labor Statistics put median employee tenure at 3.9 years in its January 2024 tenure release, and a large project can run nearly that long from pursuit to closeout. On any long job, somebody named in the proposal will probably not be there at the end.

So who inside the contractor is watching for it?

Who should own the key personnel list inside the contractor?

Operations should own it, with one named person accountable for every contract that carries a clause. In most firms nobody does. Business development chose the names to win, legal accepted the wording to close, and operations inherited a promise it never read.

The split is structural. The people who negotiate the contract sit where the documents live, and the people who staff the job sit where the work is. Each makes sensible decisions on different information. A vice president moves a strong project manager to rescue another job, which is a reasonable call, and learns three weeks later that the move needed the owner’s written consent.

A one-page register fixes most of it:

Register fieldWhat it recordsWho updates it
Named rolesEvery person each contract namesOperations lead
Clause termsNotice period, approval right, any fee consequenceContracts or legal
Identified successorAn internal name, or “none”Operations lead
Flight riskHonest read on each named personDivision leader
Owner contactWho must be told, and howProject executive

The successor column is the one that matters. Where it reads “none” against a named project manager on a large job, the contractor has found its exposure months before the owner does. That same column is what a careful owner’s representative is trying to see from the outside.

How should an owner’s representative read a proposed team?

Read the team for depth, and treat the resumes as the easy part. Ask who steps in if each named person leaves, what share of each person’s time is committed, and how many named people this contractor has replaced on its last five projects.

Useful questions at the interview stage:

  • Who is the second? A contractor that can name the assistant project manager and describe that person’s last job has a bench. One that says “we would find someone” does not.
  • What else is the project manager running? A named manager committed to three other jobs is present in the proposal and absent on site.
  • What happened last time? Every contractor has lost a named person mid-project. The good ones describe what they did in the first week.
  • How is the approval right written? A clause with no timeline for the owner’s response delays the replacement as much as the contractor does.

Surety underwriters ask a version of the same thing, as our note on what a bonding agent looks for sets out, and the logic of bench depth applies job by job as well as firm by firm. Under a multi-party agreement the owner often chooses the people before the firm, as our note on integrated delivery explains, and a named departure weighs more there. The same questions matter more on a takeover project, where a completion contractor proposes a team to finish someone else’s defaulted job for an owner who has already been let down once.

A replacement plan written before anyone resigns

The contractors that handle a named departure well did three things in advance. They knew which contracts carried a clause. They had talked, quietly, to the people who could step up. And where there was no internal successor, they had already started looking.

That last step is awkward, because the search usually cannot be advertised. Posting for a senior project manager on a named hospital job tells the owner, the incumbent and every subcontractor in Houston or Atlanta that the seat is in doubt. Selah Talent Partners runs this work by direct approach: confidential executive search for mandates that cannot be publicly posted, in the way our note on confidential search describes. For contractors in the United States carrying named-staff obligations, the search for a senior project manager is best started while the register still shows a risk and not yet a vacancy.

Where this note does not apply

  • Hard-bid public work with no named staff. If the contract buys a price and a bond, there is no clause to manage, though the superintendent requirement may still apply.
  • Small projects. A six-month tenant improvement rarely justifies a register. One person’s memory is enough.
  • Legal interpretation. Clause wording varies by owner and state. The notes above describe how these clauses operate in practice and are not legal advice on any contract.

If the successor column on your biggest job reads “none”, talk to us before the owner asks the question.

Sources and further reading