Writing a Cleaning Method Statement That Crews Actually Use

Three documents govern most commercial cleaning work, and contractors routinely mix them up. The specification says what clean means. The risk assessment says what could hurt someone. The method statement says how a named person will do the job, in what order, with what product and what control. Only one of those three gets read on a wet Tuesday morning in a stairwell.

A cleaning method statement is the working document: short enough to be usable, specific enough to be audited, and written for the person holding the mop rather than for the client's procurement file. Get it right and it doubles as a training tool, a safety record and the answer to "why did you do it that way?" after an incident.

Key takeaways

• A method statement describes sequence, product, dwell time, equipment and controls for a specific task in a specific location — not a general intention to clean
• It is a safe system of work, so it sits alongside the risk assessment rather than replacing it, and it must name the controls that reduce each risk to acceptable
• The specification defines the outcome, the method statement defines the route; where they disagree, the specification wins and the method statement gets rewritten
• Keep each statement to one task in one area, or a single page that a supervisor can hold while walking the job
• Method statements need an owner, a version date and a review trigger — new product, new equipment, new area, or any incident
• Tasks outside a contractor's competence — confined spaces, electrical work, clinical waste, pest treatment, machinery repair — belong in the statement as a report-and-stop instruction - critical

Three documents, three jobs

A specification, a risk assessment and a method statement answer different questions, and the same person often writes all three. Each has a different failure mode when it is missing.

A specification that says "washroom fixtures cleaned daily to a hygienic standard" is complete as a specification and useless as an instruction. A method statement that says "spray the fixture with the labelled product from the wall dispenser, agitate with the designated cloth, allow the label contact time, rinse, then dry the chrome with a separate cloth" is doing the job the specification cannot.

What every method statement must contain

Not every task needs a two-page document, but every method statement needs the same skeleton. Drop any of these and it stops being a safe system of work.

• Task and location named precisely — "descaling urinals, levels 3 to 7, north core", not "washroom cleaning"
• Who does it, and what training or competence that person must hold - critical
• Plant, equipment and materials, including the specific product category rather than a brand promise
• Dilution and preparation, taken from the label or the safety data sheet, with the measuring method stated
• Sequence of work, top to bottom and clean to dirty, with dwell or contact time written as a number of minutes
• Controls: ventilation, signage, barriers, isolation, wet floor management, two-bucket separation - critical
• PPE, matched to the product and task, with the glove material named where the SDS specifies one
• Waste and disposal, including sharps and anything that must not go in general waste - critical
• Stop conditions — what the worker must not do, and who to report it to
• Completion record — what gets signed, photographed or logged, and where

That list looks long. In practice a routine office task collapses into four or five lines plus a product table, while a task involving height, chemicals or a vulnerable population legitimately runs to a page.

Choosing the right level of detail

Too much detail is its own failure. A method statement nobody reads protects nobody.

The practical test for any draft: hand it to someone who has never cleaned that area, and ask them to describe what they would do first, second and third. If they cannot, the document is describing an outcome rather than a method.

Writing it with the product in hand

Method statements go wrong when they are written at a desk from memory. Dilution ratios, contact times and PPE requirements come off the label and the safety data sheet, not from habit — and habit is where most crews drift. Glove selection in particular is often wrong: the safety data sheet may call for a specific material, and "impervious gloves" as a generic phrase tells the reader almost nothing. The CCOHS guidance on chemical protective glove selection explains breakthrough time and degradation, which is the level of thinking that belongs behind a one-line PPE entry.

Write the products in by category and function — neutral floor cleaner, non-acid bowl cleaner, quaternary ammonium disinfectant, glass cleaner — and then map each to the actual product on the shelf. That mapping is what makes the document survive a supplier change, and it is also what chemical inventory and dilution control is built on.

Sequencing: the part crews get wrong

Most quality complaints trace back to sequence rather than effort. A method statement should make the order obvious, and the order is almost always the same logic.

