How Complys rewrites failed RAMS into approved documents (UK 2026 guide)

The pain of getting a RAMS sent back

You spend an hour writing a RAMS. You email it to the main contractor. Three days later it comes back with three pages of comments. Missing legislation references. Generic hazards. Vague controls. Could the PPE be more specific? Where is the emergency procedure? Why does the document still reference the 17th Edition Wiring Regulations?

The mobilisation date is in five days. The site manager is already asking when you can start. You either rewrite the whole document tonight, or you delay the start. Either way, the next job is also waiting and you have not even started its RAMS.

This is the cycle that automated RAMS rewrite tools were built to break. Take the existing document, take the feedback from the reviewer, and produce a rewritten version that addresses every point. Not a fresh RAMS from scratch but a surgical fix to the one that came back.

What an automated RAMS rewrite actually does

The simplest description: feed in the original RAMS and the feedback, and the tool produces a rewritten document that addresses each point of feedback while preserving everything in the original that was already correct.

The mechanism is the same large-language-model technology behind chatbot assistants, but constrained to UK construction safety standards and instructed to behave conservatively. It does not invent new project details, swap in different operatives, or change the scope. It addresses the feedback against the existing document and rewrites only what needs rewriting.

What the tool reads

• The original RAMS document - extracted from PDF, Word, or text
• The feedback - either pasted as text from the main contractor's email, or extracted from an automated review of the original
• The trade context - inferred from the RAMS content (electrical, scaffolding, demolition, etc)
• UK legislation library - the relevant standards for the trade and the work type

What the tool produces

• A rewritten RAMS document - same structure, same project details, with the feedback points addressed
• A change log - what was changed, where, and why (so the reviewer can verify on resubmission)
• An adequacy verdict - the tool runs an internal review on the rewrite and confirms it would pass review
• An optional re-review - re-running the original review pipeline against the new version, to verify the fixes landed

What automated rewrites fix well

The categories where AI rewrite tools genuinely add value are the same categories where AI review tools catch failures. This is not coincidence; review and rewrite are two sides of the same competence.

Generic content

If the original RAMS says "be aware of falling objects when working at height", the rewrite tool replaces this with trade-specific and site-specific language. For a roofer working on a residential reroof, the rewritten version might read "Operatives will install perimeter scaffolding with toe boards before any tile removal. Lower roof to ground via designated debris chute located in the side access (no throwing or dropping). Exclusion zone of 3m radius around the chute at ground level with hi-vis tape and supervisor sign-off before zone enters use."

Missing legislation references

The tool knows what legislation applies to each trade and adds it. Electrical RAMS get the Electricity at Work Regulations 1989 plus BS 7671. Work-at-height RAMS get the Work at Height Regulations 2005 plus HSG33 references. Asbestos work gets the Control of Asbestos Regulations 2012 plus the relevant Refurbishment and Demolition survey reference.

Outdated references

If the original references the 17th Edition Wiring Regulations, the rewrite updates to BS 7671:2018 + Amendment 2:2022. CDM 2015 timeline language is current-day-corrected. Old HSE guidance references are updated to current publications.

Vague controls

The tool converts "operatives will take care" into named, observable, sign-offable actions. The original tone of voice is preserved; only the specificity changes.

Missing PPE specifications

"Wear appropriate PPE" gets replaced with EN-standard references: EN ISO 20471 Class 2 hi-vis, EN 397 hard hats, EN ISO 20345 S3 safety boots, EN 388 cut-resistant gloves. The tool knows the standards for each trade and adds them automatically.

Missing competence evidence

If the original says "competent scaffolders" without card numbers, the rewrite cannot invent card numbers (it does not know them). What it CAN do is restructure the section to make the card number, qualification, and supervisor information into a placeholder table that the user fills in before submission. This is more useful than the original because the gap is now obvious and structured.

What automated rewrites cannot fix

Three categories that rewrite tools are honest about not handling:

Fundamental scope mismatches

If the original RAMS was written for a different project and someone tried to retrofit it, the rewrite tool cannot save it. Site-specific judgment must come from someone who knows the site. The tool will rewrite around obvious site references but cannot replace a RAMS that was the wrong document to begin with.

Missing factual content

