CRIAD
Subcontractors · Use case 04

Scope and demarcation gaps

Nobody priced the link between our scope and theirs. We found out on site.

Every element is linked to the package it is built under. Trace a path end to end and the gaps show: a link with no package against it, or a link with two.

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"Who supplies and installs each part of this path?"
2

Inspect

The full blast radius, on the model.

The package on the model, element by element, and the links that leave it.
3

Verify

Checked against the governing drawings and specs.

Each link is checked against the scope documents and the package it is listed under.
4

Publish

A dashboard, report or register, citations attached.

A demarcation list: gaps and overlaps, sources attached, ready to raise before the price is fixed.
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, electrical yard: the package isolated on the model, each element against the package it is built under.

  2. 02

    The cable runs to the halls stop at the yard fence on the tender drawings: a link with no package against it is a gap.

  3. 03

    The generators and fuel are in the electrical package but specified in DS-M02, a mechanical section: who owns the spec is raised.

  4. 04

    The list goes to the general contractor as a clarification, not as a claim later.

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