Record when the wash could not provide normal service, then match those periods to sales, member activity and repair records. Keep actual refunds and costs separate from estimated missed contribution. A closed hour does not prove an hour of lost demand. A completed repair does not prove that future outages will disappear.
- Define full closure, reduced capacity and unavailable packages separately.
- Reconcile event timestamps with the wash’s scheduled operating hours.
- Distinguish missed retail sales from prepaid membership visits.
- Keep estimated contribution and proposed earnings adjustments visible.
How should the event and unavailable time be defined?
Define downtime by the service unavailable during scheduled operating hours. Distinguish complete closure, reduced capacity and missing package components rather than assuming every fault has identical economics.
The operations hub connects this review with staff, service and operating records. Give each event one ID and use it on the incident report, service ticket, manager notes and accounting support. That link lets another reviewer follow the history. The file should not depend only on what the owner recalls.
Keep observed symptoms separate from a confirmed cause. Staff may report that a machine stopped; a qualified technician may later identify why it failed. Keep both dates and the source of each statement. An early description in the sale file does not become a technical diagnosis without supporting evidence.
Collect start, response and restoration times with their timezone and precision. Compare them with scheduled hours; overnight repairs do not automatically equal customer-facing closure.
When two faults overlap, count the shared closed time once. Keep separate repair tickets for each fault, but combine overlapping periods when counting hours of lost service. Adding both durations can overstate the closure. Check that the total does not exceed the hours the wash was scheduled to open.
Include temporary service only when it was approved and recorded. Show what customers could buy or use, which packages were restricted and what fault remained. A period with reduced capacity is neither normal service nor a full closure. Keep that distinction visible when counting lost hours and estimating sales.
What evidence belongs beside each event?
Use a compact register that distinguishes observations, financial records and unresolved questions. The following worksheet is an original diligence aid, not a manufacturer maintenance standard or a guarantee that a particular dataset exists.
| Event field | Supporting record | Analytical question |
|---|---|---|
| Affected service and interval | Incident and operating logs | Was the wash closed or partly available? |
| Repair response and work | Provider ticket and invoice | What was assessed and completed? |
| Transactions and visits | Dated POS and access exports | Which customer activity changed? |
| Credits and refunds | Provider and settlement records | Which cash amounts were actually returned? |
| Follow-up operation | Subsequent logs and reviewer notes | What evidence supports the resolution? |
Show missing fields rather than filling them with estimates that look exact. An invoice may be dated after the fault, and a late service ticket may not prove when the wash first closed. Explain what is unknown. Carry that uncertainty into any estimate of costs or missed sales.
How should comparable demand inform missed contribution?
Compare the affected hours with supported periods that had similar operating conditions. Review weekday, season, weather, promotions and access changes; a Saturday peak is a weak comparison for a weekday morning.
The peak-queue and membership-capacity guide separates service capacity from customer arrivals. A machine’s rated output does not prove that enough customers would have come to use it during the outage. Use observed demand. Explain its limits when estimating sales for the closed hours.
Show a range when the records cannot prove what would have happened without the outage. Keep the comparison periods in the file and explain why others were excluded. Let reviewers repeat the estimate and compare results using other periods.
In a fictional example, twenty estimated missed retail purchases at twelve dollars imply $240 of gross revenue. An assumed avoided variable cost of three dollars per purchase implies $180 of missed contribution before other event-specific effects.
Those figures are not industry benchmarks or observations from an actual wash. They assume the purchases would have occurred and were not recovered later. If ten customers instead return the next day, that changes the permanent-loss estimate. Paid staff time may remain, while chemical consumption may fall; costs need their own evidence.
Before proposing an earnings adjustment, assess costs avoided, sales made later and added expenses. Keep estimated missed revenue in a scenario until the assumptions have support. Correct math does not settle the earnings question. Explain which effects are recorded and which depend on estimates of customer demand or costs.
How should membership activity be treated?
Access records show member usage, while billing records show charges and cash collected. Review actual credits, refunds, cancellations and later visits, because a missed included wash does not necessarily reduce the payment received for that month.
Use the pay-station and wash-data guide to identify available exports and their definitions. Check whether a recorded entry attempt represents a completed wash, a denied entry or a duplicate event. Provider-specific fields should retain their original meanings through the analysis.
Review communication and billing changes around the event without asserting causation from timing alone. A cancellation following an outage may have another explanation. Supported customer records can clarify the issue, but the financial analysis should avoid exposing unnecessary personal identifiers.
Keep the member billing period separate from the outage interval and identify whether the provider applied any change to scheduled charges. Match any credited payment to its provider record and settlement before assigning a financial effect.
Which expenses occurred because of the outage?
Match repair invoices, emergency callout charges, freight, temporary equipment and actual customer credits to the event. Reconcile posting periods and payment support, distinguishing estimates, work orders, completed service and paid invoices as different obligation stages.
The IRS recordkeeping guidance describes maintaining business records and supporting documents. It supplies financial-record context, not a rule that a repair is removable from acquisition earnings. The buyer’s reviewer must assess the actual accounting and proposed treatment.
Do not count a supplier credit both as a reduction of repair expense and as separate event income. Similarly, an insurance receipt and an assumed reimbursement need distinct treatment. Reconcile the entries to the books before placing them in a bridge or a future cash forecast.
Show the gross invoice and each credit in one reconciliation using the same event identifier and period. Confirm whether the credit has been received or remains conditional before using the net amount.
How should maintenance and repair confirmation be reviewed?
The DOE operations and maintenance overview describes reactive, preventive, predictive and reliability-centered methods and the use of performance data. Its federal-facility context provides general upkeep concepts, without setting a wash-specific outage rate or proving how much earnings a repair will restore.
Compare the recorded upkeep plan with repeat faults. Ask whether the same machine, symptom or service issue appears again and whether the repair addressed the assessed cause. Keep proposed changes separate from results seen after the work.
The maintenance and capital-records guide helps organize this history. A repeat fault may need ongoing service, capital work or another qualified assessment. Show that open question in the event review. Do not remove all past costs and assume that the wash will run without future outages.
Use qualified staff who know the instructions for the installed equipment. The SONNY’S hydraulic power-pack manual calls for trained personnel and restricts unauthorized changes. Those instructions apply to that model. They are not a universal repair method for every wash system.
Request the assessment and proof of completed work in the deal file. Do not direct staff to bypass safeguards or test unsafe operation. Record who approved temporary service and what remained unavailable.
How should the buyer use the completed analysis?
Use the completed review to separate recorded costs and receipts from estimated missed contribution and open reliability questions. Carry supported duties and costs into the buyer’s model, showing their evidence, ownership assumptions and unresolved conditions.
- Reconcile event intervals, actual sales and supported expenses to the historical records.
- Label estimated missed contribution with its comparison periods and assumptions.
- Separate unresolved reliability questions from proposed financial adjustments.
- Carry supported continuing costs and capital needs into the buyer’s forecast.
Retain the event register alongside the financial bridge and service documents. The useful result is a traceable explanation of what happened, which financial effects are recorded and which remain estimates. Price, reserves and closing responsibilities can then be reviewed against that evidence without promising that future operation will be uninterrupted.
Assign each open item to its financial or technical reviewer. State how long the wash was observed after a repair and what evidence supports a claimed improvement. Update the log if another outage occurs before closing.