Planning & controls
Set up a project and hand it over
Take a job from the very first setup right through to handover. Create it, price the work,…
5 steps20 minOpen
Cases / Planning & controls
Planning & controls
Register source data before it blocks the schedule
Register the source documents the project depends on, verify them, see what is expiring or missing against the programme, and clear the blockers before they stop work.
How it works, step by step
4 steps across the platform - what you do at each one, and why it matters.
1
Register the source documents
Source DataLog every survey, report, consent and reference document the project relies on, with its source, its date and the date it stops being valid.
Why: A document that only lives on someone's laptop is a document the rest of the team is working blind without. Registering it is what makes it something the whole project can rely on and check.
InSurveys and reportsOutRegistered source data
2
Verify each item
Source DataCheck each registered item is complete, current and from a source the team trusts, and mark it verified so anyone downstream knows it is safe to design or build against.
Why: A registered document is not the same as a trustworthy one. Verifying it once, up front, is cheaper than a design team discovering the ground survey was preliminary after they have already built on it.
InRegistered source dataOutVerification status
3
See what is expiring or missing against the programme
4D ScheduleCompare the source data record against the schedule to find the item expiring before the activity that needs it starts, and the activity with no source data behind it at all.
Why: The cost of a missing document is not the document, it is the crew standing idle on the day the activity was due to start. Checking against the programme is what turns a filing gap into a schedule risk you can actually see.
InVerification statusUpcoming activitiesOutBlocking gaps
4
Clear the blockers
Source DataChase the missing or expiring items with enough lead time to renew, reorder or reissue them before the activity that depends on them is due.
Why: Finding the gap early is only useful if someone closes it. Clearing each blocker against its deadline is what keeps the source data list from becoming a list of excuses after the fact.
InBlocking gapsOutCleared blockers
Modules in this playbook
2 / 184 platform modules