What a completed review should leave you with
A requirement policy record that states the document guidance, required and blocking behavior, due timing, renewal rule, and reminder owner.
Evidence to collect
- Saved requirement fields, guidance, first due date, and renewal lifetime.
- Required and report-blocking decisions with their intended owner.
- Example obligation or coverage state produced for an affected franchise.
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.
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.
Manage the work in Granite
Granite's document requirements editor turns organization guidance and due rules into franchise obligations.
Open dashboard ↗