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 billing run simulation workflow
- 01
Open Billing simulation and choose the authorized organization or franchise scope.
- 02
Select the reporting context and start a preview without creating invoices.
- 03
Review eligible, deferred, blocked, and projected results in the preview.
- 04
Correct setup or data issues and rerun the preview before handing off to processing.
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 preview scope does not match the intended run.
Stop and correct the selection when the simulated organization, franchise set, or reporting context is wrong.
The simulation returns multiple outcome groups.
Review eligible, deferred, and blocked items separately so unresolved work is not hidden in the total.
The preview exposes a blocker or unexplained total.
Correct setup or data issues and rerun the simulation when projected output is incomplete or unexpected.
The eligible output and remaining deferrals are understood.
Sign off the exact simulation scope and time before handing it to processing.
A common mistake to avoid
Assuming a simulation created invoices or charges when it only previewed what a run could do.
Before you mark the work complete
A simulation signoff that records scope, period, eligible and deferred work, blocked items, projected totals, and rerun decisions.
- The simulated organization or franchise scope is correct.
- Eligible, deferred, and blocked entries are understood.
- Projected totals are reviewed before approval.
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 billing run simulation 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 is billing simulation used for?
Simulation previews eligible entries, deferred or blocked work, and projected totals before invoice creation. Teams can inspect the authorized scope, correct setup or data issues, and rerun the preview before approving processing.
Put the workflow into practice
Granite's billing simulation previews eligible, deferred, blocked, and projected results before processing.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.