From "We Need an Interpreter" to Payday: The Life of One Assignment

Somewhere right now, a nurse is standing in front of a Deaf patient, realizing she cannot do her job until someone who can sign walks through the door.

That is where an interpreting assignment begins. Not on a schedule. Not in an app. It begins with a need, a real one, felt by a real person in a real room. Everything after it exists to close the gap between that need and a qualified professional standing in that room on time.

Most people only ever see one slice of what happens next. The requester sees a name appear on a confirmation. The interpreter sees an offer buzz on their phone. The coordinator sees a slot turn green. Almost nobody sees the whole thing end to end.

So let us follow one assignment the whole way through. From the need, to the room, to the money finally landing in an interpreter's account. Every step, and why each one matters more than it looks.

Step one: the request

It starts as a request, and requests are messier than they sound.

A hospital, a school, a law office, or a Deaf consumer directly reaches out and says some version of "we need an interpreter." But an interpreter for what? A twenty-minute follow-up appointment and a three-day deposition are not the same job. A platform lecture is not a mental-health intake. The setting, the time, the length, the language and modality, the consumer's preferences, whether it needs a team, whether a Certified Deaf Interpreter belongs in the room. All of that is buried inside those four words, "we need an interpreter."

From the requester's side, this feels like the whole job. They made the ask. In their mind, coverage is now somebody else's problem.

From the coordinator's side, the request is not an answer. It is a question that just landed on their desk, and every detail they can pin down now is a detail that does not blow up later. A vague request is how you end up with a novice sent to a courtroom, or a solo interpreter booked for a job that needed two.

Step two: finding the right person

Now the coordinator has to turn a need into a name.

This is the part outsiders assume is simple, and it is the part that eats a coordinator's whole morning. Who is qualified for this setting? Who is available at that hour? Who is close enough to get there? Who has worked with this consumer before and already has the trust and the vocabulary? Who is going to be a good team match for the second interpreter? You are solving a puzzle where the pieces are human beings with lives and limits.

Then the offer goes out. Sometimes it goes to one best-fit interpreter first. Sometimes, when the clock is loud, it broadcasts to a whole group and the first qualified yes wins. Either way, the coordinator is now waiting on a person to say yes, and a job that is not accepted is not covered.

From the interpreter's side, this is the moment the assignment becomes real. An offer arrives. And a good interpreter does not just tap accept. They check their own calendar for a conflict, weigh the setting against their skills honestly, think about travel and prep, and only then commit. Saying yes to a job you are wrong for helps no one. The accept is a professional judgment, not a reflex.

When that yes lands, the coordinator confirms it back to the requester, and for the first time everyone can exhale. Coverage exists. But coverage is not completion.

Step three: the day of the job

Here is the only part the public thinks the job actually is.

The interpreter preps. They read whatever they were given, they look up the terminology, they plan the logistics, they show up early. In the room they carry the agency's name and the agency's standards, and they hold the communication between two people who could not otherwise understand each other. If it is a team job, they feed and monitor and hand off cleanly, because their partner is not their backup.

And the day of a job almost never runs exactly as booked. The two o'clock starts at two forty. The twenty-minute visit turns into an hour because the doctor found something. The one-hour deposition runs long and now needs a second interpreter who was never scheduled. The assignment as it was booked and the assignment as it actually happened are two different records, and the difference between them is not a rounding error. It is time, and time is money that somebody has earned.

Step four: the closeout nobody celebrates

The interpreter leaves the room, and the assignment is still not done. This is the step that quietly decides whether anyone gets paid correctly.

Somebody has to record what actually happened. The real start and end. The real length. The extra hour, the second interpreter, the mileage, the parking, the after-hours rate that kicked in at six. This is the closeout, and it is the single most-skipped, most-fumbled step in the entire chain.

Skip it, or scribble it on a sticky note that lives in a car cup holder for two weeks, and everything downstream breaks. The invoice is wrong. The pay is wrong. The trust erodes on both ends. From the interpreter's side, an accurate closeout is you getting paid for the work you truly did. From the coordinator's side, it is the raw material for every dollar that moves next. A job is not finished when the interpreter walks out. It is finished when the record of it is true.

Step five: billing and getting paid

Now, finally, money moves. And it moves in two separate directions that people constantly confuse.

One direction is billing the client. The agency turns that closeout into an invoice and sends it to the hospital or the school or the firm. Then it waits, because clients pay on their own timelines, and net-30 and net-60 are real. The other direction is paying the interpreter. The agency owes that interpreter for the work whether or not the client has paid yet, and payroll for W-2 staff and payouts for contractors are their own machinery, with timecards, batches, and, at year end, the tax forms everyone dreads.

And behind both of those sits the accounting. Every one of these numbers has to reconcile in the books and hold up if anyone ever asks, and in healthcare it has to do that while keeping patient information protected.

Here is the honest part almost nobody outside the field understands. The gap between "the interpreter did great work at 2 p.m. on Tuesday" and "the interpreter has the money" can be weeks. Every handoff in this chain is a place where that gap can stretch, or a payment can quietly fall through the cracks entirely.

The whole chain, in one place

Step back and look at what we just walked through. A need becomes a request. A request becomes a match. A match becomes an accepted offer. An offer becomes a job. A job becomes a closeout. A closeout becomes an invoice and a paycheck and a line in the books. One assignment, and it passed through a requester, a coordinator, one or two interpreters, a billing process, a payroll run, and an accountant.

For most of the field, each of those steps lives in a different tool, or in no tool at all, held together by email, spreadsheets, and memory. Every seam between them is a place where time leaks and money slips.

That gap is the whole reason I built OneTerp. One place where the offer, the calendar, the clock, the closeout, the invoice, the payout, and the sync to your accounting software are the same continuous thread instead of six disconnected ones. Not because software is exciting, but because an interpreter should get paid, correctly and on time, for the work they actually did. And because a coordinator should spend their morning covering the next patient, not chasing the last one's paperwork.

The nurse at the top of this post just needed someone who could sign. Everything in between is how a whole profession makes sure that person shows up, does the work, and gets paid for it. It is a long chain. It is worth understanding. And it is worth building well.