Rosters and why they are published to the buyer
A roster is a published record of which operative is assigned to which building on which days and at which hours. Publishing the roster to the buyer is not a gesture of transparency — it is a functional requirement of a checkable contract. Without it, the buyer has no basis on which to identify whether a missed service was a scheduling failure or a coverage failure, and no way to confirm that the contract is being staffed at the level it was priced at.
The roster should state: the operative's assigned name or identifier, the days and hours they are rostered to the building, and the tasks they are responsible for on each visit. Where an operative covers more than one building, the roster should be specific to the buyer's building — not a general workforce schedule that the buyer would need to interpret.
The roster is a live document. It is updated when operative assignments change, and the buyer should be notified of any permanent change to their assigned operative before the change takes effect, not after.
Filled dot = routine task scheduled. Open dot = periodic task; see separate calendar. This diagram is illustrative only.
Absence and what it actually costs
When an operative is absent and no cover is arranged, the tasks on their roster are not completed. That is a missed service. In a contract without a written absence procedure, the buyer has no reliable way to know the service was missed — unless they discover it themselves — and no documented recourse when they do.
The cost of a missed service is not just the cleaning that did not happen. It is also the cost of identifying the miss, raising it with the contractor, waiting for it to be addressed, and establishing whether it will be made good or simply logged. In a building with no written specification and no roster, that process can take longer than the cleaning itself would have taken.
A written absence procedure addresses this by stating: how the buyer is notified when an operative will not attend (and within what timeframe before the scheduled visit); whether cover will be provided and within what window; what happens if cover cannot be arranged and the service is missed; and what the buyer's recourse is. That recourse should be stated explicitly — whether it is a credit against the next invoice, a make-good visit, or some other agreed remedy. An absence procedure that states notification requirements but nothing about remedy is only half written.
Cover operatives should be inducted to the same specification as the rostered operative. A cover operative who arrives without a task list, does not know the access procedure, and is unfamiliar with the restricted areas in the building is not providing an equivalent service — they are providing a best-effort service, which is a lower standard than the buyer has contracted for.
Hours visibility
A contract priced at a particular number of hours per week should state that number in the specification. The buyer should be able to see, from the roster, how many hours per week are contracted, and from the access log, how many hours per week were actually worked. Where those numbers diverge consistently, the contract is not being delivered as priced.
Hours visibility is not about distrust. It is about having a factual basis for a conversation when standards are not being maintained. If the buyer raises a quality concern and the contractor's response is to investigate, the access log is the first place that investigation should look. If the contracted hours are being worked, the conversation is about method or task coverage. If they are not, the conversation starts somewhere more fundamental.
Hours visibility also matters when the buyer wants to amend the contract. Adding tasks, increasing frequencies, or expanding the area schedule all have a labour implication. A buyer who can see the current contracted hours has a realistic basis for that conversation. A buyer who cannot see them is negotiating without information.
Periodic works calendar
Periodic works — carpet extraction, hard floor treatment, kitchen deep cleans, high-level dusting — sit on a separate calendar from the daily roster. That calendar is agreed in writing at commencement, with specific dates or date ranges for each task, and updated at each annual review. It is not a rolling agreement to do these tasks "at some point" — it is a scheduled commitment with dates that both parties have signed off.
The calendar matters because periodic works typically require access to areas that are either occupied during normal cleaning hours or require the presence of a representative of the buyer. Advance planning is not optional for these tasks. A carpet extraction programme that arrives without notice causes operational disruption; a hard floor strip that has not been communicated means the buyer cannot clear the floor area in time.
Where a periodic task is not carried out on its scheduled date — because of a building constraint, an operative issue, or any other reason — the revised date is agreed in writing and added to the calendar. Periodic tasks that drift past their scheduled date without a rescheduled date are tasks that are becoming overdue, and overdue periodic tasks compound over the life of a contract.
| Task | Frequency band | Calendar position (illustrative) |
|---|---|---|
| Carpet extraction — meeting rooms | Quarterly | January, April, July, October |
| Hard floor strip and reseal | Annually | August (low occupancy period) |
| High-level dusting | Six-monthly | February, August |
| Kitchen deep clean | Quarterly | March, June, September, December |
| Internal window programme | Monthly | First week of each month |
Calendar positions are illustrative. Actual dates are agreed between the parties at commencement.
The verification loop
Verification is the mechanism that connects what was specified, what was signed off as completed, and what gets re-checked on the next visit. Without a verification loop, a specification is a document that was agreed at the start of a contract but has no bearing on how the contract is run week to week.
The loop operates as follows. The operative works from the task list in the specification. On completion of each visit, the tasks completed are signed off — by the operative, or by a supervisor on their behalf — against the task list. The sign-off record is retained and is available to the buyer. At the buyer's review visit (or the contractor's supervisory visit), the areas cleaned in the previous visit are checked against the task list. Any variance — a task missed, a standard not met — is documented, communicated to the operative, and confirmed as addressed on the next visit. At each scheduled specification review, the pattern of variances across the review period is considered and the specification is amended if there is a systematic issue.
Written task list and frequency table. Agreed and dated by both parties.
Operative works from task list. Each visit produces a sign-off record.
Tasks completed are signed off against the list. Record retained and available to buyer.
Areas are checked against the sign-off. Variances documented and addressed.
Pattern of variances reviewed. Specification amended in writing if required. Loop restarts.
The loop only works if all five stages are completed. A specification without sign-off is unverifiable. Sign-off without a check visit is self-certification. A check visit without a review means variances are identified but patterns are not acted upon. A review without an updated specification means the document remains out of step with how the contract is actually running. Each stage requires the previous stage to have happened, which is why the loop is a loop and not a list.