RDI
Menu
Start with RDIAssess maturity

Manifesto

Reality should become operational knowledge.

Run construction on reality, not reports, recollection, or selective updates.

The shift

The RDI operating rule

Captured reality has to become evidence, action, and learning. Otherwise it remains an archive.

  1. 1Capture

    Capture site reality

    Record the site as it is, across relevant views, locations, activities, and events.

  2. 2Verify

    Establish ground truth

    Make the record trustworthy by time, location, scope, project context, and preservation.

  3. 3Interpret

    Interpret change

    Identify patterns, exceptions, risk, progress, and likely consequences.

  4. 4Act

    Route action

    Turn the finding into an owner, task, escalation, report, claim record, or closeout.

  5. 5Measure

    Measure outcome

    Keep the decision record and use it to improve the next review, workflow, or project.

Open loop

Evidence stops at a dashboard, inbox, or archive. The record exists but does not change project behaviour.

Closed loop

A decision, assignment, closeout, or learning record is created and the evidence remains available for review.

Principles

Six rules for RDI

These principles are the test for whether construction technology is moving from visibility toward intelligence.

  1. 01

    Construction should be run from reality, not recollection.

    Project decisions should start from what actually happened, not only from what was reported after the fact.

  2. 02

    Evidence should be continuous, time-aligned, and location-aware.

    A useful record carries enough context to support responsibility, sequence, conditions, and consequence.

  3. 03

    Intelligence is not complete until it changes a decision.

    Detection, search, and dashboards are incomplete if they do not help someone decide, act, close out, or learn.

  4. 04

    A workflow is incomplete if evidence stops at a dashboard.

    RDI requires ownership, assignment, escalation, closeout, or preserved learning when the evidence matters.

  5. 05

    Value must be measured by outcomes, not feature usage.

    The unit of value is the workflow outcome: confidence, evidence, capacity, risk, quality, cost, safety, or progress.

  6. 06

    The framework should be open enough to critique and improve.

    Shared language becomes stronger when practitioners can challenge definitions and add missing workflows.

Stewardship

Open the framework, protect private data

The category becomes credible when the public language is separated from private implementation work.

Public

Shared framework

Category language that belongs in public view so the field can develop shared vocabulary.

  • Definitions, taxonomy, and the RDI stack
  • Workflow library and evidence principles
  • Maturity model and assessment
  • Value methodology and directional calculator
  • Teaching material and glossary

Protected

Private implementation

Customer data, benchmarks, quote logic, and product decisions stay outside the public category reference.

  • Customer and project data
  • Project-specific benchmarks
  • Quote logic and commercial modelling
  • Sales intelligence and pipeline
  • Product roadmap decisions

Tests

Five questions

Use these questions to test whether a technology claim is really RDI.

Test 1: Capture

What reality is captured?

Test 2: Ground Truth

What makes it trustworthy?

Test 3: Interpretation

What meaning is extracted?

Test 4: Action

What action is routed?

Test 5: Command

What outcome is measured?

Publication

First published
April 2026

The manifesto, stack, workflow library, maturity model, and measurement methodology are published together and revised as the framework is tested.

Stewardship
Initiated by Evercam. Maintained in public for the construction field.

See the stewardship note for the boundary between the public framework and private implementation work.