Most schedule loss is waiting for answers.
Answers wait on information held in different systems. Criad connects the drawings, specs, model, programme and procurement of the build, so the answer and its evidence are in the meeting.
Where the date and the margin go
You carry the facility readiness date and the cost of reaching it. Every open question ends one of two ways: pulled back to the date, or a change to the date and the price that has to stand on its evidence. A change assessment that takes weeks, a revision found after the work is done, an RFI that comes back with a question: each one is time on the critical path with nobody building and nothing to put in front of the client.
Two outcomes, both defensible. The date holds where the knock-ons can be absorbed; where they cannot, the change to the date and the price carries its evidence.
Four issues, in your words.
A design change notice lands. Finding everything it touches, and pricing it, takes weeks.
A new revision landed. Someone is still building to the old sheet.
The RFI went out without the evidence, so it came back with a question.
The take-off was right on the day it was done. The model has moved since.
One change, every knock-on, one decision
A design change notice lands. Finding everything it touches, and pricing it, takes weeks.
One change is never one change. Criad shows everything a requested change touches and checks it against the governing drawings and specs. Not an AI making the call: every knock-on and its evidence, in front of the person who decides.
Ask
A plain-language question.
Inspect
The full blast radius, on the model.
Verify
Checked against the governing drawings and specs.
Checked against the governing drawings and specs. Allowed depth 0.92 m. Requested 1.0 m is 0.08 m over.
Publish
A dashboard, report or register, citations attached.
Sequencing and work zones you can check
The master schedule says which month. It does not say which crane, which zone, or which trade has to be out of the room.
Heavy plant lifts, live electrical work and mechanical installs cannot share a space or a week. Criad links each work package to the elements and the zone it works in, so a proposed sequence can be checked on the model: what is in the way, which zone is live, which room needs a permit, and which trade is waiting on which.
Open this use caseTenant standards, checked before the corridor is built
The tenant has its own pathway and conduit standard. We found the difference after the corridor was built.
Every tenant brings a standard of its own for pathways, conduit, containment and labelling, and it rarely matches the base-build spec line for line. Criad loads the tenant standard beside the spec, shows where the two disagree, and checks the model against both before the corridor is built, not after.
Open this use caseTenant standard against drawing · containment route
Stricter than the code limit of 360 degrees
No junction boxes on tenant pathways.
Total bend between pull points shall
not exceed 180 degrees.
Pull points shall be shown on the drawings.
17 of 64
Ranked by authority
Counted on the drawing
360 degrees
rev 1 · pull points shown
Riser drop: 4 × 90 degree turns
between the frame and the first pull point
Reference campus
LV containment, riser to Hall 2
rev 1
pull points shown
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.
Open this use caseillustrative 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.
Submittal review at scale
Submittals arrive every week, each one checked by hand against a spec nobody has time to reread.
Each submittal is linked to the elements it covers and the clauses that govern them. Criad checks the proposed product against the clause and the space it has to fit, and shows the reviewer what passes, what fails and what the spec does not say. Approve once, and every unit of that product updates.
Open this use caseSpec against submittal · electrical cabinet depth
Cabinet envelope clause
Free-standing cabinets shall fit the
envelope shown on the layout drawings.
Depth shall not exceed 0.92 m.
Deeper units require a design change.
42 of 118
Ranked by authority
Modelled depth against the limit
0.90 m · request 1.0 m
Data sheet · depth 1.0 m
Overall dimensions (W × D × H):
0.60 × 1.00 × 2.00 m
96 units · one long-lead order
3 of 12
Long-lead orders tied to the design
The order was placed months ago. The design has moved since, and nobody has checked the two against each other.
Long-lead equipment sets the energise date, and lead times run to months. Criad links each order to the elements it covers, the clause it was specified under and the revision it was placed against, so a design change that touches an order shows up when the change is proposed, not when the equipment arrives. When a substitute product is offered to beat a lead time, it is checked against the client standard before it is ordered.
Open this use caseWhere authority alone cannot settle it, Criad drafts the RFI with the clauses, sheets and measurements already attached, so the question arrives ready to answer.
Open this use caseAn RFI, as it would be drafted
The client instruction and the governing sheet disagree on cabinet depth
- Governing sheet0.92 m cabinet footprintagrees
- Specallowed depth 0.92 magrees
- Client instruction1.0 m cabinet, 0.08 m overconflicts
- Model96 cabinets affectedno ruling
Both sources cited, measurements attached. Your engineer reviews it and sends it.
Take-offs that refresh
The take-off was right on the day it was done. The model has moved since.
Counts are read straight from the model, and every item is linked to its spec and package. When a revision lands, the take-off is run again, not redone.
Open this use caseTender pack review
The tender pack is hundreds of files. The bid team has days to find what is in it and what is missing.
The pack comes in as it is: drawings, specs, schedules and the model. Criad lists the requirements with their sources and checks the ones that can be measured. Your team decides whether and how to bid.
Open this use case- Reference campus
- Sources
- Drawings152 sheets
- Specifications
- Submittals
- Programme
- Registers315 files
- Model
- Hall 2
- Power
- Electrical cabinetH2-001 · 96 on site
- Hall 1 · 3 · 4 · 5 · 6
- Intelligencechecks · clarifications
Judge it on a real job.
Book a call. Bring a real question from a job you know, and see how the answer and its evidence come together.
Your project, as it is. Drawings, specs, model and programme come in without retyping.
Your questions, with evidence. Every answer cites the sheet, the clause or the measurement.
Your people decide. Every decision keeps its evidence for later review.
Stop waiting. Start building.
Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.