BUILDIT package-recovery playbook
Stop further deterioration. Rebuild the facts. Make the next controlled action visible.
A practical recovery method for packages where the records, relationships, programme or commercial position are already poor—and the team needs diagnosis, procedural control and a defensible path forward.
How to Take Control When the Records, Relationships or Commercial Position Are Already Poor · 16-page practical manual.
The first act of recovery is to stop the package becoming worse while the true position is established.
Define the mandate, authority, immediate risks and reporting line. Put protective control around live commitments and deadlines before the team disappears into a perfect reconstruction of the past.
Freeze uncontrolled commitments
Stop unauthorised promises, undocumented concessions and new positions issued before review.
Protect urgent dates
Identify notices, security, payment, programme, instruction and approval deadlines.
Set a fact-finding window
Establish a short diagnostic period, named reporting rhythm and the questions that must be answered first.
Preserve access and records
Secure current files, systems, custodians and document locations before people or platforms change.
Protect the position available now while the fuller answer is built.
Commercial recovery fails when urgent procedural control is left behind while the team perfects the narrative. Use the strongest accurate position presently available and state what remains under investigation.
Repeated statements become project folklore long before they become evidence.
Interview the people involved, but test each account against contemporaneous records. Show the ladder from evidence to conclusion so the approver can see which rung carries the weight.
Fact
A supported observation or record: what occurred, when and where it is evidenced.
Assumption
A provisional statement filling a gap that must be visible and tested.
Interpretation
What the words, events, obligations or records are considered to mean.
Judgement
The recommended action after the facts, gaps, competing meanings and consequences are weighed.
Do not manufacture certainty.
Confidence improves when the reader can see what is known, what has been inferred and where a conclusion depends on an assumption.
Build an inherited-position register.
For each repeated statement, record its category, supporting material, test and owner. This converts project folklore into a visible work programme.
A defensible narrative shows what happened, when, under which obligation and with what consequence.
Build around the events that affect scope, instruction, access, programme, cost, notice and response. Link each proposition to the record that proves it instead of transferring a pile of attachments upward.
Evidence questions
Make the reasoning reproducible.
Calculations need sources and assumptions. Contractual positions need relevant words and facts. Forecasts need ownership, probability and timing. Verbal directions need proportionate written confirmation.
The number must expose range, assumptions, recoverability and timing—not merely a single answer.
Separate what has been spent, what remains to complete, what may be contractually recoverable, when cash might move and which residual risk stays with the package.
State the assumptions and external outcomes required for the upper position to occur.
Use the present evidence, probability, programme and counterparty position—not the result the forecast needs.
Expose what happens if the critical assumption fails, delay extends or recovery cannot be collected.
Keep assessed entitlement, forecast recovery and cash timing distinct.
A strong contractual position is not automatically a booked recovery, and a booked recovery is not automatically cash. Recovery becomes credible when the differences are visible rather than blended into one reassuring number.
The disputed position is carried by people with authority, history, pressure and status.
Map who owns the analysis, who can verify it, who recommends, who endorses, who approves, who must be consulted and who will later challenge or audit the record.
Who has delegated authority to approve the commercial or operational response?
Who tests the scope, programme, valuation, evidence or contractual interpretation?
Whose margin, cash, budget and management reporting will move?
Who carries the client, consultant or subcontractor relationship after the formal decision?
Whose context or credibility can unlock, obstruct or independently confirm the position?
Who may later audit, dispute or test whether the decision and process were defensible?
Prepare for the full approval chain.
A submission can be correct for one reviewer and incomplete for the next. Map each gate before the work is finished so later reviewers do not have to rebuild the context.
Pre-brief so the formal forum decides rather than discovers.
Protect urgent rights while building enough common ground to make the package governable.
Recovery needs two things at once: defensible protective action for live dates and an agreed starting point that isolates rather than multiplies disputed elements.
Notices and time bars
Issue the strongest accurate position available now and identify what remains under investigation.
Payment and security
Track response dates, security expiry, certification, cash exposure and approval requirements.
Authority and legal input
Record who authorised each step and coordinate advice where privilege, dispute or interpretation requires it.
Minimum common ground
Agree executed scope, current status, certified value, practical constraints and the next decision dates.
A credible baseline does not require either party to abandon its legal position.
Agree what can be agreed—dates, quantities, instructions, programme states, payments and present constraints—then isolate the disputed responsibility or valuation so the entire package does not remain undefined.
Every material issue needs an owner, immediate control, decision path, evidence requirement and review date.
Run a short, disciplined rhythm with project leadership. Keep operational recovery, commercial resolution and record reconstruction visible as separate workstreams so none can hide behind the others.
Three workstreams, one governed position.
Do not let activity disguise a missing decision.
A recovery plan should show which issue is being controlled, which evidence is still needed, who can decide and when delay will change the position.
The aim is a predictable working relationship—not personal agreement about the past.
Acknowledge the dispute, set behavioural and communication boundaries, separate current delivery from historical entitlement and use a meeting and record rhythm both parties can rely on.
Do not pretend the history or distrust does not exist. State what remains disputed without relitigating it in every interaction.
Keep present access, resourcing and delivery moving while historical entitlement follows its own pathway.
Use one operational-commercial meeting, a single action register and proportionate written confirmation.
Progress what can be agreed without forcing either party to concede the unresolved past prematurely.
Trust may not return immediately; governability can.
When every email alleges bad faith, the first success is not agreement. It is a predictable forum, usable information, controlled commitments and a record that stops the dispute contaminating every current decision.
A strong case still carries management cost, delay risk and collection uncertainty.
Give the approver realistic alternatives, their consequences and a clear recommendation. Price value and cash alongside time, attention, precedent and relationship.
Recommend without pretending the answer is inevitable.
Show the realistic alternatives and why one is preferable. A sound recommendation stays open to challenge while carrying the difficult judgement rather than transferring it upward.
Keep ambition and control separate.
Where the full recovery is not yet evidenced, use the defensible base case in the forecast and track additional upside separately with the evidence required before it can move.
Recovery is incomplete if control disappears when the person who led it leaves.
Close or clearly status every issue, preserve the chronology and evidence, document authority and next dates, and introduce the successor to the stakeholder and decision pathways.
A senior reputation is built by how quickly and honestly control is restored when failure occurs.
Good recovery has a pattern: disclose early, establish the facts, contain the consequence, take proportionate responsibility, obtain help, communicate the path forward and improve the system.
Eleven connected chapters from initial containment to a package another person can safely inherit.
This is an external BUILDIT development resource. It is not company policy, an industrial instrument, a competency matrix, legal advice or a guarantee of promotion, remuneration or retention.
