For lumping agencies
Surge pricing for lumping services: when it is fair, how to state it, and how to avoid the argument
Charging more for hard-to-fill work is legitimate. Surprising a customer with it is not. The costs that justify a surge rate, the triggers worth naming, and the language that keeps an invoice from becoming a dispute.
- Published
- Length
- 6 min read
The short version
Surge pricing is legitimate when it covers a real cost: wage premiums, dispatch effort, spent float, productivity risk, and retention. Define every trigger as a checkable fact, with a notice clock, named shift windows, a written holiday list, an agreed peak date range, and a stated rule for how premiums stack. Put all of it in a one-page rate schedule at the quote, then confirm the premium in writing in the same message that confirms the crew. Do not bill a surge for your own no-show, for a peak a customer warned you about, or on a technicality. When a customer pushes back, sell them the way out: more notice, a standing block, or a forecast that lets you hold capacity at base.
On this page6 sections
Nobody argues with the principle. A Saturday night shift at a freezer dock costs an agency more to fill than a Tuesday morning at an ambient one, and if the price is the same, the agency is subsidizing the hard work with the easy work until it stops being able to. Surge pricing is how that gets corrected.
What customers argue with is discovery. A premium they agreed to in advance is a rate. The same premium appearing on an invoice for the first time is a surprise, and a surprised receiving manager does not renegotiate, they go looking for another agency. Everything useful about surge pricing sits in that distinction.
What a surge rate is actually paying for
Before setting a number, be clear about the cost it covers, because that is the conversation you will have to have.
Wage premium. The direct one. Filling a holiday, overnight, or same-day shift means paying workers more to accept it, and that premium is real money leaving the agency. A surge rate that does not reach the worker is not a surge rate, it is margin, and crews figure that out quickly.
Dispatch cost. A shift requested with two hours of notice consumes a dispatcher's afternoon: calls, declines, confirmations, a backup lined up. Planned work consumes almost none. The labor of filling is a genuine cost and it scales inversely with notice.
Opportunity cost and continuity. Pulling qualified workers onto an urgent call means taking them off something else, or spending the float pool you keep for no-show coverage. Once the float is spent, the next failure anywhere in your operation is uncovered.
Retention cost. Asking the same people repeatedly to work unwelcome shifts costs you those people. The premium is partly what keeps them willing to be asked again.
Naming these makes the rate defensible. An agency that can explain what a premium buys is negotiating; an agency that just has a higher number is haggling.
Triggers worth naming, and how to define them
A surge rate that depends on judgment will be disputed. A surge rate that depends on a fact will not. So define each trigger as something both parties can check after the fact.
- Short notice. Defined as a clock, not a feeling: a request received fewer than a stated number of hours before shift start. Say whether the clock runs on business hours or wall-clock hours, because that ambiguity is where the argument lives.
- Off-hours. Named shift windows. Overnight, weekend, and specific listed holidays, with the holiday list written out rather than left to "major holidays."
- Peak season. A stated date range agreed before it starts, not declared once it has. A range in the service agreement is a rate; a range announced in November is a price increase.
- Crew size above the committed base. For Dedicated On-Site Crews, the base headcount is contracted and anything above it is On-Demand / Overflow at the overflow rate. This is the cleanest trigger there is because the base is already in writing.
- Conditions. Freezer work, hazardous or heavily contaminated loads, live unloads with the trailer running, extended reach into a container. These are usually better handled as named adders than as a surge, because they are properties of the work rather than of the timing.
- Minimum call-out. Not strictly a surge, but it belongs in the same paragraph. A worker travelling in for two hours of work still has to be paid for the trip, and a stated minimum prevents that loss quietly.
Stack the triggers explicitly. If a same-day request for a holiday freezer shift can attract three premiums, say in the agreement whether they compound, whether they are additive, and whether there is a cap. Nothing damages an account faster than a customer discovering the stacking rule on an invoice.
State it before you need it
The right time to put surge language in front of a facility is when nobody needs a surge crew: at the quote, in the rate sheet, in the service agreement. It reads as professionalism then. It reads as opportunism at nine at night when the trailers are stacked up.
Put the rates in a schedule attached to the agreement, with the base rate, each premium, each adder, the minimum call-out, and the notice clock. One page. The facility's receiving manager should be able to work out the cost of a Saturday call without phoning you, and a manager who can predict your invoice will use you again.
Then say the number out loud before the shift. When an overflow call comes in at a premium, confirm the premium in the same message that confirms the crew, in writing, with the trigger named. "Six workers confirmed for tonight at the short-notice rate under the notice clause, invoice will show the premium as a separate line." That message is worth more than any collections process, and it is one of the quieter benefits of running dispatch in a system that can quote and confirm in one place, whether that is LumpLogix or a disciplined email habit.
Where surge pricing is not fair, and saying so
There are cases where charging a premium is bad business even when the contract allows it, and recognizing them protects the account.
When the short notice is your own fault. A worker no-show is your coverage problem, not the facility's, and billing a surge rate to cover your own gap is how an agency loses an account in one invoice. This is exactly what a float pool exists for.
When the facility gave you a forecast and you did not act on it. A receiving manager who told you in September that November would be heavy has done their part.
When the surge is permanent. If every shift at an account triggers a premium, the base rate is wrong and the honest move is to reprice the account rather than run it at a permanent surcharge. Customers notice, and they are right to.
Handling the pushback
When a facility objects, the productive answer is almost never a defense of the number. It is an offer of a way out of the premium.
Offer notice. If they can give you a day, the short-notice premium disappears, and now you are both solving the same problem. Offer a standing block, because a facility that commits to a recurring Saturday shift can be staffed with people who chose Saturdays, and that costs less than filling it each week. Offer a forecast arrangement, where they tell you their peak range early and you hold capacity at the base rate. Each of these converts a pricing fight into a planning conversation, and every one of them is cheaper for you to serve than the surge was.
And when a facility simply will not accept premium pricing for genuinely premium work, let it go. Filling unwanted shifts at a normal rate is how agencies burn crews, and a crew burned on one account fails on the others.
- Standards
- How articles are checked
- Corrections
- team@lumplist.com