Version control
Preserve what was issued, what replaced it and who acknowledged each version
Issued content should never be silently rewritten. SiteHQ preserves the earlier issue, records the successor and makes fresh acknowledgement a separate event.
Controlled pilot scopeWhat the workflow is intended to deliver
Unique identifiers
Traceable supersession
Fresh acknowledgement
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.
Identify
Assign a revision, document identifier and content hash.
Issue
Bind approval to that exact version.
Retain
Keep the issue accessible as immutable history.
Replace
Create a new version and make the current state unambiguous.
Evidence carried forward
What should remain traceable
The record is useful only when the source, version and human decision remain connected.
- Unique version ID
- SHA-256 hash
- Issued-at timestamp
- Prior and next revision links
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