Method statement approval is the formal acceptance, usually by the appointed engineer and where a project falls under public authority jurisdiction, by that authority, of a task-specific method statement and its accompanying risk assessment. The immediate next step for any contractor or project manager is to prepare a statement specific to the exact task at hand, attach a proper risk assessment, and route it for the appointed professional engineer’s endorsement before work begins.
TL;DR:
- Most approval rejections result from generic language, unannotated drawings, or missing certificates, which can be addressed by task-specific detail and proper documentation.
- Successful submissions include detailed site plans, step-by-step sequences with hazards and controls, and precise equipment and personnel information, not vague descriptions.
- Deviating from an endorsed method requires formal re-approval, and working outside approved procedures can lead to stop-work orders and legal penalties.
- Engaging specialized consultancy early ensures thorough review, proper coordination with authorities, and higher quality submissions that are more likely to pass on first review.
- Maintaining disciplined internal checks, current photos, and clear reviewer contacts reduces review cycles and streamlines approval processes.
Table of Contents
- What is a method statement and when do you need one?
- What reviewers expect to see in your submission
- How the submission and review process works from start to finish
- What PE endorsement covers and what changing an approved method requires
- Why method statements get rejected and how to fix it fast
- How a statutory-approval consultancy shortens the path to acceptance
- What experience on real projects teaches about approval
- Get your method statements endorsed without the resubmission cycle
- Sources
- FAQ
What is a method statement and when do you need one?
A method statement is a formal document describing how a specific construction task will be carried out safely, including the sequence of operations, the plant and labor involved, and the controls applied to each identified hazard. It differs from a standard operating procedure in scope: an SOP describes a repeatable, generic process used across many jobs, while a method statement is written for one defined activity on one specific site, with the particular conditions, equipment, and personnel named.
This distinction matters to reviewers. A method statement that reads like a generic SOP, without site-specific detail, is one of the most common reasons submissions come back for revision.
Certain activities almost always require an approved method statement before work starts:
- Lifting operations involving cranes, hoists, or mobile elevating platforms.
- Demolition or structural alteration of existing elements.
- Temporary works, including shoring, formwork, and scaffolding.
- Façade or hanging works performed at height.
- Excavation near existing structures, utilities, or slopes.
- Works carried out on public streets, including any activity requiring traffic control.
The requirement is not just good practice. Under the LTA GS Appendix A guidance.pdf), the contractor must identify every safety-critical activity and prepare a method statement for each one, and that statement must be accepted by the Engineer before the activity commences, with a conforming risk assessment attached. Many construction contracts mirror this clause directly, making method statement acceptance a contractual precondition rather than a discretionary safety step.
What reviewers expect to see in your submission
A method statement that passes on first review is built around specificity, not general assurance. Reviewers are checking whether the document proves the task has been thought through in detail, not whether it states the right intentions.
The following items are what a competent reviewer looks for, in the order they typically read them:
- Site location and annotated drawings. Include a plan or schematic marking the exact work zone, access routes, and any nearby hazards such as live services or public paths.
- Step-by-step sequence of operations. Each step should name the task, identify its specific risk, and state the control applied to that risk, rather than listing hazards and controls in separate, disconnected sections.
- Plant and equipment schedule. List every machine or tool by model or type, with current certificates attached, including lifting plans and maintenance checks for mechanical handling equipment.
- Named personnel and supervision. State who is responsible for each stage of the task and attach evidence of their competence, such as training records or trade certificates.
- Task-specific PPE and emergency procedures. Specify the exact PPE required for each step and describe the rescue or emergency response relevant to that particular activity, not a generic site evacuation plan.
- Supporting evidence. Attach photos of the actual work area, manufacturer documentation for key equipment, relevant test certificates, and diagrams showing how controls will be physically implemented.
The gap between a rejected and an accepted submission is usually specificity, not effort. According to Aman Engineering’s review of common rejection causes, generic phrasing is the single most frequent reason reviewers send a method statement back, and task-specific controls with exact PPE models, annotated diagrams, and photos measurably improve first-pass acceptance.
The difference shows up clearly in phrasing. “Workers will wear appropriate PPE” tells a reviewer nothing about whether the right protection has been considered for that task. “Workers performing overhead grinding will wear face shields rated to the relevant impact standard, paired with the safety goggles already specified for eye protection” tells the reviewer the risk was actually assessed. The same logic applies to equipment: “a suitable crane will be used” invites a query, while naming the crane model, its rated capacity, and the working radius does not.
Pro Tip: Write each step of your sequence of operations as a single sentence naming the action, the hazard it creates, and the specific control, so a reviewer can check all three in one read.
How the submission and review process works from start to finish
Getting a method statement through approval is a workflow with predictable stages, and skipping the internal ones is what usually causes external delays.
- Internal quality check first. Before anything goes to the appointed engineer, a site supervisor or safety officer should confirm the sequence matches actual site conditions, that all named equipment is confirmed available, and that attachments (certificates, drawings, photos) are current and legible.
- Professional engineer review. The appointed PE reviews the method against the design intent and the relevant code, checking whether the proposed controls are adequate for the hazards identified and whether the sequence is structurally and technically sound. Endorsement is recorded formally, typically as a signed or stamped acceptance on the document itself.
- Authority or client review where applicable. For works on public streets, the LTA Code of Practice for Works on Public Streets requires that the method statement be endorsed by the appointed PE and accompanied by a contingency plan, a pre-condition survey, a construction schedule, and a traffic control plan where relevant. Missing one of these accompanying items is a common cause of a multi-agency hold, even when the method statement itself is technically sound.
- Comment tracking and resubmission. Reviewer comments should be logged against each specific point raised, with a clear owner and closure date, rather than answered as a single narrative response.
- Reduce cycles by front-loading detail. Submissions that already include contingency and traffic control documentation, rather than promising to provide them later, generally clear review faster.
Turnaround windows vary by contract and by the complexity of the activity, so it is prudent to allow enough time for submission and a full review cycle before the planned start date.
What PE endorsement covers and what changing an approved method requires
PE endorsement means the appointed engineer has formally accepted that the proposed method and its controls are adequate for the task as described, not that the engineer takes on ongoing supervisory responsibility for how the work is actually carried out on site. That distinction matters contractually: the contractor remains responsible for executing the work exactly as the endorsed method describes.
- Endorsement is task-specific. It applies to the sequence, equipment, and controls exactly as submitted, not to the activity in general.
- Deviating from an approved method requires formal re-approval. Under guidance reflected in the LTA safety, health and environment appendix, a contractor intending to change an approved method must seek further approval from the Engineer before carrying out the changed method.
- Safety-critical activities almost always need explicit PE sign-off, including lifting operations, demolition, temporary works, and monitoring schemes tied to structural movement.
- Non-compliance carries real consequences. Working outside an approved method can trigger a stop-work instruction, enforcement action, or rejection of the associated inspection or completion certificate.
Treating the endorsed document as fixed, rather than as a draft to be adjusted informally on site, is the single habit that prevents most compliance disputes later in a project.
Why method statements get rejected and how to fix it fast
Most rejections trace back to a small set of predictable gaps, and each one has a direct fix.
- Generic language instead of task-specific detail. Replace phrases like “suitable equipment” or “as required” with the exact model, capacity, or standard that applies to this task.
- Missing or unannotated drawings. Attach a marked-up plan showing the work zone, access, and any hazard nearby, not just a general site layout.
- Absent equipment certificates. Confirm every crane, hoist, or piece of mechanical handling equipment has a current, attached certificate before submission.
- No named, competent personnel. State who supervises each stage and attach their relevant competence record.
- Weak contingency or rescue procedures. Write the rescue plan for the specific hazard at hand, such as a fall from height on this structure, rather than a generic emergency number.
- Slow response to reviewer comments. Assign a single point of contact to close out comments within a set number of days rather than batching them for the next revision cycle.
Pro Tip: Keep a short library of pre-approved, templated method statements for your most frequent activities and update only the site-specific details each time, which cuts most of the rework a fresh draft usually generates.
For a fuller walkthrough of fixing a rejected submission, see how to fix a failed submission for building approvals.
How a statutory-approval consultancy shortens the path to acceptance
Getting a method statement endorsed and accepted the first time depends on having the right technical sign-off and the right supporting evidence assembled before submission, and this is where a dedicated consultancy adds direct value rather than general reassurance.
- PE endorsement. A multidisciplinary professional engineer team reviews the method against the applicable code and provides the formal endorsement the appointed Engineer or authority requires.
- Statutory coordination. Submissions that touch multiple agencies, such as authority approvals spanning structural, façade, and fire safety requirements, are coordinated through a single point rather than chased separately.
- Submission quality assurance. Draft method statements are checked against reviewer expectations, including the annotated drawings, certificates, and named personnel that reviewers look for first.
- BIM and drawn evidence. 3D BIM and shop drawing production produce the annotated diagrams and sequence visuals that support a method statement’s technical claims.
- Liaison with test and certification bodies. Coordinating with accredited labs for equipment and material certification keeps supporting documents current at submission time.
Engaging consultancy support early, before a first submission goes in, can help avoid the remedial cycle of resubmission after rejection, which is a more expensive and time-consuming way to reach the same endorsement.
What experience on real projects teaches about approval
The method statements that clear review fastest are the ones built around a short, disciplined habit: a pre-submission checklist run by someone other than the person who wrote the document, current photos of the actual work area rather than stock images, and a named reviewer contact for every comment raised. Teams that skip this internal step tend to discover gaps only after the appointed engineer flags them, which costs a full review cycle.
The other lesson worth repeating is that an approved method statement is not a suggestion. Once endorsed, it becomes the standard the work is measured against, and any deviation, even one that seems minor on site, needs to go back through formal re-approval before it is carried out. Treating approval as the finish line, rather than as the baseline for how the task must actually run, is where most avoidable disputes start.
— Aman
Get your method statements endorsed without the resubmission cycle
Method statement approval moves faster when the PE endorsement, the supporting drawings, and the authority coordination are handled by one team instead of chased separately across consultants and agencies. Professional engineering consultancies can provide PE endorsements, statutory submission coordination, and document quality checks that map directly onto what reviewers expect to see, supported by BIM-generated drawings and liaison with authorities on submissions spanning structural, façade, and fire safety requirements.
If you have a method statement due for submission or one that has already come back with comments, our authority approvals team can review it against the applicable code before it goes back for endorsement.
FAQ
What is a method statement example?
A method statement example for a lifting operation would name the crane model and rated capacity, the exact lifting points on the load, the signal person’s competence record, and the exclusion zone marked on an annotated site drawing. The document ties each step of the lift to a specific control rather than listing general safety precautions separately.
What is the purpose of a method statement?
A method statement’s purpose is to prove, before work starts, that a specific task has been planned with its hazards identified and matched to concrete controls. It gives the appointed engineer or authority a basis to formally accept, under guidance such as the LTA GS Appendix A, that the proposed approach is safe to proceed.
When should a method statement be done?
A method statement should be prepared and submitted for acceptance before a safety-critical activity begins, never after work has started. Activities that typically trigger this requirement include lifting, demolition, temporary works, and any works on public streets that involve traffic control.
What is the difference between SOP and method statement?
A standard operating procedure describes a generic, repeatable process used across many jobs and sites, while a method statement is written for one specific task on one specific site with its actual conditions, equipment, and personnel named. Reviewers frequently reject method statements that read like generic SOPs because they lack the site-specific detail an approval decision depends on.