What changes in car washes operations
Car wash networks track locations, membership activity, wash programs, and seasonal operating changes. Their shared workspace should make it easy to find a location, understand which quantity rule applies, and see what still needs review. A clear distinction between saved location quantities, per-cycle entries, and effective prices prevents local exceptions from becoming permanent network assumptions.
Watch for these gaps
- Treating a paused location as a zero-producing active location
- Using membership totals when the rule counts completed washes
- Losing the reason for a temporary seasonal override
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 car washes, use wash location roster with active, paused, or archived state; membership or wash-program quantities by reporting cycle; location-level price overrides and change history 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.
Check location state before reviewing cycle quantities, especially after a pause or reopening. Confirm the unit label matches the source count, distinguish a saved quantity from a per-cycle entry, and review effective price after any override. Close the cycle only after overdue locations, deliberate zeros, and temporary adjustments have been addressed.
Download the car washes review worksheet →A situation to work through
A car wash operator can select a wash program, search for a location, and see the organization price, local override, effective price, and cycle quantity in one row. A paused location can remain visible for historical review without receiving new active work. When a count changes, the operator saves the row after previewing its current version and resulting amount.
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.