The tool cannot invent operative names, card numbers, supervisor details, or emergency contact phone numbers. These have to come from the user. A good tool flags the missing fields clearly rather than making them up.

Misalignment with site reality

If the original RAMS describes a 3m mobile tower but the actual job needs a 6m system scaffold, the rewrite cannot know. It will rewrite the original description more carefully but it cannot tell you the scope is wrong. Only a site visit or scope conversation catches this.

Adversarial pushback

If a main contractor's review is unfair or wrong (occasionally happens), the tool follows the feedback. It does not push back on a reviewer who has asked for something that is not legally required. That conversation has to come from a human who is willing to defend the original document.

How Complys handles each step

The workflow a Complys user goes through to rewrite a RAMS:

Upload the original RAMS

Drag the PDF or Word file into the upload area. The system extracts the text and identifies the trade.

Add the feedback

Paste the main contractor's email, type bullet-point feedback, or upload a comments document. Alternatively, run the RAMS through the review tool first to generate an automated findings list as the feedback input.

Configure the rewrite

Choose how aggressive the rewrite should be (light touch, standard, or full restructure), what trade and project context to maintain, and whether to add or just respond to the existing structure.

Wait roughly 60 to 90 seconds

The system rewrites the document, performs an internal adequacy check, and produces a change log.

Review the rewrite

Open the rewritten document side-by-side with the change log. Each fix is highlighted and explained. Approve, reject, or refine specific changes.

Export and submit

Export as PDF or Word. Submit to the main contractor with confidence that the feedback has been addressed.

The legal position on AI-rewritten RAMS

The same principle as AI-reviewed RAMS applies in reverse. The duty-holder is responsible for the document. The tool is an aid, not a substitute.

You sign the document. You stand behind it. If a HSE inspector challenges the RAMS during an incident investigation, "the AI wrote it" is not a defence. The defence is that the document is competent, complete, and accurate.

This is why the human review step matters. A good user reads the rewrite carefully, checks site-specific details, confirms operative names and competence references, and signs only when satisfied. The tool saves the writing time; it does not save the responsibility.

What about CDM 2015 specifically?

The Construction (Design and Management) Regulations 2015 hold duty-holders responsible for adequate RAMS. They do not require RAMS to be human-written. They require RAMS to be adequate. A human-reviewed, AI-rewritten RAMS that is adequate satisfies CDM. A human-written RAMS that is inadequate does not.

What about insurance?

UK contractor insurance policies do not exclude AI-written documentation. They cover the contractor's work and the contractor's decisions. Whether you wrote the RAMS yourself, used a template, or used an AI tool, your insurance covers the work the same way.

How long does rewriting a failed RAMS actually take?

By hand

• Re-read the original and the feedback: 15 to 30 minutes
• Identify what each feedback point needs: 15 minutes
• Rewrite each section: 1 to 3 hours
• Final review and consistency check: 15 to 30 minutes
• Total: 2 to 4 hours

With Complys

• Upload original: 30 seconds
• Paste feedback: 1 minute
• Configure and run rewrite: 30 seconds + 90 seconds processing
• Review the changes: 5 to 10 minutes
• Export and submit: 30 seconds
• Total: 10 to 15 minutes

For a small contractor receiving a rejection on a Friday afternoon with a Monday mobilisation, the difference between four hours and fifteen minutes is the difference between losing your weekend and going home on time.

Who benefits most from automated RAMS rewriting

Trade contractors working with multiple main contractors

The biggest savings. Different main contractors have different review standards. A scaffolder working with five Tier 1 contractors will inevitably get RAMS sent back from at least one or two per quarter. A rewrite tool turns each rejection into a 15-minute fix instead of a half-day rebuild.

Smaller subcontractors who are stretched on admin time

A two-person electrical firm where the owner does the books, the quoting, the customer calls, and the compliance has limited evening hours. A rewrite tool means the difference between getting RAMS done at the kitchen table after dinner and burning a Sunday.

Compliance officers in larger trade businesses

If you have a compliance officer rewriting RAMS for the operations team, automation lets one person cover the workload of three. They become the strategic editor; the tool handles the structural rewrites.

Newer businesses still building a RAMS library

A two-year-old contractor without a library of approved RAMS will face more rejections than a fifteen-year-old contractor with a battle-tested template. The rewrite tool fast-forwards the maturity curve by producing reviewed-quality output from day one.

