Professional services engagements are bought on the strength of specific people. The partner who ran the discovery workshop, the architect who understood the legacy estate, the delivery lead with prior experience in the sector. The proposal names them, the customer selects partly because of them, and the agreement includes a key personnel clause recording the point.
Six months later the architect is on a different account. There was no notification, no substitution request, and no breach was raised, because nobody was comparing the schedule of named individuals against the people actually billing time. The clause did its job at signature and nothing since. When the customer eventually raises it, usually during a difficult delivery review, the supplier points out that the change happened months ago and was never objected to, and the point is effectively conceded.
This is a tracking failure more than a drafting failure, though the drafting usually helps it along. A clause that names people without committing their time, and provides a remedy that amounts to a right to object, is difficult to enforce even when someone notices. The fix has two halves, and the second is the same point made about order form and master agreement conflicts, which is that terms only operate if the operational data can be tested against them.
What a binding clause contains
Five elements turn a statement of intent into an obligation. Each can be evidenced from data the engagement already produces, which matters more than how strongly any of them is worded. Enforceability here is a function of observability rather than of drafting severity.
- Named individuals and roles, held in a schedule referenced by the agreement so the list can change by notice rather than by amendment.
- Minimum allocation, expressed as a percentage of working time or days per month, measured against the same timesheets used for billing.
- Substitution procedure, requiring notice, a replacement of equivalent standing, a handover period and customer approval within a stated window.
- Notice period for planned reassignment, distinguishing supplier-initiated moves from departures the supplier did not choose.
- Remedy with commercial effect, such as a rate reduction, a right to reject candidates or termination of the affected workstream.
Minimum allocation is the element most often omitted and the one that does most of the work. Without it, the clause restricts removal but not dilution, and dilution is the common failure. A named lead who moves from four days a week to two is not removed, so no substitution process is triggered, and the customer experiences a material reduction in the thing it paid for with no contractual event to point at. By the time the effect is visible in delivery quality, the engagement is usually too far advanced for the customer to do anything useful about it.
Named individuals in the body of an agreement require an amendment to change, which means in practice that the list is never updated and quickly becomes fiction. A referenced schedule updatable by notice stays accurate, and an accurate list is the precondition for enforcing anything.
Making substitution workable for both sides
A substitution clause that is too tight invites breach and a clause that is too loose invites dilution. The objective is a process both sides can follow during a normal week, not a gate that is bypassed the first time somebody resigns. Five provisions keep it usable.
- Equivalence criteria. Define what equivalent means, in years of relevant experience, certifications or prior comparable engagements, rather than leaving it open.
- Customer response window. A stated period to approve or reject, with approval deemed given on silence, so the process cannot stall delivery.
- Handover overlap. A minimum period with both individuals available, which is the provision that actually preserves continuity.
- Interview right. The ability to meet a proposed replacement before approving, which costs the supplier little and reassures the customer.
- Cap on substitutions. A limit on how many named roles may change within a period, preventing wholesale team rotation by sequential approvals.
A five-step implementation roadmap
Step 1, Extract the named list into a register
For every active services engagement, pull the named individuals and their roles into a structured list against the contract record. In most portfolios this exercise alone reveals engagements where none of the named people are still involved.
Step 2, Add allocation to the standard template
Amend the template so every named role carries a minimum allocation. Suppliers will push back on precision, and a range with a floor is a reasonable landing point. A floor is still enforceable; an unstated expectation is not.
Step 3, Compare named against actual each period
Run a monthly comparison between the named schedule and the timesheet or resource report. Treat material variance as a substitution event requiring a retrospective request, which is a mild remedy that nonetheless changes supplier behaviour quickly.
Step 4, Track substitution requests to a decision
Record each request with its proposed replacement, the equivalence evidence, the response deadline and the outcome. An approval trail matters later, when the engagement is being reviewed and the question is how the team came to change.
Step 5, Review remedies at renewal
At renewal, look at whether the clause was tested during the term and how it performed. Clauses that were breached without consequence should be strengthened or dropped, since an unenforced provision teaches both sides that the schedule is decorative.
Keep named teams honest
Named schedules, allocations and substitution approvals tracked against delivery data.
The supplier's legitimate interest
It is worth stating the other side of this fairly, because a clause negotiated as if the supplier were acting in bad faith tends to be resisted and then ignored. Professional services firms manage a finite pool of senior people across many engagements, and rigid naming reduces their ability to respond to a crisis elsewhere or to develop staff. A clause that names three individuals rather than ten, commits meaningful allocation for those three, and offers a workable substitution path is more likely to be honoured than one that locks down the whole team. The same balance applies in channel terms, where overly prescriptive obligations tend to go unenforced, as discussed in managing OEM and reseller terms.
Clause elements and how to evidence them
The table maps each element to the evidence that shows whether it is being met. All of it comes from data the engagement already produces.
| Element | Where it lives | Evidence of compliance | Review cadence |
|---|---|---|---|
| Named individuals and roles | Schedule referenced by the agreement | Current schedule with change history | At each change by notice |
| Minimum allocation | Schedule, per named role | Timesheet or resource report | Monthly |
| Substitution approval | Agreement body | Request, equivalence evidence and decision | Per request |
| Handover overlap | Agreement body | Timesheets showing both individuals | Per substitution |
| Remedy applied | Agreement body | Credit note or workstream decision | At breach and at renewal |
The clause is worth having and worth enforcing, but only if someone is going to look. A key personnel provision in an agreement that nobody monitors is a statement about what the customer hoped for at signature, which is a different thing from a commitment the supplier has to keep. The monthly comparison that makes the difference takes a few minutes once the named list exists as data, and it is the only part of this that cannot be solved by better wording.
For related guidance, see The IT leader’s guide to SaaS vendor contract sprawl, Auto-renewal clause risk in enterprise SaaS contracts and Open source license clauses in customer contracts.
