Performance reviews

Runs the review cycle with a written submission for every person and a calibration step before ratings are shared, so nobody is judged on one manager's memory of nine months ago.

macOS — coming soonSee the automation
HR / AUTOMATE.md

When a review cycle opens, email each reviewer their own list of direct reports to write up by the end of week one.

Ready-made: Review cycle week one

The job, and what good looks like.

Performance reviews fail the same way every year: the cycle opens, everyone is reminded twice, and a third of the reviews are written a week late from memory or never written at all. Calibration becomes a debate about who has better recall, and identical work is rated differently depending on which manager it sits under. This workflow opens the cycle against the current org chart, so somebody who has just left or joined is not quietly missing from a list. Each reviewer gets their own people, their own deadline, and a reminder when nothing has been started. Feedback given between formal cycles, and survey themes from the last round, are attached to the person, so nobody writes from scratch. A submission still open 48 hours out is listed with the reviewer, the person being reviewed, and the missing sections, which is usually enough to get it written. Calibration then compares ratings across teams against the same descriptors before anything is shared. A human still writes the review, decides what is worth praising, and runs the conversation that follows. The workflow makes the input consistent and the record durable; it does not decide who is good at their job.

When it is handled

  • Every review written and returned on time
  • Ratings comparable across teams
  • Gaps named before calibration starts
  • No employee surprised by their own review

Works with tools like

  • Lattice
  • 15Five
  • Culture Amp
  • Google Calendar

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.

Review cycle week one

When a review cycle opens, email each reviewer their own list of direct reports to write up by the end of week one.

When a review cycle opens

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.

Review cycle week one

Approve before it sends the email?

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.

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