Construction Method Statement Examples: A Practitioner's Guide

The six method-statement types to adapt right now are scaffold erection, excavation and trenching, crane lift and heavy lifting, concrete pour and formwork, hot works and welding, and electrical isolation and lockout. Each example in this guide is structured so you can copy the framework, replace the site-specific placeholders, and submit a document that meets OSHA-aligned principal-contractor expectations. The sign-off checklist and template layout appear in Section 6 for immediate use.

What a construction method statement is and when you need one
Core components every professional method statement must include
How to convert a generic template into a site-specific method statement
Six annotated method-statement examples ready to adapt
Reusable template layout and sign-off checklist
U.S. regulatory context and why method statements carry legal weight
Why principal contractors reject method statements and how to prevent it
Key Takeaways
A consultant’s note on briefing and approval workflow
Authoritative references and resources

What a construction method statement is and when you need one

A method statement is the operational half of a Risk Assessment and Method Statement (RAMS) package. It describes the sequence of operations, the resources required, and the specific controls that will be applied at each step. The risk assessment identifies what could go wrong; the method statement explains exactly how the work will be executed safely.

In U.S. construction practice, method statements are not mandated by a single OSHA regulation, but they directly support compliance with multiple OSHA construction standards: Subpart Q (concrete and masonry), Subpart R (steel erection), Subpart P (excavations), Subpart L (scaffolds), and Subpart N (cranes and derricks). Principal contractors routinely require them before high-risk tasks begin, and permit-to-work systems often reference them as a precondition for authorization.

The document is required whenever the work involves work at height, confined-space entry, heavy lifts, hot works, or electrical isolation. It is also triggered by pre-commencement approval conditions, permit requirements, and risk assessment in construction findings that identify residual risks needing a controlled sequence.

Core components every professional method statement must include

A professional method statement must contain all of the following fields to pass principal-contractor review:

Task title and document reference number
Scope of work and explicit exclusions
Site address, access routes, and physical boundaries
Numbered sequence of operations (from mobilization to demobilization)
Personnel roles and responsibilities, including emergency roles
Plant and equipment list with last inspection dates and certificate references
Materials and substances, including hazard data sheet references
Hazard-control pairs mapped to each step in the sequence
PPE requirements with applicable standards (e.g., ANSI Z89.1 for hard hats)
Permits required and interface points with other trades
Competency and certification requirements for named operatives
Emergency and rescue plan with nearest emergency facility address
Sign-off block with version number, author, approver, and briefing record

Mapped step example: Step 3 — Install scaffold lift 1. Pre-inspect base plates and sole boards before placement. Hazards: foundation settlement, struck-by falling components. Controls: foundation survey completed, exclusion zone marked at appropriate radius, edge protection installed before operatives advance. PPE: hard hat (ANSI Z89.1), safety boots (ASTM F2413), hi-vis vest.

Pro Tip: Include a re-brief record field in the sign-off block. When site conditions change and the document is revised, the re-brief entry proves the updated version was communicated to operatives before work resumed — a critical audit trail in any enforcement review.

How to convert a generic template into a site-specific method statement

Start with the site facts before writing a single step. Record the full site address, GPS coordinates, access route restrictions, adjacent assets (utilities, public footpaths, occupied buildings), and the physical limits of the work area. The sequence should then follow the actual order of operations from arrival on site to final demobilization.

The difference between a rejected and an accepted document often comes down to one line. Compare these two scope descriptions:

Vague (rejected): “Scaffolding works to building facade.”
Site-specific (accepted): “Erect a 3-lift independent scaffold to the north elevation of Building A, working height specified; public footpath protection with minimum clearance specified; scaffold to remain in place pending facade repair.”

The accepted version gives a reviewer everything needed to verify the scope, check the lift plan, and confirm the public-protection measures. Apply the same specificity to every step.

Checklist for site-specificity before submission:

