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 sales reporting workflow
- 01
Open the assigned franchise reporting workspace and select the period that is due.
- 02
Confirm the period end date, choose the current sales report, and upload it.
- 03
Review warnings and calculation status before relying on the report downstream.
- 04
Submit the report when the source data and review state are ready.
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 selected period and source report describe different dates.
Pause and correct the selected period before uploading when the period end date does not match the source report.
The period end date and source file are aligned.
Upload the current source file and record its filename or version when the period is confirmed.
The report has warnings or a calculation state that still needs a decision.
Route the report to the assigned reviewer and hold submission while a warning or calculation issue is unresolved.
The report has passed the agreed review checks.
Submit it and record the owner and timestamp when the source data and review state are ready.
A common mistake to avoid
Treating a successful file upload as proof that the report has been reviewed and submitted.
Before you mark the work complete
A submitted-period packet that names the reporting period, source file, owner, review outcome, and submission time.
- The reporting period end date is correct.
- The uploaded file is the current source report.
- Warnings and calculation status have been reviewed.
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 sales reporting 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 should franchise teams submit sales reports?
Open the assigned reporting period, confirm its end date, upload the current report, review warnings or calculation status, and submit when the data is ready. Organization reviewers can then follow the same report in the reporting worklist.
Put the workflow into practice
Granite's sales reports workspace takes authorized teams from a reporting-period upload to review and submission.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.