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 franchise record review workflow
- 01
Search the franchise directory by the location name or other visible profile detail.
- 02
Open the matching franchise record and confirm the organization and access context.
- 03
Review the profile details and current reporting, billing, document, and service state.
- 04
Use the linked workspace that owns the next authorized operational action.
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
Search results contain ambiguous or duplicate franchise identities.
Stop and resolve the match before opening workspaces when the name or location could refer to more than one record.
A single record has been selected.
Confirm the organization and franchise context before reviewing details or taking an action.
The profile links to reporting, billing, documents, services, or team work.
Use the workspace that owns the next task instead of copying status into a separate tracker.
The record does not expose the action needed by the reviewer.
Record the missing handoff for follow-up when the expected workspace or current status is unavailable.
A common mistake to avoid
Acting on a familiar franchise name before confirming the location and active organization context.
Before you mark the work complete
A franchise record brief that confirms identity, active scope, current status, and the next linked operational workspace.
- The active organization and franchise are confirmed.
- The profile belongs to the intended location.
- Each linked workspace reflects the current access.
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 franchise record review 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.
Where do teams find a franchise's operational work?
Search the franchise directory, open the correct record, confirm the active scope, and use its reporting, billing, document, service, and team links. The record keeps the context together while each workspace owns its own actions.
Put the workflow into practice
Granite's franchise directory opens the profile and its reporting, billing, document, service, and team workspaces.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.