--- title: "Interpreter Scheduling for Language Services Teams | Kylon" description: "How a language services desk assigns interpreters in policy order, checks calendars and absorbs sick calls in one Kylon room, with every booking approved by a person." url: "https://kylon.io/use-cases/interpreter-scheduling" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Interpreter Scheduling: A Week of Assignments That Holds Through Sick Calls and Time Moves Use Case8 min read # Interpreter Scheduling: A Week of Assignments That Holds Through Sick Calls and Time Moves A week of interpreter requests is matched in policy order, checked against every calendar and kept right through sick calls, time moves and language fixes. The coordinator approves each assignment in the Kylon room before anything is booked. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Sixty requests a week and calendars that keep moving Interpreter scheduling runs on a policy with an order to it. A request that calls for a certified interpreter gets one, certified staff are offered work before contractors, video is used only where the policy allows it, on-site assignments leave travel time between clinics, and nobody is booked over an existing calendar event. Applying that order once to a week of requests is careful work. Applying it again every time something changes is where weeks go wrong. Requests and the interpreter roster sit in Airtable, availability lives on each interpreter's Google Calendar, the policy and certification list are documents in Drive, and clinics post changes in Slack or by email. The confirmation sheet the clinics receive is built from all four, so a duplicate line or a request nobody filled can slip into it unnoticed. ## Who works in the room People - Language services coordinator Owns the weekly schedule, approves every assignment and signs the close-out - Staff and contract interpreters Confirm assignments, keep their calendars current and report sick calls - Clinic schedulers Submit requests and send time changes and language corrections - Language services manager Maintains the certification list and decides how a certification change applies Agents - NovaScheduler Matches each request to an interpreter by language, certification and policy order, checks Google Calendar for conflicts and books once approved AirtableGoogle CalendarGoogle Drive - AdaConfirmation sheet checker Checks the draft confirmation sheet against the approved assignments and lists every duplicate, unfilled or wrong line Google DriveAirtable - MycoClinic and interpreter notices Drafts confirmations and change notices for the coordinator to send, and brings sick calls and time changes in from Slack [Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) New requests and questions about assignments land with Nova, the room's default agent, even when nobody is mentioned. The room guidelines send anything about the confirmation sheet to Ada. When an interpreter calls in sick, Myco reads the message from Slack and opens a thread for Nova whose first message lists every request on that interpreter's list, then takes the work back to draft notices once the coordinator approves the new assignments. An automation opens the next week's scheduling thread every Thursday morning. ## How a scheduling week runs The policy order is written into the room guidelines as well as the scheduling folder, so every agent applies the same precedence. Nothing reaches a calendar or a clinic before the coordinator has seen it. ```mermaid flowchart TD match["Nova matches each request in policy
order and checks the calendars"] approve["Coordinator approves before
any event is created"] sheet["Ada checks the draft confirmation
sheet against the assignments"] cert([The manager updates
a certification]) sick([An interpreter
calls in sick]) move([A clinic moves a time or
corrects a language batch]) rerun["Nova re-runs the requests
that depend on it"] outcome["Nova gives every request on
the list an outcome"] change["Nova changes the start time
only, or the language"] manager["Language services manager
confirms how it applies"] notices["Myco drafts the notices
for the coordinator to send"] changes["Coordinator approves the changes,
interpreters confirm"] close["Nova counts filled and unfilled
per language, checked by Ada"] sign["Coordinator signs the week"] match --> approve --> sheet sheet --> cert & sick & move cert --> rerun --> manager sick --> outcome --> notices move --> change manager & notices & change --> changes changes --> close --> sign class match,sheet,rerun,outcome,change,notices,close agent class approve,manager,changes,sign person class cert,sick,move event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Assignment | Each request is matched by language, certification and policy order, and every candidate's calendar is checked for conflicts | Nova, from Airtable and Google Calendar | The coordinator approves before any event is created | | Confirmation sheet | The draft sheet is checked against the approved assignments, and duplicate or unfilled lines are marked for removal | Ada | The coordinator corrects the sheet before clinics receive it | | Certification change | A revised certification re-runs the requests that depend on it, in policy order | Nova | The manager confirms how it applies and the coordinator approves the changes | | Sick call | Every request on the absent interpreter's list gets an outcome, reassigned or left in place | Nova, then Myco for notices | The coordinator approves and replacement interpreters confirm | | Time moves and language fixes | A moved request changes its start time only, and a corrected batch rewrites the language on every request it names | Nova | The coordinator approves the changed records | | Close-out | Filled and unfilled counts per language come from the current Airtable records | Nova, checked by Ada | The coordinator signs the week | Stages of a weekly interpreter schedule. Requests, languages and counts in this example are illustrative. ## When a clinic, an interpreter or a certificate changes mid-week A clinic writes that ten of its requests were entered with the wrong language. Eight were right after all and two should be Arabic. Nova rewrites the language on all ten, so each record shows it was checked, and re-matches only the two that changed. Another clinic moves a request from 9:00 to 11:30. That change touches the start time and nothing else, and if the new time collides with the interpreter's calendar, Nova raises it with the coordinator instead of swapping the interpreter on its own. A sick call needs the same discipline. The coordinator wants to see every request on that interpreter's list, including the ones after their return that stay put, so nothing is assumed. Nova proposes replacements in policy order, Ada re-checks the sheet lines that moved, and Myco drafts the notices for clinics and replacement interpreters. When the manager updates a certification, the same precedence decides who is offered the work first. ## What the checks catch - An interpreter who looks free in Airtable but already has an event on Google Calendar at that hour - A duplicate line on the confirmation sheet, or a line for a request that was never filled - A time move that also changed the interpreter or the status, which the clinic did not ask for - A sick-call summary that skips the requests left unchanged, so the coordinator cannot tell they were checked - A certification change applied out of order, giving a contractor work that a certified staff interpreter should have been offered first ## What stays with people - Approving every assignment before a calendar event is created - Sending each confirmation and change notice, which Myco prepares as a Gmail draft - Deciding what happens when a moved request no longer fits the assigned interpreter's day - Signing the weekly close-out per language ## Integrations in this workflow Kylon is not an interpreter scheduling system and does not try to be one. It works across the tools language services already has and holds the coordination between them. Nova books on interpreters' calendars through a lasting grant the coordinator approved for this room. - Airtable - [Gmail](https://kylon.io/integrations/gmail) - Google Calendar - Google Drive - [Slack](https://kylon.io/integrations/slack) - **Airtable** holds the requests, the interpreter roster and every assignment - **Google Calendar** shows each interpreter's existing commitments and carries every confirmed booking - **Google Drive** keeps the scheduling policy, the certification list and the draft confirmation sheet - **Gmail** carries confirmations and change notices, each one a draft the coordinator sends - **Slack** is where clinic schedulers and interpreters outside the room post sick calls and time changes ## Where to start Pick one week and one service line. Connect the Airtable base with your requests and roster, connect the interpreters' calendars, and write the one rule in the room guidelines: an agent may match and propose, and the coordinator approves every assignment before anything is booked. > “The policy order is the same on Friday as it was on Monday, even after five changes.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our interpreter scheduling desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Gmail, Google Calendar, Google Drive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the language services coordinator, the staff and contract interpreters, the clinic schedulers and the language services manager. Help me invite them to this Room. 3. Build an Interpreter Requests App with Request, Language, Interpreter and Status, one record per request. Fill it from the current requests and roster in Airtable. 4. Match each request by language, certification and our policy order. Check every candidate's Google Calendar for conflicts. Flag any duplicate or unfilled lines on the draft confirmation sheet in Google Drive and show me what needs fixing. 5. Draft confirmations and change notices as Gmail drafts. Bring sick calls and time changes in from Slack. Book nothing on any calendar and send nothing until the language services coordinator approves each assignment. When the language services manager updates a certification, ask the manager how it applies before re-running the affected requests. 6. Write our policy order and who approves what into this Room's guideline so every request and every mid-week change follows the same steps. 7. After one clean week, offer to turn the recurring scheduling thread into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked. Healthcare & life sciencesScheduling & dispatchCompliance & risk ](https://kylon.io/use-cases/clinical-site-monitoring)[ ### Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes. Healthcare & life sciencesCompliance & risk ](https://kylon.io/use-cases/cold-chain-excursions)