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 billing notification recovery workflow
- 01
Open Billing notifications and filter delivery history to failed or queued records.
- 02
Expand the delivery detail and read the latest provider-facing failure state.
- 03
Use the permitted retry, resolve, restore, or suppress action for that notice.
- 04
Follow the linked invoice or report and confirm whether the next step succeeded.
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
Notification history contains mixed statuses and business consequences.
Prioritize a failed delivery with an active invoice or report dependency over an informational history item.
A notice is failed or queued.
Read the latest delivery detail before retrying so the action addresses the current failure.
A recovery action is available.
Use retry, resolve, restore, or suppression only when that action is allowed for the notice state and role.
A recovery attempt has completed.
Follow the linked invoice or report and close the item only after its follow-up state changes.
A common mistake to avoid
Retrying every failed notice without checking whether the recipient, status, or linked record has changed.
Before you mark the work complete
A delivery recovery log naming the notice, latest failure, permitted action, retry outcome, and linked invoice or report state.
- The delivery status and notice type are understood.
- The retry or resolve action is allowed for the current role.
- The linked invoice or report reflects the 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 billing notification recovery 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.
How can teams recover a failed billing notice?
Filter notification history for failed or queued records, open delivery detail, use the permitted retry or resolve action, and follow the linked invoice or report. The delivery record shows whether the next step succeeded or still needs review.
Put the workflow into practice
Granite's billing notifications history connects failed or queued deliveries to permitted recovery actions.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.