Revision guard
A new revision just landed. What changed, and who is still building to the old sheet?
Every element drawn on that sheet is known, so the change list writes itself: what moved, what it affects, who needs to know. Before anyone builds to the old sheet.
Every answer cites its source. People decide.
How it works
Ask. Inspect. Verify. Publish.
Ask
A plain-language question.
Inspect
The full blast radius, on the model.
Verify
Checked against the governing drawings and specs.
Publish
A dashboard, report or register, citations attached.
One job, start to finish.
Values come from a structured reference campus, not from a client project.
- 01
A governing drawing on the reference campus goes from rev 1 to rev 2.
- 02
Every element drawn on that sheet is flagged.
- 03
Each flagged element carries its package, so the trades that need to know are listed.
- 04
The list is out before anyone builds to the old sheet.
illustrative example
What rev 2 touches
- Rack row C moved 0.60 m
- 12 racks affected
- Install plan: 1 package to re-sequence
- Who needs to know: 3 trades
Flagged before anyone builds to the old sheet.
Platform capabilities used
The same capabilities serve every segment. Each one links to its section.
Stop waiting. Start building.
Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.