What goes into a Site RAMS for drone operations (template walkthrough)

The RAMS is the document that decides whether a drone operator gets on a site. Procurement requests it. The principal contractor’s H&S manager reads it. The site manager signs it off. If the document is generic, the operator does not fly. If it is specific to your site and demonstrably written by someone who has stood on it, the operator flies.

This is the structure of a RAMS that survives a Tier 1 onboarding. It is not a template you can lift directly. Every site is different. The structure is what holds across all of them.

What a RAMS is and what it is not

A Risk Assessment and Method Statement is a single working document, two parts joined. The Risk Assessment identifies the hazards specific to the operation on this site, scores them, and lists the control measures. The Method Statement describes the sequence of work that will be carried out, who is responsible at each step, and what the safe envelope of the operation is.

It is not a generic policy document. It is not the operator’s standing operating manual. It is not the CAA Operational Authorisation. All three of those exist separately and feed into the RAMS. The RAMS itself is bespoke to your site. If a drone operator sends you a document that names their site rather than yours, the document is not a RAMS.

Under CDM 2015, the principal contractor has a legal obligation to ensure that contractors working on the site are competent and that the work they propose is properly planned. The RAMS is the document that demonstrates both. If it does not, the principal contractor is exposed.

The structure that holds up

A serious drone RAMS for a construction site runs to ten or twelve pages. Shorter than that and the detail is missing. Longer than that and the working detail gets buried. The structure below is the one we use across active programmes including Ballymore Embassy Gardens, the Brentford Project, and the Canary Wharf monitoring contract.

Section 1. Operation summary.

A single page at the front. What is being done, where, when, by whom. Site address. Principal contractor. Site manager named. Operator’s company, CAA Operational Authorisation reference, and the named pilot for the operation. Date of operation. Duration. Weather contingency. Equipment serial numbers.

The summary is the first thing the H&S manager reads. If they cannot tell within sixty seconds what is being proposed, the document fails. Be specific. Vague summaries are the single biggest reason RAMS get bounced.

Section 2. Site survey.

Half a page documenting the pre-operation site survey. When the operator visited the site. Who they met. What they observed. Photographs of the proposed take-off and landing point. A site plan showing the flight envelope, the exclusion zone, and the location of the principal hazards.

The survey establishes that the operator has stood on the site. Most generic RAMS skip this section. The procurement teams that are actually paying attention spot the omission immediately.

Section 3. Hazard identification and risk scoring.

A table. Each row is a hazard. Each row carries the hazard description, the people exposed, the likelihood, the severity, the gross risk score, the control measures, and the residual risk score after controls.

The hazards that should appear on every drone-on-site RAMS:

Aircraft loss of control. Equipment failure leading to drop. Controls: pre-flight checks, maintenance log, flight in safe envelope away from people, exclusion zone enforced.

Battery fire. Lithium polymer thermal event during flight or on the ground. Controls: only certified batteries used, maintained on a log, charged in fireproof bag, fire extinguisher on the take-off point.

Loss of visual line of sight. Pilot losing sight of the aircraft due to obstruction. Controls: defined flight envelope within visual line of sight, observer in position with radio, return-to-home programmed.

Loss of GPS signal. Aircraft entering an area of GPS interference. Controls: pre-flight site survey for known interference sources, manual flight contingency, return-to-home programmed.

Wind exceedance. Sudden wind gust above operational tolerance. Controls: live wind monitoring at flight altitude, defined wind threshold in the RAMS, abort criteria documented.

Strike on personnel. Aircraft striking a worker on site. Controls: exclusion zone of defined radius around the take-off point and the flight envelope, all workers in zone briefed, hi-vis observer at the boundary.

Strike on third party. Aircraft straying outside the site boundary. Controls: defined flight envelope inside the site boundary, geo-fence programmed where supported, abort criteria for boundary breach.

Strike on tower crane or MEWP. Aircraft striking active plant. Controls: pre-flight coordination with crane operator, no-fly time slots agreed for crane lift operations, exclusion of the flight envelope from active crane sweep.

Loss of comms with site. Pilot unable to reach the site manager during flight. Controls: radio check before flight, named site contact on UHF, mobile backup.

Public over-flight. Aircraft over members of the public outside the site. Controls: flight envelope inside site boundary, public footpath observer where the boundary touches a public area.

Adverse weather. Rain, low cloud, low visibility during the flight. Controls: live weather monitoring, threshold values documented, rebooking window provisioned.

Pilot incapacitation. Pilot becoming unable to continue the flight. Controls: second pilot or qualified observer on site, return-to-home programmed, abort procedure rehearsed.

Every hazard above gets a row in the table. The scoring is specific to your site. A pedestrian footpath fifty metres from the site boundary is a higher score than a closed industrial estate. A live tower crane in the flight envelope is a higher score than no overhead plant. The scoring should reflect the specifics.

Section 4. Control measures detail.

A page expanding on the headline control measures. The exclusion zone radius and how it is marked on the day. The pre-flight checks the pilot will perform. The maintenance log for the aircraft. The named observer’s responsibilities. The radio channel and the call signs.

