BUILDIT major-project entry playbook
Enter the project without pretending to know it. Build orientation, trust and control before you try to change it.
An onboarding and internal-transfer playbook for reading a major project’s contract, controls, people, legacy issues and informal operating system without creating early political or commercial mistakes.
How to Enter, Read and Become Useful to a New Team · 16-page practical manual.
Clarify the mandate, boundaries and immediate risks before the project starts defining them for you.
Obtain the role mandate, reporting line, current phase, key project documents, delegations and immediate priorities. Ask what cannot wait for normal onboarding and avoid forming private conclusions from one person’s handover.
Confirm the role
Clarify the package, reporting line, authority, expected outputs and what success should look like by Day 90.
Request the core documents
Head contract, key subcontracts, forecast, risk register, programme, delegations and organisation chart.
Identify urgent exposure
Ask which decisions, time bars, stakeholder commitments or distressed packages cannot wait.
Set boundaries
Confirm confidentiality, approval pathways and where your ability to analyse ends and delegated authority begins.
Do not arrive trying to win the project argument before you understand the project.
The first task is orientation: what the deal requires, what the team believes, what the records support, which decisions are live and where the project has already spent trust.
The organisation chart shows accountability; the first month reveals who actually carries context and influence.
Map the people who approve, explain, challenge and move work. Major projects run through formal reporting lines and a second network of technical history, credibility and access.
Strategy, client commitments, enterprise exposure and final decision routes.
Forecast, claims, variations, procurement, authority and inherited positions.
Sequence, constructability, access, package reality and current pressure.
Releases, critical path, records, baselines, interfaces and future constraints.
Cash, reporting, advice, market exposure, security and governance.
External authority, influence, relationship history and delivery dependencies.
Map more than names and titles.
Listen widely without joining a faction.
Major projects accumulate history. Treat complaints as information requiring corroboration, not as an invitation to inherit another person’s enemies.
Do not administer clauses in isolation from the deal the project priced and the strategy it is pursuing.
Read the scope, exclusions, qualifications, design responsibility, time, payment, change, security, insurance, dispute and approval pathways. Then compare tender assumptions with the current forecast, cash position and delivery reality.
Contract and strategy
Understand the governing terms, the assumptions that won the work and how the project intends to protect or recover its position.
Numbers and control
Reconcile forecast, commitments, accruals, variations, claims, cash, contingency and risk. Focus first on large movement, ageing items and assumptions without owners.
An inherited narrative is not an inherited fact.
List the issues that repeatedly return to meetings: ageing claims, incomplete notices, unresolved instructions, weak records, disputed baselines, authority gaps and relationships already under strain.
What remains undecided, why has it stalled and which evidence gap actually prevents resolution?
Which urgent rights, responses or contractual steps are exposed by delay?
Where is work proceeding without clear authority, valuation or responsibility?
Which accepted narratives are unsupported, disputed or impossible to reproduce?
Which issues have become attached to status, trust or previous failed attempts?
Which matters are settled, reserved or constrained by decisions made before your arrival?
Separate confirmed fact, inherited opinion and unresolved assumption.
Ask who has already tried to resolve the issue and what stopped it. Do not casually reopen settled matters; understand the governance and relationship history before turning old uncertainty into a new problem.
Commercial consequence follows the construction sequence.
A package can be contractually contained and operationally central. Understand the critical path, design releases, access, possessions, commissioning, client dependencies and where delay or scope ambiguity can move between packages.
Read the interface before you judge the package.
The commercially important question is not only who owns the clause. It is how design, access, sequence, procurement and adjacent work combine to create or contain the project consequence.
The fastest route to trust is clear authority, update rhythm and no-surprise behaviour.
Agree the current priorities, decision boundaries, review standard, escalation thresholds and evidence that will define a successful first 90 days. Your manager should provide clarity and backing; you should provide early warning, ownership and reliable closure.
Read their scoreboard.
Make the relationship work.
Resolve something useful enough to matter and contained enough to understand.
An early win should close an ageing issue, improve visibility, remove uncertainty or establish a reliable operating rhythm. It should demonstrate control without claiming ownership of work completed before you arrived.
Material enough
The outcome should remove a real source of delay, uncertainty, exposure or repeated management attention.
Contained enough
You must be able to understand the evidence, authority, stakeholders and consequences before acting.
Respectful of history
Acknowledge prior work, identify the remaining gap and avoid presenting inherited progress as your own.
Repeatable control
Prefer a result that also establishes a clearer record, rhythm, owner or decision pathway for future work.
Example: close the ageing variation without reopening every argument.
Identify the two remaining evidence gaps, arrange one focused review with delivery and the client representative, and move the assessment through its decision pathway. The early win is not theatre; it is visible control and respect for prior work.
Each checkpoint should convert new understanding into clearer ownership and fewer unknowns.
Day 30 establishes the map and urgent controls. Day 60 tests relationships, assumptions and operating rhythm. Day 90 confirms the stable mandate and the next capability or recovery priorities.
Map the system and contain urgent exposure.
Understand the team, contract, commercial position, programme, reporting rhythm and the few issues that cannot wait.
Evidence: people map, contract priorities, initial commercial scan and urgent-risk list.Test assumptions and operate the agreed rhythm.
Own defined workstreams, corroborate inherited narratives, build cross-functional relationships and show reliable escalation and closure.
Evidence: active workstream ownership, tested assumptions, operating update rhythm and an early win progressing.Confirm the stable mandate and what comes next.
Record credible contributions, remaining uncertainty, the responsibility you are ready to carry and the next development or recovery priorities.
Evidence: closed or controlled early win, agreed ongoing scope, review feedback and next-step plan.The aim is not to know everything by Day 90.
It is to know what matters, where the evidence sits, who carries authority and context, what remains uncertain, and which responsibilities the team can now trust you to hold.
Ten connected chapters from pre-entry preparation to stable ownership at Day 90.
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.
