RDI

Knowledge base / Workflows

Design verification workflows

A detailed walk through the design verification pack: how the captured as-built record is reconciled against the model and the design intent, and how deviations become disposition records.

Article

Design verification is the workflow where BIM and RDI most clearly meet. The model carries the intent; the captured record carries the reality; the pack reconciles the two. The output is a disposition record for every deviation that matters, a strong as-built handover, and a much shorter list of warranty surprises later.

Triggers

Triggers are activity-based. The end of a structural pour. The completion of an MEP first-fix. The closeout of a fitout phase. Each trigger initiates the verification cycle for the relevant package or area. The pack also runs against event triggers: an RFI raises a potential deviation, a quality non-conformance reveals an as-built drift, a model update needs reconciliation.

Evidence

  • 360 walks at agreed verification points along the package.
  • Time-aligned camera views of the work fronts during installation.
  • Drone or aerial captures for structure and large-area works.
  • The federated BIM model at the relevant level of development.
  • RFIs, instructions, and design changes for the period.

The strength of the pack depends on alignment between captured reality and the model coordinate system. Where the project has invested in this alignment at mobilisation, verification is fast. Where it has not, verification becomes a manual cross-check that consumes time without producing the full benefit.

Interpretation

Interpretation identifies deviations between as-built and model. Some are tolerable and need only be recorded. Some require disposition — accept, repair, or redesign. The classification is the substance of the workflow; the captured record is what makes the classification defensible later.

Action

Action varies by classification. A tolerable deviation produces an as-built record entry and a closed observation. A disposition required deviation triggers an RFI, a design change, or a non-conformance with a corrective action. Each route has a named owner and a clock.

Outcome and measurement

The pack measures the time between activity completion and verification, the proportion of deviations identified by the pack rather than by later QA, and the size of the disposition list at handover. A mature design verification pack tends to shrink the handover punch list significantly because deviations have been resolved during the works rather than at the end.

The pack is most effective on projects with an active BIM process and a digital construction lead empowered to align the model with the captured base. Without that alignment, the workflow still adds value, but it works harder for it.

Knowledge base articles are intended as durable reference. For shorter definitions, see the glossary. For shorter essays, browse field notes.