Key Person Risk: When Your Best PM Holds Everything in Their Head

The Scenario Nobody Plans For

Sarah is your best PM. She has been running a $80M infrastructure project for 14 months. She knows the NZS 3910 head contract inside out. She knows which Special Conditions tightened the Clause 13.3.1 notice period to 10 working days. She knows which variations are still under assessment. She knows the contractor's commercial manager well enough to resolve issues with a phone call before they escalate.

Sarah goes on three weeks' leave.

Her replacement is competent. They have worked NZS 3910 projects before. But they do not know this contract. They do not know which of the 180 Special Conditions changed the standard payment terms. They do not know that a notice of potential claim was issued 8 working days ago under the amended time bar. They do not know that the contractor's payment claim is due next Tuesday and the response window closes the following Friday.

When Sarah goes on leave, the project goes on leave too. The obligation tracking stops. The institutional knowledge disappears. The risk exposure quietly multiplies while everyone assumes it is under control.

This Is Not an Edge Case

Every PMC principal reading this knows exactly what I am describing. You have a PM who is exceptional. The clients love them. The contractors respect them. They have never missed a deadline. And you have quietly been terrified about what happens if they leave the firm.

The NZ construction industry is in the middle of a skills shortage that has been running for years. 486 construction companies went into liquidation in the year to March 2024, tripled since 2020. The people who are good are in high demand. They get offers. They get headhunted. They burn out.

Key person risk is not something that might happen. It is something that will happen. The only question is whether your firm and your project are prepared for it when it does.

What Lives in Their Head

The issue is not that your PM is the only person who can manage a project. You have other qualified people. The issue is what specific knowledge lives exclusively in one person's memory:

• Contract-specific amendments. An NZS 3910 contract with a government agency can contain anywhere from 7 to 310 Special Conditions. Each one modifies the standard form. Your PM knows which modifications are critical. Nobody else does unless they have read every one.
• Active deadline tracking. Under the Construction Contracts Act, missing a payment schedule response turns the full claimed amount into a debt payable immediately. Your PM knows what is due when. Their spreadsheet might too, but does anyone else know how to read it?
• Correspondence context. The formal letter says one thing. The conversation that preceded it meant something different. Your PM knows the context behind every instruction, every notice, every claim. That context is essential for making the right commercial decision.
• Relationship dynamics. Who to call when an issue needs resolving before it becomes formal. Which subcontractors are struggling financially. Where the contractor is likely to push on variations. This is pattern recognition built over months on the project.

If any of that knowledge exists only in one person's head, it is not institutional knowledge. It is personal knowledge. And personal knowledge leaves when the person does.

Handover Documents Do Not Solve It

The standard response to key person risk is documentation. "Sarah will prepare a handover before she goes on leave." And Sarah does. She writes a five-page summary of where things stand. It covers the major items. It is out of date within 48 hours of her departure because the project keeps moving.

A handover document is a snapshot. It captures a moment in time. It does not track the 15 new pieces of correspondence that arrive in the first week Sarah is away. It does not flag the notice period that started running two days after she left. It does not update itself when the contractor submits a payment claim with three new variation items the replacement PM has never seen before.

Documentation is necessary but not sufficient. What you need is a living system.

What Solves Key Person Risk

Key person risk is solved when the contract knowledge exists in a system that any qualified professional can access, understand, and act on immediately.

That means:

• Every obligation from every contract has been ingested and mapped, including all Special Conditions amendments
• Every deadline is tracked automatically, not in a spreadsheet that one person maintains
• The daily priority view shows what needs attention today regardless of who is looking at it
• CCA payment claim deadlines are tracked with zero tolerance, no matter which PM is on the project that week
• The history of every correspondence, instruction, and notice is linked to the relevant obligation

When the replacement PM arrives, they do not need Sarah's five-page handover. They log in. They see what is due this week. They see the full history of every active item. They can make informed decisions from Day 1 because the system holds the contract knowledge, not the individual.

This Is a Firm-Level Issue, Not a Project-Level One

Key person risk does not just threaten individual projects. It threatens the firm. If your ability to deliver depends on specific individuals, you cannot grow. You cannot take on more work without hiring more stars. And when one leaves, you lose more than a team member. You potentially lose the client.

A firm that runs on systems can bring new people up to speed quickly. A firm that runs on individuals cannot. That is the difference between a practice and a firm. Between a lifestyle business and one that can grow.

The firms that solve key person risk are not the ones that find better people. They are the ones that build systems so good that any qualified professional in the firm can step into any project and perform. Not because the people are interchangeable, but because the system ensures they have everything they need from the moment they arrive.

Sarah is still your best PM. The system does not replace her. It means the project can survive without her.