ATM route operations: weekly and monthly review rhythm for owners

What to take away

A route is not a driving job with a cash box in it. It is a small operation with a review cycle, a set of measured numbers and a relationship list.

The daily work has to happen, but the decisions that keep a route alive are made in the weekly and monthly reviews, and in the calls you schedule before anything is wrong.

The weekly review, and what it is for

The weekly review is where you look at the whole route at once, not one machine at a time. Block an hour. Pull the monitoring data for every machine and read it as a set.

Review the route as a whole, using the machine list to identify exceptions and patterns:

The output is a short list: what changes this week, and what you are watching for next week. A review that produces no decisions was a status meeting.

The monthly review, and the numbers that belong in it

The monthly review is where the route gets judged as a business rather than managed as a job. This is where downtime cost, cash utilisation and break-even volume per machine get compared across the fleet.

Put the monthly review on the same calendar day each month, after that month’s reconciliations are complete. Use the same review date and table structure each cycle so the fleet’s results can be compared month to month.

Use these six fixed columns, with one row per machine: Machine/site; hours unavailable, cause and time-to-know; estimated downtime cost; cash dispensed, average cash float committed and cash utilization; transactions in available hours, average transactions per available hour and net contribution per transaction; monthly fixed costs and break-even transaction volume.

Calculate estimated downtime cost as unavailable hours × average transactions per comparable available hour × net contribution per transaction. Treat this as estimated forgone contribution: it assumes the unavailable machine’s transactions were lost, so note if customers may have used another machine instead.

Calculate cash utilization as cash dispensed during the month ÷ average cash float committed during the month. This is a turnover multiple, not a percentage. Calculate break-even transaction volume as monthly fixed costs ÷ net contribution per transaction; net contribution should account for transaction-level variable costs.

The pattern across rows matters more than any single row. Three machines with the same cause in one month is a process problem, not three incidents.

Downtime metrics that actually change behaviour

Hours unavailable is the headline, but on its own it tells you what happened, not what to fix. Pair it with cause and time-to-know and the fix usually names itself.

Cause codes should be few and specific. These include cash-out, dispenser fault, card reader fault, and communications loss. Other codes are part on order, site closed or inaccessible, and processor hold. If a machine is down because you are waiting on a part, that is an inventory decision, not a repair decision.

Time-to-know is the metric most operators skip, and it is usually where the money is. A machine that is empty for six hours and reported by the host was empty for six hours you did not know about.

Monitoring that alerts you in minutes instead of hours is worth more than most hardware upgrades, and it is the cheapest downtime reduction available.

Set a target for time-to-know and hold yourself to it. Two hours is a reasonable starting point for a monitored machine; the right number is whatever your sites and your monitoring can actually deliver.

Scheduling host contact before it is needed

Host contact scheduled only when something is wrong is a complaint call, not a relationship. The operator who calls in a good month is the one who keeps the placement when a competitor walks into the venue.

Put every host on a contact calendar. Monthly for high-traffic sites, quarterly for the rest is a workable split. The call is short: how the machine has performed for them, anything they have heard from customers, and a reminder of who to call when something looks wrong.

Two things come out of these calls almost every time. Early warning on a lease or ownership change at the venue, and early warning that someone else has been asking about the space. Both are cheaper to handle in a scheduled call than in a termination notice.

Scaling signals, and the cash float that limits them

The signal to scale is not a machine count. It is a set of symptoms: unplanned trips appearing in the week, reviews slipping, hosts reporting faults you did not know about, and reconciliations running late.

Every added machine needs a float, and the float is tied up until the machine dispenses it back.

If your vault cash and your replenishment cycle cannot cover a new site without starving an existing one, the route is expanding past its float, and the symptom will be cash-outs on machines that were previously fine.

Run the arithmetic in your own figures before adding a site. Take the new machine's expected daily dispense, multiply by the days between your replenishments, and that is the float the site needs.

Add the float already committed across the route and compare the total to the cash you can actually keep available. If the total exceeds it, the next site is a financing decision, not a route decision.

The other scaling lever is the cash-in-transit contract. Moving from self-carried cash to an armoured carrier changes the cost structure and the risk profile at once. Name a licensed CIT carrier and your insurer in that conversation, and take their terms as the operating rule.

When the process has to be written down

A route that lives in one person's head fails the first week that person is unavailable. The written version does not need to be long. It needs to be current and findable.

Where the route sits in licensing and reporting terms is mapped in the licensing and compliance overview. Registration as a money services business runs through FinCEN and, in most states, a state banking or financial institutions regulator. Whether a specific operation must register, and under which exemption if any, is a question for licensed counsel, not for a guide.

Records, retention and the paper trail behind the numbers

The monthly review is only as good as the records feeding it. Visit logs, fault logs, reconciliation notes and host contact dates are business records, and they have a retention life.

The IRS guidance on the records a business should keep sets out what has to sit behind what your books report.

Tax treatment, depreciation elections and 1099 obligations for your own business go to a CPA.

The systems holding this data are business systems and worth securing like ones. The NIST small business quick-start guides are a practical starting point for a small operation with no dedicated IT staff.

Banking relationships sit inside a risk-based review as well, and the expectations banks apply to independent ATM owners are described in the FinCEN statement on independent ATM operators. Read it before a bank asks you about it.

Where the rest of the decisions live

The review rhythm only pays off if the underlying decisions are sound. Site choice determines how often a machine is unavailable and how expensive each visit is, and the trade-offs are set out in the site selection guide.

What each stop can carry, and what surcharge and interchange leave behind, is the arithmetic in the pricing and profit guide.

And how a route earns as it grows, including when to bring in a CIT partner, is covered in the startup and market overview.

Common questions

How often should the whole route be reviewed?

Weekly for operational decisions and monthly for financial ones. The weekly review changes what happens in the next seven days; the monthly review changes what you believe about each machine. Skipping the monthly review is how a route ends up with sites that have quietly stopped earning.

What is a reasonable time-to-know target?

Whatever your monitoring can deliver, held consistently. Two hours is a common starting point for a monitored machine. The number matters less than measuring it, because time-to-know is the only downtime metric you can improve without touching the hardware.

How do I know when to stop adding machines?

When the float cannot cover another site without causing cash-outs elsewhere. Run the arithmetic on expected daily dispense and your replenishment interval, add the float already committed, and compare it to the cash you can keep available. If it does not fit, the next site is a financing decision.

Who do I ask about registration and tax treatment?

FinCEN and your state banking or financial institutions regulator for registration questions, through licensed counsel. The IRS and a CPA for tax treatment, depreciation and 1099 obligations. No guide can answer those for a specific business, and the answer varies by state.