Passing the Baton Without Dropping the Promises: A Post-Award Week One Protocol
Photo: Philippine Government - Radio Television Malacañang, Public domain, via Wikimedia Commons
Contract award is often treated as the end of a commercial process and the beginning of mobilisation. In practice it is a handover, and a fragile one. The bid team has sold a version of the future based on promises, assumptions and commercial compromises. The delivery team inherits that version and is expected to make it real, often before anyone has explained where the pressure points sit.
The first week after award is the best opportunity to close that gap. It is early enough to influence mobilisation, late enough for the contract to be real, and short enough to force prioritisation. A structured handover in that week is not administrative tidying. It is a delivery control.
The inherited promise
Bid teams are not dishonest by design. They work under commercial pressure and incomplete information. A price is built on assumptions about productivity, availability and client behaviour. A timetable is built on a sequence that assumes timely decisions. A solution is described at a level that allows the customer to say yes. By the time the contract is signed, some of those assumptions will be sound, some will be optimistic and some will already be out of date.
Delivery teams, meanwhile, are usually mobilised quickly. Recruitment starts, suppliers are engaged, and the customer expects momentum. If the handover is weak, the sold plan becomes the delivery plan by default. That is how avoidable problems become inherited problems.
Day one: assemble the handover group and freeze the story
The first step is to bring the right people into one room, physically or virtually. The group should include the bid lead, the delivery lead, commercial and finance representation, and the person accountable for the customer relationship. For complex programmes, legal and technical leads should attend the sessions where their commitments are examined.
The bid lead should present the offer as it was sold, not as it should have been sold. That means the pricing basis, the delivery model, the schedule, the assumptions and the known departures from standard terms. The delivery lead should be allowed to ask naive questions. The purpose of day one is not to defend the bid. It is to make the inherited story explicit.
Day two: extract commitments into a register
The second day should produce a commitments register. This is not a copy of the statement of work. It is a practical list of what the organisation has promised to do, when, and on what basis.
Each entry should record the commitment, the source document or conversation, the owner, the date by which it must be met, and the confidence level. Commitments can be commercial, technical, operational or reputational. A promise to provide a named specialist for the first eight weeks is a commitment. A promise to deliver a report within five working days of a request is a commitment. A promise that the customer will make a decision within a stated period is also a commitment, even if it sits on the other side of the contract.
The register should include commitments that are implicit as well as explicit. If the bid assumed a particular level of customer resource, that assumption belongs in the register as a dependency to be confirmed.
Day three: test the priced assumptions
Pricing assumptions deserve particular attention because they are where commercial pressure and delivery reality most often diverge. The handover group should list the assumptions that materially affect cost or schedule and mark each one as validated, unvalidated or already invalid.
Typical examples include labour rates, subcontractor availability, productivity levels, travel and expenses, implementation duration, customer decision times and the cost of compliance with UK regulatory or reporting requirements. For each assumption, the group should identify the evidence that would confirm or challenge it, and the date by which that evidence is needed. An unvalidated assumption is not necessarily a problem. An unowned unvalidated assumption is.
Day four: assign owners to unresolved dependencies
Bid documents are good at describing dependencies and poor at assigning them. The fourth day should convert unresolved dependencies into managed items. Each dependency needs a named owner, a required date, a consequence if it is late and an escalation route.
This is also the point to separate dependencies the delivery team controls from those it does not. Customer-side approvals, third-party supplier commitments and internal specialist availability should be visible in the same register. If a dependency cannot be owned by anyone in the delivery team, it still needs an owner for chasing and escalation. Leaving it unassigned is not neutrality. It is a decision to be surprised later.
Day five: reconcile the sold plan with the deliverable plan
The final day should produce a reconciled view. The sold plan is the schedule and cost baseline that supported the bid. The deliverable plan is what the delivery team believes it can actually achieve with the resources, dependencies and constraints now known.
The two should be compared at milestone level, not task level. Where they differ, the group should record whether the difference is a timing issue, a cost issue, a scope issue or a dependency issue. Not every difference needs to be escalated immediately. But every material difference should be visible before mobilisation gathers pace.
The output of the week should be a short pack: the commitments register, the assumption log, the dependency register, the reconciled plan and a list of decisions required from senior management. That pack becomes the basis for the first delivery board and the first conversation with the customer about how the programme will actually run.
What good looks like at day five
A successful handover week does not resolve every uncertainty. It makes uncertainty visible and assigns it. The delivery team should know which promises are firm, which assumptions are still exposed, which dependencies are at risk and which decisions need to be taken before recruitment or supplier mobilisation accelerates.
The test is simple. If a new delivery lead joined the programme at the end of week one, could they explain what has been sold, what has been assumed and what must happen next? If the answer is yes, the baton has been passed properly. If the answer is no, the programme is still relying on the bid team's memory rather than a delivery control.