Offboarding and access revocation

Closes the employee record, revokes access on time, and captures the exit conversation while it is still useful.

macOS — coming soonSee the 2 automations
HR / AUTOMATE.md

When an exit interview is logged, group the answers into themes and post the summary to the managers who own the affected work.

Ready-made: Exit interview themes

The job, and what good looks like.

Offboarding is the workflow that gets dropped, and the cost shows up months later. Email, code repositories, and shared drives stay open because nobody owns a revocation list, credentials in personal accounts are never collected, and the exit conversation happens weeks after the person has left. This workflow starts when a resignation is recorded. It builds the list of every account still assigned to that person, gives each one an owner and a due date, and lines the revocation up with the last working day rather than a convenient week later. In parallel, the exit conversation is scheduled while the person can still answer properly, and the notes are grouped into themes alongside the work those themes point at. A human still decides what happens to shared files and personal credentials, and chooses which themes are safe to share more widely. The workflow closes the record on time and keeps the learning; it does not replace the conversation.

When it is handled

  • No accounts left open
  • Exit notes captured on time
  • Recurring themes logged

Works with tools like

  • BambooHR
  • Google Calendar
  • Asana
  • Notion
  • Slack

Ready-made automations. Pick the one that fits.

Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.

Exit interview themes

When an exit interview is logged, group the answers into themes and post the summary to the managers who own the affected work.

7 days after the last day

Last day access sweep

When a resignation is recorded, list the accounts still assigned to that person and assign each revocation to an owner with a due date.

When a resignation is recorded

You stay in charge.
At every step.

It reads and ranks. People decide about people.

  • It never rejects anyone

    It ranks and summarizes against your written criteria, with a reason for each. Every decision stays with you.

  • Undo what you don't want

    Every step is recorded, and a file it changed can be put back.

  • Candidate data stays contained

    Each automation reaches only the inbox and folders you connect for it.

Exit interview themes

Approve before it posts in Slack?

ReviewApprove

Before you download.

Where does it run?
On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
How does it connect to our CRM and other tools?
Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
Does it run when my computer is asleep?
It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
How does my team use it?
Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
Do I need anyone technical to set it up?
No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.

Already have tools for this? Here is the difference.

Your applicant tracking system's automations

Moving candidates between stages and sending template emails.

They can't read a CV against your real criteria or explain why someone made the shortlist.

Flowchart automation tools

Copying records between HR apps.

Every exception becomes another branch someone has to build and maintain.

AI chat assistants

Summarizing a CV when you paste it in.

Applications keep arriving while nobody is asking, and the criteria live in a chat.

AUTOMATE.md

Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.

Related workflows.

Employee records

Keeps one complete employee file from signed offer to exit, so an audit question or a reference request is answered from the record instead of a trail of emails.

Write your own

Engagement survey follow-up

Turns survey results into named follow-up conversations with the managers whose teams scored lowest.

2 automations

Leave tracking

Turns a leave request into a decision, a corrected balance, and cover the team can see, so an absence is never discovered at payroll or on the Monday it happens.

1 automation

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 3

    Try it, then turn it on

    Run it once and check the result. It only runs on its own once you switch it on.

macOS — coming soon