Controlled documents

Show the right CPP and RAMS, with their status intact

For the founding pilot, the document viewer is bounded to project-specific CPP and RAMS. It identifies the exact version and prevents an old issue being mistaken for the current one.

Reviewer working through controlled construction documents.Controlled pilot scope

What the workflow is intended to deliver

01

Clear version and status

02

Immutable issued history

03

Current-document route

04

Fresh acknowledgement after change

The working sequence

A bounded, reviewable journey

Each stage leaves a record that can be checked. Where the information is unknown or a competent assessment is required, the workflow should say so.

01

Draft

Prepare and amend a working version without presenting it as issued.

02

Approve

Record the competent-person decision against the exact content hash.

03

Issue

Publish that exact version to the bounded project journey.

04

Supersede

Retain the earlier issue and require acknowledgement of the replacement.

Evidence carried forward

What should remain traceable

The record is useful only when the source, version and human decision remain connected.

  • Document type and revision
  • Issue timestamp
  • Content hash
  • Superseded-by reference

Important boundaries

Assistance without false assurance

  • SiteHQ supports a controlled process; it does not approve or certify construction safety.
  • The customer remains responsible for project facts, suitability, competent-person review and approval before use.
  • AI-assisted drafts may be incomplete or wrong and must not be treated as physical site observations.

One controlled founding pilot

One contractor. One active project. A supervised first journey.

£195 + VAT per month · two-month minimum · manual invoice · no automatic renewal.

Discuss fit with SiteHQ