What to look for in a RAMS rewrite tool

Preserves the original where appropriate

A good rewrite tool changes only what the feedback flagged. Everything else stays. A bad tool rewrites from scratch and loses the project-specific details you spent time on the first time. Test this on a real document: feed in feedback that addresses only one section, and check that the other sections are unchanged.

Trade-aware rewriting

The tool should know that an electrical RAMS rewrite must reference BS 7671 and the Electricity at Work Regulations 1989, while a scaffolding RAMS rewrite must reference TG20 and the Work at Height Regulations 2005. Generic tools produce rewrites that pass surface review but fail deeper inspection.

Change log transparency

You should be able to see exactly what changed and why. If a section was rewritten, the diff should be visible. If a legislation reference was added, you should know where and why. Black-box rewrites are useless because you cannot verify them.

Internal adequacy check

The tool should run a review on its own output before showing it to you. If the rewrite still has gaps, the tool should call them out rather than pretending the job is done. Good tools refuse to claim Pass when their own internal review finds issues.

Honest scope of what it cannot do

A tool that promises to "rewrite any RAMS to perfection" is overpromising. Tools that explicitly explain what they cannot do (missing facts, scope mismatches, site-specific judgment) are more trustworthy and more useful.

Original-document preservation

The rewrite tool should keep the original document available alongside the rewrite, not overwrite it. You may need to refer back, compare versions, or undo specific changes.

Editable output

The output should be a document you can edit, not a locked-down rendering. Your name on the bottom; your changes on top.

Common questions about RAMS rewriting

Is rewriting a failed RAMS the same as writing one from scratch?

Mostly yes, in legal and structural terms. The rewritten RAMS is your new submission. You signed off, you submitted. The difference is purely about workflow efficiency: starting from a draft that addresses known feedback is faster than starting from a blank page.

Will the main contractor be annoyed that I used AI to rewrite?

Almost certainly not. Main contractors care about whether the document is adequate, not how you produced it. If the rewrite addresses every feedback point professionally, the response is "good, thanks", not "did you use AI?". You can keep tool usage invisible if you prefer.

Can the rewrite tool fix a RAMS that was rejected for the wrong scope?

No. If the scope itself is wrong (the original was for a different project), the rewrite cannot save it. You need to write a new RAMS for the actual scope. The tool can help you produce that new RAMS faster but it cannot turn the wrong document into the right one.

What if I disagree with one of the feedback points?

Edit the tool's output before submitting. The change log shows you what was changed in response to each feedback point. If you disagree with a specific change, revert it and submit your defended version. Some feedback is genuinely wrong and you should push back through normal channels.

How many times can I rewrite the same document?

As many times as needed. Each rewrite uses fresh feedback and produces a fresh output. If the first rewrite was not accepted and you got new feedback, run the rewrite again with the new feedback. Tools that limit rewrites per document are penalising the work-mode they should be supporting.

Does the tool produce different output if I run it twice with the same inputs?

Slightly, yes. AI-driven tools have inherent variability. The structure and content addressing each feedback point will be consistent but specific word choices will differ. If you want absolute reproducibility, save the first rewrite rather than re-running.

What about for non-construction RAMS (events, manufacturing, agriculture)?

UK-specific tools like Complys are typically construction-trained. They will produce reasonable output for adjacent industries but will not have the same depth of trade-specific knowledge. For pure construction (any UK trade), tools are well-tuned. For sectors with very different hazard profiles, evaluate carefully.

The bottom line

RAMS rewriting is one of the least pleasant compliance tasks. It feels like rework, it usually happens under time pressure, and the original feedback often arrives at the wrong moment. Tools that compress it from half a day to 15 minutes are not just convenient; they are time you get back to work on the actual job.

For trade contractors who routinely get RAMS feedback (most of them), rewriting automation has become genuinely competitive. The contractors who can turn a rejection around the same day will mobilise faster, frustrate main contractors less, and protect their margins on tight programmes.

For more on what main contractors look for in subbie compliance documents, see our honest 2026 insider guide. For the underlying standards your RAMS must meet, see our complete UK RAMS guide. And if you want to see why your RAMS keep coming back, our guide to automated RAMS review walks through the same logic the main contractor uses.