Spec, local code and vendor guide
The spec says one thing, the local code another, the vendor guide a third.
A global spec meets a local rule on every project, and a tenant standard for pathways and conduit often arrives on top. Criad loads the code and the tenant standard beside the spec and the vendor guide, shows where they disagree, and checks the model against each. The finding goes to the person who decides, with every source cited.
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
The local rule puts wheelchair reach at 1.10 to 1.30 m.
- 02
The vendor guide says 1.38 to 1.50 m.
- 03
The spec says nothing.
- 04
The code may require two alarms in this class of zone. The model shows one.
A finding, as it would be raised
One reader is mounted above wheelchair reach
- Local rulewheelchair reach 1.10 to 1.30 magrees
- Vendor guide1.38 to 1.50 m, standing adultsno ruling
- Specno mounting height givenno ruling
- Modelone reader measured at 1.50 mconflicts
The rule sets the height. The model shows the height. People decide what to do about it.
A finding, as it would be raised
Two zones have one alarm where the code may require two
- Local codeat least 2 alarms in this class of zoneagrees
- Model1 alarm in each of two zonesconflicts
- Submittalproduct approvedagrees
The code sets the count. The model shows the count. The designers decide.
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.