How to Write a Cleaning SOP Your Team Will Actually Follow
Operations · Quality
Listen to this article
Narrated from this CleanLog article.
A cleaning SOP should help someone perform the work correctly without needing the person who wrote it beside them.
That sounds simple. In practice, many SOPs mix contract language, training notes, safety warnings and long equipment lists into one document. The cleaner receives plenty of information but still has to ask which steps apply at this site.
The best place to begin is a real task. Watch how it is done, check the approved method and write for the person who will use the procedure during the shift.
What is a cleaning SOP?
A cleaning standard operating procedure describes the approved method for completing a defined type of work. It should state where the procedure applies, who is responsible, what needs to be prepared, which steps must be followed, what safe completion looks like and what to do when conditions differ.
An SOP is not the same as a checklist or inspection.
| Document | Question it answers |
|---|---|
| SOP | How should this work be performed? |
| Task checklist | What work should be completed during this shift? |
| Inspection checklist | Did the result meet the agreed standard? |
Keep these roles separate. The cleaning checklist system can link to the SOP without copying every instruction into the shift. The quality audit process evaluates the outcome without asking the inspector to repeat the cleaner’s method.
Choose the right level for the procedure
Do not write one SOP called “Office Cleaning” and expect it to cover every material, room and risk.
A procedure should be narrow enough that its method stays consistent. Examples could include:
- Routine cleaning of an office pantry
- Post-service cleaning of a washroom
- Responding to a drink spill on a specified floor type
- Preparing and storing approved cleaning equipment
- Completing periodic carpet work using approved equipment
Site-specific differences should be visible. If two locations use different chemicals, access rules or waste arrangements, do not hide that difference inside a general paragraph. Use a site appendix, clearly marked variation or separate procedure where necessary.
Build the SOP from observed work and approved guidance
Start by watching an experienced person perform the task at the actual site. Ask what they check before beginning, what usually goes wrong and which parts depend on the condition they find.
Then compare the observed method with:
- The contract and site requirements
- Equipment manufacturer instructions
- Product labels and safety data sheets
- Workplace safety requirements
- Applicable public-health or sector guidance
- The client’s own facility policies
Observation alone can preserve an unsafe shortcut. A document alone can describe work that is impossible at the site. The SOP needs both operational reality and the approved method.
The National Environment Agency’s pictorial cleaning guides are a good example of procedures designed for use during work. They show cleaning sequences and safety measures visually and provide versions in Singapore’s official languages.
The sections every cleaning SOP needs
1. Purpose and scope
State the task and where it applies.
Include the premises type, area, surface or equipment covered. Also state important exclusions. A procedure for a general office area should not quietly become the procedure for a clinic or food-preparation space.
2. Responsibility
Name the role responsible for performing the work and the role responsible for escalation or approval.
Use roles rather than a person’s name where the responsibility belongs to the job. If another team owns part of the work, make the boundary clear.
3. Required preparation
List what must be ready before the task begins:
- Approved equipment and materials
- Required personal protective equipment
- Warning signs or access controls
- Site access and keys
- Any isolation, ventilation or preparation requirement
- The information needed to identify the correct area
Do not include every item the company owns. List what this procedure actually requires.
4. Safety and stop conditions
Put the important safety instruction before the step where the risk occurs.
Also explain when the cleaner should stop and ask for help. Examples may include an unknown chemical, damaged electrical equipment, an unsafe spill, missing protective equipment or a surface not covered by the approved method.
“Use caution” is not a useful stop rule. State the condition and the person or role to contact.
5. The work sequence
Write the steps in the order they happen.
Each step should begin with a clear action. Keep one main action in each numbered step. Where a decision changes the path, show the condition explicitly.
For example:
- Confirm that the area and surface match this procedure.
- Place the required warning signs before bringing liquid onto the floor.
- Remove loose waste using the approved equipment.
- Apply the approved cleaning method for the surface.
- Inspect the area against the completion standard.
- Remove signs only when the area is safe for normal use.
This is only a structural example. The actual method, product, contact time and protective equipment must come from the approved site procedure and product instructions.
6. Completion standard
Describe what should be true when the task is finished.
The completion standard should be observable. It may cover condition, safety, consumables, equipment storage and whether the area has been returned to normal use.
This is the bridge between the procedure and inspection. The SOP explains how to produce the result. The inspection checklist can use the agreed outcome without repeating every step.
7. Exceptions and escalation
Work does not always follow the normal sequence.
Include common exceptions such as:
- The area is occupied
- Access is unavailable
- The required product or equipment is missing
- Damage is found
- The surface condition is outside the procedure
- Additional work is requested
For each one, say whether the cleaner should wait, use an approved alternative, report the condition or create follow-up work. Do not leave the decision to a general instruction such as “inform supervisor if necessary.”
8. Required record
Specify what needs to be recorded after the work.
This may be a completed task item, a note, a photograph, a quantity, an exception or a work order. Evidence should be required because it serves an operational or contractual purpose, not because software makes it possible to collect.
9. Version and approval
Every SOP needs an owner, version, approval date and effective date.
When the method changes, keep the old version with the records created while it was active. A new procedure should not make it appear that yesterday’s cleaner was working under today’s instructions.
A one-page cleaning SOP template
Use the following structure as the first draft:
| Section | Content |
|---|---|
| SOP title | Specific task and area or surface |
| Purpose | Why the procedure exists |
| Scope | Where it applies and does not apply |
| Responsible roles | Performer, supervisor and escalation owner |
| Preparation | Equipment, product, PPE, signs and access |
| Safety and stop conditions | Risks, prohibitions and escalation triggers |
| Procedure | Numbered steps in working order |
| Completion standard | Observable acceptable result |
| Exceptions | Approved response when normal work is blocked |
| Required record | Checklist result, note, photograph or follow-up work |
| Document control | Owner, version, approval and effective date |
Keep the main procedure short enough to use. Put detailed product data, diagrams or site maps in linked references where they are easier to maintain.
Use pictures where words create unnecessary work
Some instructions are easier to understand as a photograph, diagram or short demonstration.
Pictures can show the correct equipment, colour coding, storage position, area boundary or final setup. Add a caption that explains what the image proves. Do not use a generic stock photograph that merely shows somebody cleaning.
The NEA office space cleaning procedure and office common-area procedure show how a sequence can be communicated with task-specific illustrations and multilingual text.
Test whether another person can use it
Give the draft to someone who did not help write it. Ask them to explain the preparation, perform or talk through the steps, identify the stop conditions and describe the finished result.
Do not help until the test is finished. Every question is evidence that the SOP assumes knowledge it has not provided.
Then test it at the site. A procedure that is clear in a meeting can still fail because the equipment is stored elsewhere, the area is occupied or the sequence conflicts with how the building operates.
Specialised and healthcare environments
Specialised sites need their own approved procedures.
For healthcare environmental cleaning, the CDC cleaning-program guidance calls for facility-specific policies, cleaning schedules, roles, methods and detailed SOPs. Its procedure guidance also distinguishes areas by patient vulnerability, contamination risk and touch frequency.
Those requirements should be developed with the facility’s responsible clinical or infection-prevention team. A general commercial cleaning template is not a substitute.
How CleanLog connects the SOP to the work
In CleanLog, the shift checklist tells the cleaner what is due at that site. The relevant item can point to the approved procedure or instruction without placing the whole document inside every task.
The completed checklist records what was done. Exceptions can become work orders with the site and task context attached. A separate inspection then evaluates the result.
This keeps the three questions separate:
- What method was approved?
- What work was assigned and recorded?
- What result did the inspection find?
If you are replacing a folder of procedures or turning supervisor knowledge into a repeatable process, talk to us. We can help map the procedure, checklist, exception and inspection records before you configure them.
Sources
Get the next post
Practical writing on scheduling, payroll, and daily ops. About once a month.