Onboarding docs
Builds each new hire's document pack from the role template and chases signatures until it is complete, so nobody starts a job without a signed contract or a valid payroll form.
When a start date is confirmed, build the new hire's onboarding document pack from the role template and send the links to the hire and the manager.
The job, and what good looks like.
The paperwork a new hire signs is the most binding thing an employer does, and it is usually handled by whoever has a spare afternoon. Each document is sent separately, one of them is missed, and the returned copies sit in a folder with nowhere to belong. This workflow builds one pack per person from the template matching their country, employment type, and role: the contract, the confidentiality agreement, the payroll starter form, and the handbook acknowledgement. The pack goes out as a single signature request, so the person signs once and every completed document returns to the same place. Anything unsigned is listed with the date it went out, with the hire, their manager, and the payroll deadline named beside it, so chasing is visible rather than a favour. Documents a contractor or an overseas hire needs are added from the list for that jurisdiction. A human still checks the template is the right one, watches for a signature from the wrong address, and tells the hire directly when something will not be back in time. The workflow makes the pack complete and provable; it does not replace the welcome.
When it is handled
- Signed documents filed before day one
- One pack per hire, from the role template
- Nothing requested twice from a new hire
- Payroll never blocked by a missing form
Works with tools like
- BambooHR
- HiBob
- DocuSign
- Dropbox Sign
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.
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.
Onboarding pack draft
Approve before it sends the email?
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
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 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.