Skip to main content
HOME>Use Cases>Work Authorization Tracking: Permit Dates and Case Owners Kept Current
Use Case8 min read

Work Authorization Tracking: Permit Dates and Case Owners Kept Current

Permit dates, HR notices, caseworker assignments and renewals are tracked in one Kylon room. Agents read the Attio records and OneDrive permits and draft every message, the mobility lead approves each change, and counsel decides every filing.

Get started
Kylon TeamProduct

Permit dates, HR notices and caseworkers that drift apart

A mobility team tracks one thing per employee that cannot slip: the date their work authorization needs attention. Each employee's authorization record sits in Attio, in a custom object the team keeps for it. The permit itself is a scanned document in OneDrive. Role changes, transfers and reorganizations arrive as HR notices in Outlook, and the mobility policy in Google Drive sets the internal lead time for starting each kind of renewal.

Those sources drift. The deadline worksheet someone keeps by hand stops matching Attio. A reorg sets a role change flag on several people and is then reversed, and the flags are cleared without anyone running the rest of the policy. A renewal is approved and the case keeps its caseworker, so the workload view says that person is busier than they are. None of this is a legal question. It is record keeping, and it is where cases slip.

Who works in the room

People

  • Global mobility lead

    Owns the tracker, approves every status and caseworker change, and signs the cycle closeout

  • Caseworkers

    Manage each open case with the employee and outside counsel

  • Immigration counsel

    Advises on every filing and confirms dates; the room never decides a filing

  • HR business partners

    Send notices of role changes, transfers and reorganizations

Agents

  • NovaCase tracker

    Reads each Attio authorization record, the permit on file in OneDrive and new HR notices, and proposes a status and caseworker for each employee

    AttioOneDriveOutlook
  • RyanDeadline checker

    Checks the deadline worksheet against the records, recomputes lead times when the policy changes and checks every re-run before it is approved

    Google DriveAttio
  • MycoCorrespondence

    Drafts notes to counsel and document reminders to employees for a person to send, and collects managers' questions from Slack

Anything about an employee's status goes to Nova, the default agent, unless another agent is named. Ryan takes dates, the worksheet and the lead time table; Myco takes correspondence. Nova opens OneDrive only through the person it is working for, checked on every call, so a permit is read only when someone with access has asked. Attio changes use a lasting grant the mobility lead approved, and each one waits for the lead's approval. Nova hands every changed record to Ryan for a date check.

A review cycle, step by step

The policy's rule order is in Drive and summarized in the room guidelines, and every status is derived from the top of that order, never by editing the last answer. Between cycles, a weekly automation has Nova check which renewal windows have opened and start a thread for each one, so no case waits for the next review.

  • Agent works
  • Person decides
  • Arrives or gets recorded
Scroll sideways to see the whole flow.
StageWhat happensWho actsWho decides
First passEach employee's record, permit and recent HR notices are read, and a status is proposed: no action, monitor, renewal due or counsel reviewNovaThe mobility lead approves before Attio changes
Caseworker assignmentOpen cases are matched to caseworkers by workload and permit categoryNovaThe mobility lead confirms each assignment
Worksheet correctionThe hand-kept deadline worksheet is checked against Attio, and each correction is noted in the description on the employee's Attio recordRyanThe mobility lead approves the corrected text
Lead time changeWhen the policy lengthens the lead time for one permit category, only that category's dates are recomputedRyanCounsel confirms how the policy change reads
Reorg reversalRole change flags are cleared, and each affected employee is re-run through the full rule orderNova, checked by RyanThe mobility lead approves each new status
Renewals approvedApproved renewals get their new dates, and the caseworker field is set back to noneNovaThe caseworker confirms the approval notice, and the mobility lead approves the record
CloseoutCycle totals by status and caseworker are counted from the final Attio recordsNovaThe mobility lead signs the closeout
Stages of one authorization review cycle. Employee IDs, permit categories and dates in this example are illustrative.

Clearing a flag is not deciding a status

When the reorg memo is reversed, the role change flag comes off, and each affected employee goes back through the full rule order. Some return to no action. Some are now inside their renewal window, because time passed while the flag was on. Nova shows which rule decided each one, and Ryan checks the dates before the mobility lead approves anything.

A lead time change is narrow on purpose. If the policy lengthens the lead time for one permit category, Ryan recomputes dates for that category only and leaves every other category exactly as it was. Counsel confirms how the change reads before it goes into the room guidelines. Myco drafts notes to counsel and reminders to employees for a person to send, and nothing in the room tells an employee what their status means for them; that conversation belongs to their caseworker and counsel.

What the checks catch

  • A cleared role change flag where the status was set by hand instead of re-run through the full rule order
  • A lead time change applied to every permit category instead of the one the policy named
  • A renewal approved while the record still names a caseworker, which is set back to none
  • A deadline worksheet date that disagrees with the permit on file, corrected and noted on the employee's Attio record
  • An HR notice about a transfer or title change that has not yet reached the employee's Attio record

What stays with people

  • Approving every status and caseworker change before Attio is written
  • Every decision about a filing, which belongs to counsel and the employee
  • Talking with the employee about their case, which their caseworker does
  • Sending every message to counsel or an employee, and signing the closeout

Integrations in this workflow

Kylon is not an immigration case management system, and it does not stand in for one or for counsel. It sits across the records, documents and mailboxes the team already uses, and the room keeps the dates, decisions and drafts together.

  • Attio holds the authorization record for each employee: permit category, key dates, status and caseworker
  • OneDrive holds the permit documents and approval notices, opened only when someone with access asks
  • Outlook carries the HR notices of role changes, transfers and reorganizations
  • Gmail is the mobility inbox shared with outside counsel, and every outgoing note is a draft a person sends
  • Google Drive keeps the mobility policy, the lead time table and the deadline worksheet
  • Slack is where managers ask whether a team member's case is on track, and Myco brings those questions to the caseworker

Where to start

Limit the first cycle to employees whose permits expire within the next year. Connect the Attio object that holds their records, let Nova read OneDrive through each caseworker's own account, and state the rule plainly in the room guidelines: agents track dates and propose statuses, the mobility lead approves every change, and counsel decides filings.

“The worksheet, the records and the permits now say the same thing, and the people who decide can see why.”

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

Your first company harness. Where humans and agents run your business together.

Get started

More Use Cases

View all

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

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