How to Bill for Equipment on Standby
Standby is where rental yards quietly bleed margin. A frac crew gets weathered out, a permit slips, the completion gets pushed — and your iron sits on the pad doing nothing while the customer assumes the meter stopped. If you have not decided in advance whether that idle time bills at full rate, at a reduced standby rate, or at nothing, you will decide it in an argument after the unit comes home. This guide walks through how standby actually unfolds on an oilfield location, when reduced billing is fair versus when full rate holds, and how to write the policy onto the contract so nobody is guessing when the gear goes quiet.
What standby actually means on a pad
Standby is not the same as a return. The customer still has your gear staged on their location, you still carry every risk that comes with iron sitting in someone else's yard, and that unit is unavailable to the next caller. What changed is only that the customer stopped using it. On an oilfield pad, this shows up constantly: a string of frac tanks staged for a job that gets bumped, a light tower lighting a site where work paused, mobile storage tanks holding fluid while the crew waits on the next stage. The unit is earning nothing for the customer, so they want relief. Fair enough — but idle on their pad is very different from back on your lot. Standby billing exists to price that gap honestly instead of pretending the gear came home.
Standby rate versus full rate: where to draw the line
The cleanest rule is to tie the rate to who caused the idle time and whether your costs actually dropped. If the customer chose to stage equipment early or hold it for convenience, that is full rate — they are reserving capacity. If an outside event stopped the work — weather, a permit hold, an upstream delay — a reduced standby rate is defensible, because you are covering ownership and opportunity cost without the wear and consumables of active use. The reduction should never reach zero. Free standby tells customers your iron is a free staging service, and the efficient operator who returns gear promptly ends up subsidizing the one who hoards it. Price standby as a meaningful fraction of the day rate, not a courtesy. Your tank or light tower is still off the market the entire time.
Why low-wear gear is the hardest standby call
Equipment that barely wears while idle creates the temptation to discount standby to nothing — and that is exactly where yards lose the most. A frac tank holding fluid, a bank of mobile storage tanks, a light tower running a few hours a night: none of these rack up engine hours or hydraulic wear the way a working machine does. So the customer argues there is no cost to idle time. There is. The asset is unavailable, the deposit risk is live, and on a remote location you may still run inspections and fuel runs. With this class of gear, anchor your standby rate to opportunity cost and replacement exposure, not to wear. The less a unit visibly suffers from sitting, the more disciplined your standby pricing has to be, because nothing else is pushing the customer to send it back.
Writing standby into the contract
Standby disputes are almost always contract failures, not billing failures. The agreement has to answer four questions before the gear leaves your lot: who can declare standby, how they declare it, what the standby rate is per unit class, and what caps or conditions apply. Put the trigger in writing — a phone call does not count unless your contract says it does and you log it. State a maximum standby duration after which full rate resumes or the unit must come home, so a pad does not become permanent cheap storage. Spell out that standby covers idle use only, not damage, loss, or the customer's own scheduling. With a rental platform driving billing, the standby rate, the trigger date, and the unit it applies to live on the agreement itself, so the invoice reflects the policy automatically instead of being reconstructed from memory.
Operating the standby switch without disputes
Even a clean contract falls apart if standby gets toggled by memory. The day a customer declares standby, log it against the specific units and timestamp it — which tanks, which tower, which agreement. When work resumes, log that too, because the resume date is what customers contest most. Bill standby as its own line on the invoice rather than burying it in the day rate, so the customer sees exactly what idle time cost and why. That transparency is what keeps the relationship intact: a separate, dated standby line reads as fair accounting, while a silently reduced total reads as a mistake waiting to be challenged. Tie the standby clock to the rental record so the gap between declared and resumed bills itself, and the argument never starts.
Key takeaways
Standby means the customer's gear is idle on their pad, not returned to your lot — you still carry the risk and the unit is off the market, so idle time has real cost.
Set the rate by cause and cost: full rate when the customer chose to stage or hold, a reduced standby rate when an outside delay stopped the work — but never let standby reach zero.
Low-wear gear like tanks and light towers is the hardest call; anchor standby to opportunity and replacement cost, not engine hours, or you give the iron away.
Write the trigger, the per-class rate, and a maximum standby duration into the contract before the gear ships, so nobody reconstructs the policy after the fact.
Log the declare and resume dates against specific units and bill standby as its own dated invoice line, because the resume date is what customers contest most.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“What do I say when a customer insists they should owe nothing because they never touched the unit?”
Reframe it from use to availability. Tell them the charge was never for running the gear, it was for holding their spot in your fleet while no other job could have it. Walk through what you still carry while it sits on their location: the asset off the market, the deposit risk, the trips out to check on it. Most customers accept that quickly once you separate paying for use from paying for reserved capacity, and the standby rate itself signals you already discounted the idle stretch.
“What if the customer claims standby started earlier than the date I logged?”
Hold the logged date and explain why up front, before it turns into a credit fight. Idle time only counts from the moment a declaration lands in your system, because that is the first point you could have offered the unit to another caller. Time before that billed at full rate, since you were still treating it as active. If a crew genuinely went quiet days before anyone told you, that is a conversation for the next contract, not a backdated discount. Document the call so the record settles it.
“Who eats the cost if a unit gets damaged or goes missing while it is sitting on standby?”
The customer does, and your contract has to say so in the same breath it grants the reduced rate. A lower idle rate is relief on use, not a transfer of responsibility for the iron. While the gear sits on their location they still own theft risk, vandalism, weather damage, and anything a passing rig hits. Spell out that the standby rate does not touch the deposit or any damage terms, so nobody argues the cheaper line item also bought them out of the loss.
“How do I stop a customer from re-declaring standby over and over to dodge the duration cap?”
Treat repeated toggling on the same job as one continuous standby window, not a fresh clock each time. Write it that way so a customer cannot resume for a single shift, idle again, and reset the count to keep cheap storage going indefinitely. When you see the pattern, the right move is a call: either the unit goes back to active full-rate use or it comes home. The cap protects your fleet rotation, and the contract should let you enforce it without renegotiating mid-job.
“How do I handle a pad where some units are working and others are idle?”
Bill each unit on its own status rather than putting the whole load on one rate. Standby is declared and logged per unit, so a working light tower stays at full rate while idle tanks next to it drop to standby. Resist the customer's push to average the pad or call the entire delivery idle because part of it paused. Tracking each tag separately is also what lets you bring just the dead units home while the rest keep earning, instead of pulling or holding everything together.
“What about a repeat customer who threatens to take their volume elsewhere over standby charges?”
Decide your floor before the call, not during it. A steady account can earn a lower standby fraction or a longer cap as a written term you choose deliberately, which is different from waiving the line under pressure. Folding the moment someone pushes teaches every customer that standby is negotiable on the spot and invites the same fight every job. If the relationship warrants better terms, set them in the next agreement so they apply evenly and you are not improvising margin away one phone call at a time.
See how EquipFlow handles this on a live yard.
Bring your fleet count and a rough sense of your current workflow. Twenty minutes covers the dispatch board live, MSA billing, and an honest answer on fit.
Book a demoStay in the loop
Yard ops notes, once a week.
Operator-written. Covers dispatch, billing, maintenance, and what we ship. No fluff.