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 document requirement setup workflow
- 01
Open organization document requirements and select the requirement to create or edit.
- 02
Set the document name, guidance, required state, and sales-report blocking behavior.
- 03
Choose the first due date, renewal lifetime, upload instructions, and reminder recipients.
- 04
Save the requirement and review the obligations it creates for affected franchises.
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 requirement's presence and its operational consequence are being defined.
Make the requirement required or optional according to the operating policy, and decide separately whether it blocks reporting.
The policy needs recurring coverage rather than one-time collection.
Set the first due date and renewal lifetime from the intended coverage cycle.
The document type has format, date, or content expectations.
Write upload guidance that a franchise contact can follow without needing the setup author.
The policy values are complete and affected franchises are known.
Review the resulting obligation behavior before publishing the requirement.
A common mistake to avoid
Using a global requirement policy to encode a one-franchise exception that belongs in the follow-up workflow.
Before you mark the work complete
A requirement policy record that states the document guidance, required and blocking behavior, due timing, renewal rule, and reminder owner.
- Required and report-blocking behavior are intentional.
- The first due date and lifetime match the policy.
- Reminder recipients and guidance are clear.
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 document requirement 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.
How are franchise document requirements configured?
Organization managers define the document guidance, required state, report-blocking behavior, due date, lifetime, and reminder recipients in one editor. After saving, the resulting obligations provide the operational follow-up for each affected franchise.
Put the workflow into practice
Granite's document requirements editor turns organization guidance and due rules into franchise obligations.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.