A service specification for building cleaning must describe the scope of work clearly enough that all bidders can understand and price it on the same basis. This is not merely a formal requirement: vague area data, imprecise intervals, and undefined quality standards routinely produce incomparable bids, inflated risk allowances, and avoidable contract disputes. The following twelve mistakes appear most frequently when organisations tender cleaning services.
Floor Area Data: Accuracy Over Convenience
Many specifications rely on aggregate square metre figures drawn from outdated inventory lists, without defining which surfaces actually count as cleanable area. Furniture density, built-in fixtures, and hard-to-access zones all affect workload in ways that a headline number cannot capture. The result is bids that appear comparable on the surface but rest on entirely different assumptions. A current area matrix broken down by room type – supported by plans, room schedules, or site access – provides a far more reliable basis. Building-specific characteristics matter equally: soiling trap zones, security-restricted areas, high glass ratios, and heavily trafficked entrances all influence method, materials, and time. These details belong in the documents as a formal annex, not as an informal comment during a site visit.
Separate the Service Types – and Be Specific About Frequency
Routine cleaning, periodic deep cleaning, and special cleaning are three distinct service categories with different objectives, methods, and pricing logic. Blending them into the same line items creates either duplicate pricing or coverage gaps – both of which tend to surface as disputes once the contract is running. Each service type needs its own description covering scope, trigger, interval, and billing method. The same discipline applies to cleaning frequencies: phrases like "regularly" or "as required" are too imprecise for a procurement context. A washroom has different demands than a rarely used archive – these differences must translate into specific cleaning cycles per room group, calibrated to usage patterns, soiling levels, and operational hours.
Quality Standards Must Be Measurable
Specifications that call for work to be carried out "properly" or "to a high standard" may sound reasonable, but they cannot serve as a meaningful control benchmark. Without defined criteria, it remains unclear when a service is deficient and how performance should be assessed. Quality measurement systems referenced in relevant standards and current tender documents consistently show that effective management requires criteria, inspection scope, and documentation to be fixed before the contract begins – not improvised afterward. The same applies to the inspection framework itself: test areas, review intervals, escalation paths, and documentation formats belong in the tender documents, not on the agenda of the first contract review meeting.
Test Feasibility Before the Documents Go Out
Specifications frequently contain unstated assumptions about staffing: tight cleaning windows, high area loads, and short response times are combined without verifying whether they are actually achievable on site. The predictable outcome is either higher prices as risks are priced in, or underperformance once work begins. Contracting authorities can conduct market soundings before launching a procedure to sense-check the specification against operational reality. It is also worth examining whether individually reasonable requirements create conflicts when taken together: short execution windows, restrictive product lists, and a lack of storage or preparation areas can collectively make a specification undeliverable. A practicality review from an operational perspective is always worthwhile before publication.
Interfaces, Site Operations, and Hygiene Require Explicit Rules
Ambiguity often arises not at the core of the cleaning service but at its edges: are consumables, waste disposal, mat service, glazing, or ad hoc special cleans included or not? Leaving these questions open creates gaps, duplicated commissions, and variation disputes. A well-constructed specification names the interface for each service component explicitly – and states with equal clarity what falls outside the scope. The operational context of the building matters just as much: teaching timetables, shift patterns, catering operations, or laboratory schedules determine when and how cleaning can take place. Ignoring these factors leads to windows that are too short and restricted areas that cannot be accessed. In hygiene-sensitive environments such as hospitals, care facilities, or food preparation areas, a general reference to "enhanced hygiene" is not sufficient – product selection, protective measures, and hygiene plans must be tailored to each specific area. Finally, even a well-written specification loses force if reporting and feedback mechanisms are not in place. Monitoring records, complaint channels, and response time requirements should be anchored in the contract from the outset, not assembled on the fly once issues arise.
Strong cleaning specifications are defined not by their length but by their precision. When areas, service types, frequencies, hygiene logic, interfaces, and quality controls are described clearly enough to make bids genuinely comparable and performance manageable throughout the contract period, the foundation for a workable agreement is in place. Everything left undefined tends to resurface later – as queries, variations, and disputes that could have been avoided at the drafting stage.