See one case become a pack.

Awaab's Law demo for social landlords

Five minutes on DEMO-001: report, clock, gaps, proof request, pack limits. Synthetic records only, so buyers can judge the workflow without tenant data.

EvidenceTrail supports evidence gathering, clock visibility, operational review, and pack preparation. It does not guarantee legal compliance, financial outcomes, regulator acceptance, Ombudsman findings, or litigation outcomes.

Controlled pilot next step

The guided demo routes to the same controlled-pilot request journey: review the synthetic demo, check procurement and trust material, then request scoped pilot planning through the demo-request path.

Pilot scoping is a review workflow only. It does not approve procurement, production processing, legal compliance, security certification, or live tenant-data use.

Public proof path

Follow the buyer evidence path

One public thread connects the homepage promise, guided synthetic demo, watermarked sample pack, and pilot request. No customer records or outcome claims are implied.

  1. 1 Public case promise
  2. 2 Guided demo
  3. 3 Sample pack
  4. 4 Pilot request
Phase 2 update

Phase 2 announced for Oct 2026: see what changes.

Five-minute walkthrough

  1. Start with a damp or mould report Open DEMO-001 with awareness time, route, tenant contact, and source reference.
  2. Statutory clock triage See the investigation, written-summary, safety-work, and emergency-response posture.
  3. Evidence gap chase Name the missing inbox, contractor, no-access, and proof-link evidence.
  4. Review-ready evidence pack Generate citations, custody steps, gaps, review status, and integrity evidence.
  5. Privacy and redaction review Mark redaction, DSR, disclosure, and controller-review limits before export.

DEMO-001 report to pack story

The guided readout follows one synthetic damp and mould case through four reviewable moments. It shows what the product can organise, not whether the landlord has met every legal duty.

  1. 1 · Report Start from the source record

    Show the reported hazard, awareness timestamp, route, and source reference.

  2. 2 · Gaps Name what is missing

    Surface unresolved inspection, contractor, tenant-update, and access evidence.

  3. 3 · Proof Send scoped evidence requests

    Use zero-login proof links for tenant or contractor evidence without blame.

  4. 4 · Pack Review the pack limits

    Bring sources, custody, redaction notes, known gaps, and limits together.

14-day pilot promise

In 14 days, the pilot should give repairs, compliance, procurement, and information-governance reviewers a shared buyer readout: what evidence exists, what remains missing, what can be reviewed safely, and what would block a paid rollout decision.

Pilot scope

Work around one damp and mould case cohort, one named owner, and one review ritual for clock, evidence, privacy, and pack-readiness questions.

Pilot inputs

Use sample data, CSV exports, shared inbox examples, source-system references, and named reviewer roles before any production tenant file import.

Pilot outputs

Produce a clock-risk snapshot, evidence-gap register, proof-link plan, review-ready pack sample, and buyer readout for the pilot review meeting.

Pilot exclusions

Production legal advice, compliance certification, live tenant messaging without controller approval, and fabricated outcome claims are excluded.

Pricing path

The pricing path is explicit: pricing starts from the pilot plan, then moves to provider or group packaging only after agreed rollout criteria.

Success criteria

Success means the buyer can name the first cohort, owner, evidence sources, go/no-go blockers, and next paid rollout decision without treating the pilot as a compliance guarantee.

Buyer readout format

14-day pilot success criteria and buyer readout format
Readout area Buyer question Success signal
Workflow fit Can the pilot follow the case across repairs, inbox, and review owners? Named source systems, owner, reviewer, and first import/mapping route.
Evidence value Can the team see gaps and reviewer-ready pack limits quickly? Clock-risk snapshot, gap register, and sample pack reviewed together.
Commercial next step Can procurement and IG decide whether a paid rollout is worth scoping? Go/no-go blockers, pricing path, data approvals, and rollout owner named.

The pilot promise is operational proof for a narrow cohort, not legal advice, not a compliance guarantee, and not a promise of regulator, Ombudsman, or court outcomes.

EvidenceTrail workflow console

A compact synthetic view of the moment a buyer cares about: whether the case is clocked, evidenced, reviewable, and still honest about what remains missing.

