How to Write a Method Statement for a Small Build, With AI Help

Write the sequence of works first, step by step, then attach the plant, hazards and controls to each step. AI can draft the layout and wording from your notes, but a competent person who knows the job must check it, sign it and brief the crew. The client or principal contractor often approves it before work starts.

A method statement is not a risk assessment, and it is not an electrician's RAMS. It says how this job will be done, in order, with this plant and these people. The weak ones are generic: they could describe any job on any site, and an AI draft with no site facts will be generic by default. Everything below is about feeding the draft real facts and then catching what it still gets wrong.

Follow me on Instagram@sagnikteaches

What a method statement is, and what it is not

Designing Buildings' page on method statements describes them as a way of controlling specific health and safety risks, and notes that a risk assessment and a method statement together are sometimes called RAMS. Its list of possible contents runs from the organisation in control of the activity and the individual responsible for it, through the plant and a step-by-step description of the work, to protective measures, emergency procedures, temporary works designs and a procedure for changing the method. It says a competent person familiar with the process should write it, that it should be peer-reviewed before use, and that it may need to be agreed between the client, principal contractor and contractor.

Connect on LinkedInSagnik Bhattacharya

Two cautions. First, whether a written method statement is a legal requirement depends on the place and on the task. Some high-risk tasks need a written plan, and many clients, principal contractors and insurers ask for one anyway, so check your regulator's guidance and your contract. Second, this tutorial is not electrical RAMS. Those centre on isolation, proving dead, testing and the rules for live work, and can AI write RAMS for electrical work, and who must sign it off covers them. A builder's statement centres on the order of building operations, structure, temporary works, access, plant, neighbours and waste. On a job that includes both, the electrician's isolation steps belong in the electrician's RAMS and are referenced, not copied, in yours.

Subscribe on YouTube@sagnikteaches

What goes in, and where AI usually slips

Lay the document out in the order the work happens, so a supervisor can read it top to bottom on the day. Each section below is one heading in the finished statement, and the right-hand column is where an unprompted AI draft tends to go wrong.

A worked example: taking out a load-bearing wall in an occupied house

This is the classic small-build job where the sequence matters. The illustration: a 4.2 m opening between a kitchen and a dining room on the ground floor of a two-storey house, a steel beam designed by the structural engineer, a crew of three and five working days, with the family living upstairs. The numbers that carry weight (beam size, bearings, support positions) come from the engineer's design, not from this tutorial and not from an AI. Here is the sequence a competent person might write, with the hold points marked. A hold point is a step where work stops until a named person has checked and signed.

1. Pre-start checks. Confirm the current revision of the engineer's drawing. Check the delivered beam against the design schedule. Review the asbestos information for the house and the services survey for the wall. Stop and report if anything unexpected is found.
2. Isolate and divert services. The electrician and plumber locate, isolate and divert cables and pipes in the wall. Nothing is cut until they have confirmed the services are dead or drained.
3. Protect. Floor and stair protection, dust barrier across the doorway to the rest of the house, adjacent finishes covered, working hours agreed with the household.
4. Install the temporary supports to the engineer's temporary works design. Hold point 1: the supports are checked by the person named in the design before anyone cuts into the wall.
5. Cut the bearing pockets at the positions on the design and check the bearing lengths against the drawing before the beam is lifted.
6. Install the beam on its bearings using the lifting method set out in the manual handling assessment, and pack it as the design requires.
7. Allow the packing to gain strength for the time the engineer states. Hold point 2: no load is transferred and no wall is removed until the engineer's condition is met.
8. Remove the wall in stages from the top down, with dust suppression or on-tool extraction, and clear debris by the agreed route.
9. Remove the temporary supports only when told to by the person who checked them. Hold point 3.
10. Make good and finish. Fire protection to the steel as specified, close up, clean down, remove protection and record the handover.

Notice what is missing: every number that matters structurally. The statement says "per the engineer's design", names the checker and stops work at the hold points. That is the right place for an AI draft to stop as well, and the prompts below force it to.

Next comes the hazards-and-controls table, tied to the steps above. This is the part reviewers read hardest, because a control with no owner is a wish.

Gathering the facts the AI cannot guess

