What changes in plumbing services operations
Plumbing franchises work across emergency calls, scheduled maintenance, and project-based repairs. Their records become easier to manage when the central team can distinguish location assignments, service units, and period state. Give branch managers a clear path to report quantities and corporate reviewers a clear path to investigate exceptions without editing the underlying rule by accident.
Watch for these gaps
- Treating emergency call volume as the same unit as scheduled maintenance
- Changing a branch assignment to work around an unreviewed quantity
- Finalizing an entry while a correction request is still unresolved
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 plumbing services, use branch and territory assignments with current operating status; scheduled service or maintenance-unit quantities for each cycle; correction notes and audit history for changed period entries 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.
Map each branch to the service rule it actually uses, then check the cycle's unit label and due date. Review open and overdue entries separately from completed work, and do not use a pricing override to correct a quantity mistake. Save only after the preview is clean, and record a specific reason for any reopen or void action.
Download the plumbing services review worksheet →A situation to work through
A plumbing network can review its open cycle by branch, search directly for a franchise, and see which rows are ready, overdue, or still incomplete. The reviewer compares the saved service count with the local manager's submission, makes a bounded correction when needed, and keeps the original period and version context visible before the entry is finalized.
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.