What changes in hvac services operations
HVAC service networks manage maintenance plans, dispatch activity, replacement work, and seasonal demand across local branches. A corporate team benefits from a single operational view that distinguishes recurring plan units from project work. Keep branch assignments, period quantities, customer-facing documents, and billing readiness close together so high-volume seasons do not turn into manual reconciliation.
Watch for these gaps
- Counting a quoted replacement as completed service
- Using seasonal volume as a permanent saved quantity
- Missing a branch whose reporting period is open but overdue
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 hvac services, use branch roster with service territory and operating status; maintenance-plan or service-unit quantities by reporting period; period exceptions, approvals, and supporting work-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.
Check that each branch has the correct recurring rule and reporting owner. Review whether quantities represent completed maintenance units rather than proposals or appointments, and separate a temporary override from the saved organization amount. Before closeout, inspect overdue periods, confirm zero quantities explicitly, and retain the reason for any reopened or voided entry.
Download the hvac services review worksheet →A situation to work through
During a summer surge, an HVAC operator can select the current period, search for a branch, and see its maintenance quantity beside the organization price and local override. A branch with a blank quantity stays open for follow-up; a confirmed zero can be finalized intentionally. The team can then compare the period record with its supporting documents before preparing downstream billing work.
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.