The Unclaimed Fortnight: A Pre-Start Protocol for UK Delivery Programmes

In many UK programmes, the delivery clock is treated as starting at the kick-off workshop. Invitations are issued, a room or video bridge is booked, and the first sprint or workstream meeting becomes the symbolic beginning of the work. Yet the days between contract signature and that first session are rarely idle. They are filled with access requests, induction scheduling, clarification emails and quiet waiting. The difficulty is that this period is seldom planned, seldom funded and seldom owned. It becomes an unclaimed fortnight — a phase that exists in practice but not in the plan.

Where the fortnight goes missing

The gap forms for understandable reasons. Procurement teams close a contract and regard the milestone as complete. The supplier awaits a purchase order or a formal instruction to proceed. The client-side delivery team has not yet been stood up, or is still closing previous work. Access to systems, sites and data requires requests that no one has been appointed to raise. Inductions sit with human resources or facilities, each assuming the other holds the list. Decision rights are described in a governance appendix but not yet exercised by named individuals.

None of this is dramatic. It is administrative residue, and because it is unglamorous it is easily deferred. But the effect is cumulative. A week lost to unraised access requests becomes a week of supplier standby, or a compressed first sprint, or a baseline that is quietly renegotiated before anyone has tested it. The gap does not announce itself as a risk. It appears later as a schedule variance with no obvious cause.

Four matters that should be settled before the first working session

A pre-start protocol need not be elaborate, but it should address the items that determine whether the first workshop is a productive session or a status meeting about blockers.

Access. System permissions, site passes, shared drives, repository licences and data-room credentials should be requested, granted and tested before the start date. Testing matters as much as granting; an account that exists but cannot reach the relevant environment is not access.

Inductions. Named supplier and client personnel should complete the inductions required by the organisation — health and safety, information security, financial controls, equality and diversity where relevant. Induction should be tracked against a named list, not left to individual initiative.

Decision rights. The governance terms should be translated into a short register: who decides what, within which threshold, and who is the nominated deputy. A decision rights matrix that has never been tested is a document, not a control. The pre-start period is the moment to confirm that the named individuals accept their roles.

Baseline confirmations. Both parties should confirm in writing the baseline assumptions that will govern early delivery: scope boundaries, key dates, dependency owners and the definition of the first deliverable. This is not a renegotiation of the contract; it is a confirmation that the contract's intent has been understood identically on both sides.

The case for a named mobilisation owner

The most common cause of a lost fortnight is the absence of a single accountable person. Responsibility is distributed across procurement, information technology, human resources and the delivery team, and distributed responsibility is easily nobody's responsibility.

A named mobilisation owner — distinct from the programme manager if necessary — should hold the pre-start checklist and have the authority to escalate. The role is temporary but not informal. It should be recorded in the plan, introduced to both parties, and given a clear reporting line. The owner does not need to perform every task, but must be able to see the whole sequence and know when a task is genuinely complete rather than merely reported as in progress.

Funding the fortnight

Mobilisation effort is real work. It consumes project management time, information technology support, human resources administration and legal or commercial clarification. When it is not budgeted, it is absorbed invisibly by individuals who are already committed elsewhere. The result is predictable: the work happens slowly, or not at all, and the delay is attributed to the delivery phase that follows.

A modest, explicit budget line for mobilisation — proportionate to the programme — gives the work standing. It also makes visible a cost that would otherwise be hidden. For UK programmes with tightly negotiated contracts, this line should be agreed before signature rather than discovered afterwards.

An exit test, not just a date

The strongest safeguard is to define completion of the pre-start phase by evidence rather than by calendar. An exit test might require: access granted and tested for all named roles; inductions completed and recorded; decision rights accepted in writing by the named individuals; baseline confirmations signed by both parties; and a mobilisation owner's sign-off that the checklist is complete.

Only when the test is met should the delivery clock start. This does not lengthen programmes; it prevents the first weeks of delivery from being spent on work that should have preceded them. It also gives the programme board an honest picture: a start date that has been earned, rather than a date that has merely arrived.

The fortnight between signature and start is not a formality. It is a delivery phase with its own tasks, risks and dependencies. Treated as such, it protects the plan that follows. Left unclaimed, it becomes the first undocumented variance of the programme — and the easiest one to repeat.