The key personnel clause in a QA contract

Testing vendors win work on the strength of the people they present: the test lead who walked through your product, the automation engineer who asked sharp questions about your pipeline. A key personnel clause keeps those people on your account after signature, or at least makes their departure a managed event rather than a surprise.

This post explains the clause, what to insist on, and how to respond to common vendor positions. It draws on the UK government's Model Services Contract, which is public and widely used as a reference. It is not legal advice; have your own counsel review the final wording.

What the clause does

A key personnel clause has three parts:

1. A list of key roles and named people, usually in a schedule.
2. A restriction on removal or replacement, with exceptions.
3. Rules for replacement: notice, overlap, standard and approval.

The Model Services Contract (MSC) Core Terms are a useful model. The supplier must ensure that the key personnel fill the key roles at all times during the term. It may not remove or replace them unless the buyer asks, the person resigns, retires, dies, is on family or long-term sick leave, is dismissed for material breach, or the buyer gives prior written consent, which is not to be unreasonably withheld or delayed.

Notice and vacancy limits

The MSC requires the supplier to give at least 60 working days' notice before removing or replacing a key person, except in cases of death, unexpected ill health or material breach of their employment contract. It also requires that no key role is vacant for longer than 10 working days, and that absences are reported promptly, with temporary cover for short absences.

Those numbers were set for large, long government contracts. For a testing engagement you might agree shorter periods, but keep both mechanisms: a notice period for planned changes and a cap on how long a key role can stay empty.

Handover and replacement standard

The MSC requires planned changes to include adequate periods during which incoming and outgoing people work together, and that the change does not harm the service. The replacement must have qualifications and experience appropriate to the role and be fully competent to do the work of the person they replace.

For testing, the overlap is where product knowledge moves. Without it, you pay for the new tester to rediscover what the old one knew.

What to insist on

• Names, not roles. At a minimum, the test lead. For automation work, the lead automation engineer as well.
• A committed share of time. A named lead who spends a small fraction of their week on your account offers little protection.
• Consent for planned moves. Reassignment to another client is a move the vendor controls. It should need your consent.
• An overlap at the vendor's cost. If the vendor causes the change, it should carry the cost of the handover and the ramp-up.
• Your right to interview replacements. The MSC's standard of equivalent qualifications is useful; the right to meet the person makes it checkable.
• A consequence for repeated changes. For example, treating repeated or unapproved changes as a material breach.

The 2023 US interagency guidance on third-party relationships lists succession and redundancy planning for key personnel as a due diligence factor. Ask about it before you sign, not after the first departure.

Common vendor positions and how to respond

"We cannot guarantee individuals; people leave." Agree. The clause does not stop resignation. It controls planned moves and sets the rules for replacement. Point to the list of exceptions.

"We will replace anyone within two weeks." Speed is not the issue. Ask what standard the replacement must meet, whether you can interview them, and whether there will be an overlap.

"Naming people limits our flexibility." That flexibility is the risk you are pricing. If the vendor needs it, ask for a lower rate or a shorter term in exchange.

"Overlap time is billable." Where the change is at the vendor's initiative, it should not be. Where you request the change, sharing the cost is reasonable.

"Consent will slow us down." The MSC includes a standard that consent is not to be unreasonably withheld or delayed. Offer the same.

Link to the rest of the contract

A key personnel clause works with the general staff replacement terms for non-key team members, with service levels that show whether quality drops after a change, and with the exit plan. Check that the named people are also named in the statement of work.

What this means for your selection

Ask for named people in your RFP, and score staff continuity terms in the scorecard. The contract clause builder includes key personnel and staff replacement clauses you can edit. For more on how vendors assign people, read how QA vendors staff projects and what goes in a software testing statement of work.