What Is AI Automation? The Definition We Build Against

AI automation is software that carries a piece of work from trigger to done, with a model handling the steps that used to need a person's judgment: reading, classifying, deciding, drafting.

That sentence is the definition we build against, and every word in it is doing a job. This post unpacks it, draws the boundaries, and gives you a test for whether a task in your company qualifies.

What Each Part of the Definition Means

"A piece of work." Not a department, not "operations," not a transformation. A nameable unit someone currently does: answer this inbound email, process this invoice, produce this Monday report. Automation succeeds at the granularity of pieces and dies at the granularity of visions.

"From trigger to done." The trigger is the event that starts the work: an email arrives, a form is submitted, the clock strikes Monday. Done is a state you can test: the reply is sent, the record is updated, the report is delivered. If either end is fuzzy, what you have is not yet an automatable piece of work; it's an idea.

"A model handling the judgment steps." This is the part that's new. Traditional automation moves data between systems on fixed rules, and it's excellent at that. What it could never do is the part in between: someone still had to read the email, decide what it was about, and write the response. Those judgment steps kept a person in the loop of every run. A model can now carry them, which means the whole piece of work can run, not just its mechanical halves.

What AI Automation Is Not

The category is easier to hold onto once you know its neighbors:

• Not a chatbot. A chat window waits for a person to bring the work to it, sentence by sentence. An automation is wired to the trigger and runs without being asked.
• Not a copilot. Copilots make a person faster at a task the person still performs. Useful, but the work still routes through human hands on every run. Automation removes the run from the queue entirely.
• Not a tool subscription. Buying an AI tool gives you a capability. Until that capability is wired to your triggers, your systems, and your definition of done, no work is being carried. (This distinction has its own post: AI Automation Tools Are Not AI Automation.)
• Not plain integration or RPA. Zapier-style integration and RPA are automation, and where the work is fully rule-shaped they're the right tool. They stop at the judgment steps. AI automation is the superset that covers those steps too. Choosing between an LLM, RPA, and classic ML for a given problem is its own decision, and we published a framework for it.

The Four Kinds of Work It Carries

Across companies and industries, the pieces of work that qualify cluster into four categories, which is how we organize our own practice:

1. Intake. Email, documents, forms, and tickets read, understood, and routed the moment they arrive.
2. Triage. Requests classified and the next step decided: by rule where a rule exists, by model where it doesn't.
3. Drafting. Responses, summaries, and first drafts written for a person to approve rather than start from blank.
4. Reporting. What happened, pulled from the systems where it happened, delivered on schedule.

Most companies' first successful automation is an intake or drafting piece: high volume, bounded judgment, obviously reversible. When the middle of the work is too varied for fixed rules and the model chooses the route at runtime, the automation has a specific name and its own trade-offs: that shape is an agentic workflow. The gap between receiving a signal and acting on it is usually the most expensive quiet problem in the building; we wrote about that gap in The Intake-to-Action Loop.

Does the Model Get the Last Word?

The definition says a model handles the judgment steps. It does not say a model gets the last word. In a well-built automation, routine steps run and report what they did; consequential steps (sending money, deleting records, making commitments to customers) wait for a person's approval before they happen. Deciding which steps are which is a design decision the client makes, not a default the software imposes.

This is also the honest answer to the fear that "AI automation" means firing the people who do the work today. What it removes is the reading, re-keying, chasing, and blank-page drafting. What it leaves is the judgment that was always the actual job.

A Three-Part Test for Your Own Work

A piece of work is a candidate for AI automation when it passes three checks:

1. The trigger is observable. The work starts with an event a system can see: a message, a file, a status change, a schedule.
2. Done is testable. You can write one sentence that a system could check: the reply is sent, the record matches, the report is in the inbox.
3. The judgment is bounded. The human steps in the middle are reading, classifying, deciding among known options, or drafting from known material. If the middle requires novel strategy or relationships, automate around it, not through it.

Run that test across a department and you'll typically find a dozen candidates before lunch. Ranking them (by volume, by reversibility, by how much the delay costs) is the real planning work, and it's a better use of a planning hour than any vision deck.

If you'd rather walk through that ranking with people who deploy these systems for a living, tell us about the work you want carried.