Cleaning Specifications for Tender Documents
How to write a cleaning specification for tender documents: scope, frequencies, standards and evidence, plus the clauses that prevent disputes after award.
Every janitorial dispute you will have is written into the tender, months before the contractor's first shift. If the document says "washrooms cleaned daily, as required", the winning bid prices a five-day frequency and your busiest washroom gets serviced once a day. If it names areas, tasks, frequencies, the standard to be reached, and the evidence required to prove it, bids are comparable and the argument in year two is about execution rather than interpretation.
This is written for the property or facilities manager who issues or reviews tender documents for a building or portfolio — the client side of the table. It covers the cleaning specification itself: what goes in it, how to make it measurable, and which clauses you will wish you had included. It sits alongside the wider discipline of managing a cleaning contractor.
Key takeaways
- A specification is the definition of done; if two bidders can read it differently, it is not finished.
- Specify areas, tasks, frequencies, standard, and evidence — in that order.
- Replace "as required" and "regularly" with measurable frequencies and tolerances before the tender goes out.
- Reference a recognised standard of clean, such as APPA 1–5, so condition is scored rather than debated.
What must a cleaning specification contain?
It must state what is cleaned, how often, to what standard, and how the contractor proves it. Those five elements — areas, tasks, frequencies, standards, evidence — are the backbone; the rest is support.
| Section | What to state | The test it has to pass |
|---|---|---|
| Areas | Room-level or zone list with floor areas and use type | A bidder can price it without guessing |
| Tasks | Specific work per area, including periodic tasks | Each task can be observed and checked |
| Frequencies | Numeric frequency per task, with a tolerance | A supervisor can schedule from it |
| Standard | Measurable condition per area, e.g. APPA Level 2 or 3 | Two inspectors score it the same way |
| Evidence | Completion records, inspection results, photos | You can audit without watching the work |
| Resources | Supervision, staffing hours, equipment expectations | Price can be compared like for like |
| Compliance | Insurance, WHMIS training, safety documentation | You can verify it before mobilisation |
If a section needs a qualifier, that area needs a site visit and a decision, not a vaguer sentence.
Why does a vague specification cost more?
Vagueness does not lower the price; it moves the cost to the year after award. Bidders price ambiguity defensively — lower frequency, periodic work excluded, a contingency added — and you pay for the exclusion or the arguments.
Three consequences follow. Bids become incomparable because each bidder priced a different service. The winning contractor's interpretation becomes the real contract. And any correction becomes a change order, because the work was never in scope.
The fix is cheap at tender stage: walk the building, photograph each area type, count the fixtures, and write against what you saw.
How do you write frequencies that can be measured?
Write a number and a window, not an adjective. "Washrooms: 2 services per day, one before 10:00 and one after 14:00" is measurable. "Washrooms: cleaned as needed" transfers every judgement call to the contractor and every complaint to you.
Work through three steps per area:
- List the tasks that apply — a parkade needs sweeping, machine scrubbing, and drain checks; a boardroom needs table surfaces, glass, and floor care.
- Set frequency against use and visibility. Lobby floors might need daily mopping and a twice-weekly scrub; the freight elevator might need weekly detail.
- Set the tolerance — when a variation counts as a miss. Two hours late on a washroom service during a tenant event is a miss; the same two hours on a quiet Saturday rarely is.
Where frequency is genuinely event-driven, specify the trigger: "spill response within 30 minutes of notification during business hours" is a frequency. "Spot clean as needed" is not.
How should the standard of clean be defined?
Define it per area type, in observable terms, and reference a scoring scheme the contract can use. APPA cleanliness levels run from Level 1 (orderly, high attention to detail) to Level 5 (unsuitable for occupancy), so a specification can require Level 2 in lobbies and Level 3 in stairwells without a paragraph of prose.
Two additions make the levels usable. Visual descriptors per area — what Level 2 means for a washroom floor, a lobby glass wall, or a lunchroom counter, in the words your inspector will use. And a list of critical items where any failure is unacceptable regardless of score: washroom sanitation, blood or bodily fluid response, blocked exits, and chemical storage — critical.
The specification should also say what a failure triggers: correction within a stated window, re-inspection, and a record. Without that, a score is an opinion rather than a consequence.
What evidence should the specification require?
Require the records you will manage with, in the format you will file. If you audit monthly, specify per-area completion records and scored inspection results at that cadence — not a single monthly summary line.
Practical evidence clauses:
- Completion records per area, per shift, with time and initials.
- Supervisor inspections at a stated cadence, scored against the specification with photos.
- Deficiency closure showing date found, date corrected, and who verified it.
- Chemical records including dilution control and safety data sheets, plus a monthly report consolidating condition and open items.
State the retention period: 12 to 24 months is workable for most commercial properties, longer where an insurer or owner asks. If you need to compare contractors at renewal, ask for a format you can aggregate, which is why client-visible cleaning records should be designed rather than improvised.
What should the specification say about staffing and equipment?
State the supervision model and the equipment expectation in the specification, not in the pricing schedule. Bids are rarely cheap because a contractor has better equipment; they are cheap because supervision was assumed to be free.
Include a named site supervisor with stated hours on site, a night check-in procedure where the work is after hours, and the equipment the contractor provides — HEPA-filtered vacuums where required, floor machines matched to the surface, colour-coded cloths, and a mop system with clean-water separation. Require that equipment be maintained and breakdowns reported rather than worked around.
If the building has lifts, escalators, high glazing, or roof access, say who is responsible and who is not. Work at height, electrical rooms, and confined spaces sit outside a cleaning scope and belong to specialist contractors.
What about chemicals, safety and compliance clauses?
Require WHMIS training, safety data sheets for every product on site, and a documented dilution method, because a specification that ignores chemicals is one that will be violated quietly. The CCOHS guide to cleaning products and working safely is useful for drafting the clause.
Clauses worth including:
- Current certificate of insurance and workers' compensation clearance, verified annually.
- Safety data sheets held on site and at the contractor's office, with products named.
- PPE requirements per task, and a stated process for blood or bodily fluid incidents — critical.
- Incident and near-miss reporting to the building within 24 hours.
- No substitution of products or equipment without written approval.
Not regulatory advice. Requirements vary by province and are enforced by your provincial regulator. Confirm the specifics for your jurisdiction and follow the building's own procedures.
How do you handle periodic work and changing conditions?
Price periodic work as separate unit rates in the tender, not buried in the monthly fee. Deep cleans, floor stripping, carpet extraction, high dusting, window cleaning, and post-construction work are event-driven; folded into a monthly rate, nobody can tell whether they were done.
Two clauses do most of the work. A periodic schedule naming each task, its frequency, and its season — floor stripping in spring and autumn, carpet extraction annually per zone. And a renovation clause setting out dust control, daily housekeeping, and who pays for extra cleaning, which is the most common source of unplanned cost in an occupied building.
If you are assembling scope from scratch, defining the scope of work before drafting the specification saves a rewrite, because scope decides what is in and what is excluded.
What clauses protect you if performance slips?
Include the consequence mechanism, and make it mechanical rather than relational. Most disputes are about what happens next, and the specification should already have answered that.
The set that works:
- Correction window per failure type — 4 hours for hygiene-critical items, 2 business days for surface condition.
- Re-clean at no charge where a task in scope was missed, with a re-inspection date.
- Service credits tied to repeated failures or missed inspections, calculated from the monthly fee.
- Improvement plan triggered by a numeric threshold — three confirmed failures on the same route in 30 days, for example.
- Termination for cause with a stated notice period and a handover obligation.
Keep thresholds numeric. "Persistent poor performance" cannot be enforced; "three confirmed failures in 30 days on the same route" can.
Frequently asked questions
How long should a cleaning specification be?
Long enough to define every area, task, frequency, and standard, and no longer. In practice that is 10 to 25 pages for one commercial building once area schedules and frequencies are tabulated. Length is not the measure; unambiguity is.
Should I use APPA levels in the tender?
Yes, as the reference point for scoring condition. APPA levels give bidders a known target and give you a way to describe a failure without adjectives. State the required level per area type and use the same scale in your inspections, so the contract and the audit speak one language.
Who should write the specification — me or the contractor?
You. A specification written by the incumbent describes the service the incumbent already provides and quietly excludes what it does not. A consultant can sanity-check frequencies and pricing, but the requirement has to come from the building and the owner.
What is the biggest mistake in janitorial tenders?
Omitting the evidence requirement. Properties that specify tasks and frequencies but not records end up unable to prove whether work happened, which removes every mechanism for managing performance short of complaint-driven escalation.
Can I change the specification after award?
Only through a written variation with a price and a date. Changes made in conversation are the classic route to a disputed invoice. If the building's use changes — a new tenant, a renovation — vary the specification formally, which is also why the tender process should name who can approve a variation.
Write the contract you want to manage
A cleaning specification is a management document, not a procurement formality. Name the areas, list the tasks, number the frequencies, score the standard, require the evidence, and keep thresholds numeric. Do that and it becomes the tool you use every month, not a PDF you open once at renewal.
NeatScore is built for the verification side of that document: area-specific checklists drawn from your specification, critical items flagged, APPA 1–5 scoring, photos per item, and dated reports you can compare against the winning bid. Try it free for 14 days, or see pricing.