This section gives the H&S manager confidence that the controls in the table are not aspirational. They are operational, with named responsibilities and physical evidence on the day.

Section 5. Exclusion zone definition.

A diagram. The site plan with the exclusion zone marked. The radius. The boundary marker positions. The position of the take-off and landing point. The position of the observer. The position of the pilot. The position of any personnel on the ground who must remain inside the exclusion zone for the duration of the flight (typically the pilot, the observer, and the site contact).

The diagram is the document that the site manager will hold on the morning of the flight. It needs to be readable on a phone in the rain. Annotate clearly. Use the same site plan the principal contractor uses, not a Google Earth screenshot.

Section 6. Weather thresholds.

A table. Wind speed, gust speed, visibility, precipitation, cloud base, temperature. Each parameter with its operational limit. Each parameter with the source of the live data on the day (handheld anemometer, Met Office METAR, site weather station).

Wind speed is the parameter that scrubs most flights. Set the threshold to the manufacturer’s operational limit, not the absolute limit. Most operators run a 10 metre per second sustained wind threshold, with a 12 metre per second gust threshold. Lower the threshold for high-altitude flight or for flight in close proximity to occupied buildings.

Visibility and cloud base matter for line-of-sight maintenance. Set the threshold to the maximum altitude of the planned flight envelope. The pilot must maintain visual contact with the aircraft at all times.

Document the rebooking window. A standard programme should carry a five-day rebooking window for weather. The first available day inside the window with all parameters within limits is the rebooked flight. If the rebooking window expires without a compliant window, the flight rolls to the next month.

Section 7. Emergency procedures.

A page. What happens if the aircraft drops. What happens if the aircraft strikes. What happens if a battery fires. What happens if a worker is injured. What happens if the pilot is incapacitated.

For each scenario: the immediate response, the named responsible person, the escalation chain, the reporting obligation to the CAA (a Mandatory Occurrence Report is required within 72 hours for any aircraft incident), and the reporting obligation to the principal contractor’s incident system.

The emergency procedures should be rehearsed at the pre-flight briefing on the morning of the operation. The site manager and the pilot should be able to recite the immediate response without referring to the document. If they cannot, the briefing has not been done.

Section 8. Public liaison.

For sites with a public boundary or active footways nearby. The plan for managing the public during the flight. Banksmen at the site boundary. Notice on the hoarding twenty-four hours ahead. Coordination with the local council if the flight crosses a public highway boundary.

For Central London sites, this section also covers the airspace authority coordination. NATS Non-Standard Flight Permission reference. Battersea Heliport ATC coordination if applicable. Met Police MPSFU coordination if applicable. The references go in the document, with the dates of the relevant clearances.

Section 9. CDM 2015 alignment.

Half a page. A statement that the operation is being carried out under the CDM 2015 framework, that the principal contractor’s site rules apply, that the operator’s CSCS-carded crew will sign in via the site induction, and that the RAMS has been issued to the principal contractor for review at least 48 hours before the operation.

This section is the legal anchor. CDM 2015 places the duty on the principal contractor. The operator’s RAMS demonstrates compliance with the duty. Without this section, the document is a drone safety statement, not a construction-site RAMS.

Section 10. Review and approval.

A signature block. The operator’s accountable manager signs as the issuing authority. The named pilot signs as the operating pilot. The site manager signs as acceptance.

Issue the document at least 48 hours before the operation. The site manager needs time to read it. If they have queries, time to resolve them. If they need it amended, time to amend it. RAMS issued on the morning of the flight do not survive scrutiny.

What gets the document bounced

Three patterns we see when a drone operator’s RAMS is rejected.

Generic boilerplate. The site address is wrong. The hazards are not specific to the site. The exclusion zone diagram is a stock plan. The H&S manager bounces the document on the first read because the operator has clearly not visited.

No CAA reference. The Operational Authorisation is missing or vague. The pilot’s GVC reference is missing. The H&S manager cannot verify the operator’s authorisation. The document bounces.

Aspirational controls. The control measures read as policy rather than as operational instructions. “All flights conducted in accordance with safe operating practice” is not a control measure. “Exclusion zone of 30 metres marked by hi-vis cones at the take-off point, monitored by observer with radio on Channel 4” is a control measure. The first phrasing fails. The second passes.

What a procurement team should ask for

A short list to run before commissioning any drone operator on a UK construction site.

1. The RAMS specific to your site, issued at least 48 hours before the proposed operation.
2. The operator’s CAA Operational Authorisation reference, verifiable on the CAA register.
3. The named pilot’s GVC reference and the named observer’s qualifications.
4. The maintenance log for the aircraft to be used.
5. The current Certificate of Insurance, including public liability at the level your principal contractor requires (typically £10m on Tier 1 sites).
6. Evidence of any restricted airspace clearance if the site sits inside a Restricted Zone or near a heliport notification envelope.

If the operator can provide all six cleanly, they can fly the site. If any one is missing, that is the bit that will stop the flight on the morning.

---

If your site is being onboarded for an aerial monitoring programme, the capability deck includes a redacted sample RAMS, the standard operating envelope, and the CDM 2015 compliance summary. Request the capability deck or call 0207 458 4997.