Private beta · regulated UK construction
RAMS written for this site, not the last one.
Upload the client's pre-construction pack. ProtechOS supports the drafting of the safe system of work, construction phase plan and COSHH from it, with gaps marked rather than guessed and citations checked against UK law. Your competent person reviews and approves, on a record nobody can edit afterwards.
Illustrative · fictional project
Citations checked against a register of UK law, including
- CDM 2015
- MHSWR 1999
- COSHH 2002
- CAR 2012 · HSG247
- LOLER 1998
- WAHR 2005
The argument
Page 12 still says Manchester. The job is in Leeds.
Most method statements that reach a principal contractor were written for another job. The reviewer spots it in a minute and sends it back, and the start date moves with it. The ones that get through are worse: signed at 07:20 while the gang queues for the welfare, then filed as proof that everyone had the information.
47
pages, last revised for a different site
Illustration: a 47-page method statement in which 40 pages were carried over from another job. Page 12 still gives the site address as Manchester; the job is in Leeds.
0
pages carried over from another job
Every section drafted from this site's facts; anything missing, marked.
Illustration: four pages of a safe system of work drafted for the Leeds job, each with its own title and section band; the rescue arrangements page marks a fact still to confirm.
Illustrative, not survey data.
What it holds to
Specific, grounded, defensible
Three properties a document needs before a competent person should put their name to it.
It asks before it drafts, and marks what it was not told
It reads the client's pack into activities and site facts, asks for what it still needs before drafting, and writes [TO CONFIRM by author] rather than a plausible guess.
- Pack read, not retyped
- Fact check before drafting
- Gaps marked, never guessed
Your wording. Citations checked against UK law.
Your hazard and hold-point wording, per-substance COSHH keyed to safety data sheets, seasonal hazards from thirty-year climate normals, and every legislation citation checked against a register.
- Drafted from your libraries
- Citations checked before approval
- Weather from named sources
A record you can hand over without wincing
A named person at every step, approval separate from authorship, hold points that freeze at approval, and an audit trail nobody can edit afterwards.
- Approval separate from authorship
- Append-only trail
- Approval fixes the issued document
How it works
From the client's pack to an approved set
The work left for you is the work that needs judgement: confirming the facts, and signing the document.
-
Illustration: the pre-construction pack for a drainage connection in Leeds, uploaded and read into three suggested activities.
01Give it the pack
Pre-construction information, phase plan, design and fire strategy. Read, not retyped.
-
Illustration: the fact check asks for site facts; rescue arrangements, not yet supplied, are marked to confirm by the author.
02Answer the fact check
It asks for the site facts each document needs before it drafts. What it is not told stays marked.
-
Illustration: the safe system of work for the Leeds drainage connection generating, its sections arriving one after another.
03Generate the set
Core content readable in about a minute. Appendices stream in. Nothing partial can be issued.
-
Illustration: revision 3 approved by a named person after review, ready to export as a pack.
04Review, approve, issue
Edit the page as it prints. Citations checked. Approval is a named, recorded act, separate from authorship.
Illustrative · fictional project
What it produces
Twelve controlled documents. One set of facts.
Every document in the register is drafted from the same project context, so they agree with each other — the lifting plan and the method statement are describing the same lift.
| Code | Document | Scope | Tier | Where it comes from |
|---|---|---|---|---|
| SSOW | Safe system of work · 15 parts
| Activity | Core | The pre-construction pack, the fact check and your hazard and hold-point wording. One document, one revision, one approval. |
| CPP | Construction phase plan | Project | Core | The pre-construction information and the CDM stakeholders named in it, on a formal template with contents and numbering. |
| COSHH | COSHH assessment | Substance | Core | Materials picked up from the design pack; one assessment per substance, CLP-classified and keyed to its safety data sheet. |
| ENV-RA | Environmental risk assessment | Site | Core | The site, its receptors and the programme window. |
| LIFT | Lifting plan | Activity | Core | The activity: load, plant, appointed person, exclusion zone and sequence. |
| TW | Temporary works assessment | Activity | Core | The design brief, category, coordinator and check regime. |
| ASB-POW | Asbestos plan of work | Activity | Specialist | Suggested only when the scope contains licensed asbestos work, under HSG247. |
| RAD-RA | Radiological risk assessment | Activity | Nuclear-licensed sites | Dose constraints, controlled areas and monitoring. |
| CCP | Contamination control plan | Activity | Nuclear-licensed sites | Containment, transit and clearance arrangements. |
| SFAIRP | SFAIRP demonstration | Activity | Nuclear-licensed sites | The written case that risk has been reduced so far as is reasonably practicable. |
| DOSE | Dosimetry plan | Activity | Nuclear-licensed sites | The dosimetry regime for the personnel on the activity. |
| BRIEF | Daily briefing record | Day | Core | An approved safe system of work, summarised for the day's task without adding facts, with a printed attendance grid. |
-
SSOW Safe system of work
The pre-construction pack, the fact check and your hazard and hold-point wording. One document, one revision, one approval.
Activity Core
- Risk assessment
- Method statement
- Hold points and permits
- PPE assessment
- COSHH per substance
- Environmental risk
- HAVS
- Manual handling
- Work at height and access
- Emergency procedures
- Legislation
- ALARP
- Competency
- Inspection and monitoring
- Incident reporting
-
CPP Construction phase plan
The pre-construction information and the CDM stakeholders named in it, on a formal template with contents and numbering.
Project Core
-
COSHH COSHH assessment
Materials picked up from the design pack; one assessment per substance, CLP-classified and keyed to its safety data sheet.
Substance Core
-
ENV-RA Environmental risk assessment
The site, its receptors and the programme window.
Site Core
-
LIFT Lifting plan
The activity: load, plant, appointed person, exclusion zone and sequence.
Activity Core
-
TW Temporary works assessment
The design brief, category, coordinator and check regime.
Activity Core
-
ASB-POW Asbestos plan of work
Suggested only when the scope contains licensed asbestos work, under HSG247.
Activity Specialist
-
RAD-RA Radiological risk assessment
Dose constraints, controlled areas and monitoring.
Activity Nuclear-licensed sites
-
CCP Contamination control plan
Containment, transit and clearance arrangements.
Activity Nuclear-licensed sites
-
SFAIRP SFAIRP demonstration
The written case that risk has been reduced so far as is reasonably practicable.
Activity Nuclear-licensed sites
-
DOSE Dosimetry plan
The dosimetry regime for the personnel on the activity.
Activity Nuclear-licensed sites
-
BRIEF Daily briefing record
An approved safe system of work, summarised for the day's task without adding facts, with a printed attendance grid.
Day Core
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.
Commitments
Your wording, your branding, your documents
-
Every document type on every plan. No document you are legally required to produce sits behind an upgrade.
-
Your branding, never ours. Logo, address, company number and contact details on every cover. Approval fixes them into the issued document.
-
You keep your documents. Export any document as a PDF, or everything your organisation holds, whenever you choose.
First-call questions
What people ask before they try it
Will a principal contractor accept a document produced this way?
No one can promise that; acceptance is the principal contractor's decision. What gets a submission returned is usually generic content written for another site. What leaves ProtechOS is drafted from this site's facts, marks anything unconfirmed, carries checked citations, and names the approver and the revision.
Does it write our documents for us?
It supports drafting them from your project facts and your own libraries. Your competent person reviews, edits and approves, and the author cannot approve their own document unless an exception is recorded with a reason. Accountability sits exactly where it does today; the difference is the draft is about this job rather than the last one.
What stops it inventing something?
It is not allowed to invent a site fact — anything it was not told is marked [TO CONFIRM by author] and listed for you. And every legislation citation is validated against a register of UK health and safety law before the document can be approved, so an invented regulation is flagged rather than published.
Can we use our own hazard wording and branding?
Yes. Your hazard bank, hold-point wording and standing clauses are supplied to the drafting step, so the output uses wording your clients have already accepted. Your logo, address and company details sit on every cover — never ours.
How long does a full pack take?
Core content on a safe system of work is readable in about a minute and the full document lands in a few minutes, with appendices arriving as they finish. A whole project runs as a queue with live progress. The real constraint is how fast you can answer the fact check — which is what makes the output specific.
What happens to our documents if we stop?
They stay yours. Documents export as PDF at any time, and an administrator can export everything the organisation holds, self-serve. Leaving does not cost you your records.
Private beta
Put it against a real job
Bring a pack you already have. See what comes back, with your wording and your branding on it, and tell us where it falls short.
No cost during the beta. Every document type included — COSHH and construction phase plans are never behind an upgrade.