Skip to main content

Validation programme

Test one important material decision from inventory to handoff.

A RubblePass pilot is a controlled validation engagement: limited scope, named participants, explicit evidence requirements and success measures agreed before work begins.

We are preparing validation in Istanbul. A pilot conversation is not a claim of an existing deployment, customer relationship or guaranteed result.

Good pilot fit

Bring a real constraint and the people who own the decision.

Bounded timing

A defined upcoming project

A building, portfolio process or programme with an identifiable pre-demolition decision window.

Named roles

The relevant participants

At least one evidence owner and one decision or receiving role able to test the handoff.

Lawful scope

Permissioned source data

Enough drawings, records or site access to test the workflow without using unnecessary personal or sensitive data.

Pilot path

Define first. Configure second. Learn from the evidence.

  1. 01

    Discovery

    Identify the decision, participants, timeline, constraints and current process.

    Fit check
  2. 02

    Validation brief

    Agree scope, data, roles, evidence gates and measurable success criteria.

    Written plan
  3. 03

    Configuration

    Set up the limited project workflow and fictional training records if needed.

    No broad rollout
  4. 04

    Guided use

    Run the selected inventory, review, matching or handoff scenario.

    Observed workflow
  5. 05

    Evidence review

    Compare the result with the baseline and document gaps, risks and changes.

    No inflated claims
  6. 06

    Decision

    Stop, iterate or define the next validation stage with a new scope.

    Mutual choice

Success measures

Use measures that the pilot can actually observe.

  • Required material fields completed and attributable
  • Evidence gaps and blockers identified before routing
  • Quantity range and assumptions understandable to reviewers
  • Time or rework compared with the agreed baseline process
  • Permissioned handoff completed between the named roles
  • Projected and verified statuses used consistently
  • Participant feedback recorded by workflow stage
  • Security, privacy and professional boundaries accepted

What to include

A useful first message can be short.

Your organization and role

The site, process or programme

The decision date and current blocker

The participants and data likely available

Start with evidence

Start with the decision you need to improve.

Use the contact form and choose a pilot conversation. We will respond with fit questions and the current validation availability.