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 sales report issue review workflow
- 01
Open the submitted report from the reporting worklist or franchise record.
- 02
Read the calculation status and inspect each warning in its source context.
- 03
Correct the underlying report data or route the issue to an authorized reviewer.
- 04
Recheck the report status before using it as billing input.
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 warning explains a condition that the reviewer has checked and accepted.
Record the warning as informational and continue the review when it does not change the reported result.
The warning points to data that would change the report outcome.
Correct the source data and request a fresh calculation when the warning identifies an input or mapping error.
The warning is ambiguous or requires a decision outside the reviewer's authority.
Escalate with the report context attached when the reviewer cannot determine the intended treatment.
The source or decision has been changed.
Close the issue only after the new calculation or reviewer decision is visible on the report.
A common mistake to avoid
Clearing a warning without recording why it was accepted or what source value resolved it.
Before you mark the work complete
An issue log that ties every report warning to its source location, disposition, reviewer, and resulting status.
- The report and reporting period are the intended source.
- Every warning has a readable explanation.
- The final calculation status is visible before follow-up.
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 sales report issue review 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 happens when a sales report needs review?
Open the report's calculation and warning details, inspect the source context, and resolve the issue before relying on billing output. Granite keeps the report status visible so authorized teams can distinguish a warning, a review state, and a completed calculation.
Put the workflow into practice
Granite keeps sales report warnings and calculation status with the review handoff for authorized teams.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.