What changes in home cleaning services operations
Home cleaning franchises coordinate recurring visits, add-on services, territories, and local teams. Corporate operators need to see whether each territory has reported its activity and whether the configured service rule still matches the work being counted. A shared workspace turns territory follow-up, quantity review, billing preparation, and history into one repeatable operating flow.
Watch for these gaps
- Combining recurring visits and one-off add-ons into one unexplained total
- Finalizing a territory before its service count is confirmed
- Overlooking a franchise that changed ownership during the period
A repeatable unit-based billing rule setup workflow
- 01
Open Billing Rules and choose the unit-based rule family.
- 02
Set the organization price, unit labels, cadence, quantity mode, reminders, and payment destination.
- 03
Choose the franchise assignment policy and review the next complete billing cycle.
- 04
Resolve readiness blockers before activating the rule for future cycles.
Bring the industry records into the review
For home cleaning services, use territory roster with franchise status and operating contact; completed visit and add-on quantities for each billing cycle; open corrections, document requests, and period submission history as the evidence packet. Keep the franchise and reporting period attached to each record so a reviewer can follow the source without reconstructing the conversation.
What to do when the review finds a problem
The rule's recurring charge is being defined.
Set the unit price, label, and cadence together so the future charge has an unambiguous basis.
The rule can use changing quantities or a fixed configured quantity.
Choose a quantity mode that reflects where the cycle's count will come from.
The pricing and quantity decisions are complete.
Confirm assignments, reminders, and payment destination before activation.
The rule is ready for a future-cycle readiness check.
Review the next complete billing cycle and resolve blockers before publishing.
A common mistake to avoid
Using a quantity override to conceal a missing franchise assignment or unclear unit definition.
Before you mark the work complete
A unit-rule specification that states price, unit label, cadence, quantity mode, assignment policy, reminders, route, and next cycle.
- The unit price, cadence, and quantity mode are intentional.
- Assignments and payment destination are ready.
- The next cycle and activation blockers are understood.
Confirm the territory list and franchise status before reviewing quantities. Separate recurring visits from add-on work, look for blank values in otherwise active territories, and compare overrides with the organization price. Resolve stale rows before saving, then review the period history for any reopened or voided entry and the reason attached to that action.
Download the home cleaning services review worksheet →A situation to work through
Suppose a cleaning network receives cycle reports from forty territories. The operator can filter to one territory, verify visits and add-ons against the applicable rules, and see whether a manager left a quantity blank or entered zero. A correction can be saved with its expected version, while the period remains visibly open until the responsible team finishes review.
Apply the unit-based billing rule setup steps above to this situation. Record the original evidence, the unresolved question, and the person who can answer it before treating the item as complete. This is a planning example, not a customer result.
What does a unit billing rule need before activation?
Set the unit price and labels, cadence, quantity mode, assignment policy, reminders, and payment destination. Review the next cycle and readiness blockers, then activate only when the rule clearly explains the future franchise charge.
Put the workflow into practice
Granite's unit-based billing rules connect quantity settings and assignments to future billing cycles.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.