By the myPitLab team · Last updated 8 July 2026 · 9 min read
TL;DR
- Every MH, IC and utility survey job needs a credible RAMS before boots hit the ground — but most firms still rebuild Word documents from scratch per project
- Digital RAMS tied to your project context (client, site, scope, team) cuts first-draft time from hours to minutes without sacrificing audit quality
- UK survey RAMS must cover confined space, buried services, traffic, lone working and client-specific controls — not generic construction boilerplate
- PAS128, rail, petrochemical and highways flags should pre-fill method text and hazard libraries, not sit as manual copy-paste afterthoughts
- RAMS that live beside inspections, survey reports and client delivery stop the safety pack becoming a forgotten PDF in a separate folder
- Two UK-built options from the same team: myPitLab (RAMS inside full MH/IC field ops) and MySafeOps (dedicated RAMS + survey report generator)
Key takeaways
- RAMS is not paperwork for paperwork's sake — it is how you prove competence to clients, frameworks and your own field teams before opening a chamber
- Start from project data already in your operations system; do not re-type client names, site addresses and scope on every job
- Hazard libraries with control measures and P×S scoring beat free-text risk tables that drift between surveyors
- Issue, print, share read-only links and record sign-off in one place — version history matters when something changes mid-project
- myPitLab suits teams who want RAMS beside field capture, QA and client delivery; MySafeOps suits teams who want a focused RAMS and survey report generator first
In this article
- What RAMS means on UK survey jobs
- Why Word templates break at scale
- What a survey-grade RAMS must include
- PAS128, rail and confined space — conditional content that matters
- From generator to issued document
- Sign-off, sharing and audit trails
- RAMS alongside inspections and survey reports
- myPitLab vs MySafeOps — which platform fits?
- How to evaluate RAMS software for your firm
- Frequently asked questions
Introduction
Before your surveyor lifts a manhole cover, someone has written a RAMS. Before a framework client releases a PO, someone has checked it. Before an operative enters a chamber, someone has briefed the team against it.
Risk Assessment and Method Statement packs are non-negotiable on UK utility mapping, drainage inspection, PAS128 detection and highways MH programmes. Yet most survey firms still treat RAMS as a parallel workflow: a Word folder, a safety manager who becomes the bottleneck, and a PDF that rarely matches the live project scope by the time the crew arrives on site.
That gap costs money. Late starts waiting for paperwork. Inconsistent hazard wording across teams. Client reviewers bouncing documents because the method statement still references the wrong site address. Auditors asking for revision history you cannot produce.
myPitLab RAMS starts from your field project — client, site, work types and environment — and generates a structured first draft you review, issue and share without leaving the same workspace as inspections and survey reports.
If your priority is RAMS and client survey reports without the full MH/IC field stack, MySafeOps offers a dedicated RAMS generator and survey report generator built for UK site safety and documentation workflows — the same product family, aimed at teams who want safety and reporting tooling first.
This guide explains what UK survey operations teams should demand from digital RAMS in 2026 — whether you evaluate myPitLab, MySafeOps or any other platform.
What RAMS means on UK survey jobs
RAMS (Risk Assessment and Method Statement) is the documented agreement on how work will be performed safely and what hazards exist with what controls. On survey work it is distinct from generic construction RAMS because the hazards are specific:
| Hazard category | Typical survey context |
|---|---|
| Confined space | MH/IC entry, chamber inspection, CCTV launch |
| Buried services | CAT & Genny, trial holes, core holes |
| Traffic | Roadside covers, lane closures, Chapter 8 |
| Lone working | Remote rural runs, out-of-hours possession |
| Manual handling | Covers, tripods, GPR sleds, TS setups |
| Biological / hygiene | Sewerage chambers, standing water, sharps |
| Working at height | Tripods over chambers, rail access |
Clients and principal contractors expect method statements that describe your actual survey sequence — isolation, proving dead, entry protocol, survey equipment setup, data capture, reinstatement — not a paragraph copied from a building site excavation RAMS.
The risk assessment table should list hazards, control measures, and (where your process requires) probability × severity scoring with residual risk levels. PPE, emergency procedures, welfare and management arrangements complete the pack.
If your RAMS reads like it was written for bricklayers, framework reviewers notice.
Why Word templates break at scale
Template Word documents feel cheap until you run ten concurrent jobs:
- Version drift — Surveyor A's "final_v3_really_final.docx" is not what the office issued
- Re-keying — Client name, site address, project reference and dates typed again for every job
- Scope mismatch — Method statement still says topo when the PO added PAS128 D and CCTV
- No linkage — RAMS sits in SharePoint; inspections sit in another system; nobody knows which RAMS matches which phase
- Slow sign-off — Email chains with PDF attachments instead of a read-only review link and acknowledgement log
Digital RAMS does not remove the need for a competent person to review content. It removes the clerical tax of rebuilding structure every time.
The benchmark: project context in → credible first draft out → human review → issue → share → sign-off recorded.
What a survey-grade RAMS must include
A RAMS platform built for utility and infrastructure survey work should produce documents with these sections (print-ready, in sensible order):
- Cover — Client, project reference, site address, description of works, dates, revision, optional document number and review-by date, your branding
- Survey boundary / map — Geo context from KML/KMZ or project map; screenshot for site briefings
- Site weather — Conditions line for the survey date where available
- Method statement — Narrative of how work is performed; conditional blocks for PAS128, UAV, rail, petrochemical, confined space entry
- Pre-start checklist — Tick-list operatives use on site before work begins
- Risk assessment — Hazards, controls, optional P×S matrix, residual scores and risk levels
- PPE requirements — Aligned to hazards and, where possible, team certifications
- Emergency procedures — Including nearest A&E and out-of-hours contacts when configured
- Management arrangements — Monitoring, first aid, welfare, emergency — consistent across projects via org presets
- Acknowledgements / sign-off — Names, roles, dates
- Version history and integrity — Revision register and optional document hash for tamper-evidence
Missing pre-start checklists or emergency contacts is how RAMS fail client QA on technicality, even when the method statement is sound.
PAS128, rail and confined space — conditional content that matters
UK utility survey firms win work on PAS128 programmes, rail possessions, petrochemical sites and highways frameworks. Your RAMS generator should treat these as structured options, not manual paragraphs you paste in if you remember.
PAS128-oriented options might include:
- Detection intervals and confidence levels per utility type
- Method references (EML, GPR, TS, CCTV) selected per scope
- Limitation language aligned to site conditions
Rail flags should pull in trackside-specific controls — possession references, COSS briefings, distance from live rail, isolation protocols.
Confined space entry for MH/IC work should trigger entry procedure text, gas monitoring expectations, rescue arrangements and stand-by roles — not a single generic line about "awareness training."
Petrochemical / high-hazard sites need enhanced PPE, permit-to-work cross-references and restricted-area protocols.
When these blocks generate from selections made at RAMS creation time, the document matches the PO scope. When they rely on memory, they get skipped on busy Fridays.
From generator to issued document
A practical end-user flow looks like this:
- Select project — Client, address, reference and dates pre-fill from the job record
- Choose work types — Utility mapping, topo, MH/IC inspection, CCTV, GPR, monitoring — multiple types on one RAMS when the PO covers combined scope
- Set environment — Road, footpath, confined space, rail corridor, industrial unit
- Assign team and equipment — Pull typical kit strings (TS, GNSS, GPR, CCTV, CAT/Genny) from presets; suggest hazards from work type + environment keywords
- Select hazards from an organisation hazard library with standard control measures
- Generate — Server produces structured JSON payload; editor opens for review
- Edit — Adjust method wording, risk scores, PPE, emergency contacts, boundary map
- Issue — Mark final; freeze version; enable PDF print and optional cloud storage
- Share — Read-only token link for client or principal contractor reviewer where required
Field and office entry points should edit the same records — surveyors briefed on site should see what the safety manager approved in the office, not an exported snapshot from yesterday.
💡 Project context → defensible RAMS in minutes myPitLab — RAMS inside full MH/IC field ops, QA and client delivery. MySafeOps — dedicated RAMS + survey report generator when safety and reporting are your starting point. myPitLab → · MySafeOps →
Sign-off, sharing and audit trails
Framework clients increasingly ask:
- Who approved this RAMS and when?
- What changed between revision 1 and revision 2?
- Did every operative on site acknowledge the final version?
Your system should support:
- Draft vs final status — clear at a glance in the RAMS list
- Read-only share links — for external reviewers without giving edit access
- Acknowledgement table — names, dates, optional role (operative, supervisor, client rep)
- Revision register — when scope changed mid-project (extra shift, additional work type)
- Document integrity — optional hash so issued PDFs can be checked against the approved record
Emailing unsigned PDFs fails audits. A recorded sign-off chain does not.
RAMS alongside inspections and survey reports
The strongest operational fit is RAMS in the same platform as the work it governs:
| Workflow | Why linkage matters |
|---|---|
| MH/IC inspection | Method statement describes entry protocol; inspection record proves what was done |
| PAS128 utility survey | RAMS intervals match survey report limitations |
| CCTV | Confined space and hygiene controls align with launch records |
| Survey monitoring | Rail or construction monitoring RAMS references the same project phase |
| Client delivery | Principal contractor sees RAMS, survey report and deliverables under one project |
When RAMS lives in a siloed folder, project managers maintain two truths. When it sits beside all-in-one survey operations, the site briefing matches the data the client receives.
AI-assisted survey reports should pull structured field data only — never invent hazards or asset counts. RAMS remains the authoritative safety document; the survey report describes what was found. Keeping both in one org-scoped workspace prevents contradictory narratives.
On myPitLab, the Field Survey Report aggregates project assets, geo-photos, limitations and methodology from live inspection data. On MySafeOps, the survey report generator focuses on producing client-ready documentation packs alongside RAMS — ideal when your workflow centres on safety paperwork and formal reporting rather than day-to-day MH/IC capture.
myPitLab vs MySafeOps — which platform fits?
Both platforms are UK-built tools from the same team. The choice is operational scope, not quality of RAMS output.
| myPitLab | MySafeOps | |
|---|---|---|
| Best for | Drainage and utility firms running MH/IC surveys end-to-end | Teams who need RAMS + survey reports first; safety-led workflows |
| RAMS | Integrated with field projects, inspections and PAS128 options | Dedicated RAMS generator |
| Survey reports | Field Survey Report from live asset and geo-photo data | Survey report generator for client documentation |
| Field capture | MH/IC forms, offline sync, sketches, geo-photos | Not the primary focus |
| Deliverables | PDF, DXF, KML, KMZ, client portal from approved inspections | Report and RAMS packs for issue and share |
| Typical buyer | Operations director scaling field + office delivery | H&S lead, project manager, smaller crew needing fast RAMS/reports |
Choose myPitLab when RAMS must sit beside the same inspection record that generates DXF, KML and portal delivery — one source of truth from cover lift to client handover.
Choose MySafeOps when you want to stop rebuilding Word RAMS and survey reports on every job, and your immediate pain is site safety documentation and client report packs — not replacing your entire field capture stack yet.
Many firms evaluate MySafeOps for RAMS and reporting, then adopt myPitLab when field capture and deliverable exports need the same platform. Both beat a template folder in SharePoint.
How to evaluate RAMS software for your firm
Use this checklist when comparing platforms:
| Criterion | Pass | Fail |
|---|---|---|
| Project-linked generation | Client/site/scope pre-fill from job | Blank document every time |
| Survey work types | Utility mapping, MH, CCTV, GPR, PAS128 flags | Generic "construction" only |
| Hazard library | Org-level with controls; suggestions by context | Free-text only |
| Risk matrix | Configurable P×S with levels | No scoring |
| Multi-work-type RAMS | Combined scope on one document | One job type per file |
| Field + office access | Same records, mobile-friendly brief | Desktop-only or duplicate exports |
| PDF + share | Issue, print, read-only link | Copy-paste to Word for PDF |
| Sign-off | Acknowledgements and version history | No audit trail |
| Org isolation | Multi-tenant safe; your data only | Shared templates across companies |
| Integration | Beside inspections, reports, exports | Standalone silo |
Ask vendors to run a live job — your client name, a real site address, PAS128 + MH inspection combined — and time first draft to issued PDF.
Frequently asked questions
Is a RAMS legally required for manhole surveys? UK health and safety law requires suitable and sufficient risk assessment for work activities. Clients and principal contractors almost always contractually require a RAMS before site access — especially confined space entry, rail and highways work.
Can one RAMS cover multiple work types on the same project? Yes, and it should when the PO covers combined scope (e.g. PAS128 detection plus MH validation). Separate RAMS per work type create sign-off confusion when the same crew performs both.
How often should RAMS be reviewed? At minimum when scope, site conditions, team or method changes. Cover blocks should show review-by dates. Major scope changes warrant a new revision, not silent edits.
Does digital RAMS replace a competent safety reviewer? No. Software accelerates structure and consistency. A competent person still approves content for your organisation and the specific site.
Can clients sign RAMS electronically? Many firms use read-only share links plus acknowledgement records. Contractual requirements vary — confirm with your client framework.
How does RAMS relate to PAS128 survey reports? RAMS describes how work is performed safely. The survey report describes findings, limitations and deliverables. Method and limitation language should align; contradictory documents trigger client queries. Use myPitLab Field Survey Report or the MySafeOps survey report generator depending on your platform.
What is the difference between myPitLab and MySafeOps for RAMS? myPitLab integrates RAMS with MH/IC field capture, QA and multi-format client delivery. MySafeOps is a dedicated RAMS and survey report generator for teams whose priority is safety documentation and client reports — both are UK-built options from the same product family.
Summary
RAMS for manhole and utility surveys is too important to leave in a Word template graveyard. UK firms that win framework work and pass audits treat RAMS as operational data — generated from project context, reviewed by competent staff, issued with version control and stored beside the inspections and reports the RAMS governs.
Next steps: Audit your last three projects — how long did RAMS take, and did the issued pack match the live scope? Browse all insights, start a free myPitLab trial, or explore MySafeOps for RAMS and survey report generation.