Measurable dimensions and working heights stated in every relevant step
Exact plant IDs and current inspection dates confirmed
Named competent operatives or required certifications listed
Exclusion zones defined with physical markers specified
Interface points with other trades identified by trade and location
Rescue arrangements tied to the exact hazard and nearest emergency facility

Pro Tip: Fold controls into the step where the hazard occurs. Cross-reference the originating risk assessment line number in each step so a reviewer can trace the control back to its source without searching a separate document.

Six annotated method-statement examples ready to adapt

The examples below follow the worked-example approach of writing from arrival to demobilization and mapping controls into each step.

1. Scaffold erection

Scope: Erect a temporary scaffold structure to [Elevation/Location], [X] lifts, [Y] m working height.

Mobilize — deliver components, check delivery manifest, inspect for damage.
Survey foundation — confirm load-bearing capacity; install sole boards and base plates. Hazard: settlement. Control: geotechnical confirmation on file.
Erect standards and ledgers, lift 1. Hazard: falls, struck-by. Controls: exclusion zone [radius], edge protection before advance. PPE: hard hat, harness (ANSI Z359.1), safety boots.
Install working platform and toe boards. Hazard: falling objects. Control: toe boards secured, debris netting installed.
Inspect each lift before operatives advance. Competence: OSHA 29 CFR 1926 Subpart L competent person.
Tag scaffold as approved or out-of-service. Record inspection in site register.

Replace: [Elevation/Location], lift count, working height, exclusion zone radius, foundation survey reference.

2. Excavation and trenching

Scope: Excavate [trench dimensions] at [location] for [purpose].

Conduct desktop utility study; obtain utility locate records.
Mark dig zone; photograph pre-dig condition.
CAT scan and signal generator sweep before any ground break. Hazard: utility strike. Control: hand-dig within 500 mm of marked services.
Excavate with [plant ID]; competent operator only. Hazard: trench collapse. Control: shoring or benching as required by OSHA 29 CFR 1926 Subpart P.
Maintain exclusion zone from trench edge; barrier and signage in place.
Monitor atmosphere if depth exceeds 4 ft (confined-space protocol if applicable).
Backfill, compact, and reinstate surface. Record completion.

Replace: trench dimensions, location, plant ID, exclusion zone distance, utility locate reference number.

3. Crane lift and heavy lifting

Scope: Lift [load description, weight] using [crane ID] at [location].

Pre-lift meeting: review lift plan, confirm crane capacity, ground conditions, and exclusion zone.
Position crane per lift plan; ground mats installed. Hazard: overturning. Control: outrigger pads on rated bearing surface.
Rig load using certified slings [cert ref]; appointed rigger only. Hazard: dropped load. Control: tag lines attached, exclusion zone [radius] enforced.
Trial lift to a small height; hold and inspect. Proceed only on signal from appointed person.
Land load on prepared bearing surface; de-rig under appointed person supervision.
Record lift completion in crane log.

Replace: load description and weight, crane ID and certificate reference, lift plan document number, exclusion zone radius, nearest emergency facility.

4. Concrete pour and formwork

Scope: Pour [volume] m³ of [mix specification] concrete to [element] at [location].

Inspect formwork and falsework; confirm design approval and propping schedule. Hazard: formwork collapse. Control: temporary works design on file, independent check completed.
Position concrete pump [plant ID]; set up exclusion zone around pump boom radius.
Commence pour in planned sequence [sequence ref]; do not exceed pour rate of [X] m³/hr. Hazard: lateral pressure. Control: pour rate monitored, formwork deflection checks every 30 min.
Vibrate concrete systematically; avoid contact with reinforcement. PPE: gloves (chemical-resistant), safety boots, eye protection.
Strike formwork only after [curing period] confirmed by [competent person].
Clean pump and equipment; dispose of washout water per site waste plan.

Replace: volume, mix specification, element, pour rate, curing period, pump plant ID, sequence reference.

5. Hot works and welding

Scope: [Welding/cutting/grinding] at [location] for [purpose].