An assistant writes a generic statement because you gave it a generic request. The fix is a fact sheet that takes 20 minutes to fill in and makes every later prompt specific. Keep the client and the site address out of it: the assistant needs the building, the structure, the people and the constraints, not the name on the door. A completed example for the job above:

JOB FACT SHEET (redacted: no client name, no address)
Task: remove a load-bearing wall between kitchen and dining room; install a steel beam
Building: two-storey house; ground-floor opening about 4.2 m; occupied, family upstairs
Design: structural engineer's drawing [ref, revision]; temporary works design [ref]; person who checks the supports: [role]
Services in the wall: [electrics / gas / water / unknown]
Asbestos information: [survey available? result?]
Crew: site supervisor [role]; two operatives [trades]; electrician and plumber attend for isolation
Plant and equipment: props and needles per the design; dust-extracting cutting tools; lifting aids [list]
Programme: five working days; working hours [hours]
Access and constraints: front door only; no waste container on the drive; party wall with the neighbouring house
Welfare and waste: [toilet, drinking water, waste route]
Emergency: first aider [role]; fire extinguisher [location]; route for emergency services [described generally]

Fill the square brackets from your own paperwork, not from memory. If a bracket stays empty, that is a gap in your planning, and the assistant has just found it for you. Settle what may be pasted first: the AI policy tutorial for construction companies covers photos, drawings and subcontractor details.

Four prompts that produce a usable draft

One prompt that asks for the whole statement produces a smooth, plausible and unchecked document. Four narrower prompts let you check each layer before the next one depends on it.

Prompt one: the sequence

Using the job fact sheet below, draft the sequence of works for a method statement as a numbered list.
Rules: put the steps in the order they must happen. Mark hold points where work must stop until a named role has checked and signed. Do not state any dimension, load, prop spacing, beam size, curing time or product; where one is needed, write "per engineer's design [ref]". Do not include the detail of other trades' work beyond "isolate and confirm". If a fact is missing, write [to confirm].
[paste the fact sheet]

A realistic first draft (illustrative) is neat, and it breaks the rules in three places. It writes "props at 1.2 m centres" in the support step, which is a number nobody gave it. It writes "remove props after 24 hours" in the last steps, another invented figure that is the engineer's call. And it puts "remove the wall" before "allow the packing to gain strength", so the structure would be unloaded before the beam was ready to carry anything. The first two are deleted and replaced with "per engineer's design". The third is the dangerous one, and the next technique catches it.

Read the sequence backwards. Start from the last step and, for each, ask what must already be true. The wall cannot come out until the beam carries load; the beam cannot carry load until the packing has gained strength; the packing cannot be loaded until it is installed. The moment a step depends on something that appears later, the order is wrong. It takes two minutes and it finds mistakes that a quick read-through glides past.

Prompt two: hazards and controls, step by step

For each numbered step in the sequence below, list the hazards that arise in that step only, the control for each, and the role that checks it. Table columns: step number, hazard, control, who checks.
Rules: no generic lists such as "slips, trips and falls" unless the step creates that hazard. Name each control concretely: what is done, with what. Do not claim compliance with any regulation or standard.
[paste the corrected sequence]
[paste the fact sheet]

Typical faults: "wear appropriate PPE" appears as the control in six rows, which is not a control because it says nothing about what protection against what. Replace it, for example, with "respiratory protection of the class the risk assessment specifies" for the dust step. The draft also forgets the household upstairs, even though the fact sheet says so in one line. Add the occupants row yourself and check the rest, because an assistant overlooks facts it was given as readily as it invents ones it was not.

Prompt three: make it argue with itself

Act as a site safety reviewer reading this method statement for the first time. List what is missing, unclear or contradictory, in order of seriousness. Do not rewrite it. Do not say it is acceptable or compliant.
[paste the full draft]

This is the most useful of the four, because reviewing is easier for an assistant than writing. A typical result (illustrative): there is no instruction for what to do on finding an unexpected service; no route for the household to leave in an emergency; and hold point 3 does not say who releases the supports. All three are real gaps, and all three take a minute to fix. The last line of the prompt matters. Left to itself, an assistant will often end a review with "overall this looks comprehensive", which is the one sentence you must not let anyone rely on.

Prompt four: the one-page crew briefing

