How agencies price rush and after-hours work

A Tuesday 10 AM assignment and a Tuesday 8 PM assignment are not the same product. The evening job pulls an interpreter away from dinner, draws from a smaller pool of willing professionals, and is harder to fill on short notice. Every agency knows this intuitively; the difference between a profitable agency and a stressed one is whether that intuition is written down as pricing policy — and whether the software applies it automatically.

Under the hood there are actually two different scarcities being priced. After-hours premiums price the inconvenient clock: the job sits at a time fewer interpreters want to work. Rush premiums price the short countdown: whatever the hour, there isn’t much runway to fill it. They deserve separate rules, because one booking can trigger both at once — which is exactly where undecided policies go to die. Here’s how the premiums typically work, and the decisions you need to make for your own rate card.

After-hours: adder or multiplier?

The first structural choice for out-of-business-hours (OBH) work is between a flat adder — a fixed dollar amount per hour on top of the base rate — and a multiplier, like time-and-a-quarter or time-and-a-half on the whole job.

• Flat adders are transparent and easy to explain on an invoice: base rate plus an evening premium, two visible line components. Say the evening adder is a fixed amount per hour — every client sees the same premium regardless of their negotiated base, which keeps the policy feeling even-handed across the roster of accounts.
• Multipliers scale with the base rate, which some agencies prefer precisely because premium clients then carry proportionally more of the after-hours cost. They’re familiar from overtime norms, but they can produce eyebrow-raising totals on already-high base rates — and a multiplier quietly raises the premium every time a base rate is renegotiated upward.

Neither is wrong. Consistency is what matters — one structure, applied to everyone on a given rate schedule, visible on the invoice as its own component rather than blended invisibly into a mystery hourly figure.

Define the window to the minute

Whatever the structure, the boundary needs to be exact. A common pattern treats weekday evenings after a set hour, plus weekends and holidays, as OBH — but “after 5” is not a policy until it answers the boring questions. Is 5:00 PM inside or outside? Which holidays, by name, on a published list? And which clock governs: does a job starting at 4:30 and running to 6:30 bill entirely at standard rates, entirely at OBH, or split at the boundary?

All three answers exist in the wild. Trigger-by-start-time is the simplest to explain and to automate; split-billing is the most precise and the most work to communicate. Pick deliberately, write it down to the minute, and make sure your platform evaluates the rule from the job’s actual date and time — a 5:00 PM start and a 5:01 PM start should never be a judgment call, or a discount that depends on who built the invoice.

Rush: pricing the countdown

Rush is about notice, not clock time. A booking placed a month ahead can be filled calmly through normal channels; the same booking placed six hours out requires immediate broadcast, rapid responses, and often a premium to motivate an interpreter to rearrange their day. Agencies typically define one or more rush windows — bookings inside a set number of hours before the start time — each carrying its own adder or multiplier, with the shortest-notice tier priced highest.

The critical operational detail: rush should be computed from when the booking was placed relative to the start time, automatically. The moment rush becomes something a dispatcher remembers to add, two things happen — it gets forgotten on busy days (you eat the cost) and applied inconsistently across clients (you get the awkward call). The booking timestamp already knows the answer; let it do the work.

One refinement worth stealing: some agencies waive the rush premium when the short notice is their own doing — a reassignment after an interpreter cancellation, say. It’s a one-line exception that buys enormous goodwill, and it only stays manageable if the system records why a premium was waived.

When both apply: the stacking question

Sooner or later a client books an 8 PM job at 2 PM the same day. Now both premiums are in play, and you need a stacking policy before it happens, not during the invoice dispute after.

Three common answers, each defensible:

Whichever you pick, it should live in the rate schedule — applied by the system, printed clearly on the invoice, identical for every client on that schedule. An unwritten stacking policy isn’t a policy; it’s a future argument.

Decide your stacking policy before the 2 PM booking for the 8 PM job — not during the invoice dispute after.

Rule of thumb

The other side of the premium

A premium usually has two sides, and the second one is easy to forget at the pricing whiteboard: the interpreter is the person actually rearranging their evening or dropping their afternoon to take the job. Many agencies pass a share of rush and OBH premiums through to interpreter pay — and there’s a hard-nosed operational case for it beyond fairness. Fill rates on bad-hour and short-notice work are a direct function of whether saying yes is worth an interpreter’s while; the premium is the lever you own.

Structurally, treat the billing side and the pay side as independent settings on each rule. The client-facing adder and the interpreter’s share of it are separate business decisions — you may pass through half of one premium and all of another — and software that welds them together will force a bad compromise on one side or the other.

The supporting cast: minimums and cancellations

Two adjacent policies keep the premium structure coherent. Billing minimums — commonly two hours for on-site work — ensure a short evening assignment still compensates the interpreter’s travel and disruption. Sequence matters and belongs in writing: the minimum applies first, then premiums compute on the billed duration, so a 30-minute Saturday job bills as two premium-rate hours, not thirty premium minutes.

Cancellation windows mirror your rush logic in the other direction: if a booking cancelled inside 24 or 48 hours bills at some or all of its value, that’s the same recognition that short notice has a cost. Define the window, the percentage, and the no-show rule together, and put them on the same page of the rate schedule as the rush tiers — clients understand the symmetry when both halves are written down side by side, and interpreters should know how a late cancellation flows through to their pay as well.

Put the policy where everyone can see it

Premium structures fail socially before they fail mathematically. Three habits keep them healthy. First, the rate schedule is a document clients receive — windows, tiers, stacking rule, minimums, cancellation terms, on one page — not folklore rediscovered invoice by invoice. Second, the invoice itself shows the premium as a labeled line, because a number a client can see is a number a client can accept. Third, review the structure on a calendar — once a year, with your fill-rate data for evening and short-notice work in hand. If nobody is declining your 8 PM jobs, your premium might be someone else’s margin; if everything after 6 PM is a struggle, the interpreter share is telling you something.

Make the software carry the policy

None of this is complicated arithmetic. What makes it hard in practice is that it’s conditional arithmetic performed dozens of times a week under time pressure — exactly the work humans do inconsistently and software does perfectly. A proper rate engine lets you define the OBH window, the rush tiers, the stacking rule, the minimums, and the interpreter shares once per rate schedule, then prices every job from its own date, time, and booking timestamp with each premium visible as its own line on the invoice. (Evaluating platforms? The rate engine is the section of our buyer’s guide worth reading twice.)

The payoff isn’t just accuracy. It’s that when a client questions an evening invoice, the answer is a policy — agreed, written, uniformly applied — rather than a dispatcher’s recollection. Premiums priced by policy get paid. Premiums priced by memory get negotiated, one uncomfortable phone call at a time.

Frequently asked questions