Find Where Your Tunnel Is Losing Cars and Fix It
A car wash has two capacities and operators usually only know one. The tunnel is rated for a number of cars per hour, and on a Saturday after rain you feel every one of them. But the pay station, the loader, the member lane, the vacuums, and the crew each have their own ceiling, and on most sites one of those — not the tunnel — is what actually turns cars away or leaves hours half empty. This guide uses your controller and pay-station data to find which constraint binds at which hour, strips out the weather so you can see habitual dead zones from rain-driven ones, checks whether members are crowding out retail at peak, measures what the vacuums and detail bays are really doing, and puts a labor cost on every car by hour. Then it picks one leak and runs a 30-day test on it.
What You’ll Get
- A throughput map: rated tunnel cars-per-hour vs. actual by hour and day, with the binding constraint named for each block
- A weather-adjusted hourly capacity baseline that separates habitual dead zones from rain effects
- A member-lane vs. retail-lane mix analysis showing where members help and where they crowd out paying retail
- Vacuum and detail bay utilization with a dollar value on idle time
- Labor cost per car by hour, with the blocks that run below breakeven flagged
- A 30-day test plan for the single biggest leak and a monthly capacity review
Step-by-Step Guide
Pull tunnel, pay-station, lane, and labor data for 90 days
Get the four data sources side by side before asking AI anything. The controller and the pay station tell different stories, and the gap between them is often the finding.
Data you need
From the tunnel controller (DRB, Sonny's/ICS, WashCard, or similar): cars per hour by day, and the conveyor's rated or set cars-per-hour. From the pay station or POS: transaction timestamps with lane (member/RFID vs. retail), package, and amount. From the schedule: staff on the clock by hour and role, with hourly wage. From memory or a free weather-history site: rain days and the 1–3 days after each. If you have vacuum timers or detail bay tickets, pull those too — if not, note that and estimate from observation.
I run a [express / flex-serve / full-service] car wash and I want to set up a capacity audit. Help me get the data in shape before analyzing it. My site: - Tunnel rated capacity (cars per hour at current conveyor speed): [NUMBER] - Lanes: [e.g. 2 pay stations + 1 member/RFID lane] - Free vacuum spaces: [NUMBER] · Detail or prep bays: [NUMBER] - Hours: [e.g. 7am–8pm, 7 days] - Membership program: [yes/no, member count] What I can export: [describe — e.g. "controller gives cars/hour by day; pay station gives timestamped transactions with lane and package; I have the weekly schedule with wages; no vacuum data"] Here is a sample of each source: [PASTE 20–50 ROWS OF EACH] Please: 1. **Design one combined hourly table** — for every hour of every day in the 90 days: cars through the tunnel, retail transactions, member scans, revenue, staff on clock, labor dollars, and a weather tag (rain day / hangover day 1–3 / normal) 2. **Tell me what's missing** and the cheapest way to fill each gap (e.g. estimating vacuum use from a week of tally marks) 3. **Flag data problems** — hours where tunnel counts and pay-station counts disagree by more than 10%, and what usually causes that (rewash, member scans not logged, pay-station outage) 4. **Give me the cleanup steps** in the order to do them, so I can build this table in a spreadsheet in under an hour
Find the binding constraint: tunnel vs. pay station vs. loading
Most operators assume the tunnel is the ceiling. Often it is the pay station — a 45-second transaction on two stations caps you well under what the conveyor could run.
I want to know what actually limits my throughput at peak. My combined hourly table: [PASTE OR SUMMARIZE FROM STEP 1] Tunnel rated capacity: [NUMBER] cars/hour Pay stations: [NUMBER], average transaction time (if known): [SECONDS] — if unknown, say so and I'll time ten Member/RFID lane: [yes/no], average scan-to-gate time: [SECONDS] Loader/prep staff at peak: [NUMBER] Please analyze: 1. **Theoretical ceiling per stage** — tunnel, pay stations, member lane, loader — in cars per hour, from the numbers above 2. **Actual peak throughput** — my best 10 hours in the 90 days, and how they compare to each ceiling 3. **Which stage binds** — at peak, is the constraint the conveyor, the pay stations, the member gate, or loading? Show the reasoning 4. **The cost of the bottleneck** — cars per hour I'm losing at peak and roughly what that's worth in revenue on a hangover Saturday 5. **Cheapest fixes for the binding stage** — e.g. a pay-station attendant with a handheld at peak, member-lane signage, pre-selling packages in the queue, conveyor speed change (with the quality trade-off spelled out) 6. **A "queue abandonment" estimate** — a way to measure cars that pull out of the line, and what it would take to observe that for one weekend
Pro guide
Unlock the full playbook.
This guide has 6 steps — prompts, frameworks, and templates built for your industry. Unlock for $5.
one-time, unlock this guide forever on this browser. Secure checkout via Stripe.
More guides
More for Car Wash
Build an Unlimited Wash Membership That Prints Recurring Revenue
A complete membership program — pricing and tier design, financial modeling across adoption scenarios, full launch plan with staff scripts and signage, 90-day optimization cycle, and a retention system.
Build a Weather-Smart Demand and Staffing Plan
Turn weather from an unpredictable disruptor into a planned variable — demand forecasting, staffing schedules that match actual volume, dynamic chemical and labor cost control, and a rain-week revenue protection playbook.
Design an Upsell System That Increases Average Ticket
Move customers up the menu from base wash to premium — menu engineering, pay-station UX, staff upsell scripts, and targeted promos for light-wash buyers.