1. Prepare — signage, barriers, ventilation, equipment check, product made up at the correct dilution
2. Dry work first — high dusting, vents, ledges, cobwebs, so nothing falls onto a wet surface
3. Then wet work — fixtures, surfaces, then floors last so nothing is walked over
4. Dwell — apply, leave for the labelled contact time, then agitate or rinse
5. Finish — dry, polish, restore furniture, remove signage once the floor is dry - critical
6. Verify and record — check against the specification line for that area, note defects, log completion

Two-bucket mopping, top-to-bottom wall washing, and cleaning from the far corner back toward the exit are all sequence rules that belong written down, because they are the ones a rushed crew abandons first.

Controls, PPE and the safety core

A method statement is a safe system of work, which means it must show how the risk assessment's controls actually get applied. Where a risk assessment says "reduce exposure to chemical by dilution and ventilation", the method statement says which dispenser, which setting and which window. Where it says "manual handling risk", the method statement says two-person lift over 20 kg and where the trolley lives.

Five controls come up again and again in commercial cleaning:

• Ventilation in small washrooms and enclosed rooms, and never decanting product in a cupboard - critical
• Signage and barriers before a wet floor exists, not after
• Never mixing products, particularly anything chlorine-based with anything acidic - critical
• No food or drink in chemical handling areas, and wash hands before breaks
• Report, do not act on damaged fittings, exposed wiring, suspected asbestos, sharps, mould beyond surface growth, or anything in a locked plant room - critical

Not regulatory advice. Requirements vary by province and are enforced by provincial labour ministries and health and safety regulators. CCOHS publishes the hierarchy of controls that underpins this section, but confirm specifics with your provincial regulator and follow the facility's own procedures.

Reviewing, versioning and training

An unsigned, undated method statement is a liability rather than an asset. Treat each one as a controlled document with a number, an owner and a review date, and set review triggers rather than relying on an annual calendar:

Training is the last mile. A method statement that lives in a folder has no effect on quality; the same document explained at the area, with the actual products in hand, changes how a new starter works from day one. The wider onboarding sequence is covered in training and onboarding cleaning staff, and the way supervisors verify that the method was followed sits in cleaning checklist vs inspection.

The most useful move for a small contractor is to treat the method statement as the checklist source. Each step in the method becomes an item, each stop condition becomes a critical item, and each completion record becomes a photo. Written that way, the document is not paperwork at all — it is the asset that makes a growing company's quality stop depending on whoever happens to be on site that night.

Where this fits in the quality system

This sits under our APPA levels explained, which sets out the standard these checks are measured against.

Frequently asked questions

What is the difference between a cleaning specification and a method statement?

A specification defines the required outcome and frequency for each area — what standard, how often, to what tolerance. A method statement defines how the work is carried out safely and consistently to reach that standard. The specification is normally a contract document; the method statement is an operational and safety document beneath it.

Does a method statement replace a risk assessment?

No. The risk assessment identifies hazards and sets the controls; the method statement applies those controls to a specific task and location and adds the practical sequence, products and stop conditions. Many contractors attach the relevant risk assessment so the two are read together on site.

How long should a cleaning method statement be?

As short as it can be while still naming the sequence, products, dwell time, PPE, controls and stop conditions. Routine low-risk tasks work as a quarter-page task card, most commercial tasks fit on half to one page, and only tasks involving height, chemicals, plant rooms or sensitive environments justify one to two pages.

Who should write the method statement?

The site supervisor should draft it, because that person knows the building, the equipment and the crew. It should be reviewed by whoever holds health and safety responsibility, and ideally checked once with the operative who does the task. Documents written solely by head office from a template get ignored.

How often should method statements be reviewed?

Set triggers rather than a fixed interval: any new or substituted product, new equipment, change of layout or occupancy, an incident or near miss, a complaint trend, or a change in the client's specification. A universal annual review is fine as a backstop but will not catch the changes that actually matter.

NeatScore lets you build area-specific checklists with critical items flagged, record completion with photos, and keep a dated report your client can trust. Try it free for 14 days, or see pricing.