Incident logging

Records every failure with its asset, cause and fix at the moment it happens, so a repeat fault stops being diagnosed from scratch.

macOS — coming soonSee the automation
Ops / AUTOMATE.md

At the start of each month, group closed incidents by cause and draft a repeat fault summary.

Ready-made: Incident recurring pattern

The job, and what good looks like.

Incidents reach the system a day late, or as a note in a shift log nobody keeps, so the record of what broke lives in three people's heads and the monthly review starts from a blank page. Anyone on shift reports a failure from the floor with the asset, the time, the symptom and what stopped. Each report is matched against the equipment history and against any open incident on the same asset, so a repeat is flagged as a repeat instead of opening a fresh investigation. Cause codes come from the team's own list, downtime hours are captured against the production lost, and anything still unclassified after a day is queued for the reliability engineer rather than left ambiguous. The weekly digest shows what is open, what is overdue and which assets keep failing. What a human still decides is the cause code itself, which incidents become permanent fixes, and which workaround gets the crew first when a patch and a real repair compete for the same day.

When it is handled

  • Every failure logged the day it happens
  • Repeat causes visible by asset
  • No fault diagnosed twice
  • Downtime cost traced to a cause

Works with tools like

  • ServiceNow
  • Freshservice
  • MaintainX
  • Grafana
  • monday.com

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.

Incident recurring pattern

At the start of each month, group closed incidents by cause and draft a repeat fault summary.

On the first working day of each month

You stay in charge.
At every step.

It checks and drafts. Your team decides what is ordered and sent.

  • No order placed on its own

    Requisitions and supplier notes wait for a buyer to approve and send.

  • Undo what you don't want

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

  • Only the systems you connect

    Each automation reaches only the folders and apps you give it.

Incident recurring pattern

Approve before it saves the document?

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 ERP's alerts and rules

Flagging thresholds inside the ERP.

They can't read a supplier's email or a scanned delivery note, or draft the next step.

Flowchart automation tools

Moving data between apps at high volume.

Real-world exceptions multiply branches until the flow is harder to follow than the work.

AI chat assistants

Explaining a document when you paste it in.

Deliveries keep arriving while nobody is asking, and the procedure lives 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