Turn this method statement into a one-page briefing for the crew. Plain English, ten bullet points at most, in the order the work happens, with the hold points in bold. Include who to call and when to stop work. Add no new rules.
[paste the checked method statement]

The briefing is what the crew will actually read, so it matters as much as the full document. Read it aloud to them on the first morning, let them ask questions, and have each person sign the briefing record. A statement the crew has never heard of is paperwork. For short daily talks on the same job, can AI write toolbox talks, and what a competent person must check covers the format.

What AI gets wrong in method statements

Beyond the three faults above, these are the failures worth checking for every time. Each is a common way for an assistant's draft to go wrong.

• Invented numbers. Prop spacings, beam sizes, curing times, exclusion distances. Every figure must trace to a design, a data sheet or your risk assessment. If it traces nowhere, delete it.
• Wrong order. The backwards read catches it.
• Generic hazards. "Slips, trips and falls" under every step. A hazard belongs in a row only if that step creates it.
• Steps from another trade. Electrical isolation procedures or hot-work rules copied in from RAMS or a template. Reference them; do not reproduce them.
• Compliance claims. "All work will comply with relevant regulations and standards." The assistant has not checked anything. Delete it, and say instead what you will do.
• Carry-over. The previous job's address, dates or names surviving from earlier in a long chat. Search the finished file for every proper noun, and start each statement in a fresh chat.
• Soft verbs at hold points. "Supports should be checked" is a suggestion. "Work stops until [role] has checked and signed the supports" is a hold point.
• Unnamed competence. "Only competent operatives will carry out the work." Name the supervisor and say what each person is trained for.

The builder's safe-use routine for building code questions applies the same suspicion to rules and standards: ask the assistant where to look, then read the source yourself. For the hazard-analysis side of the same job, a job hazard analysis template drafted with AI is a useful companion, and the broader risk-assessment routine is in how to draft risk assessments with AI and what a human must check.

Who approves it, who signs it, who briefs the crew

Four jobs, and in a firm big enough they belong to different people. AI is none of them.

In a firm of three, the author and checker may be two of the same three people, but nobody checks their own work. Who has to approve a statement depends on your contract and on the rules where you work, so ask the client or principal contractor in writing at tender stage whether they need to approve it, in what format, and how many days they need. A late submission can hold up a start date as effectively as a late delivery.

Record all of it on the statement itself. A sign-off block you can paste, with the AI line included so nobody wonders later:

SIGN-OFF
Prepared by: [name, role]    Date: [date]    Version: 1.0
Checked by (competent person): [name, role]    Date: [date]
Temporary works design checked by: [role, per design reference]
Approved by (client or principal contractor): [name, organisation]    Date: [date]
Drafting aids: AI assistant used for layout and wording; all content checked against site facts by the checker.
Crew briefing: briefed on [date] by [name]; signatures attached.

If the method changes on site, work stops, the supervisor tells the checker, the statement is revised and reissued with a new version number, and the crew is briefed again. Write that rule into section 11 of every statement, and mean it.

After the job: keep it, learn from it, reuse only the structure

When the job ends, the supervisor adds two lines to the file: what the statement missed, and what the crew changed on site. Those two lines are the best material for the next fact sheet, and they feed straight into near-miss logging, which is worth keeping in one place. Keep the statement with the job records for as long as your insurer and contract require, which is a question for them, not for this tutorial.

Reuse the structure of a good statement, never its content. Before a copied statement goes near a new job, change every item on this list:

• Address, client and dates
• Names and roles, including the competent person and the first aider
• Plant and equipment lists
• Services, asbestos information and the survey references
• Neighbours, access and working hours
• Every design, drawing and temporary works reference
• Emergency arrangements

Then have the checker read it as if it were new. A reused statement that still names last job's engineer is the commonest embarrassment in this field, and the crew will trust it exactly as much as a correct one.

A realistic time budget

These are planning figures, not measurements, for the five-day wall removal above. Filling in the fact sheet takes about 20 minutes. Running the first three prompts and fixing what they get wrong takes about 40. The checker's read against the site takes 20, the crew briefing sheet 10, and the briefing itself 15. That adds up to about 105 minutes, under two hours, against whatever your current process costs you. Time your first job honestly. If the checking takes much less time than the drafting used to, ask whether the checking is real.

