What changes in landscaping services operations
Landscaping franchises often combine recurring grounds care, seasonal projects, and weather-driven schedule changes. A network needs to know which locations reported their service units and where a quantity differs from the configured rule. Use location-level records with period status, owner, price source, and supporting requests so the central team can follow up on exceptions before the cycle closes.
Watch for these gaps
- Using an empty field to mean both postponed work and no work
- Rolling a seasonal project into a recurring route quantity
- Failing to revisit an open entry after a weather-driven correction
A repeatable required document upload workflow
- 01
Open the franchise document center and select the specific required obligation.
- 02
Read the requirement guidance, due state, and any reporting-blocking notice.
- 03
Upload the current document version with the information the requirement requests.
- 04
Check the resulting review and coverage status before closing the task.
Bring the industry records into the review
For landscaping services, use location roster with territory owner and seasonal operating status; recurring route or service-unit quantities by cycle; weather-related corrections 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 franchise has more than one document requirement or version.
Open the exact obligation and read its guidance before selecting a file.
The selected file matches the obligation's instructions.
Upload the current document version when its content and date satisfy the requirement.
The document needs acceptance or the file does not meet the stated guidance.
Send the item for review or correction when the upload is present but its coverage state is unresolved.
The upload and review action have finished.
Return to the obligation and confirm current coverage before closing the task.
A common mistake to avoid
Uploading a file without checking that it belongs to the selected obligation and reporting period.
Before you mark the work complete
A document coverage record linking the obligation, uploaded version, review result, owner, and date coverage was restored.
- The upload matches the requirement guidance.
- The current version has the expected review state.
- The obligation reports coverage after the upload.
Separate recurring care from seasonal projects and decide how postponed work is represented before collecting counts. Check that active locations have a current owner, review blank and zero values independently, and verify any price override against the rule. Before finalizing, inspect overdue rows and confirm each correction has a clear period-specific reason.
Download the landscaping services review worksheet →A situation to work through
A landscaping operator can open the current cycle, search a location, and see its recurring route quantity alongside the organization and effective prices. A manager can leave the row blank while work is unconfirmed, enter zero when no charge is due, or submit a corrected count after a weather delay. The review history keeps each state change tied to the cycle.
Apply the required document upload 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 does a franchise satisfy a required document?
Open the obligation, read its guidance and due state, upload the current document version, and check the resulting review and coverage status. A historical upload alone does not prove that the current obligation is covered.
Put the workflow into practice
Granite's franchise document center lets authorized users upload the current version and check coverage.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.