--- title: "Mandatory Training Compliance Tracking With AI Agents | Kylon" description: "How a People Ops desk tracks mandatory training in Airtable, books sessions and files department closeouts in Asana, with a person approving each change." url: "https://kylon.io/use-cases/mandatory-training-compliance" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Mandatory Training Compliance: Bookings and Closeouts That Match the Records Use Case8 min read # Mandatory Training Compliance: Bookings and Closeouts That Match the Records Training dispositions, session bookings, completions, a canceled session and department closeouts run through one Kylon room. Agents work the Airtable records, the session calendar and Asana, and the People Ops lead approves every change before it is made. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Twenty-six people, one policy, and session seats that run out Mandatory training looks simple on paper. Each employee has a course, a due date and a role, and the policy says who is exempt, who is overdue and who needs a seat in the next session. The training records live in Airtable, the policy and the role exemption matrix in Google Drive, the sessions on Google Calendar, and the follow-ups for managers in Asana. The cycle gets hard after the first pass. HR revises the exemption matrix. The learning system exports a batch of completions. Facilities loses a session room for good. An audit finds two due dates entered wrong. Each change touches some people and not others, and most mistakes come from touching the wrong ones: rebooking someone who already finished, rewriting a calendar event for someone who was not affected, or counting the closeout from an old version of the sheet. ## Who works in the room People - People Ops lead Owns the training cycle, approves every disposition, booking and rebooking, and signs the department closeouts - People Ops coordinator Keeps the compliance sheet and the session schedule, and handles room changes with facilities - HR policy owner Maintains the role exemption matrix and confirms how each revision applies - Department managers Release people from shifts to attend and receive their department's closeout Agents - FinCompliance coordinator Runs each employee through the training policy, proposes dispositions and bookings, and makes the Airtable, calendar and Asana changes once they are approved AirtableGoogle CalendarAsanaGoogle Drive - MycoRecords checker Checks the draft sheet, the completion exports and the due date corrections against the records, and lists every line that disagrees Google DriveAirtable[Slack](https://kylon.io/integrations/slack) Fin is the default agent here, and Myco takes anything that compares two sources, such as the coordinator's draft sheet against Airtable. The People Ops lead approved a lasting grant for this room, so Fin can make Airtable, calendar and Asana changes, but only after the lead approves each one in the thread. When Myco finds a disagreement, it mentions Fin with the employee IDs and the record each value came from. ## The cycle from first disposition to closeout Out-of-scope records, such as terminated employees and duplicate rows, are named in the room guidelines, so neither agent touches them at any stage. ```mermaid flowchart TD disp["Fin proposes each employee's
disposition and booking"] ok1["People Ops lead approves before
Airtable or calendars change"] sheet["Myco checks the draft sheet
line by line, writing nothing"] hr["HR policy owner
confirms the revised matrix"] export([The learning system
exports completions]) cancel([Facilities loses a
session room for good]) tech["Fin runs Field Technicians
through the full policy"] done["Fin marks only
those people complete"] rebook["Fin moves only named
people to a free seat"] cross["Myco cross-checks them
against the latest export"] batch["People Ops lead
approves the batch"] release["Department managers
confirm release"] audit["Myco checks the due date
corrections against the records"] close["Fin reads closeout counts from
the final Airtable records"] sign["People Ops lead signs off
each department"] disp --> ok1 --> sheet sheet --> hr & export & cancel hr --> tech --> cross export --> done --> batch cancel --> rebook --> release cross & batch & release --> audit --> close --> sign class disp,sheet,tech,done,rebook,cross,audit,close agent class ok1,hr,batch,release,sign person class export,cancel 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 | | --- | --- | --- | --- | | Initial disposition | Each in-scope employee gets a disposition and days overdue from the policy, and bookings and manager follow-ups are proposed | Fin | The People Ops lead approves before Airtable, calendars or Asana change | | Draft sheet review | The coordinator's draft compliance sheet is checked line by line against the approved results, and nothing is written | Myco | The lead decides which corrections go back to the coordinator | | Exemption removed | All twelve Field Technicians are run through the full policy for the first time | Fin, checked by Myco | The HR policy owner confirms the revised matrix | | Completions | Each person in the learning system export is marked complete with their completion date, and no one else is re-run | Fin | The lead approves the batch | | Canceled session | Only the people named for rebooking move to the earliest date with a free seat, and their old events are replaced | Fin | The lead approves each move, and managers confirm release | | Due date audit | Two corrected due dates are written, then every open record is re-run and three completed ones are spot-checked | Myco, then Fin | The lead approves the changed records | | Closeout | Headcount, the number complete or exempt and the number still open per department are read from the final Airtable records, with one Asana closeout per department | Fin | The lead signs off each department | Stages of one training compliance cycle. Employee counts, roles and session dates in this example are illustrative. ## A canceled room and an exemption that disappears An exemption sits at the top of the rule order, so an exempt employee was never checked against anything below it. When HR removes the Field Technician exemption, Fin treats all twelve technicians as new work: due date, completion history, the next session with a free seat, the manager follow-up. Myco cross-checks the results against the latest completion export before anything is booked. A canceled session is narrower. The date is gone for good, so no one is rebooked into it, and only the people on the rebooking list move. Someone who completed the course after being booked is not on that list, and Fin leaves their calendar alone, even where tidying looks harmless; that call is the coordinator's. Between stages, a Monday automation has Fin check the due dates in Airtable and post anyone overdue without a completion. ## What the checks catch - A terminated employee or duplicate row in the roster, which stays out of scope and untouched - A Field Technician who completed the course before the exemption was removed and needs no booking - A rebooking that would land someone on the canceled date or in a session with no seats left - A calendar event for someone not on the rebooking list, including people who already completed, which is left as it is - Closeout counts that differ from the final Airtable records because they were carried over from an earlier stage ## What stays with people - Approving each disposition, booking and rebooking before Airtable or a calendar changes - Deciding exemptions and how the role matrix reads, which belongs to HR - Releasing someone from a shift to attend, which their manager confirms - Signing each department's closeout ## Integrations in this workflow Kylon is not a learning management system, and it does not replace the one you have. Completions still come from its export, and the room holds the coordination around them. - Airtable - Asana - Google Calendar - Google Drive - [Slack](https://kylon.io/integrations/slack) - **Airtable** holds each employee's training record: disposition, due date, days overdue and completion - **Google Calendar** holds the training sessions and each person's booking - **Asana** carries the follow-ups for managers and one closeout per department - **Google Drive** keeps the training policy, the role exemption matrix, the completion exports and the coordinator's draft sheet - **Slack** is where managers and facilities post shift conflicts and room changes, and Myco picks up anything that affects a booking ## Where to start Begin with one course and one cycle. Connect the Airtable base that holds the training records and share the Drive folder with the policy. Then write the rule the whole cycle rests on into the room guidelines: agents propose dispositions and bookings, the People Ops lead approves them, and no calendar event changes unless that person is named in the instruction. > “The closeout used to be rebuilt from three spreadsheets. Now it is read from the records the cycle actually ended with.” ## 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 mandatory training compliance desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Asana, Google Calendar, Google Drive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the People Ops lead, the People Ops coordinator, the HR policy owner and the department managers. Help me invite them to this Room. 3. Build a Training Cycle App with columns Needs Session, Booked, Rebook and Complete, one record per in-scope employee. Flag any terminated employees or duplicate rows so we can mark them out of scope before we go further. 4. Run each in-scope employee through our policy and the role exemption matrix in Google Drive. Propose a disposition, days overdue and a booking for each, and show me every line that needs attention. 5. Check the coordinator's draft sheet and any completion exports against the Airtable records line by line. List every disagreement and name the source each value came from. 6. Hold every Airtable write, calendar change and Asana update until the People Ops lead approves each one in the thread. Department managers confirm shift release before any rebooking moves, and the HR policy owner confirms any exemption change before affected employees are re-run. 7. Write our rules and who approves what into this Room's guideline, so every stage of the cycle follows it. 8. After one clean cycle, offer to turn the due date check 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)