CRIAD
General contractors · Use case 09

Tender 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.

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"What does this pack require of us, and where does it disagree with itself?"
2

Inspect

The full blast radius, on the model.

The requirements, point by point, each with the sheet or clause it comes from.
3

Verify

Checked against the governing drawings and specs.

Where a requirement sets a limit, it is measured on the model. Where two sources disagree, both are shown with their authority.
4

Publish

A dashboard, report or register, citations attached.

A clarification list and a scope summary, sources attached, ready for the bid team.
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 pack: 152 contract sheets and 315 published files.

  2. 02

    Every sheet is readable as data. Every file is addressable.

  3. 03

    Envelope check: model cabinet depth 0.90 m against 0.92 m allowed. Pass.

  4. 04

    Gaps and disagreements go on one clarification list, each with its source.

One connected structure
  • 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

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