MJM · RAMS
How MJM Industrial made safety paperwork faster to write and easier to fix
Safety documents slowed every job down
MJM Industrial carries out engineering work on major airport sites. Before anyone can go on site, the team needs a RAMS pack (risk assessment and method statement) that the client is happy with.
Most of that work lived in Word. People copied old files, changed the job details by hand, and emailed versions back and forth. When the client sent changes, someone had to read the whole thread and edit the document line by line.
A form that fills in the template for you
We built a simple web form that matches MJM's own template. Dropdowns, dates, and default text cut out a lot of typing, and longer sections can be drafted with AI so the engineer is editing rather than staring at a blank page.
They upload the template once, answer the questions for the job, and download a finished document. Their SimPro job system stays as it is; this just takes the slow document prep off the side of the desk. Work that often took two hours or more in Word usually lands in about half an hour, before the engineer signs it off.
When feedback arrives by email
When a client sends rejection notes or comments by email, the system picks up that message, works out what they are asking for, and adds suggested changes onto the RAMS file stored in SharePoint.
An engineer still reviews everything before anything goes back. The difference is they are checking suggested edits, not rebuilding the file from scratch after an afternoon in Track Changes.
How it works day to day
- 01
Fill in the job details
The form follows your existing template.
- 02
Generate the document
Download a draft ready for review.
- 03
Send it for approval
Same process the client already knows.
- 04
Handle feedback
Email comments turned into edits to review.
What it runs on
Paperwork keeps up with the jobs on the board
Before
2+ hrs
Building each RAMS by hand in Word
After
~30 min
Form, draft sections, and one-click generate
Typical time for a new pack. When clients send changes, the team spends time reviewing, not rewriting from zero.
