Your walkthrough notes may contain room names, quick observations and phrases such as “usual cleaning.” Those notes are a starting point. Before pricing the work, turn them into a draft that another person can read and question.
A scope of work describes the work you are proposing. This article offers an organizing method, not a legal contract or a cleaning procedure. Use your own site observations and confirm the proposed arrangement with the client.
1. Give every area a recognizable name
Start with the areas that might be included. Use labels the client recognizes, such as “ground-floor meeting room” or “reception by the main entrance.” If your notes use abbreviations, expand them while the visit is still fresh. The person reviewing the draft may not have walked beside you.
Do not let a room’s appearance in your notes silently become an inclusion. You might have passed a storage room while discussing access. Mark the room as proposed, excluded or awaiting confirmation. That small distinction protects the conversation from an assumption neither person remembers making.
2. Replace broad labels with specific tasks
“Kitchen” identifies a place. It does not describe what you intend to do there. Break the proposed work into actions that can be discussed, then record the relevant limits. Use ordinary language and leave technical methods to appropriate procedures and training.
For an illustrative example, “wipe the accessible counter surfaces after agreed items are cleared” invites clearer discussion than “clean the kitchen.” It opens questions about preparation, access and what happens when items remain. Do not copy that wording into every job automatically; write what the actual site and proposed service require.
3. Put a frequency beside each task
A task without a frequency leaves a major planning question open. Record when the work is proposed and distinguish routine visits from periodic or separately requested work. If the client wants a task “as needed,” discuss who identifies that need and how it will be communicated.
Keep the proposed service schedule separate from the frequency of individual tasks. Three visits in a week does not necessarily mean every listed task happens three times. Read each row across: area, task, frequency and any condition. If one part is blank, treat that row as unfinished rather than filling the gap from habit.
- Area: where the task applies.
- Task: the work being proposed.
- Frequency: when that task is included.
- Condition: any agreed dependency or limit.
4. Capture the arrangements the work depends on
Access windows, keys, alarms, supplies and equipment can affect whether the proposed schedule is workable. Record who is expected to provide or confirm each item. Avoid collecting security credentials in a general worksheet that may be widely shared; agree an appropriate way to exchange those details.
Create a short open-questions list with an owner and a next step. A question such as “Can the meeting rooms be accessed during the proposed visit?” should not disappear inside a paragraph. When it is answered, update the scope and record the decision so the estimate and proposal use the same version.
5. Review inclusions, exclusions and uncertainties together
Read the draft as if you were the client. Could you tell what will happen, where and how often? Are exclusions clear enough to discuss? Have you labeled uncertain details as uncertain? A useful review makes disagreements visible before they become assumptions in a price.
Send or discuss the draft through your normal business process and keep the confirmed version with the estimate. If the client changes the scope later, review the time and costs again before updating the proposal. The document is most useful when it stays connected to the work you actually intend to price.
Take one room from your walkthrough notes and write a complete row: area, task, frequency and condition. Mark every detail you still need the client to confirm.