Document Approval Workflows With a Human in the Loop

TL;DR: Human in the loop means an automated workflow stops and waits for a person before it does something that matters. It holds up only when people review by exception: confident, reversible moves go through and are logged, while new folders, unsure matches, and anything destructive wait for a decision. In The Drive AI, the Ask a Person to Approve step pauses the run, shows the file and the planned move in the Approvals inbox, and nothing downstream runs until someone approves, rejects, or the wait expires.

A finance lead gets 214 approval notifications a week. She approves all of them, not because she reads them but because clearing the queue is the only way to get back to work. The control exists on the org chart. It stopped working months ago.

That is the real risk in letting software file your documents. Not that the AI gets one invoice wrong, but that the review you added to catch it has turned into a button people press. Human in the loop is the fix and also the trap: done well, a person decides the few things that need a person; done badly, the rubber stamp buys false confidence.

A human in the loop document approval workflow is an automated sequence that stops at a defined point, hands one specific decision to a named person or group, and runs nothing downstream until that person decides or the wait runs out.

What does human in the loop mean in document automation?

It means the automation cannot continue past a step without a human decision. Not a notification. A hard stop.

Three things make it real. Execution halts at a defined point, rather than a message going out while the file moves anyway. A specific person has the authority and the context to decide, and can see what the system is about to do. The decision is recorded against the file, so months later you can answer who approved it.

A Slack alert saying a file was filed is a broadcast, not a loop. Nothing waited, so a wrong move stays wrong until someone notices. Plenty of tools advertising AI with human review work this way: review is available, not required.

Why does approval fatigue break most approval workflows?

Because attention is a fixed budget, and routing everything through a person spends it on the documents that never needed one.

Two hundred documents a week at a genuine 40 seconds each is over two hours of focused attention, arriving in 30-second interruptions. Nobody sustains that. The reviewer learns, correctly, that almost everything is fine, and clears in bulk.

You can measure the failure without asking anyone. Approvals cleared in under three seconds each. A rejection rate of zero across hundreds of decisions, because a control that has never said no is not a control. Routing more through review after an incident only makes the queue deeper and the next miss more likely.

Review by exception: what should a person actually see?

Review by exception means the system acts on its own where it is confident and the move is reversible, and asks a person everywhere else. The queue then gets short enough to read.

Two questions decide every step. Is this reversible, and is the system confident?

• Reversible and confident. A clearly identified invoice filed into a vendor folder that already exists. Let it go, and log it. A wrong move costs one drag back.
• Reversible and unsure. The document could be a quote or an invoice. Ask: it is cheap, and the answer is fast because the question is narrow.
• Irreversible, at any confidence. Deleting, sending outside the company, paying. Ask every time.

Three things should never run without a person. Anything destructive, including soft deletes, because nobody looks in trash for a file they do not know is missing. Anything that creates new structure: filing into an existing folder is a move, but creating Clients/Northwind Holdings/ beside the existing Clients/Northwind/ decides how the company is organized, and one unreviewed new folder becomes twelve by quarter end. Anything the system is unsure about, because surfacing borderline cases beats resolving them silently.

The principle predates AI: expense policies and exception reports have always worked this way, and it runs through the complete guide to automated document workflows.

How does Ask a Person to Approve work in The Drive AI?

Ask a Person to Approve is a step you place anywhere in a workflow. It pauses that run, and nothing downstream runs until someone decides.

You describe the workflow in plain English and the steps appear on a canvas, each carrying a cost badge. This one is human: the run waits. The others are free, ai, and external, covered in the guide to every workflow step.

The step has four settings.

What should the approver decide? Free text, shown in the Approvals inbox next to the file. Write the real question: "OK to file this in the client folder?" beats "Approve?", and that decides whether someone thinks or clicks.

Who decides? Admins asks every owner and admin. Specific people asks named members, which is how a payment threshold reaches whoever owns that budget. Everyone asks the whole workspace. In all three, any one person asked can decide.

When to ask? Always ask stops every file, which is right for a branch only irreversible files reach. Only when unsure is review by exception in the product: confident filing into existing folders goes ahead and is logged, while new folders, unsure matches, and anything destructive still ask.

Under "Only when unsure" a caution setting offers three presets. Careful acts on its own only when nearly certain and asks about the rest. Balanced acts on confident matches and asks about borderline ones. Relaxed asks less often, so more borderline matches go through on their own. Start at Careful and loosen as the questions start looking obvious.

Wait up to is 24 hours, 3 days (the default), or 1 week. Then the file takes the Expired exit.

What keeps the queue honest is that the request shows the plan, not just the question: the file, what it will be renamed to, and where it will go. Every decision is recorded on the run, and any run can be replayed on the canvas exactly as it happened.

The three exits

The step has three exits: approved, rejected, and expired. Whatever you connect to each is what happens. Approved usually continues to Rename and Move. Rejected is where the useful design happens: send the file to a review folder, or message whoever submitted it, so a rejection produces an outcome rather than a dead end. If nothing is connected to an exit, nothing happens to the file, and the outcome is still recorded.

