Resources / How it works
Day one · month three · go-live
How rollout actually works.
No big-bang go-live. No six-month implementation project before anything is usable. The contract engine is live in week one. The safety spine is live in week one. The operative app rolls out in month two when the workforce is on the floor. The Cx Spine activates in month three when commissioning begins. The system scales with the project.
-
1
Day −7 · Discovery
Review the executed contract. Identify the three pilot personas. Scope the first 30-day pilot window. Agree the contract form (JCT D&B, NEC4 Option C, or bespoke) and the project WBS structure. Confirm the on-site workforce size and language profile for the operative app. No technical installation required at this stage.
-
2
Day 1 · Contract intake
The Contract-Aware Engine ingests the executed contract. Clauses are extracted, time-bars are set, the notice-route map is built, and the Contract Health Score baseline is recorded. Coughlan reviews the extraction output and signs off the clause register before the first event is logged. The engine is live. The Watchtower is watching.
-
3
Day 3 · Spine activation
The Safety Spine and PM Command Centre go live for the three pilot personas. Halloran has her morning brief. Cassidy has her gatehouse view and permit queue. Coughlan has his contract dashboard. The record is live. The first event — induction or near-miss or programme update — can be logged. Three personas, one record, day three.
-
4
Day 14 · First Friday board paper
The live record generates the first board paper — programme status, cost status, open near-misses, permit compliance, contract health. Halloran reviews it, edits if needed, and signs. The Krupa-equivalent receives it. It looks like the board paper they are used to — but it came from the live record, not from a manual compilation on Thursday evening. It will look the same next month. And the month after.
-
5
Day 30 · Commercial Engine
Coughlan runs the first month of notices through the Contract Engine. Pay Less Notices are inside the window for the first time. Early Warning obligations are flagged at the trigger event, not two weeks later. The first compensation event is drafted, reviewed, and issued with the clause cited and Coughlan's signature on the record. The Watchtower has not missed a window.
-
6
Day 60 · Operative App on the floor
Induction, RAMS, sign-on, near-miss capture, toolbox talk acknowledgement, and permit visibility rolled out to the workforce. Voice channel live in five languages. The first near-miss captured by voice in Polish. The first toolbox talk acknowledged on-device with a 100% confirmation rate before the gang leaves the welfare unit. The operative who raises a near-miss is told what happened to it, by name, in language.
-
7
Day 90 · Cx Spine on the calendar
Witness testing goes live against the commissioning programme calendar. Calibration vault activated — 94 instruments across six subcontractors, all current. The independent CxA (Donnelly · Sentinel equivalent) is onboarded with their own credentials. They begin writing directly to the Cx Spine. The client has read access from this day. No more commissioning records delivered at handover.
-
8
Go-live · ongoing
The system runs. The contract watches itself. The Watchtower fires before windows close. The board paper generates on the first Friday of every month. The operative's near-miss loop closes in hours, not weeks. Quarterly governance review: what is the project learning, and what does the next project inherit. Lessons compound across projects. The industry stops re-learning the same things.