What changes in electrical services operations
Electrical service groups coordinate branches that may handle inspections, repairs, installations, and recurring programs. Corporate staff need a reliable way to compare what each branch reported with the unit rule that governs it. A focused operations record links the branch, period, quantity, price source, supporting files, and review state so a discrepancy can be resolved without losing context.
Watch for these gaps
- Blending installation projects with recurring inspection units
- Leaving a local override in place after the underlying program changes
- Assuming every branch uses the same currency or unit label
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 electrical services, use branch directory with assigned manager and active or archived state; inspection, repair, or program-unit quantities by period; price overrides and reviewer changes tied to a specific branch row 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 branch and program pairing before looking at amounts. Check that the quantity represents the configured work unit, that any override is intentional, and that the effective price is the one used for the open period. Review archived branches separately, resolve version conflicts by reloading, and keep a short business reason with every exception.
Download the electrical services review worksheet →A situation to work through
Imagine a multi-state electrical group reviewing a monthly inspection program. The corporate reviewer selects the rule, searches for a branch, and sees the base organization price, any branch override, and the effective amount beside the reported quantity. The reviewer can save a corrected row through its preview, while the branch's existing period entry remains version-aware and traceable.
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.