The temptation with a fast draft is to skip the slow part, and the slow part is the entire value of the document. Start with your next small job: fill in the fact sheet, run the sequence prompt, read it backwards, and see how many of the steps you would have written yourself.

Questions builders ask about method statements

Is a method statement the same as RAMS?

RAMS combines a risk assessment and a method statement, often in one document. The risk assessment lists hazards and how serious they are; the method statement sets out the order of work, the plant and the controls. Electrical RAMS centre on isolation and testing, while a builder's method statement centres on structure, temporary works, access and protection.

Does every small job need a written method statement?

Not always. Whether the law requires one depends on the place and the task, and some high-risk tasks need a written plan. Clients, principal contractors and insurers often ask for one regardless. Check your regulator's guidance and your contract, and write one for any job where a wrong sequence could injure someone.

Can I reuse last year's method statement for a similar job?

Reuse the structure, never the content. Change the address, dates, names, plant, services, neighbours and every design reference, then have the checker read it as if it were new. A copied statement that still describes the last site is worse than none, because the crew trusts it.

Can AI sign or approve a method statement?

No. A competent person at your firm signs it after checking it against the real site, and the client or principal contractor approves it where your contract requires. AI only drafts. Keep a record of who checked it and when, and brief the crew before work starts.

Further reads

• Roofing RAMS Template: AI Drafts, a Competent Person Signs It Off — A roofing version of the same draft-and-sign-off routine.
• Groundworks Tenders: Build a Tender Pack and Method Statements With AI — Method statements inside a groundworks tender pack.
• ChatGPT for Civil Engineers: Reports, Method Statements and Emails — How engineers use ChatGPT on reports and method statements.
• Best AI App for a Construction Company: Logging Near Misses — Feed near misses back into your next statement.
• Tree Surgeon Risk Assessment Template: AI Drafts, You Sign Off — Another trade's AI-drafted risk assessment, signed off by you.
• AI Tool for Construction Planning: Pre-Start Checklist and Long-Lead Items — A pre-start checklist to run before the method statement.
• Best AI Tool for Construction Design: What It Drafts and What Needs a Stamp — Which AI design outputs a small builder can issue (sketches, option comparisons, specification wording) and which need an engineer's or architect's sign-off.
• Best AI for Building Companies: Quotes, Programmes and Site Admin — Tool types for a small building company, sorted by quotes, programmes and site paperwork, with one rear extension priced, programmed and documented.
• Construction Tender Writing With AI: Draft, Then Check Against Scoring — Extract the scoring, build a compliance matrix, draft the method statement from your own evidence, then have AI mark it before you submit.
• Demolition Estimate Template: Scope, Waste and Disposal Lines With AI — A demolition estimate template for a rear extension: scope, asbestos and services exclusions, tonnes by waste stream, and skip and disposal lines.
• Loft Conversion Quote Template: Stages and Provisional Sums With AI — How to split a loft conversion quote into fixed price, allowances and provisional sums, with a filled-in stage table and two AI prompts.
• Lone Working Policy for Trades Firms: Check-In Rules Drafted With AI — A two-page lone working policy for a small trades firm: tasks needing two people, check-in rules, an escalation ladder and an AI drafting prompt.
• Translation App for Construction Workers: Brief Mixed-Language Crews — How to brief a mixed-language crew: what Google, Apple, DeepL and Jobber each do, a 20-phrase test with a bilingual lead and a checked daily routine.
• Benefits of AI in Construction: What a Small Firm Can Actually Measure — Five benefits of AI a small building firm can track with a before-and-after sheet: quote time, site diaries, payment chasing, scope gaps and safety drafts.
• Can AI Design a Scaffold? What Software Can and Cannot Do — Why a chatbot cannot design a scaffold, what scaffold design software does, how TG20-style compliance sheets fit, and where AI helps with paperwork.
• Commercial Plumbing Tenders: Can a Small Firm Use AI to Answer? — How a small plumbing firm can draft a commercial tender with AI: method statement, programme, exclusions, insurance wording and pre-submission checks.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Designing Buildings' method statement page, read in November 2026, for the typical contents and the link to risk assessments. The worked example and sample outputs are invented illustrations, not engineering advice.