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.

No ready-made setup for this job yet.

Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.

The job, and what good looks like.

The employee file is what an employer is judged on and what nobody enjoys maintaining, so it decays one quiet correction at a time. A job title goes into the HR system but not the org chart, a salary change reaches payroll and not the record, and a probation end date passes with nobody checking it. This workflow treats the record as the one place the facts live. Every change is written once, at source, and pushed to the systems that need it, so payroll, benefits, and the org chart cannot disagree. Dates that carry a consequence, such as probation ends, review points, and contract renewals, are checked daily and raised while something can still be done. Missing documents are listed by person and by age, oldest first, and anything past an agreed deadline is escalated rather than left in a folder. Someone who left last year and needs a record for a mortgage is served from the same place. A human still decides what is recorded, who can see a sensitive field, and how to treat a conflict. The workflow keeps the file true; the judgement about a person stays with a person.

When it is handled

  • One record, not four copies
  • Audit questions answered the same day
  • No two systems disagree on a start date
  • Probation and review dates never missed

Works with tools like

  • BambooHR
  • HiBob
  • Workday Recruiting
  • Rippling
  • ADP

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.

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.

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.