What to look for in interpreter scheduling software

Every scheduling product demos beautifully. A calendar appears, an appointment gets dragged onto a Tuesday, everyone nods. The problem is that interpreter scheduling fails in ways a demo never shows: at 4:50 PM when a client cancels tomorrow’s 8 AM job, when two hospitals book the same Korean interpreter into overlapping slots across town, when the invoice goes out with weekday rates on a Saturday evening assignment. Evaluating software means evaluating it against those moments — the failure modes — not against the happy path.

Here’s what to actually test, how to test it, and — at the end — a scorecard you can run every vendor through, including us.

Conflict detection that understands travel

The baseline question: can the same interpreter be booked into two overlapping jobs? If the answer is yes, stop the evaluation — everything else is decoration on a system that will eventually strand a client in a waiting room.

But overlap is the easy case. The real test is travel time. An on-site job ending at 10:30 on one side of town and another starting at 10:45 on the other side don’t overlap on a calendar, and they are absolutely a conflict in the real world. Good scheduling software lets you attach a buffer to on-site work so that back-to-back bookings account for the drive between them.

Ask the vendor to reproduce exactly this scenario in the demo: one interpreter, one morning job with a buffer, then attempt the 10:45 booking. If the system shrugs and accepts it, you’ve learned what you needed to know.

Recurring series as a real object

A huge share of interpreting work is recurring — a weekly therapy appointment, a semester of classes, a standing Tuesday clinic. The test isn’t whether the software can create a repeating job; nearly anything can. The test is what happens to the rest of the series when reality intervenes:

• Cancel one instance — do the other nineteen survive untouched?
• Change the time from week twelve onward — does it fork cleanly, or does the whole series rewrite itself?
• Swap the interpreter for one week of a series — is that a two-click substitution or a delete-and-recreate?

Agencies that live with weak series handling end up creating every instance by hand “just to be safe,” which means the software has failed at the exact thing it was bought for. And when you eventually migrate platforms, series are the data most likely to be silently lost — a system that treats them as first-class objects protects you on the way in and the way out.

Broadcast when you want speed, assign when you want control

Filling a job has two legitimate modes. Sometimes the dispatcher knows exactly who should take it — the client asked for a familiar interpreter, or the assignment needs a specific certification — and direct assignment is right. Sometimes the job needs to fill fast, and the right move is to broadcast it to every qualified, available interpreter at once and let the first acceptance win.

Look for both, and look for what “qualified” means in the broadcast: it should filter on language, credentials, and availability automatically, so a broadcast never becomes a spam blast to interpreters who could never take the job. Then test the awkward race on purpose — have two interpreters tap accept within seconds of each other. The correct outcome is one assignment and one polite “already filled.” Anything else is a double booking with extra steps.

The rate engine is the product

This is the section vendors hope you skim. Interpreting billing is genuinely complicated, and the rate engine is where scheduling software either earns its subscription or quietly costs you money every month.

At minimum the engine needs to model:

• Dual rates on every job — what the client is billed and what the interpreter is paid are different numbers with different rules, tracked together so every assignment knows its margin.
• Time-based adjustments — evening, weekend, and holiday rules that apply themselves from the job’s actual date and time, not from a biller remembering to tick a box.
• Rush premiums — bookings made inside a short-notice window priced accordingly, automatically. (We’ve written a whole playbook on structuring rush and after-hours pricing.)
• Minimums — the two-hour minimum is an industry standard; a thirty-minute job should bill as two hours without human intervention.
• Mileage and travel — on-site work carries travel costs; they belong on the job, not on a sticky note.
• Per-client exceptions — that one contract with negotiated rates from 2023 has to be representable, or your team will be hand-editing its invoices forever.

Then confirm the engine’s output flows straight into invoicing. A rate engine that computes the right number but makes you re-type it into an invoice has only done half the job — and re-typing is where Saturday jobs get weekday rates.

The calendar is what you see in the demo. The rate engine is what you live with every month after.

Where to spend your evaluation time

The three-portals test

An interpreting agency has three audiences, and each needs its own door into the system.

Admins need the full dispatch view. Interpreters need to see offers, accept work, and check their schedule and pay from a phone in a hospital hallway — if accepting a job takes a laptop, your fill times will show it. Clients need to request services, see status, and find their invoices without emailing you for every question. If any of the three is missing, that audience’s workload lands on your staff as phone calls and email — which is to say, the software has outsourced its missing features to your payroll.

Notifications the software sends so you don’t

Every confirmed job generates a small flurry of communication: the interpreter’s confirmation, the client’s confirmation, the reminder before the appointment, the notice when something changes. Multiply by your weekly job count and this is hours of typing — or it’s automatic. Check that notifications fire on the events that matter, that their content is professional enough to represent you, and that a change to a job notifies everyone affected without anyone remembering to hit send.

Room for the fields only your agency needs

Every agency has intake details generic software never heard of — the purchase-order number one client requires, the room and floor for hospital work, the case number for legal assignments. If those can’t live as structured fields on the job, they end up in a free-text notes box: unsearchable, unreportable, and invisible to the invoice that needed the PO number on it. A quick test: name the three oddest things your team tracks today, and make the vendor show you where each one lives.

Reporting you’ll actually open

Finally, make sure the operational exhaust is usable: jobs by client, hours by interpreter, revenue by service type, fill rates, cancellation patterns. You don’t need a data-science suite — you need reports that answer the Monday-morning questions without exporting to a spreadsheet first. In the demo, ask for last month’s revenue by client and time it.

The vendor scorecard

Run every candidate through the same table, with your own data in the demo wherever possible.

The evaluation checklist

• Double-booking is impossible, and travel buffers make near-overlaps visible.
• Recurring series survive single-instance edits, forks, and substitutions.
• Both broadcast and direct assignment exist, with real qualification filters and a safe acceptance race.
• The rate engine models dual rates, time-based adjustments, rush, minimums, mileage, and per-client exceptions — and feeds invoicing directly.
• All three portals exist: admin, interpreter, client — and the interpreter one works from a phone.
• Notifications fire automatically on confirmations, reminders, and changes.
• Your agency’s oddball intake details fit as structured custom fields.
• Reports answer your Monday questions out of the box, and the exit-export story is concrete.

Run every vendor through the same list, using your own ugliest real-world scenarios rather than their demo script. The software that handles your worst Tuesday is the one that deserves your best years.

Frequently asked questions