People lose 6.4 hours a week supervising AI. Cut the context tax, keep only the review that matters and get the hours back with an AI employee.
To cut the hours you spend babysitting AI, stop carrying context to the AI and put the AI where the context already lives: in the work chat, with real read access to the tools that hold the facts and a memory of past corrections. Keep review only on output that touches money, customers or the public record, make that review a one-reply approval, and count corrections so you can see whether the supervision load is falling. Done that way, most of the six-plus weekly hours people lose to supervising AI come back within a month.
Key takeaways
- The time AI saves is being spent supervising AI. In the Work AI Index 2026 from Glean’s Work AI Institute, a survey of 6,000 digital workers, people report saving about 11 hours a week through AI and then spending 6.4 hours a week making AI usable.
- Four buckets, and only some of the work is worth doing. The same report splits that time into feeding context (2.3 hours), supervising output (2.2 hours), debugging (1.7 hours) and cleanup or tool switching (0.2 hours).
- Re-pasting context is the biggest and most avoidable bucket. If the AI already sits where the conversation and the files are, most of that typing disappears.
- Reviewing high-stakes output is not waste. Keep it, make it fast, and stop fully re-auditing the same job once it has been right twenty times.
- Running one request through three tools is a symptom. It means no single tool has enough context to be trusted, so you compare guesses instead of using an answer.
- Track supervision hours like saved hours. Untracked supervision is why leadership sees a productivity story nobody on the team recognises.
What is babysitting AI?
Babysitting AI, which the Work AI Index 2026 calls “botsitting”, is the unrecognised work of making AI output usable: feeding it context, checking what it produces, re-prompting when it misses, and cleaning up after it. The report puts it at 6.4 hours a week for the average digital worker, more than the time people spend using AI to produce work in the first place.
A simple experiment shows the shape of it. One operations lead kept a note for a week every time she typed something into an AI tool that the tool should already have known: which client, which quarter, which spreadsheet, which naming convention, what the team decided in a thread two days earlier. By Friday the note had 41 entries. None took longer than four minutes. Together they cost her most of a working day, and the output still needed a read-through because the tool had never seen the underlying files.
Why does AI create work while saving time?
Because most AI tools are strangers to your business. Every session starts from zero, so a person hands over the context first, then verifies what comes back, because a stranger’s confident answer cannot be trusted on sight.
The Work AI Index found that 87% of digital workers use AI at work and 75% say it makes them more productive, while only 13% say their organisation performs significantly better because of it. Those findings only fit together if the gains are eaten somewhere between the desk and the business result. The leak is almost always structural, not personal. Nobody is prompting wrong. The tool has no memory, no access and no shared thread with the team, so a human keeps stepping in to connect the pieces.
Where the hours go | What it looks like on a Tuesday | Worth keeping? |
|---|---|---|
Feeding context | Pasting the same client background, last quarter’s numbers and tone rules into a fresh chat | No. The system should already have this |
Supervising output | Reading a summary against the source spreadsheet before it goes to a client | Yes, on anything that leaves the building |
Debugging | Re-prompting, adding detail, switching models until something usable appears | Rarely. Usually a missing-access problem in disguise |
Comparing tools | Running the same request through three different tools because none felt right | No. Pick the one that can see your work |
Cleanup after handoff | Fixing work someone shipped without reading it | No, and it lands on the wrong person |
How do you cut the context tax?
Stop retyping what already exists in your tools, and put the AI where the context lives.
That means three changes:
- Make the request where the decision was made. When you ask in the chat thread where the work was discussed, the thread itself is the brief.
- Connect the tools that hold the facts. With real read access, numbers get pulled instead of pasted.
- Store corrections. The second request should start from the corrected version, not from the original mistake.
The difference is easiest to see in one request to an AI employee who already has access:
Nothing in that message explains what Northvale is, where the data lives or what the format should be. Nine of the 41 entries in the operations lead’s note were format instructions she had already given once.
A useful test before you adopt any AI tool: give it a task on Monday, come back on Thursday and reference that task without re-explaining it. If the thread continues instead of restarting, the context tax mostly goes away. If it asks you to restate everything, you have bought yourself another supervision job.
Which supervision should you keep?
Keep review on anything that touches money, customers or the public record, and make the review cheap rather than optional.
Cheap review has two properties. The output arrives next to its sources, so checking it is a glance rather than an investigation. And it arrives as a draft in the same thread as the request, so approving it is one reply instead of a copy-paste into another tool.
Type of output | Review level |
|---|---|
Money and legal | Always reviewed, no exceptions |
Client-facing writing | Reviewed until the voice is consistently right, then spot-checked |
Internal reporting | Reviewed for the first month, then checked monthly against the source |
Research and first drafts | Read, not audited; the cost of a bad draft is a rewrite |
The report’s framing is worth borrowing: verifying high-stakes output is productive supervision, while reloading context or comparing three tools is not. Sort your week into those two piles and cut the second one.
How do you make invisible AI work visible?
Put a number on it, because untracked effort never gets fixed.
The Work AI Index found that frequent botsitters are 73% more likely to be actively looking for another job. The mechanism is familiar: someone quietly absorbs the cleanup, gets no credit because it is not on any plan, and eventually stops absorbing it, which pushes the mess downstream to someone with even less context.
Two habits fix most of it:
- Name an owner for each recurring AI job, so cleanup has an address instead of landing on whoever opens the file.
- Count corrections. If ten outputs a week need a human fix and that number never falls, corrections are not being stored anywhere. That is a tool problem, not an effort problem.
You can even hand the counting to the AI itself:
An AI that reports on the jobs nobody reads is more useful than one that only reports wins.
How do you get the first hours back this month?
Pick the single job you re-explain most often, move it to where your team already talks, and connect the two tools that hold its facts.
- Choose one weekly job and write the request once, naming its sources.
- Keep review on for two weeks.
- Correct in the thread every time something is off, so the correction is stored.
- After two weeks, schedule the job so the output arrives before anyone asks.
What not to do: buy a second AI tool because the first keeps missing context. That trades a context problem for a switching problem. The Work AI Index found 77% of workers already juggle several AI tools every week, and a third use four or more.
How an AI employee changes the supervision math
An AI employee lives in the work chat, keeps memory across weeks and has access to the tools where the facts sit, so the context work happens once instead of at every request. Viktor works this way: he sits in Slack or Microsoft Teams, connects to 9,800+ tools, drafts first and waits for approval before sensitive actions, and remembers the corrections your team gives him. That moves your hours from feeding context and debugging into the one kind of supervision worth keeping: a quick approval on work that matters.
FAQ
What is botsitting?
Botsitting is the Work AI Index 2026 term for the unrecognised work of making AI usable: feeding it context, supervising its output, debugging its mistakes and cleaning up after it. The report puts it at 6.4 hours a week for the average digital worker.
Why do I spend so long explaining things to AI?
Most AI tools have no memory of your business and no access to your systems, so each session starts from nothing. The fix is persistent memory plus real read access to the tools that hold the facts, not longer prompts.
Is reviewing AI output a waste of time?
No, on anything that reaches a customer, a regulator or a set of accounts. It becomes waste when it is the only defence, when the same thing is re-audited forever, or when checking it means opening five tabs to find the sources.
Does using more AI tools help or hurt?
Usually it hurts. Running one request through several tools produces answers to compare instead of an answer to use, and the context has to be loaded into each of them. One tool that can see your actual work beats three that cannot.
How do I measure the time my team loses to supervising AI?
Keep a one-week log: every time you retype context, re-prompt or fix AI output, note the task and the minutes. Many teams find the total is close to a full day per person per week.
Can I stop reviewing AI output eventually?
On narrow, repetitive jobs with a clean record, yes, and it should be a deliberate decision rather than drift. Keep review permanently on money, legal and anything public.
Start cutting supervision hours today
Take the job you have re-explained three times this month and hand it to Viktor in the channel where the work is already discussed. Start free with up to $100 in credits, no credit card required, connect the two tools that hold the job’s data, and count the minutes you no longer spend on it.
Ask ChatGPT
Ask Claude