An output-based specification pays for a defined, auditable standard; an input-based specification pays for a set number of cleaner hours. Output-based specs reward a clean building and put delivery risk on the provider; input-based specs reward attendance and leave quality risk with you. Bottom line: buy the output, not the hours, unless you have a specific reason to control inputs.
What an output-based specification is
An output-based (or outcome-based) specification defines the standard each area must reach — 'washrooms clean, stocked and odour-free', 'floors clean and dry', measured against agreed criteria and audited. It does not dictate how many hours or people are used to get there; that is the provider's problem. You pay for a result, and the provider carries the risk of delivering it efficiently. It pairs naturally with the fixed monthly fee model.
What an input-based specification is
An input-based specification buys a defined quantity of resource — for example, one cleaner for two hours a night, five nights a week. You are paying for attendance and time, not for a guaranteed standard. If the building is not clean at the end of those hours, you have still had what you paid for. The risk of the hours being enough sits with you, the buyer.
Why output-based usually protects the buyer
Output-based specs align the provider's incentive with yours: they only succeed if the building meets the standard, so they must resource it properly and cover absence themselves. They are also easier to audit fairly — you measure the result, not whether someone clocked in. This is why professional buyers and public-sector frameworks increasingly write cleaning as outcomes with measurable criteria. It fits an ongoing contract cleanly.
When input-based makes sense
Input-based specs suit situations where you genuinely need to control who is on site and for how long — a fixed daytime porter presence, a security-sensitive site where headcount is capped, or a space where a visible, constant presence is the point. In those cases you are deliberately buying time, not just outcome, and that is a valid choice.
Writing a spec that holds up
A good specification lists areas, tasks, frequencies and the standard for each, plus how it will be audited and what happens if a standard is missed. Whether output or input, clarity is what prevents disputes — the classic failure is a vague scope that lets tasks like windows and high-level areas quietly fall out. We help scope this during the survey so the contract says exactly what a good clean looks like.
Output-based vs input-based cleaning specification
| Factor | Output-based spec | Input-based spec |
|---|---|---|
| Cost | Fixed fee for a defined standard | Priced on hours/resource supplied |
| Control | Control the standard and audit criteria | Control headcount and hours on site |
| Reliability / cover | Provider must cover absence to hit the standard | Cover is only what the hours bought include |
| Compliance | Auditable against measurable criteria | Verified by attendance, not outcome |
| Best for | Most buyers wanting a guaranteed result | Fixed presence, capped headcount, security-sensitive sites |