Example approval workflows

Each is a sentence a user types. The approval settings are edited on the canvas.

An invoice over a threshold, held for a named approver:

When an invoice arrives from @pineconesystems.com, read the vendor and the total. If the total is over $5,000, ask Dana to approve first. If she approves, file it under Vendors/Pinecone Systems/2026. If she rejects, move it to Finance/On Hold.

A contract missing a signature, routed to legal:

When a contract lands in Clients/Northwind/Contracts, check whether it is fully signed. If it is, rename it with the counterparty and the signing date. If a signature is missing, ask the legal team, and if they reject it file it under Clients/Northwind/Contracts/Unsigned.

A new hire packet with a form missing:

When a file is shared in the #people-ops Slack channel, check whether it has a signed offer letter, a W-4, and an I-9. If all three are there, file it under HR/New Hires/2026. If one is missing, ask the People team and say which form is missing.

A deletion branch that always asks:

On the first of every month, go through every file in Marketing/Archive. If a file is older than 540 days and larger than 200 MB, ask an admin, and move it to trash only if they approve. Wait up to a week.

On the last one, set Always ask and leave the Expired exit unconnected: nobody deciding means nothing is deleted. Files you already have are handled by scheduled workflows.

Which review model should you use?

Power Automate handles approval mechanics well and licenses alongside Microsoft 365. Its limit sits upstream of the approval: flows branch on metadata, file events, and column values, so whether a file gets held depends on a column someone filled in, unless you add AI Builder.

Limits worth knowing

Approvals expire. Three days is the default, and then the file takes the Expired exit. The only escalation is the wait length and what you connect to that exit.

Any one person in the chosen group can decide, so there is no two-person sign-off and no ordered chain. Each approval belongs to one run and one file, so a workflow handling 40 files creates 40 pending decisions, the argument for "Only when unsure" on anything with volume.

Steps with the ai badge read the file and can occasionally be wrong, which is what the approval step is for.

A workflow watching a folder in Google Drive, OneDrive, SharePoint, or Dropbox renames and moves files in place, inside that storage. Nothing is imported unless the workflow includes a Save a Copy step, and the mailbox or channel behind an attachment is never modified.

Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail, Outlook, Slack, Teams, Google Drive, OneDrive, SharePoint, or Dropbox needs the Max plan on a personal workspace, or any Team plan.

Setting it up

1. Pick the one decision that needs a person, not a category: a payment above a threshold, a contract without a signature, a deletion.
2. Connect the source: a mailbox, as in Gmail attachment workflows, a Slack channel, or a folder in your existing storage.
3. Describe the workflow in plain English, approval included: "ask Dana first" is enough for the step to land in the right place.
4. Set the four fields. Write a real question, choose Specific people for anything with an owner, and use Always ask on irreversible branches, Only when unsure elsewhere, starting at Careful.
5. Connect all three exits. Approved continues, rejected goes somewhere a person will look, and Expired does nothing only if you decide that deliberately. Then watch the inbox for a week: a queue nobody reads means the step asks too often.

Payables teams usually start from accounts payable workflow automation, and HR teams from onboarding packets.

Frequently Asked Questions

What is human in the loop automation?

Human in the loop automation is a process that runs on its own until it reaches a point where a person must decide, then stops and waits. What matters is whether the work actually pauses. A system that notifies you while continuing is not human in the loop, it is a system with a log. In document workflows the pause applies to one file and one run.

How do I stop approval fatigue in a document approval workflow?

Reduce the number of decisions rather than the time spent on each. Set the approval step to "Only when unsure" so confident filing into existing folders goes ahead and is logged, while new folders, unsure matches, and anything destructive still ask. Show the plan, not just a question. Then watch queue depth and rejection rate, which tell you whether anyone is reading.

Can AI file documents without a person approving every one?

Yes, and that is the point of review by exception. Under "Only when unsure" the workflow acts on confident matches into folders that already exist, records what it did, and holds back borderline cases. The caution setting has three presets: Careful acts only when nearly certain, Balanced acts on confident matches, and Relaxed lets more borderline matches through.

What happens if nobody approves a document in time?

The file takes the Expired exit after the wait you chose, which is 24 hours, 3 days, or 1 week. Whatever you connect to that exit is what happens next. If nothing is connected, nothing happens to the file and the outcome is still recorded, which is the safe default on a deletion branch. On a filing branch, connect Expired to a holding folder.

How is this different from a Power Automate approval?

Power Automate has an Approvals action and routes reliably across SharePoint, OneDrive, Outlook, and Teams. The difference is the condition in front of it. Power Automate branches on metadata, file events, and column values, so whether a file gets held depends on a column filled in correctly, unless you add AI Builder separately. Here the branch reads what the document says, so a $5,000 threshold works on the total inside the PDF.

Start with one approval step

Pick the single decision you would not want a machine making alone, put a person in front of it, and let everything else file itself and stay on record. Create your first workflow, or see what Workflows do on either side of the approval.