Hand off today
First drafts, outlines, headline variants and length trims.
Productivity & daily use
Quick answer
Describe a single task rather than a whole job and the tool scores its exposure to automation, estimates the hours you would get back each month, and lists the guardrails needed before handing it over. Task-level scoring is far more actionable than a job-title score, because tasks are what you actually delegate.
Not your whole job — one task. Pick the category, see the split between what hands off cleanly and what stays yours.
Published · Last updated
Task exposure
80%
Most of this task is already automatable. Your value moves to review and judgement.
First drafts, outlines, headline variants and length trims.
The argument, the point of view and the final edit.
Never publish a draft you did not rewrite at least once in your own voice.
Spend the reclaimed time on interviews and original examples — the part nothing can fake.
Each category carries a fixed exposure figure based on how much of the work is text in, text out, with verifiable output. Data cleanup and drafting sit high; negotiation and feedback sit low, because the value there is trust rather than throughput.
Hours back apply a sixty percent realisation factor to the exposed share. You never recover the full theoretical saving, because reviewing, correcting and re-prompting all cost real minutes that most estimates quietly ignore.
The guardrail line matters more than the number. Almost every bad outcome from delegating work to a model comes from skipping verification on the one task where being wrong was expensive.
| What it answers | Exposure, hours back and guardrails per task. |
|---|---|
| How the answer is produced | Whole jobs are almost never automated; individual tasks are. |
| What you need to enter | Describe one narrow task, not a responsibility. |
| Where it stops being reliable | It scores the task as you describe it; a vague description produces a vague score. |
| Cost and sign-up | Free, runs in your browser, no account and no stored inputs. |
Whole jobs are almost never automated; individual tasks are. This tool works at that level, scoring one specific task on four dimensions: how structured the input is, how objectively the output can be checked, how costly a mistake would be, and how much context outside the task is required to do it well.
Structured input with checkable output and a cheap failure mode is the profile that automates immediately. Ambiguous input, subjective quality and expensive failure is the profile that stays human even when the model is technically capable of attempting it.
The estimated hours returned come from your own stated frequency and duration, discounted by a realistic supervision overhead. Reviewing generated output is not free, and plans that assume it is are the reason automation projects under-deliver.
Automation conversations usually happen at the wrong level of granularity — asking whether 'my job' can be automated invites a defensive, all-or-nothing answer, when the honest picture is that most jobs are bundles of dozens of tasks with wildly different automation profiles sitting side by side. Scoring one task in isolation produces an answer you can actually act on: adopt automation for the three tasks that score well, keep doing the rest yourself, and the job as a whole is untouched even though a meaningful slice of the week changes.
Interpreting the four-dimension score means recognising that structure and checkability usually move together and dominate the result — a task where you would recognise a wrong answer in seconds is fundamentally different from one where quality is a matter of judgement, even if both take the same amount of time today. Cost of failure acts as a multiplier on top of that: a task that is structured and checkable but where an error reaches a client unreviewed deserves a much lower score than the same structure applied to an internal draft.
What changes the estimated hours saved most is the supervision discount, and it is the single figure people are most tempted to skip, because reviewing a generated draft feels like it should be nearly free compared with writing it from scratch — it usually is not, particularly for anything leaving the building. The most common mistake is describing a responsibility rather than a task, which produces a meaninglessly broad score; narrow the description until it names one concrete, repeatable action before scoring it.
Describing this task at three times a week, twenty minutes each, scores high on structure and checkability, since the inputs are last week's metrics and the output is easy to verify against them. The tool estimates roughly forty minutes saved weekly after a 30% supervision discount, which is realistic since a wrong figure in a client email is embarrassing but not costly enough to require a second reviewer.
Describing this task scores low, despite being frequent, because the cost-of-failure dimension dominates: a mishandled escalation can lose an account, and the input — an upset customer's specific complaint — is not structured enough for reliable checking of an automated response before it is sent. The tool's guardrail flags this as a task to keep entirely human, or at most to use for drafting internal notes after the call rather than customer-facing text.
Describing this task at fifty times a day, roughly two minutes each, scores near the top of the range: the input is a short text with a small fixed set of valid categories, so a wrong categorisation is cheap to spot and correct with a single click rather than a rewrite. The tool estimates over an hour saved daily even after discounting for a supervisor spot-checking a sample of the categorisations each shift.
High-frequency, low-stakes tasks with output you can verify in seconds — first drafts, formatting, summarising, categorising.
Budget roughly a quarter to a third of the original task time for review on anything that leaves your team. Skipping that budget is how errors reach clients.
Usually the reverse in the short term: the person who understands where the output fails becomes the one who owns the process.
Start with whichever has the higher frequency, since the four-dimension score measures fit rather than total time saved — a task done fifty times a week at a moderate saving per instance usually beats a task done twice a week at a larger saving per instance, and the more frequent habit is also easier to build and notice the benefit of.
Written and reviewed by Jim Vernon, Editor, AI Intelligence International. Published by AI Answer Engine, a service of AI Intelligence International, and checked against our editorial standards.