Mandatory Training Compliance: Bookings and Closeouts That Match the Records

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

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.

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

• 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.