CRIAD
Subcontractors · Use case 01

Tender scope and take-off

We priced it from the tender pack in a week. What we missed, we now own.

The tender pack comes in as it is: drawings, specs, schedules and the model. Criad connects them, counts your scope from the model, and lists where the documents disagree or say nothing, so the clarifications go in with the bid and not after it.

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"What is in our scope, how much of it is there, and what does the pack not tell us?"
2

Inspect

The full blast radius, on the model.

Your scope isolated on the model, by area and by system, with the sheets and clauses that describe it.
3

Verify

Checked against the governing drawings and specs.

Counts are read from the model and checked against the schedules and the spec. Disagreements and gaps are listed with their sources.
4

Publish

A dashboard, report or register, citations attached.

A take-off by area and system, and a clarification list to send with the bid, sources attached.
Worked example

One job, start to finish.

Values come from a structured reference campus, not from a client project.

Reference campus
  1. 01

    Reference campus: 152 sheets and 315 files in the pack.

  2. 02

    The electrical yard package counted from the model: 9 transformers, 4 switchboards, 2 grid intakes, 50 cable runs. Generators and fuel sit in another package.

  3. 03

    Each count links to the elements behind it and the spec clause that governs them.

  4. 04

    Where the tender drawings stop at the yard fence, the gap is listed as a clarification, not priced blind.

Electrical yard Electrical yard · one package isolated
Highlighted: the elements the answer refers to

Stop waiting. Start building.

Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.

Book a call