A Zelvari Flow field guide
How to handle extra cleaning requests without losing track of the scope
Turn “one more thing” into a clear task, price, and customer decision, with a practical request-and-response example.
Make the original agreement easy to see
An extra request is easier to discuss when both people can see what the visit already includes. Write a short checklist of included tasks, relevant exclusions, and the visit frequency. “Kitchen surfaces and sink” gives a more useful starting point than “everything in the kitchen.” Be specific about appliance interiors, dishes, laundry, and any other work you price separately.
The aim is a shared expectation, not a long list of reasons to say no. A customer may not know which tasks change the time required. A clear question before you begin can prevent an accidental recurring commitment.
Record the request before doing the extra work
Write down the requested task and whether it is a one-time extra or part of every future visit. Estimate additional cleaner-minutes across the whole crew: two people spending 15 minutes each means 30 cleaner-minutes. Record a proposed extra amount in the same currency as the job.
Keep this record separate from completed-visit time. A request is not work already performed, and an estimate is not an actual result. If you cannot assess the condition or time yet, say you need to confirm the scope and price before committing.
Offer a small set of clear choices
A useful conversation leaves room for the customer’s priorities. You do not need to assume that a higher total is their preferred answer. Explain what changes and let them choose an option you can deliver.
- Keep the original checklist and current price; leave the extra task outside this visit.
- Add the requested task at an agreed additional price, once or on a stated recurring schedule.
- Keep the current budget and agree which existing tasks to swap, reduce, or rotate.
A request and response you can adapt
Here is an illustrative one-time proposal, with an example price: “I can add the refrigerator interior to Friday’s visit for an additional $35, provided it is emptied before we arrive. That would be a one-time extra; our regular checklist and price would stay the same afterward. Would you prefer to add it, keep Friday’s original scope, or discuss a task swap within the current budget?”
Suppose the customer replies: “Yes, please add the refrigerator interior for $35 this Friday. I’ll empty it first.” Your internal record could say: “Approved — customer SMS received October 29, 2026; one-time refrigerator interior on the agreed Friday, additional $35, customer to empty it.” Keep the original message through your usual process. Do not use this illustrative reply as evidence of a real customer decision.
Keep a proposal separate from an approval
Before a reply arrives, the status is Draft or Proposed. Copying a note, sending it, or saving a proposed price does not establish approval. Record the actual response, its date, and the channel before marking an item Approved. A private note is your record of the conversation, not verified consent or an electronic signature.
If you change the task, amount, or recurrence after approval, confirm the revised proposal again. An approval of a $35 one-time task should not silently become approval of a $35 charge on every visit.
Carry the decision into the next visit
Once agreed, update the relevant checklist and quote yourself. After completing the work, log the actual time and supplies so the next estimate has better evidence. Keep one-off extras separate from the regular-visit baseline. If the recurring scope changes permanently, start a new baseline instead of mixing unlike visits and treating the average as the same job.
From reading to reviewing
Look at one recurring job.
Enter your own time, costs, and target margin in the free check. You can also see what the full toolkit includes and its current launch status.