Obtain hot-works permit [permit ID] before start; confirm fire watch arrangements.
Clear combustibles within [radius] m of work area; wet down surfaces where required.
Position fire extinguisher [type, rating] within 3 m of work point.
Conduct work; fire watch operative present throughout. Hazard: ignition of adjacent materials. Control: permit conditions enforced, extinguisher accessible.
On completion, fire watch continues for a recommended post-work duration. Hazard: smoldering. Control: thermal imaging check if available.
Close permit; record fire watch completion time and operative name.

Replace: permit ID, location, combustible clearance radius, extinguisher type and rating, fire watch operative name.

6. Electrical isolation and lockout

Scope: Isolate [circuit/panel ID] to permit [downstream work] at [location].

Identify isolation point from approved single-line diagram [drawing ref].
Notify affected parties; confirm no live work in progress downstream.
De-energize circuit; apply lockout device and personal lock. Hazard: inadvertent re-energization. Control: multi-lock hasp if multiple trades affected.
Test for absence of voltage using calibrated tester [tester ID, cal date]. Verify at all phases.
Apply “Do Not Operate” tags; record in isolation register.
On completion of downstream work, remove locks in reverse order; restore supply only after all personnel clear.

Replace: circuit/panel ID, drawing reference, tester ID and calibration date, downstream work description.

Reusable template layout and sign-off checklist

A complete method-statement template should follow this header structure, then expand into the body sections below.

Header block:

Body sections (in order): Scope and exclusions; Responsibilities (role, name, contact); Sequence of operations (numbered steps with embedded hazard-control pairs); Plant and equipment register (see table below); Materials and substances; PPE required with standards; Permits and hold points; Emergency and rescue plan; Training and competence table; Sign-off and briefing record.

Plant and equipment register:

Plant ID	Item	Last inspection date	Certificate reference	Competence required
[ID]	[Description]	[Date]	[Ref]	[Certification]

Sign-off block example:

Field	Entry
Re-brief trigger events	Scope change, new hazard identified, personnel change

Pre-submission checklist (minimum for principal-contractor acceptance):

Site-specific scope with measurable dimensions confirmed
Numbered sequence present from mobilization to demobilization
Controls embedded in each step, not listed only at the end
Equipment inspection certificates attached or referenced
Emergency and rescue plan includes nearest emergency facility address
Named competent person confirmed for each high-risk activity
Version number, date, and approver signature present
Briefing record field completed or scheduled

U.S. regulatory context and why method statements carry legal weight

Method statements are litigable documents. Ambiguous language or missing controls can be cited in OSHA enforcement actions and civil litigation as evidence that a safe system of work was not established. The relevant OSHA construction standards to reference when drafting include:

29 CFR 1926 Subpart P — Excavations: shoring, sloping, and competent-person requirements
29 CFR 1926 Subpart L — Scaffolds: erection, inspection, and competent-person designation
29 CFR 1926 Subpart N — Cranes and derricks: lift plans, operator certification, and ground conditions
29 CFR 1926 Subpart Q — Concrete and masonry: formwork design, shoring removal, and pour controls
29 CFR 1926 Subpart R — Steel erection: decking, fall protection, and connection sequences
29 CFR 1926 Subpart S — Underground construction and confined space
29 CFR 1910.147 — Control of hazardous energy (lockout/tagout), applicable to electrical isolation

Method statements do not replace required permits, operator certifications, or competent-person designations. They demonstrate that the employer planned the work and communicated the controls before exposure occurred. For construction approval workflows, traceable cross-references between the method statement and the originating risk assessment are the single most effective way to shorten regulatory review cycles.

This article provides general technical guidance and does not constitute legal or regulatory advice. Confirm current OSHA requirements with a qualified safety professional or the relevant OSHA area office for your specific project.

Why principal contractors reject method statements and how to prevent it

The most common rejection reason is vague language — a statement written so generally that an operative unfamiliar with the task could not follow it safely. Catchall phrases like “work safely at all times” or “follow site rules” carry no operational value and will draw a rejection comment from any competent reviewer.

Common rejection reasons:

Scope is generic (activity name only, no dimensions or location)
Controls listed only in a separate hazard table, not embedded in the sequence
Equipment inspection dates missing or certificates not referenced
No named competent person for high-risk activities
Site-specific dimensions, heights, or exclusion zones absent
Emergency plan does not name the nearest emergency facility
Permit references missing or permit not yet obtained

Before/after example:

Rejected: “Excavate trench. Shore as required. PPE to be worn.”
Accepted: “Excavate trench 1.2 m wide × 2.4 m deep at Grid Ref [X] using [Plant ID]. Install hydraulic shoring per OSHA 29 CFR 1926 Subpart P before operatives enter. Exclusion zone 2 m from trench edge marked with barrier tape. PPE: hard hat, safety boots, hi-vis vest.”

Pro Tip: When responding to reviewer comments, log each change with a revision note in the document control block, highlight the altered steps in the resubmitted version, and attach supporting evidence (inspection certificates, competence cards, photographs) rather than rewriting without a traceable record. Reviewers accept revisions faster when the evidence accompanies the change.

Key Takeaways

A defensible, OSHA-aligned method statement embeds controls directly into each operational step, names a competent person for every high-risk activity, and carries a signed briefing record before work begins.

Point	Details
Six core example types	Scaffold erection, excavation, crane lift, concrete pour, hot works, and electrical isolation cover the highest-risk activities.
Controls belong in the sequence	Embed hazard-control pairs at the step where exposure occurs, not only in a separate table at the end.
Site-specificity prevents rejection	Replace all generic labels with measurable dimensions, plant IDs, inspection dates, and named competent persons.
Sign-off block is auditable evidence	A briefing record with attendees, date, and re-brief triggers proves the document was communicated before work started.
Method statements support OSHA compliance	They do not replace required permits or certifications but demonstrate a planned, communicated safe system of work.

A consultant’s note on briefing and approval workflow

The most reliable drafting workflow starts from the completed risk assessment, not a blank template. Once the hazards and controls are established, the method statement sequence writes itself: each step is the operational instruction that activates the control identified in the assessment. Pre-populate the plant and equipment register with certificate references before circulating the draft, because missing cert data is the single most common cause of a second review cycle. Circulate the draft to the design team and other trades for interface checks before submission to the principal contractor, since sequencing conflicts between trades are far easier to resolve on paper than on site.

Brief the document on site before the task starts, record attendees and the briefing date, and keep the signed record with the site file. When scope or site conditions change, revise the document, update the version block, and re-brief. Storing versioned copies in a named folder with the revision date in the file name takes less than two minutes and provides a complete audit trail if the project is ever subject to enforcement review. Treating the method statement as a living safety communication tool rather than a one-time submission document is what separates a defensible project record from a liability.

Authoritative references and resources

The following sources informed the examples, template structure, and compliance guidance in this guide:

SafetyStack: How to Write a Method Statement — Practitioner-focused writing workflow and guidance on embedding controls in sequence steps; the source for the litigation-risk and defensibility notes.
Paperless Construction: Method Statement Examples — Real-world construction examples including small-scale excavation and temporary works scenarios; useful for adapting the annotated examples above.
Paperless Construction: How to Write a Professional Method Statement — Template layout, sign-off field guidance, and the practitioner insight that method statements are communication tools, not compliance paperwork.
ProjectManager: How to Write a Method Statement — Worked examples with role breakdowns and step-by-step procedure formats.
OSHA 29 CFR 1926 — The primary U.S. regulatory reference for construction safety standards; consult the relevant subpart for each activity type.
Oscar On Site: NVQ Diploma in Occupational Work Supervision — Supervisory competence qualification relevant for named competent persons on method statements requiring a designated site supervisor.

For engineering and architectural consultancy clients preparing submission-ready documentation for U.S. or cross-jurisdiction projects, Aectechnicalsg’s engineering consultancy services provide technical advisory support across structural, geotechnical, and M&E disciplines, including authority submission management and compliance documentation.