What changes in property restoration operations
Property restoration groups manage branches handling water, fire, mold, and rebuild work with different reporting rhythms. Their central team needs a business view that separates recurring program units from project activity and identifies branch exceptions early. Keep each period tied to its branch, rule, quantity, price source, supporting document request, and review state so urgent work does not erase ordinary controls.
Watch for these gaps
- Using project milestones as recurring service quantities
- Letting an urgent job bypass period ownership and review
- Leaving a temporary branch override in place after the project ends
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 property restoration companies, use branch directory with service mix and operating status; program or service-unit quantities by reporting period; project-period exceptions and supporting document requests 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.
Separate recurring program work from project milestones before checking amounts. Confirm the branch owner and period, then review whether any override is temporary and tied to the right cycle. Use a preview before saving, follow up on missing documents, and keep urgent exceptions visible until the accountable reviewer closes them.
Download the property restoration review worksheet →A situation to work through
A restoration operator can select a program, search a branch, and see the reported unit count, organization price, local override, and effective amount together. A project-related correction can be documented without rewriting the recurring rule. The operator reviews the row's current version before saving and keeps the period status visible while a supporting document is still requested.
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.