The document
A scope of work records the cleaning areas, tasks, frequencies, access conditions, and boundaries that have been discussed for a facility.
A commercial cleaning scope of work can identify the areas covered, tasks associated with those areas, task frequencies, access conditions, and service limits. It turns a general cleaning conversation into a document that can be reviewed when the facility or service needs change.
Start with the floors, suites, shared spaces, and service areas included in the work.
Areas are usually grouped by how they behave rather than by geography alone—restrooms together, break and food areas together, circulation space together—because tasks and frequencies tend to follow those groupings.
Each area group carries a list of tasks written plainly enough to be read the same way by two different people a year apart. The aim is recognizable description, not procedural depth.
Some tasks appear in several area groups with different associated frequencies. That is normal and is clearer than writing a single list that applies unevenly across a building.
Frequency is recorded against tasks rather than declared once for the whole building. Different areas legitimately carry different rhythms, and a document that flattens them can be harder to follow.
Where a frequency depends on a condition—a seasonal pattern, a building event, an occupancy change—the condition is stated alongside it rather than left implied.
The document records what the work depends on to happen at all: how areas are entered, which spaces are restricted, whether particular rooms are only available at certain hours, and which areas cannot be entered while occupied.
Boundaries between occupied-hour and after-hours coverage belong here too. Where a building uses both, the split is written down rather than held as a general understanding, since it is the element most prone to drift.
List what the service does and does not cover, including inaccessible areas and spaces handled by others.
Record how scope changes are requested and added so the document stays current.
Swipe or scroll horizontally to review every column.
| Component | What it records | Ambiguity it prevents |
|---|---|---|
| Areas | Floors, suites, shared and service spaces in and out | Disagreement over whether a space was ever included |
| Tasks | Plainly described work attached to each area group | Two readers interpreting the same line differently |
| Frequencies | How often each task recurs, per area | One building-wide rhythm being applied unevenly |
| Access and boundaries | Entry conditions, restricted areas, occupied vs after-hours split | Uncertainty about when and how areas can be reached |
| Service limits and change review | What is outside the arrangement and how it gets amended | Gradual expansion and a document that stops matching the building |
Continue exploring
Request information
Name the facility or the service question you are working through; a complete task list is not needed to begin.
Common questions
Detailed enough to be recognized consistently by different readers over time, and no deeper. Excessive procedural detail tends to go unread.
Rarely. Recording frequency per task and area reflects how buildings actually behave and holds up better than a single uniform rhythm.
Because unstated boundaries are where arrangements quietly expand. Naming what is outside the document keeps what is inside it meaningful.
Through the review path the document itself describes. Buildings change use, and a scope that cannot be amended cleanly falls out of date.
