Car wash site access and attainable throughput evidence

Separate road counts, arrivals, service bottlenecks and waiting space, then test a fictional four-hour operating pattern.

New York Car Wash Broker editorial teamContent reviewed October 17, 2026Educational guidance

Passing traffic, access, customer arrivals and completed washes are different quantities. A useful site review connects them through evidence without assuming a universal capture rate or treating equipment capacity as demand. This original model tests four one-hour periods and makes the unserved work visible.

Hourly service capacity and backlog model

Four consecutive one-hour periods. Enter arrivals independently of road traffic. Both cases share the same arrivals and whole-line downtime; only the alternative finishing rate changes.

Private on-device planning inputs
Hour 1: arrivals and downtime
Hour 2: arrivals and downtime
Hour 3: arrivals and downtime
Hour 4: arrivals and downtime

Inputs remain in this page’s browser memory. No upload, provider connection, automatic storage or input tracking. Save locally before leaving or refreshing. Use aliases and non-sensitive reference IDs; keep records, credentials and personal information in your own authorized systems.

Identify what each count measures

MeasureEvidence to recordWhat it cannot establish alone
Road trafficStation, road segment, count year, direction and measureActual entry opportunities, customer demand or wash conversion.
Site arrivalsDated observations or appropriately defined operating recordsThat every arrival can wait, enter or complete the service.
Service capacitySupported entry, wash and finishing/exit rates under stated conditionsDemand, safe staffing or performance during a particular outage.
Completed serviceA consistent completion count with timestamps and downtime contextEvery earlier arrival or the maximum queue during the period.
Usable waiting spaceA supported site plan and professional observation of operational constraintsPermission to block crossings, emergency access or a public road.

NYSDOT’s Traffic Data Viewer provides traffic-station and road-segment context, including AADT and other count information. Save the station, measure and observation year rather than copying a number without its definition. An annual average daily road count is not an hourly wash-arrival forecast. This tool deliberately has no AADT-to-customers conversion input.

Review access before attaching value to capacity

Identify the road owner and approved entrances, exits, turning movements and conditions. Observe pedestrian routes, delivery activity, conflicting service movements, parking, finishing areas and emergency access. Compare the actual layout and proposed operation with the relevant approved documents and professional review.

NYSDOT’s commercial-access guidance addresses new or modified state-highway access and relevant use or development changes. Its current highway-permit page describes an online application route. That state process is not a universal local-road process or a dimensional queue rule. The actual highway or municipal authority and site professional must establish the applicable review path.

Use the parcel screening register to tie each source and question to the correct site and proposal. An existing driveway, a drawing from a different project or a neighbor’s entrance does not establish the buyer’s rights or the feasibility of a changed plan.

Use the limiting stage, with explicit downtime

The simple chain has an entry/payment stage, wash stage and finishing/exit stage, each entered as a supported vehicles-per-hour capacity. The limiting service rate is their minimum. Actual systems can have parallel lanes, staging constraints and interruptions that need a more detailed model; do not divide or combine published equipment specifications without understanding their operating conditions.

Limiting rate = min(entry capacity, wash capacity, finishing/exit capacity)
Available whole-vehicle slots = floor(limiting rate × (60 − downtime minutes) / 60)
Completed = min(opening backlog + arrivals, available slots)
Closing backlog = opening backlog + arrivals − completed

Each row is one hour. Downtime is modeled as a whole-line loss for that hour, and fractional available slots are rounded down. Unused capacity does not carry forward. All entered arrivals are assumed to wait. There is no abandonment, access blocking, random arrival pattern or feedback from insufficient waiting space. Those limitations can be decisive in a real layout.

Reproduce the fictional four-hour case

The invented entry rate is 90 vehicles/hour, wash rate 120, and base finishing/exit rate 60. The base bottleneck is therefore 60. Opening backlog is zero. Arrivals over four hours are 50, 80, 100 and 40, totaling 270. The second hour loses fifteen minutes to whole-line downtime; the others lose none.

HourArrivalsAvailable base slotsBase completedBase ending backlogAlternative ending backlog
150605000
28045453513
310060607523
4406060550

