November 20, 2026

Key personnel clause in your first enterprise contract

A customer contract, not a VC term sheet: what a key personnel clause binds, when to offer roles instead, and what to do about contractors.

Startup

Guide

A key personnel clause in an enterprise customer contract names the engineers you must keep on the work and requires the customer's consent to swap them. Agree to it only for people you can actually keep, which means employees. For contractors and vendor-placed engineers, offer a role, a seniority floor and a substitution process, and match their notice terms to your promise before you sign.

What does a key personnel clause commit you to?

It binds you to five things. The named individuals. The customer's consent before you swap one. Notice of the swap. A quality bar for the replacement. A remedy if you break the rest.

Federal contracts use the clause, for example the HUD clause at 48 CFR 2452.237-70. It says no diversion of a named person happens without the contracting officer's written consent. The contractor must also notify the customer "reasonably in advance", with a justification and proposed substitutes. It sets no number of days, so you set the notice period yourself in a commercial deal. Commercial software contracts borrow the idea. Morgan Lewis's sourcing blog describes it in IT outsourcing. Identify the key people, give advance notice of changes, and let the customer take part in vetting key personnel before they join the account.

The clause gives the customer continuity of named staff and a say in who works on their system. The risk for you is that the contract fixes people in place, and people aren't fixed. (The "key person clause" in a VC term sheet is a different thing: it protects investors if named founders or partners leave.)

Should you name people, or roles?

You have three options, and they commit you to very different things.

OptionWhat you promiseFits when
Named peopleThese individuals, until the customer agrees otherwiseYou control the person's availability
Named roles with a seniority floorSomeone at this level fills this seatA pool of contractors rotates
Substitution process onlyHow a change gets proposed, approved and handed overThe work isn't tied to individuals

Our rule: name a founder CTO as technical lead without a second thought, and name employees you're confident will stay. Everyone else goes in by role and level. A seniority floor plus the customer's approval right gives the customer continuity without chaining you to individuals.

Here's how it reads as example wording, not as any standard form: "Supplier will keep the following individuals assigned to the Services: [CTO], [Engineer A]. Supplier will keep the following roles filled at the stated level: [Senior backend engineer, 5+ years]. Any substitution requires Customer's prior written approval." The role line is the counter-offer.

What changes when a named engineer is a contractor or comes through a vendor?

It changes who can keep the promise.

First, the customer's clause can reach people you don't employ. The HUD clause defines "personnel" to include employees of subcontractors, affiliates, joint venture partners and team members. A freelancer or a vendor's engineer named in your schedule is inside the clause, and you're the one who answers for them. GovCon Giants, writing about US federal proposals, says the prime stays responsible to the customer for subcontractor performance. Until a substitution is approved, the contractor may be technically in breach.

Second, your promise is only as good as the paper behind the person. If your freelancer can leave on shorter notice than the 30 days you promised the customer, you're exposed. That's logic, not a legal rule. Federal practice offers the fix: GovCon Giants advises letters of commitment from non-employees and a teaming agreement stating their commitment and your rights if they become unavailable. For a startup, that means the notice period and replacement terms in your own development agreement with a vendor must match what you sign with the customer.

Third, watch the delegation line. A Law Insider sample bars passing key duties to "another Contractor employee, subcontractor or agent" without written consent. If your customer's draft has a line like that, your own vendor may need the customer's approval before handing work to someone else.

Fourth, don't write terms that make a freelancer look directed like an employee, such as fixed hours set by you or an exclusive assignment to one customer. How to run mixed teams is covered in running contractors and employees as one team.

Search more than 300,000 open roles in one place
From more than 19,000 companies across the UK, the US and Spain. Free during the open beta, until the end of November.
Try Job Search

What happens when a named person resigns, falls ill or gets pulled?

Real filings give a feel for the usual answers; read each as an example, not a norm. Afterpattern collects clauses from SEC filings. The MR2 Group sample excuses illness, death and termination of employment, and asks for at least 30 calendar days' written notice of a substitution "if possible". An IDEX Biometrics sample covers full-time assignment, where reassignment needs the client's consent unless the person resigns, is dismissed, can't perform or is removed at the client's request. Accept carve-outs like these. They're what lets you survive an ordinary resignation.

