Clear Records, Fewer Surprises: A Six-Document Test for UK Commercial Projects

A UK commercial project can look calm on a status report and still be drifting. The warning signs are often administrative rather than dramatic: a decision that cannot be found, a change that was discussed but never logged, a payment milestone that no one can quite define. The ten-minute test is simple. Ask the project team to produce six documents within ten minutes. If they can, the project has a commercial memory. If they cannot, the client should ask why.

The six documents are not intended to be elaborate. They are the minimum records that allow a client to understand what was agreed, what has changed, what might go wrong, who decided what, when money is due, and what completion means. Each should be short enough to use and current enough to trust.

1. The scope baseline

What good looks like. A scope baseline states the agreed deliverables, the exclusions, the assumptions and the acceptance criteria. It carries a version number and a date, and it matches the contract rather than an early presentation. It can be a concise main document with technical appendices, but the commercial core should be readable by a non-specialist.

What goes wrong without it. Without a baseline, every conversation about scope becomes a debate about memory. Suppliers may deliver what they believe was implied; clients may expect what they believe was promised. Extra work becomes easier to request and harder to price, because there is no fixed point from which to measure change.

Questions to ask. What is explicitly excluded? Which version is current, and who approved it? Where are the acceptance criteria recorded? If a new supplier joined tomorrow, could they understand the boundary of the work from this document alone?

2. The change log

What good looks like. A change log records each requested change, its date, the requester, the cost and time impact, the approval status and the effect on other deliverables. It is sequential, and each entry links to the approval that authorised it. It does not need to be complex; a controlled spreadsheet can be sufficient if it is kept current.

What goes wrong without it. Changes become invisible. Small requests accumulate into a material shift in cost or programme, but no single conversation appears significant. At final account stage, the client and supplier can spend weeks reconstructing what was agreed. The supplier may have a stronger record simply because it raised the changes.

Questions to ask. How many changes are open, approved or rejected? What is their total value and time impact? Which changes have been approved but not yet reflected in the scope baseline or payment schedule? Who is responsible for keeping the log current?

3. The risk register

What good looks like. A risk register lists the main risks, their owners, likelihood and impact, mitigation actions, trigger points and review dates. It is live rather than archival. The top five risks should be visible to the client and discussed at project reviews, not buried in a workbook.

What goes wrong without it. Risks are managed informally until they become issues. A supplier may be aware of a supply-chain constraint, a regulatory approval or a site-access problem, but the client learns about it only when the programme is affected. Without named owners, mitigation is everyone's intention and no one's task.

Questions to ask. What are the top three risks to cost and programme? Who owns each one? What would trigger the contingency plan? When was the register last reviewed, and what changed?

4. The decision log

What good looks like. A decision log records significant decisions, the date, the decision-maker, the rationale and any documents affected. It is short and factual. It does not need to capture every operational choice, but it should capture the decisions that change scope, cost, programme or risk.

What goes wrong without it. Teams relitigate decisions that were settled months earlier. Accountability becomes unclear, especially when a decision was made in a meeting but never confirmed in writing. New stakeholders reopen old questions because the rationale is missing.

Questions to ask. Who made this decision, and under what authority? What options were considered? Which documents or plans changed as a result? If the decision were challenged, where is the record?

5. The payment schedule

What good looks like. A payment schedule sets out milestones, amounts, the evidence required to trigger an invoice, due dates and any retention or set-off arrangements. It aligns with the scope baseline and acceptance criteria. Each milestone should be objectively demonstrable, not a matter of opinion.

What goes wrong without it. Cash flow becomes a source of friction. Suppliers invoice against progress that the client does not accept; clients withhold payment because the evidence is incomplete. The dispute is rarely about the money alone; it is about the absence of a shared definition of what the payment was for.

Questions to ask. What exactly triggers each invoice? What evidence must be provided? Who certifies acceptance, and by when? How are changes reflected in the schedule? What happens if a milestone is partially complete?

6. The handover criteria

What good looks like. Handover criteria define what completion looks like: the documents to be provided, training to be delivered, tests to be passed, defects to be recorded and the sign-off required. They are measurable and agreed before the final phase, not invented at the end.

What goes wrong without it. Completion becomes a matter of negotiation. Snagging lists expand, final payments are withheld, and operational teams inherit assets without the information they need. The supplier believes it has finished; the client believes it has received something incomplete.

Questions to ask. What does 'complete' mean in measurable terms? What evidence will be required? Who signs off, and what happens to minor defects? Are the handover documents listed and owned?

Making the ten-minute test routine

The value of these six documents is not in their length. It is in their currency and connection. A scope baseline that does not match the change log is a false comfort. A payment schedule that ignores acceptance criteria invites dispute. A risk register without owners is a list of worries.

UK commercial clients should ask for the six records at the start of a project and test them at regular intervals. Ten minutes is enough to reveal whether the project is being controlled or merely reported. Clarity is not an administrative overhead. It is one of the most effective commercial controls available.