A genuinely usable, room-by-room template for building a janitorial scope of work — the document every accurate quote and every quality conversation depends on.
Why does a janitorial contract need a written scope of work?
A written scope of work is the only document that turns 'clean the building' into something enforceable — it names every space, the task performed in it, and how often. Without it, quality disputes have no reference point, and a vendor's promise is the only thing holding the contract together.
Most janitorial disputes aren't about a vendor refusing to do the work — they're about two sides disagreeing on what 'the work' was supposed to be. A facility manager assumes daily restroom detailing includes wiping partition doors; the cleaning crew's understanding stops at fixtures and floors. Both sides can be acting in good faith and still end up in a dispute, because nothing was ever written down at the level of a room and a task and a frequency.
A scope of work fixes that by forcing specificity before the contract starts, not after something is missed. It becomes the inspection standard, the training document for new staff, and the reference point for any quality conversation. This template is built room-by-room, the way a facility actually works, rather than as a vague paragraph of adjectives like 'thorough' and 'professional' that mean nothing when something gets missed.
What belongs in a restroom scope, task by task?
A restroom scope should separate daily fixture-and-surface cleaning from periodic deep cleaning, and name every consumable that gets restocked. Restrooms are the highest-scrutiny space in most buildings, so this is the section worth over-specifying rather than under-specifying.
Restroom scope of work — sample task × frequency
Clean and disinfect toilets, urinals, sinks
- Frequency
- Every visit
- Notes
- Name the disinfectant contact time expected, not just 'disinfect'
Restock toilet paper, soap, paper towels/hand dryer check
- Frequency
- Every visit
- Notes
- Define a par level so restocking isn't reactive
Empty and reline trash and sanitary receptacles
- Frequency
- Every visit
- Notes
- Confirm liner size/count so it's not silently substituted
Spot-clean mirrors, partitions, dispensers
- Frequency
- Every visit
- Notes
- Fingerprints and splash marks are the most-noticed miss in restrooms
Damp mop floor with disinfectant solution
- Frequency
- Every visit
- Notes
- Specify floor type — tile grout needs different chemistry than sealed concrete
Detail-clean partition doors, walls, vents
- Frequency
- Weekly
- Notes
- This is the task most often assumed but not written down
Deep-scrub grout lines and floor drains
- Frequency
- Monthly or per inspection finding
- Notes
- Tie to the inspection standard below rather than a blind calendar date
Descale fixtures for hard-water buildup
- Frequency
- Monthly, or as water hardness requires
- Notes
- Water hardness varies across the Inland Empire — confirm with the vendor what's assumed
| Task | Frequency | Notes |
|---|---|---|
| Clean and disinfect toilets, urinals, sinks | Every visit | Name the disinfectant contact time expected, not just 'disinfect' |
| Restock toilet paper, soap, paper towels/hand dryer check | Every visit | Define a par level so restocking isn't reactive |
| Empty and reline trash and sanitary receptacles | Every visit | Confirm liner size/count so it's not silently substituted |
| Spot-clean mirrors, partitions, dispensers | Every visit | Fingerprints and splash marks are the most-noticed miss in restrooms |
| Damp mop floor with disinfectant solution | Every visit | Specify floor type — tile grout needs different chemistry than sealed concrete |
| Detail-clean partition doors, walls, vents | Weekly | This is the task most often assumed but not written down |
| Deep-scrub grout lines and floor drains | Monthly or per inspection finding | Tie to the inspection standard below rather than a blind calendar date |
| Descale fixtures for hard-water buildup | Monthly, or as water hardness requires | Water hardness varies across the Inland Empire — confirm with the vendor what's assumed |
What should an office and common-area scope specify?
Office and common-area scopes should separate daily touchpoint cleaning from weekly detail work and monthly deep cleaning, and should explicitly name what does not get moved or cleaned — like personal items on desks — to prevent liability disputes over misplaced belongings.
Office, lobby and common-area scope of work — sample task × frequency
Offices/cubicles
- Task
- Empty trash and recycling, reline as needed
- Frequency
- Every visit
Offices/cubicles
- Task
- Vacuum carpeted floors / dust mop hard floors
- Frequency
- Every visit
Offices/cubicles
- Task
- Dust reachable horizontal surfaces (not personal items or paperwork)
- Frequency
- Weekly
Lobby/reception
- Task
- Clean glass entry doors and interior glass partitions
- Frequency
- Every visit
Lobby/reception
- Task
- Vacuum or mop, spot-clean high-touch surfaces (door handles, counters)
- Frequency
- Every visit
Lobby/reception
- Task
- Detail furniture, baseboards, light fixtures
- Frequency
- Monthly
Breakrooms/kitchens
- Task
- Clean counters, sink, exterior of appliances, empty trash
- Frequency
- Every visit
Breakrooms/kitchens
- Task
- Clean interior of microwave, refrigerator exterior detail
- Frequency
- Weekly
Conference rooms
- Task
- Wipe table and chairs, reset chairs, empty trash
- Frequency
- Every visit
| Space | Task | Frequency |
|---|---|---|
| Offices/cubicles | Empty trash and recycling, reline as needed | Every visit |
| Offices/cubicles | Vacuum carpeted floors / dust mop hard floors | Every visit |
| Offices/cubicles | Dust reachable horizontal surfaces (not personal items or paperwork) | Weekly |
| Lobby/reception | Clean glass entry doors and interior glass partitions | Every visit |
| Lobby/reception | Vacuum or mop, spot-clean high-touch surfaces (door handles, counters) | Every visit |
| Lobby/reception | Detail furniture, baseboards, light fixtures | Monthly |
| Breakrooms/kitchens | Clean counters, sink, exterior of appliances, empty trash | Every visit |
| Breakrooms/kitchens | Clean interior of microwave, refrigerator exterior detail | Weekly |
| Conference rooms | Wipe table and chairs, reset chairs, empty trash | Every visit |
The line about personal items matters more than it looks: it's the single most common source of he-said-she-said disputes in office janitorial. Writing 'desks are dusted but papers, personal items and electronics are not moved' into the scope protects both the cleaning crew and the client before anything goes missing or gets shuffled.
How does a production and warehouse scope differ from an office scope?
Production and warehouse scopes are built around what surrounds the equipment, not the equipment itself — floors, walkways, dock areas and support spaces — plus safety-driven items like spill response and aisle-marking visibility that an office scope never needs.
- **Production floor perimeter and walkways** — sweep/scrub on a schedule that fits around running lines, not a fixed clock time; coordinate with operations for access windows.
- **Dock aprons and loading areas** — debris, oil drip and pallet residue removal, typically higher frequency than interior floors due to vehicle traffic.
- **Break and locker rooms in production areas** — same standard as office breakrooms, but often higher-traffic across three shifts.
- **High dusting** — overhead pipe runs, conduit, racking and light fixtures in warehouse and production spaces; see high dusting for the equipment and access this requires.
- **Spill and safety-line visibility** — floor markings, safety-line paint and aisle stripes kept visible and unobstructed, not buried under residue.
- **Restrooms serving production areas** — same task list as the restroom table above, scaled to shift-based traffic rather than office hours.
Manufacturing and warehouse scopes should also state explicitly what the janitorial crew is not responsible for: production equipment interiors, machine guarding, and anything requiring lockout/tagout access. That line belongs in the exclusions section below, but it starts here, in the task table, by naming only the surfaces around the equipment.
What is an inspection standard, and why does the scope need one?
An inspection standard is a documented, repeatable way of scoring completed work — usually a checklist or rating scale walked by a supervisor on a set schedule — so quality is measured against the same criteria every time instead of a subjective impression.
A scope of work says what should happen. An inspection standard says how anyone checks that it did. Without one, quality conversations default to 'it doesn't look right' — which is impossible to act on consistently. A working inspection standard typically walks a defined route through the facility on a set cadence, scores a sample of spaces against the task list in the scope, and produces a record (often with photos) that both sides can refer back to.
- Define the inspection route and how often it runs — for example, weekly spot inspections plus a monthly full walk.
- Score against the scope's own task list — an inspection standard that doesn't map back to the written scope is measuring something else.
- Require photo documentation for any deficiency, dated and tied to the specific space.
- Set a response window for correcting a flagged item — same-day for restrooms and safety items, next-visit for lower-priority cosmetic items.
What should the scope say about consumables and exclusions?
The scope should name who supplies consumables (paper products, liners, hand soap) and at what par level, and should list exclusions explicitly — anything not named as included is, by default, not part of the contract, which is exactly why exclusions need to be written rather than assumed.
Consumables disputes are usually a supply-chain problem disguised as a quality problem — restrooms run out of paper towels not because the crew skipped a step, but because nobody defined who restocks the supply closet and how often it gets checked. Naming a supplier, a par level and a restocking frequency in the scope removes the ambiguity before it becomes a complaint.
- **Consumables supplier** — vendor-supplied, client-supplied, or a hybrid (vendor restocks from client-purchased stock)?
- **Par levels** — a minimum on-hand quantity that triggers restocking, not a reactive 'restock when empty.'
- **Common exclusions** — production equipment interiors, IT/server room equipment, personal workstations and belongings, exterior building envelope beyond scheduled window cleaning, and anything requiring specialized certification or lockout/tagout access.
- **Specialty and deep-cycle work carved out separately** — floor stripping/refinishing, carpet extraction, window cleaning, pressure washing and post-construction cleanup are typically scheduled and priced apart from the recurring scope; see floor care, carpet cleaning and post-construction cleaning.
What does a written escalation path actually look like?
An escalation path names a specific contact, a specific response time, and a specific next step if the first response doesn't resolve the issue — replacing 'call the office' with an actual chain someone can follow under pressure.
- 01
Named first contact
One person or role, not a general phone line, responsible for same-day response to a reported issue.
- 02
Response window
State a specific time — for example, same business day for quality issues, immediate for safety issues like a spill or a restroom outage.
- 03
Documentation of the fix
The response includes what was done and when, not just a verbal confirmation that it's 'handled.'
- 04
Second-level escalation
If the first contact doesn't resolve it within the response window, name who gets it next and how — this is usually where an owner-led operation differs from a call-center model.
- 05
Recurring-issue review
Anything that escalates more than once in a defined period triggers a scope or staffing review, not just another one-off fix.
How should a facility manager actually use this template?
Copy the task tables above, delete anything that doesn't apply to the building, add any facility-specific tasks the tables don't cover, and send the finished document to every bidder before asking for a price — the template is only useful once it's specific to one real building.
This is deliberately built as a starting draft, not a finished contract. Every real building has something the generic tables don't cover — a specific piece of equipment near a break area, a compliance requirement for one wing of a facility, a landlord-imposed rule about after-hours access. Add those lines before sending the scope out, because a generic scope produces generic bids, and generic bids are exactly what makes contract comparison impossible. Pair this with how to choose a commercial cleaning company for the rest of the vetting process once bids come back.
Common questions.
Do I need a written scope of work if I already trust my cleaning vendor?
Yes — trust and documentation solve different problems. A written scope protects a good relationship from drifting when staff turns over on either side, and it's the only reference point either party has when a new manager, new crew lead, or new building tenant changes what 'normal' looks like.
How often should the scope of work be reviewed and updated?
At minimum annually, and any time the building changes materially — a new tenant, an added shift, a renovated space, or new equipment. A scope written for a building as it existed two years ago is not the scope for the building as it exists today.
Should the scope specify products and chemicals, or just tasks and frequency?
Task and frequency are the core of the document; naming specific products is optional unless a compliance requirement (like GMP disinfectant rotation) makes it necessary. Over-specifying products can box out a vendor's own effective, EPA-registered chemistry without adding real quality assurance.
What's the difference between a scope of work and an inspection standard?
The scope defines what should be done and how often; the inspection standard defines how anyone verifies it was done and to what quality level. A contract needs both — a scope without an inspection standard has no enforcement mechanism.
Who should write the first draft of the scope — the client or the vendor?
The client, ideally using a neutral template like this one, then reviewed with the vendor before signing. A scope written entirely by the vendor tends to default to whatever that vendor already does, rather than what the specific building actually needs.
How detailed should the exclusions section be?
Detailed enough that neither side is guessing. List categories explicitly — equipment interiors, personal belongings, specialty deep-cycle work — rather than a single vague line like 'standard exclusions apply,' which settles nothing when a dispute actually happens.
Can one scope of work cover multiple building types on the same campus?
Yes, but it should be organized by space type within the document, not by building — an office wing, a warehouse wing and a lab wing on the same campus need three different task tables even if they're priced under one contract.
What happens if the actual cleaning doesn't match the written scope?
That's exactly the gap the inspection standard and escalation path are built to catch and correct. A documented deviation gets flagged, logged with a timestamp and often a photo, and resolved within the response window named in the escalation path — not argued about after the fact.
Should consumables like toilet paper and soap be included in the janitorial price?
It varies by contract, and either approach works — what matters is that the scope states clearly who supplies them, at what par level, and how restocking is monitored, so an empty dispenser is a defined process failure, not a mystery.
Reviewed by Nexara Facility Services · Updated