The base completes 215 vehicles and ends with 55 unserved. Its highest hour-end backlog is 75 in hour three. Against an explicitly entered twenty usable waiting spaces, that endpoint is 55 vehicles beyond the entered storage assumption. This does not tell those vehicles to wait on the road; it identifies that the assumed arrivals and service pattern cannot be accommodated as entered.

Improve one stage and check what still fails

The alternative increases only finishing/exit capacity to 90. Entry then shares the bottleneck at 90. The downtime-adjusted second hour provides 67 whole slots because 90 × 45/60 is 67.5 and the model rounds down. The alternative completes all 270 arrivals by the end of hour four, but reaches an hour-end backlog of 23 in hour three.

Against twenty entered spaces, that intermediate endpoint still exceeds storage by three vehicles even though the final backlog is zero. A successful end-of-day total can therefore hide an earlier operating problem. The alternative does not establish that the capacity change is physically attainable, permitted, affordable or supported by staff and equipment.

Do not confuse hourly endpoints with the maximum queue

A short burst of arrivals can exceed available waiting space and later clear within the same hour. The model’s highest endpoint is not a maximum queue prediction, and a zero endpoint difference is not evidence of safe circulation. Observe shorter intervals where timing matters and have the traffic or site professional choose the appropriate analysis.

Similarly, full unused slots earlier in an hour cannot necessarily serve vehicles that arrive after closing or during the outage. This simplified period arithmetic intentionally omits that sequencing. Retain timestamps, service-completion definitions and the stage affected by each interruption before using observed data to support a more detailed case.

Connect feasibility to the operating and investment plan

Request equipment conditions and rate evidence, observe the full service sequence, and identify whether any apparent bottleneck is payment, wash processing, finishing, exit conflict or unavailable staff. A proposed equipment purchase can move the bottleneck rather than remove it. Obtain design, installation and staffing evidence before treating the alternative as an achievable improvement.

Keep arrivals as an explicit scenario supported by operating evidence or a professional demand analysis. Do not multiply AADT by a guessed percentage and treat the result as a verified business forecast. Feed supported project costs and downtime into the equipment reserve tool and cash plan, and test person-level work in the owner replacement planner.

Download the fictional four-hour base and alternative case v1

Download the blank access and service observation log

Continue with the traffic and site-selection guide and conversion guide. No generic AADT, capture-rate or queue-space minimum is supplied.

Review the plan when the operating assumptions change

The buyer and operating lead maintain observations; the traffic, site and equipment professionals review the relevant feasibility and safety questions. Recheck authorities and plan versions when access, layout, service mix or equipment changes. The website editor reviews this method annually. This arithmetic model is not a traffic engineering study, land-use opinion or permission to operate.

Questions before using the result

Does the smallest equipment rate equal actual completed washes?

No. It is the model’s limiting service-rate assumption. Arrivals, downtime, time sequencing, staff, layout and other constraints affect actual completions.

Does zero final backlog mean the site has enough waiting space?

No. The fictional alternative clears by hour four while exceeding the entered waiting-space assumption at the end of hour three. Shorter intra-hour peaks can be larger still.

Where does the arrival forecast come from?

You enter it. The model does not derive arrivals from road traffic, calculate a capture rate or predict demand.

Can backlog beyond entered spaces wait on the street?

The tool grants no permission and assumes no such arrangement. Treat it as unresolved feasibility and obtain the relevant professional and authority review.

Compare service burden and contribution

Compare service burden and contribution with the method, private tool and reproducible fictional case. Reconcile periods and amounts before carrying a result into another model.

Connect operating evidence and the next decision

Retail package pricing and mix. Keep periods and definitions consistent when manually carrying results between tools.

Sources and scope

Official and original sources checked October 17, 2026. These sources support the identified rules and methods; they do not verify a particular business or property.

Continue your review

Verify the revenue · Normalize earnings · Model the cash flow

A clearer next step

Bring the questions.
Start with a conversation.

Discuss an acquisition, sale or valuation question and identify the information needed to move forward.

Book a conversation