Case DEMO-001
Route Potential significant damp and mould route
Clock 6 working days remaining
Pack posture Reviewable with gaps
Clock risk Source-cited milestone

Awareness time is linked to the first report; the investigation clock is visible with statutory source references and a human-review warning.

Evidence chase Missing proof, named

Contractor photo, tenant contact attempt, and no-access note are tracked as separate evidence gaps rather than hidden inside a generic task list.

Pack review Facts separated from limits

The pack can show source register, custody steps, audit events, redaction status, and unresolved gaps without claiming the landlord is compliant.

Privacy gate Controller review first

Disclosure bundles, DSR inventory, and redaction outcomes remain review evidence. Customer-approved proof required before production claims.

DEMO-001 guided evidence readout

Deterministic sample case, not customer data. The readout fixes the same case, same timestamps, and same evidence gaps on every demo so buyers can judge the workflow rather than a changing story.

Awareness source

Tenant damp and mould report logged on 27 October 2025 at 09:00.

Clock assessment

Potential significant route; investigation and written-summary milestones visible.

Evidence gap chase

Missing contractor photo, tenant contact attempt, and no-access note separated.

Proof request

Zero-login proof link asks for scoped tenant or contractor evidence only.

Pack review

Review-ready pack shows sources, custody trail, unresolved gaps, and limitations.

Guided proof journey for DEMO-001
Demo moment What the buyer sees Why it matters
Minute 3 Awareness timestamp, route, source reference, and fixed case summary. Confirms the clock story starts from visible source evidence.
Minute 7 Evidence gaps split by tenant, contractor, repairs, and complaint source. Shows the product chases missing proof without hiding uncertainty.
Minute 12 First value by minute 12: one reviewable pack readout with named gaps. Lets the buyer assess pilot usefulness before deeper integrations.

This deterministic readout is product evidence for a synthetic fixture, not legal advice, not a customer outcome, and not a compliance guarantee.

Download the watermarked sample evidence pack or continue into the live read-only demo.

Demo reset and readiness evidence

The operator demo can be reset to the same synthetic dataset, then checked for the `DEMO-001` aha case before a buyer walkthrough. This keeps the script, dataset, and public readout aligned.

Reset command

POST /operator/demo/dataset/reset

Readiness check

GET /operator/demo/readiness

Script evidence

2026-06-06_DAY_07_GUIDED_DEMO_STORYBOARD.md

These operator endpoints require authorised access. The public page documents the demo evidence shape without exposing tenant or customer records.

Synthetic scenario evidence matrix

Synthetic case: DEMO-001. This is a product walkthrough fixture for buyer review, not a customer story, not production data, and not evidence that any landlord has achieved a particular outcome.

No customer name, logo, testimonial, usage statistic, or outcome claim is implied.

What a pilot demo can prove without fabricated customer evidence
Evidence question What the demo can show Current proof status
Can the team see the Awaab's Law clock basis? Awareness time, route, milestone names, official source links, and conservative limitation text in one review surface. Synthetic fixture plus source-cited product behaviour.
Can missing evidence be chased without tenant logins? Proof-link intake, inbox matching, contractor evidence, no-access notes, and gap status shown as separate evidence sources. Prototype workflow evidence; delivery provider is not live.
Can a pack separate facts from review limits? Pack narrative, source register, custody steps, redaction markers, review status, pack hash, and unresolved evidence gaps. Operational pack evidence, not solicitor-grade filing.
Can privacy reviewers see what remains blocked? DSR inventory, disclosure-bundle manifest, lifecycle policy blockers, and privacy outcome logs without exposing raw PII in public materials. Internal DPO/controller review evidence, not legal-approved SAR tooling.

What the demo is trying to prove

For repairs operations

The demo shows a single view of clocks, risk route, appointments, contractor progress, no-access attempts, and unresolved evidence gaps.

For compliance and legal review

The pack narrative separates facts, statutory source references, evidence gaps, tenant communications, review status, and explicit limitations.

For information governance

Privacy review stays deliberate: raw personal data is not placed in public reports, redaction actions are audited, and disclosure manifests are review evidence rather than automated SAR decisions.

Best-fit pilot shape

Official sources to review