How it works
From a pre-construction pack to an approved, issued set
Six steps. Two need your judgement: confirming the facts and approving the document. The reading, drafting and cross-checking in between is the system's job.
- 01
Give it the pack
Upload the pre-construction information and the phase plan. ProtechOS reads them into suggested activities, extracted site arrangements and the CDM stakeholders named in the documents. Design, structural and fire strategy documents go in too — materials that need a COSHH assessment are picked up from them.
Illustration: the pre-construction pack for a drainage connection in Leeds, uploaded and read into three suggested activities.
- 02
Confirm the activities
The project breaks into key activities and each gets the documents that activity needs. Add what the pack did not say, remove what does not apply. Specialist types — an asbestos plan of work, say — only appear when the scope contains that specialism.
- 03 Your judgement
Answer the fact check
Before anything is drafted, it asks for the site facts each document type requires: access arrangements, isolation points, ground conditions, adjacent works, emergency arrangements. Whatever stays unanswered is marked in the document rather than guessed.
Illustration: the fact check asks for site facts; rescue arrangements, not yet supplied, are marked to confirm by the author.
- 04
Generate the set
Core content on a safe system of work is readable in about a minute; the full document lands in a few minutes and appendices arrive as they complete. A partial document cannot be exported or approved.
Illustration: the safe system of work for the Leeds drainage connection generating, its sections arriving one after another.
- 05 Your judgement
Review and approve
Edit the document as it will print, with comments beside the section they concern. Citations are checked against a register of UK legislation before approval. Submit for review, send back with changes, approve. Approval is separate from authorship. Any exception is recorded with a reason.
Illustration: revision 3 approved by a named person after review, ready to export as a pack.
- 06
Issue and hold the record
Export a branded PDF, or the whole project as one pack. Each hold point becomes a pending sign-off, released on site by the named people. Every step sits in an append-only trail.
Illustrative · fictional project
The evidence chain
A record you would be glad to hand an inspector
Not a report you assemble for the audit. The trail the work already produced, with a named person at every step.
- Drafted
R. Ahmed
08:52 · from the pack
- Reviewed
M. Okafor
clause 3.2 — exclusion zone widened
- Approved
J. Whitfield
rev 3 · 31 Jul 2026 09:14
- Issued
S. Patel
export pack · hold points frozen · PDF as approved
The author does not approve their own work
The author cannot approve their own document. The two exceptions — an administrator override that needs a written reason, and a waiver for one-person organisations — are recorded as exactly that, never as independent approval.
The trail cannot be edited
Append-only. A trigger blocks update and delete — for your administrator and for us.
Every drafting call is kept
Instruction, model, response, timing. Replayable months later to explain why the document says what it says.
Questions
What people ask
What if the pre-construction information is poor?
That is the common case. Whatever the pack does not tell the system becomes a question in the fact check, and anything still unanswered is marked in the document rather than invented. A thin pack produces a document with visible gaps — the correct outcome, and safer than a complete-looking one.
Can more than one person work on a project?
Yes. Team members have roles — administrator, team lead, assessor, staff — and those roles govern who can draft, review and approve. Reviewer comments attach to the section they concern.
Private beta
Request beta access
Leave a work email. We will reply to arrange a call and run one of your own packs through it with you.