Guide · Approve-first
Human-in-the-loop automation
Human-in-the-loop automation is a pattern where AI prepares the work and a person approves it before it takes effect. The machine drafts, researches and assembles; a named human makes the decision that reaches a customer, spends money, or publishes in public. The practical question is which decision a person must make, what they need to review, and what happens if they say no.
In this guide7 sections
In the loop, on the loop, out of the loop
Three positions, and most teams use all three at once on different work. Naming which one applies where is most of the job.
Swipe to read all columns →
| Position | What it means | Where it fits | What it costs |
|---|---|---|---|
| In the loop | The work stops. A person reviews and approves before the action happens. | Anything that reaches a customer, spends money, or is published in public | One review step; the work waits for a person |
| On the loop | The work proceeds. A person watches, can intervene, and reviews the record afterwards. | High-volume, low-consequence steps a team has already watched for a while | Mistakes are caught after the fact, not before |
| Out of the loop | The work runs under predefined rules without routine human review. Exceptions can still be reported to an owner. | Internal, reversible, well-bounded tasks | Problems may persist without monitoring, limits and an exception path |
Why teams want a gate before send, spend and publish
Not because the model is bad at writing. Because these are the five failures that are cheap to prevent and expensive to undo.
The wrong claim, in public
A confident sentence about a capability, a price or a result that is not exactly true. Cheap to catch in review; expensive to retract.
The wrong recipient
A sequence that goes to a competitor, a customer who already complained, or the same person twice. Nothing about the copy is wrong — the routing is.
Budget on an untested variant
Ad spend behind creative nobody looked at. The loss is not the impressions; it is the week you spent believing the test.
Voice drift
Everything is defensible and none of it sounds like the company. It shows up gradually, which is why it survives.
No record
It went out, it worked or it did not, and the reason lives in a chat thread nobody will open again.
Where the gate belongs
At the boundary where work leaves the company. Three boundaries cover almost everything: before an email or sequence sends, before budget is spent, before content is published to a public destination.
Research, drafts, captions, ad variants and summaries can be prepared for review. Decide which internal steps also need oversight based on the information and tools involved. Make the approval boundary clear before introducing automation.
Hypothetical ecommerce example
A customer asks why an order is late. An agent prepares a reply using the order record and the latest available shipping status. The reviewer sees the customer, the source information and the exact message, including any delivery promise, before approving the send. Missing or conflicting information goes to a person.
Ask to see what happens when the reviewer rejects the draft or edits its recipient. The action should remain stopped until the revised work is approved. This illustrates an approval pattern; it does not establish a live OfficeSpace order or shipping connection.
Improve preparation and keep approval
Give AI a clear preparation task and give the reviewer a clear decision. To choose that first task, see the AI implementation gap. Keep approval before anything sends, posts, or spends.
01
Start with the gate on everything
Every send, every spend, every publish stops for a person. This is the default because it is the state you can reason about.
02
Watch one desk for a few weeks
Approve the work and notice what you are actually changing. If you approve thirty items without editing one, that is data.
03
Improve preparation from reviewed work
Use corrections to improve internal drafts and research. Keep a person’s approval before anything sends, posts, or spends.
04
Keep the record either way
Keep the request, the decision, and what was observed at the destination. A completion message alone does not show the outcome.
05
Move it back when something changes
Review the workflow again when the task, team, or business rules change. Keep the person responsible for approval clear.
What to keep as evidence
An approval that leaves no record is a feeling. The minimum worth keeping: the request and source information, the exact content and recipient reviewed, who approved it, when the action was attempted, and whether it landed as intended. Material changes after approval need a fresh decision.
That last part is the one teams skip. Approve is not the finish line — a send can bounce, a post can fail, a platform can accept the call and publish nothing. Knowing the outcome turns an approval into an observation your team can review.
A useful demonstration includes an unsuccessful action. Check that the record distinguishes a draft, an approval, an attempted send and a confirmed result, and that the team can identify who handles an unresolved outcome.
Related: How to review an AI agent’s work · CRM handoffs.
Approval and checking the outcome
OfficeSpace by 77systems gives your agents the tools to run your business. You set goals and approve. Your agent plans and coordinates. OfficeSpace brings the business knowledge, departments, workflows, controls and tools into one place. For documented examples, see the workflow examples at 77 Bark Ave.
OfficeSpace workflow outcomes help distinguish permission from the result. The approval decision and measurable outcome are different parts of the workflow. OfficeSpace remains in development, including growth and learning; we confirm the qualified capabilities and tool support for your workflow during the demo.
AI implementation services remain $2,500 initially, then $500 a month, with continuous training and onboarding. OfficeSpace customers may also add team training to help staff use AI and OfficeSpace effectively. Discuss the training scope with us.
Related: What is a business operating system? · Agents and OfficeSpace · How to choose AI sales tools · Sales outreach with human approval · Ad creative and spending approvals.
FAQ
What is human-in-the-loop automation?
What is the difference between human in the loop and human on the loop?
Does an approval step slow the work down?
Where should the approval gate sit?
What if the draft changes after approval?
How does approval fit into OfficeSpace?
Can AI do more without removing approval?
Does this work with any AI model?
Explore approval in your workflow
Contact us for a free demo to discuss your workflow, the supported OfficeSpace capabilities, and training for your team.
77systems
Santa Monica. hello@77systems.ai