
A practical guide to RAMS on site
Connect risk assessments and method statements to review, briefing and acknowledgement, with a practical document-control workflow.
Read the guideKeep permit preparation, review, issue and closure in one workflow. Connect the scope of work, responsible people and supporting documents to the permit record.

How Permits connects the task, the people and the record.
Identify the site, planned work, scope and supporting documents. Keep relevant RAMS and conditions with the permit so reviewers have the context they need.
Route the record to the people responsible for authorisation. Record the issue decision and validity information against the permit for that work.
Keep the handover and closure information with the issued permit. Retain the history so the team can trace preparation, authorisation and completion.
Workflow illustration for Permits. No customer records are shown.
Permit details linked to the site and planned work
Scope, conditions and supporting documents kept together
Named people responsible for review and authorisation
Recorded issue, validity and closure information
A permit history connected to RAMS and site records
Clear answers to help you choose the right setup for your team.
Yes. Keep the relevant work information and supporting records with the permit so the reviewer can follow its scope and conditions.
No. Preparation, review and issue are separate steps. The responsible people control the authorisation decision and the conditions for the work.
The workflow retains validity and closure information, together with the issue history and the people responsible for the record.

Connect risk assessments and method statements to review, briefing and acknowledgement, with a practical document-control workflow.
Read the guide
Understand how a risk assessment and a method statement differ, how they work together, and how to keep their revisions aligned.
Read the guideBring the people, the paperwork and the site record together in one toolbox.