Writing a Scope of Work for Cleaning Contracts – Opora Supply

Who this is for

This guide is for BSC owners and operations managers writing or reviewing cleaning contracts, and for facility managers reviewing a BSC's proposed scope before signing. A well-written SOW protects both parties — it defines what success looks like so there is no ambiguity at inspection time or contract renewal.

Use the Scope of Work Generator to build a structured, zone-specific SOW you can customize with the protective language in this guide. Once the scope is defined, use the Bid Generator to price it accurately.

Why scope language causes disputes

Cleaning contracts are often written in outcome language ("maintain clean restrooms") rather than procedure language ("service restroom fixtures, floors, and consumables nightly Monday through Friday"). Outcome language sounds reasonable until a dispute arises — at which point "clean" means different things to the BSC and the client. The client believes "clean" means a certain appearance standard; the BSC believes "clean" means a certain set of tasks performed. Both can be true simultaneously and still produce a dispute.

The fix is not to write every task with military precision — that is impractical. The fix is to identify the highest-dispute-risk clauses and write those specifically, while using reasonable outcome language for low-ambiguity tasks.

The 12 common SOW ambiguities and model language

1. Floor type not specified

Problem: "Clean all floors" does not tell the crew — or a disputes arbitrator — whether that means sweep, mop, scrub, buff, or refinish. Different floor surfaces require different methods.

Model language: "Floor maintenance shall be performed as follows by zone: Zone A (VCT, 18,500 sq ft) — nightly dust mop and damp mop; Zone B (polished concrete, 3,200 sq ft) — nightly auto-scrub with pH-neutral chemistry; Zone C (carpet, 6,800 sq ft) — nightly vacuum."

2. Consumable responsibility unclear

Problem: Who buys toilet paper, paper towels, soap, and trash liners? If the SOW is silent, expect a dispute within 60 days.

Model language: "Client shall supply and maintain adequate inventory of all restroom consumables (toilet tissue, paper towels, hand soap) and trash can liners. BSC shall restock dispensers and replace liners from client-supplied inventory during each service visit. BSC is not responsible for consumable procurement or inventory shortages."

3. Frequency vs. outcome vs. procedure language mixed inconsistently

Problem: A SOW that specifies "vacuum daily" (frequency), "floors shall be free of visible debris" (outcome), and "use a HEPA-filter upright vacuum" (procedure) in different sections creates conflicting obligations. If the crew uses a backpack vacuum (not an upright) and meets the outcome standard, has the contract been fulfilled?

Model language: Choose one language type per task category and apply it consistently. For daily tasks, frequency language is most practical. For periodic tasks and appearance standards, outcome language works well. Reserve procedure language for tasks where method is a compliance requirement (e.g., EPA-registered disinfectant for restrooms).

4. "Deep clean" undefined

Problem: "Monthly deep clean" appears in many SOWs with no definition. Every party imagines a different scope.

Model language: "Monthly deep clean shall include: interior glass and partition surfaces; baseboards and door frames in all corridors; elevator cab interior walls and door tracks; kitchen/break room appliance exteriors; carpet spot treatment; and light fixture exterior surfaces accessible without lift equipment. Monthly deep clean does not include window washing, high-dusting above 10 feet, or strip-and-recoat floor services unless separately specified."

5. High-dusting altitude not defined

Problem: "Dust all surfaces" — does that include the top of 14-foot shelving units? Light fixtures at 20 feet? Ceiling HVAC diffusers?

Model language: "Routine dusting shall include all horizontal surfaces accessible from floor level without ladder or lift equipment, to a maximum height of 8 feet. Dusting above 8 feet requires a separate periodic service schedule and is not included in nightly service."

6. Periodic floor refinishing schedule not specified

Problem: Floor finish cycles (scrub-and-recoat, strip-and-recoat) are often left out of the base SOW or described vaguely as "as needed." The client assumes quarterly; the BSC prices for annual.