Then comes the remedy. In the same IDEX sample the client can interview candidates and end the affected SOW without penalty. ContractKen's client-side template goes further: replacement approval, a 25% fee reduction, or termination on 15 days' notice. Offer the first, resist the fee cut, and make any termination right apply to the affected SOW only. Ask the customer's procurement team for their key personnel schedule and how they've handled past waivers.

Two things to add yourself. Put an overlap period in the clause so the leaver trains the replacement, using a 30-day knowledge transfer plan as the template. And settle who pays when a swap costs the customer money. Morgan Lewis lists training reimbursement as a remedy when turnover exceeds an agreed service level, so a customer may ask you to repay its training costs after a breach. Decide how much of that you'll accept before they ask.

A four-person SOW, before and after

Take a 20-person SaaS company. Its first SOW names four engineers: the CTO and one other employee, a freelancer on a B2B contract, and an engineer placed by a vendor.

The customer's draft, in example wording modelled on the MR2 sample: no substitution without written consent; the replacement's experience and education at least substantially equal; 30 calendar days' written notice before a substitution, if possible; carve-outs for illness, death and termination of employment.

Before: the startup signs as drafted. The freelancer's contract needs N days' notice, a number you read off your own contract. The vendor's replacement terms are unknown. If N is below 30, a freelancer who gives N days leaves the startup holding a 30-day promise it can't keep, and the startup is the party in breach of the customer's SOW.

After: the startup names the CTO and the employee. It names the other two by role and level, for example "senior backend engineer, 5+ years". It keeps the customer's approval right and the 30 days' notice, adds an overlap period for handover, and asks the vendor in writing for matching notice and replacement terms before signing. The freelancer gets a notice period at least as long as the customer's.

Nothing was refused. The startup traded the promise it couldn't back for one it can, and fixed the paper underneath.

What this means for the clause you sign

You're deciding who goes into the schedule by name. Our judgment: name employees only. For contractors and vendor-placed engineers, counter with the role, the seniority floor and a substitution process, and keep the customer's approval right, which answers the continuity concern behind the clause.

Before signing, send two asks this week. Ask each contractor to match the notice you're promising. Ask each vendor for its replacement terms in writing. If either says no, that person goes in by role. Have counsel read the final redline.

For the other decisions that land around a first enterprise deal, the Startup CTO guides: leadership, diligence and the first hires are the next stop.

If your named engineers come through a vendor

When two of the engineers your customer names come through a vendor, the vendor's replacement terms are what you can actually promise. If you're choosing that vendor, compare those terms first. HighCircl places senior engineers and replaces one at no additional recruitment cost if the engagement isn't working, which is the kind of written term to look for. See HighCircl's hiring service.

FAQ

What is a key personnel clause?

It's a contract term that names the people a supplier must keep on the work and requires the customer's consent to replace them. It usually adds notice of a change, a quality bar for the replacement, and a remedy such as replacement approval, a fee reduction or termination of the affected SOW.

Can contractors or vendor staff be named as key personnel?

They can be named, and the federal HUD clause defines personnel to include subcontractor and team-member employees. You're still the one answerable to the customer. Name them only if their own contract gives you matching notice and replacement terms. Otherwise name the role and level.

Can the customer refuse the person I propose as a replacement?

Often, where the contract has a consent right: the Geron sample gives the client approval of replacements, "not to be unreasonably withheld, conditioned or delayed". Treat that as one example, not a rule.

What if a named engineer resigns or falls ill?

Ask for a carve-out. The MR2 Group sample excuses illness, death and termination of employment. Give notice as early as you can, propose a replacement of equal experience, and plan a handover. Ask your lawyer what your own contract allows.

Is this the same as the key person clause in a funding term sheet?

No. The term-sheet clause protects investors if named founders or partners leave. This clause sits in a customer contract and protects the customer's continuity of service.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.

Take Me to the Experts

Access our network of industry-leading software engineers.

Start Now