BUILDIT major-project communication playbook
Build the decision path before you distribute the information.
A major-project playbook for deciding who receives a matter, in what sequence, through which channel and under which confidentiality and approval conditions.
Who to Send to Whom, When to Include or Exclude, and How to Build a Defensible Decision Path · 23-page playbook.
Complex projects fail through pathway errors as often as through analysis errors.
A technically sound matter may still stall or cause damage because authority, audience, sequence, status, confidentiality or the final record was handled poorly.
The analysis is complete but nobody with authority has been engaged or prepared to decide.
Facts, calculations, programme or technical basis reach governance without the required challenge.
A material party first discovers the issue in a formal meeting and must defend their position publicly.
Over-distribution exposes personal, legal or commercially sensitive material and weakens the record.
Copying everybody creates noise, status threat and confusion about who actually owns the decision.
Copying everybody is not safe routing.
It can create discoverability, premature positions, political pressure and unclear ownership. Copying too few can create ambush, invalid approval or a decision nobody is prepared to implement.
Audience selection begins with what must be decided and who carries the result.
Before opening the spreadsheet or drafting the paper, write the approval sentence: “Approval is sought to…” or “A decision is required on…”. If the decision cannot be stated in one sentence, the detail is not ready.
Define the route before the matter begins moving.
Know when you can decide, recommend or must escalate.
Delegated authority defines who may commit money, accept risk, issue positions, approve settlements, alter forecasts or bind the organisation. A submission should state the authority required.
Do not issue the position before approval.
Technically strong analysis circulated externally too early creates apparent commitment, relationship damage and a governance problem. Correct work can be undermined by the wrong sequence.
Name what each person contributes before deciding whether they belong in the pathway.
A submission may travel through several gates. Each one asks a different question and needs different information. Map the chain before the work is finished so later reviewers do not rebuild the context.
Owns the underlying analysis, factual record and draft position.
Tests calculations, programme, technical basis or contractual application.
Adds specialist legal, finance, tax, safety, design, insurance or people input.
Carries implementation, budget, programme, client or operational consequence.
Challenges the position, range, precedent, cash and enterprise risk.
Selects the preferred course and explains the trade-off.
Confirms project, function, JV or business-unit alignment before authority is exercised.
Holds delegation to accept the consequence and bind the organisation.
Provides senior access, context or advocacy without replacing approval.
Controls the forum, process, calendar, information or pathway to authority.
Needs the final position or action but does not belong in developing it.
May later audit, challenge or rely on the retained decision trail.
The formal approver may rely on people without delegation and be constrained by stakeholders the preparer cannot see.
Do not substitute a powerful influencer for the accountable approver, or ignore the delivery owner who must implement the decision after the paper is approved.
Who can decide?
Map the contract, delegation, reserved matter, governance threshold and formal approval route.
Who shapes the decision?
Identify trusted advisers, senior relationships, technical voices, sponsors and institutional expectations.
Who carries the outcome?
Identify the people responsible for implementation, budget, programme, client response and downstream consequence.
A complete pathway reconciles all three lenses.
Approval that ignores implementation creates friction after the meeting. Influence that bypasses authority creates governance risk. Impact without consultation creates resistance, surprise and rework.
Include the people whose authority, expertise, implementation duty or material exposure is necessary to a sound decision.
Mandatory inclusion may arise from delegation, contract, law, safety, assurance, client governance, JV rules, specialist advice, affected operations or relationship consequence.
Who holds the relevant delegation or formal accountability?
Who must test facts, calculations, programme or technical basis?
Who carries the operational or downstream consequence?
Who must advise on legal, finance, tax, safety, design, insurance or people risk?
Who should not first discover the issue in the formal forum?
Protect relevance, confidentiality and decision quality—not avoidance of accountability or challenge.
Legitimate reasons to defer
Exclusion becomes unsafe when it hides the decision.
Do not copy broad groups for political cover. Do not exclude an approver, verifier or affected owner because they may disagree. Where exclusion is material, record the governance reason.
The preparer rarely sees the entire institutional field.
Where the pathway is politically, legally or operationally sensitive, ask the accountable owner who must be involved, who should remain outside the working group and what restrictions apply.
Use the accountable-owner question.
“I propose to pre-brief the Project Director and Planning Manager, obtain Legal’s view, then submit through the Commercial Director for approval before the client meeting. Is anyone else required—or deliberately outside the working group at this stage?”
Formal meetings should decide or govern—not be the first place material stakeholders discover the issue.
The exact route depends on urgency and authority, but material matters usually benefit from an intentional progression from analysis through challenge, approval, communication and record.
Build the factual, contractual, technical and commercial position.
Test facts, calculation, programme, authority and assumptions.
Give material stakeholders context before formal circulation.
Red-team the weak point, alternatives and what could defeat the case.
Update the position and capture material corrections or conditions.
Confirm project, functional, JV or business alignment.
Obtain the required delegated decision before commitment.
Issue the position to the people who must act or be informed.
Retain decision, conditions, actions, owners, timing and distribution.
Use conversation when meaning may be contested and writing when the record matters.
The approval begins before the paper arrives.
A short conversation gives the approver context, tests misunderstanding and avoids an important position arriving cold by email. The written submission then confirms the decision and basis.
Read the location.
A challenge in front of a client, correction in an open office or confidential issue within earshot of others may be factually justified and professionally clumsy. Choose the setting that gives the truth the best chance of being heard.
The channel signals urgency, confidentiality, authority and finality.
Communication transfers meaning, confidence and action—not merely information. Match the medium and room to the consequence rather than defaulting to email.
Use when tone, trust, resistance or ambiguity matter.
Risk: weak record if not closed in writing.
Use to assemble facts, challenge assumptions and align disciplines.
Risk: audience drift and unclear authority.
Use to organise the decision, evidence, consequence and request.
Risk: premature or over-broad circulation.
Use where contract or governance requires formal issue.
Risk: relationship surprise if badly sequenced.
Use for legal, HR, safety, personal or restricted commercial issues.
Risk: over-distribution or privilege loss.
The message and messenger are assessed at the same time.
Use calm pace, open posture, steady attention and a level tone. When tension rises, lower volume and speed.
Notice who can hear, who carries status, whose position is exposed and what each person needs.
Let the person finish, ask a clarifying question and identify the concern beneath the stated objection.
End with the decision, open point, action, owner and due date—then create the proportionate written record.
The purpose is not to display how much you know.
Help the right people understand what matters and what happens next quickly and accurately—with the detail available behind the recommendation if they need to stress-test it.
Pre-briefing prepares the formal pathway; it must not secretly replace required governance.
Share the issue, likely recommendation, weak point and decision need with stakeholders who should not be surprised. Keep the pending formal authority explicit.
Do not let private support appear to authorise the position.
Use the discussion to improve facts, assumptions, consequence and route.
Do not promise the outcome, bypass delegation or exclude required challenge.
Put material facts, conditions and limits into the formal submission and record.
Different consequences require different owners, specialists, sequences and records.
The playbook applies the routing discipline to deteriorating forecasts, client and counterparty matters, legal or sensitive information, and layered JV or alliance governance.
Verify the movement, brief the accountable manager, test specialist assumptions, pre-brief the sponsor, then use the formal forecast route.
Map who can commit the company, who owns the relationship, who holds the facts and who must issue the formal record.
Use the required legal channel, keep advice separate from ordinary records and restrict personal, conduct and health information.
Identify project delegation, reserved matters, alliance leadership, client, certifier, lender, public and board requirements.
Deteriorating forecast
A $4 million package movement should be verified with finance and delivery, briefed privately to the Commercial Manager, tested against legal recovery assumptions and pre-briefed to the Project Director before the board pack states movement, range, containment and decision.
Disputed access
An informal indication from a superintendent is not necessarily a direction. Verify with delivery, protect the contractual position, pre-brief the relationship owner and obtain formal client confirmation before cost is committed.
The wider the distribution, the harder it is to preserve confidentiality, privilege and a clean factual record.
Engage Legal through the required channel, mark purpose and distribution accurately, separate legal advice from ordinary project records and ask the accountable owner who may receive it.
Control the material.
Restricted does not mean disconnected.
Operational teams may still need a clean factual direction or control without receiving the sensitive advice behind it. Design the route so necessary action occurs without over-distributing the protected material.
One approval may not satisfy project, business-unit, JV, client or external accountability.
Identify the decision threshold, representative, route and record required at each legitimate layer before a commitment is made.
Map the interfaces between legitimate pathways.
Reserved matters, alliance leadership, independent certification, client governance, lender conditions and public accountability can coexist. Reconcile them before the position is circulated or cost is committed.
Pathway discipline prevents noise, ambush, bypass and decision paralysis.
Red-team the route before material circulation. The purpose is to test whether the decision can move cleanly through authority, challenge, implementation and record.
Are both named clearly and does the proposed route reach the correct delegation?
Are mandatory specialists, reviewers and affected delivery owners included?
Has the accountable owner tested the proposed audience and restricted group?
Do conversations prepare the formal decision rather than replace governance?
Do medium, room, tone and timing fit the sensitivity and status consequence?
Will the decision, conditions, actions and recipients remain controlled and defensible?
Common failures
Copying everyone, excluding the implementer, bypassing the manager, confusing reviewer with approver, seeking support before facts are tested, disclosing sensitive information and issuing formal notice before the relationship owner knows.
Silence is not proof of understanding.
Do not assume every email will be read on time or at the expected level of detail. For consequential matters, provide the context by phone or in person and confirm the landing.
A defensible record shows who knew, who advised, who decided, what conditions applied and what was communicated.
Keep the decision brief, material advice, approvals, conditions, issue record and distribution. After material matters, review whether the route created avoidable delay, surprise or rework.
Use the record to improve the system—not only defend the past.
Recurring pathway failures often reveal unclear delegation, duplicated review, weak stakeholder mapping, uncontrolled channels or forums that discover issues too late. Convert the lesson into a repeatable change.
Sixteen connected chapters from decision framing to defensible pathway records.
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.