Model language: "VCT floor maintenance shall follow this schedule: nightly dust mop and damp mop; monthly scrub-and-recoat of high-traffic corridors (Zones A and B); semi-annual full-building strip-and-recoat. Strip-and-recoat service to be scheduled at least 14 days in advance and performed during non-business hours."

7. Spill response and emergency service undefined

Problem: A client calls for an emergency floor service after a flooding incident. Is that in scope? At what cost?

Model language: "Routine scope does not include emergency or unscheduled service calls. Emergency service (defined as service requested outside the contracted schedule) may be provided at BSC's discretion at an hourly rate of $[rate] per crew member, with a minimum 2-hour charge, billed separately."

8. Day porter scope not separated from nightly scope

Problem: If a daytime porter is part of the contract, their tasks must be defined separately from the nightly crew's tasks — otherwise both groups assume the other is handling something, and it doesn't get done.

Model language: "Daytime porter service (M–F, 8:00 AM–4:00 PM) shall include: restroom check and restock every 2 hours; lobby entrance and vestibule maintenance; spill response upon notification; and trash can monitoring. Daytime porter shall not perform nightly floor maintenance tasks."

9. Locked or restricted areas not defined

Problem: The bid assumed full access to all floors. Three suites turn out to require escort or after-hours key card access the BSC does not have.

Model language: "Client shall provide BSC with appropriate key, access card, or after-hours access code for all areas included in the cleaning scope. Areas requiring escort access shall be serviced at a mutually agreed-upon schedule. BSC is not responsible for service gaps in areas where access was not available during the scheduled service window."

10. Exterior scope boundary unclear

Problem: "Clean the building" — does that include sidewalks, parking lot, or just interior?

Model language: "This agreement covers interior cleaning of the building as defined in the attached zone map. Exterior services (sidewalk sweeping, parking lot cleaning, exterior window washing, pressure washing) are not included unless listed as separate line items in Exhibit A."

11. Damage and breakage protocol not defined

Problem: A crew member breaks a decorative item. The client expects replacement. The BSC disputes liability. Without a protocol, this becomes a legal question.

Model language: "BSC shall report any damage, breakage, or discovered pre-existing damage to client management within 24 hours of discovery. BSC's general liability insurance covers damage caused by negligence; intentional damage or damage to items not disclosed as present in the cleaning area are excluded. Client is encouraged to remove irreplaceable or high-value items from cleaning areas."

12. Contract termination and cure period undefined

Problem: Client terminates with 30 days' notice after a single complaint. BSC had no opportunity to correct the issue.

Model language: "Either party may terminate this agreement with 30 days' written notice. In the event of a service performance dispute, client shall provide written notice of deficiency; BSC shall have 10 business days to remedy the deficiency before termination proceedings may be initiated."

Common mistakes

Using a generic template without adapting it to the account. Boilerplate SOWs miss account-specific variables every time. At minimum, define floor types, zone boundaries, and consumable responsibility for every account.
Leaving periodic services vague. "As needed" is not a schedule. Clients interpret it as "whenever I ask." Define periodic services with explicit frequency and advance notice requirements.
Omitting the access protocol. Access gaps are the BSC's most defensible excuse for a service gap — but only if the SOW documents that access is the client's responsibility.
No cure period in the termination clause. Without a cure period, any complaint can trigger immediate termination. A 10-business-day cure window is standard in BSCAI-recommended contract language.

Quick checklist

Are all floor types and zones identified with specific maintenance methods?
Is consumable responsibility explicitly assigned to BSC or client for every consumable category?
Is "deep clean" defined with a task list, not just a label?
Are periodic floor services (scrub-and-recoat, strip-and-recoat) on a named schedule?
Is emergency and after-hours service explicitly excluded from base scope and priced separately?
Does the termination clause include a written notice of deficiency and cure period?
Is the exterior scope boundary explicitly defined?