Ask three people in a building what 'the restrooms are cleaned daily' means and you will get three answers. One assumes fixtures are disinfected and consumables restocked. One assumes floors are machine-scrubbed. One assumes someone walks through with a cart. All three are reading the same contract line — and the vendor is reading a fourth interpretation, usually the cheapest one that still fits the words.
This is where most facility service relationships fail. Not through negligence, but through a specification loose enough that nobody is technically wrong. By the time complaints escalate, both sides are arguing about intent rather than performance, and there is no document that settles it.
What a usable scope actually specifies
A scope that can be enforced describes tasks, areas, and frequencies separately, and it describes the standard each task must meet. That is more work to produce, which is exactly why vendors competing purely on price avoid producing it.
- Every area named, with square footage and surface types identified
- Each task listed against the areas it applies to, not bundled as 'general cleaning'
- Frequencies attached per task per area, not per building
- A defined standard of completion — what the area looks like when the task is done correctly
- Explicit exclusions, so both sides know what is not covered
- The inspection method and cadence that will be used to verify it
The exclusions matter as much as the inclusions
A scope that lists only what is included creates an argument every time something falls outside it. Naming the exclusions up front — high-access glass, post-construction debris, biohazard response, specialty flooring treatments — turns a future dispute into a line item that can be priced when it is needed.
If the scope cannot be inspected against, it is not a scope. It is a hope with a price attached.
How to test the scope you already have
Take your current contract and pick one line at random. Ask whether a new employee could read it and know exactly what to do, and whether an inspector could read it and know exactly what to check. If the answer to either is no, that line will eventually produce a disagreement.
Rewriting a scope mid-contract is easier than most operators expect. It usually costs nothing, because the work is already being performed or already being skipped — writing it down simply makes which one is happening visible.