How to Know if AI Can Do Your Task: A Simple Test

Every article about AI tells you what it can do in general. That is not the question you actually have. Your question is about the specific thing on your list, the one with the awkward exception and the client who always wants it differently.

General capability lists cannot answer that, because whether AI can do your task depends less on the AI than on the task. The good news is that you can work it out yourself in about three minutes, without trying it first.

The test below is the one we use internally before handing anything over. It has no scoring spreadsheet and no maturity model. It has four questions, and the reason it works is that each one maps to a real property of how this technology succeeds or fails.

It also assumes the right setup. A chat window fails question two on almost every task, because it has no access to anything. An AI Employee on Sistava connects to the mailbox, files, calendar, and records the task actually lives in, holds a standing brief, remembers your corrections, and runs on a schedule. That changes which tasks pass.

How do I know if AI can do my task?

Run these four questions in order and count the yes answers. Each one tests a different failure mode, and a task that fails any of them fails for a reason you can usually fix. Do not skip ahead to the answer, because the value is in noticing which question you hesitated on.

The questions are deliberately about your task and your business, not about the model. Nothing here requires you to understand how AI works, and that is intentional.

• Can you describe it in five lines? What starts it, what information it needs, what a good result looks like, what tone, and where it stops and asks you. If you cannot write those, the rule is in your head and the AI will invent a different one.
• Is everything it needs written down and reachable? The rate card, the past emails, the customer record, the policy. If a key input exists only in your memory or on a whiteboard, the output will be plausible and wrong.
• Can you spot a bad result in under two minutes? You have to be able to check the work quickly. If verifying takes as long as doing it yourself, you have moved the work rather than removed it, which is the most common quiet failure.
• What does undoing a mistake cost? A bad draft costs nothing. A wrong refund costs money and trust. This question does not decide whether to hand the task over, it decides whether a human stays on the trigger permanently.

What do the scores actually mean?

Four yes answers with a cheap undo cost means hand it over and let it run unattended after a week of drafts. Four yes answers with an expensive undo cost means hand it over but keep the approval step forever. Three yes answers means fix the failing one first, and it is almost always question one or two.

Two or fewer means the task itself is the problem. That is genuinely useful information, because a task nobody can describe and nobody can check is also a task no human employee could take over from you. Automation just made the gap visible.

What does the test look like on real tasks?

It looks like a five item list where two pass, two need a fix, and one should never be handed over. Ken runs a print shop with four staff doing signage, business cards, and short run booklets. He ran the test on the five jobs he most wanted off his plate.

Quoting standard print jobs scored four yes with a cheap undo. The rules are on a price sheet, the spec arrives in the enquiry, and a wrong quote is caught in ten seconds. It went first, and now every standard enquiry gets a same day quote instead of a next day one.

Chasing artwork from customers also scored four. Reordering paper stock failed question two, because the reorder points lived in his head, not in the system. He spent forty minutes writing them into the stock sheet and it passed on the retest.

Quoting complex jobs failed question one. His pricing on unusual work depends on whether the customer is likely to change their mind twice, which he cannot express as a rule because it is a judgment about people. And handling complaints scored three yes with an expensive undo, so the AI drafts the reply and Ken always sends it himself.

What if my task is mostly, but not entirely, describable?

Split it. Almost every task that feels borderline is actually two tasks stapled together: a mechanical part with clear rules and a judgment part that needs you. Handing over the mechanical half is where most of the time saving lives anyway.

Ken's complex quoting is the example. The measuring, the material calculation, and the drafting all pass the test easily. Only the final number needs his read on the customer. So the AI prepares the whole quote and leaves the price blank.

If a task fails on the judgment side for reasons that feel permanent, that is worth understanding properly rather than working around. The structural limits are laid out in what AI still cannot do, and they explain most of the hard no answers.

How do I run the test properly?

Take your three most annoying recurring tasks, score each one on paper, and act on the highest scorer. Doing it on paper matters, because the point is to notice which question made you pause. That hesitation is the actual finding.

Running the test on your own work

1. List your three worst recurring tasks — Recurring is the filter. A one off task is never worth the setup, however painful it was. Write down how often each one happens.
2. Try to write five lines for each — Trigger, inputs, what good looks like, tone, and the stop line. The one you cannot finish is telling you something important about your own process.
3. Check where each input actually lives — For every piece of information the task needs, name the file, mailbox, or record it sits in. Anything you cannot name is in your head and needs writing down.
4. Time yourself checking one past output — Take a result you produced last week and see how long it takes to judge whether it was good. Over two minutes means the task needs splitting.
5. Write the undo cost next to each — In money or in trust. This decides whether the approval gate is temporary or permanent, and it is the one answer you should never soften.
6. Hand over the winner and retest the rest — Act on the highest scorer this week. Fix the failing question on the others and they will usually pass a fortnight later.

People are often surprised that the test rules out fewer tasks than they expected and rules out different ones than they expected. The task you assumed was too complicated usually passes. The simple one you assumed was easy often fails question two.

That is because complexity is not the constraint. Describability, reachable inputs, and checkable output are the constraints, and those are properties of how organized your business is rather than how hard the work is.

What if I get it wrong?

You will, on one of the first few, and it costs almost nothing if you kept the approval step on. That is the entire purpose of the draft week. A task that turns out to be a bad fit shows up as drafts you keep rewriting, and you will know by day three.

Plans start at 50 a month, so the cost of a wrong guess is a week of reviewing drafts rather than a wasted project. That is a much cheaper way to find out than a planning exercise.

Once you have scored a few tasks you will start seeing which role should own them, and that is the next decision rather than this one. The framework below covers choosing the first employee rather than the first task.

Whether AI can do your task depends on the task, not the technology. Describable, reachable, checkable, and reversible are the four properties that matter. Score your three worst jobs on paper this week, and act on whichever one scores highest rather than whichever one annoys you most.