Product case study

Siteproof: structured evidence from field to office.

Siteproof demonstrates how an evidence-heavy field workflow can be treated as one operational system: capture at source, structure the record, review it deliberately, and retain what matters.

Design context

The handoff is part of the product.

Evidence-heavy field work can break down when site records, photographs, notes, and office checks live in separate tools or arrive without enough context. The product problem is not only capture; it is the full route from work completed to evidence understood.

Siteproof shows how Wolsten approaches that problem: one structured path from capture through office review, with the evidence, exceptions, and ownership kept around the job.

Product decisions

One record from capture to review.

The workflow is designed around evidence quality, operational ownership, and the decisions that happen after information leaves the field.

  1. 01

    Capture at source

    Treat field evidence as part of the operational record from the moment it is created, rather than as an attachment reconstructed later.

  2. 02

    Structure the record

    Organise evidence around the job and its required context so office teams can review a coherent record instead of disconnected files.

  3. 03

    Keep review human

    Make review status, exceptions, and ownership visible so the system supports a decision without pretending to replace accountability.

  4. 04

    Design for retrieval

    Preserve evidence in a form that can be found and inspected when operational, commercial, or assurance questions arise.

Operational fit

Start with the evidence problem.

If field records, office review, and assurance sit across disconnected tools, the first step is to map the workflow, owners, and evidence requirements before choosing what to build.