Human-in-the-loop, designed as an operating system: which AI actions need a person, who reviews what, on what cadence.
A human approval workflow is the operating design that decides which AI actions a person must review or sign off before they take effect, who that person is, and how the decision and any override are recorded. It puts a human in the loop on outputs with significant effect on people — credit, employment, healthcare triage, tenancy — and produces the records a PDPL-aware review expects.
Human-in-the-loop fails when it is a slogan instead of a map. Approving everything stalls the business; approving nothing exports your liability to a model. The work is to tier each AI action by effect and reversibility, then attach a review rule to each tier.
We use three tiers. Auto-execute: low-effect, easily reversible actions — drafting an internal summary, tagging a CRM record, suggesting a reply a person still sends. Human-on-the-loop: the AI acts but a person samples and can claw back — routing leads, ranking applicants for a shortlist, flagging an invoice. Human-in-the-loop (mandatory sign-off): any decision with significant effect on a person before it takes effect — declining credit, rejecting a candidate, healthcare triage, ending or refusing a tenancy.
The deciding questions are concrete: does this output change someone's access to money, work, housing, or care? Is it reversible within a day, or does it land as a final answer? If the effect is significant and the action is hard to undo, it sits in the mandatory-sign-off tier — independent of how confident the model looks.
An escalation taxonomy names the situations that bump an action up a tier: low model confidence, an output that contradicts a prior human decision, a protected-attribute proximity (age, nationality, health), a customer dispute, or a value above a money threshold. Each named trigger routes to a specific reviewer, not a generic queue — the broker principal for a tenancy refusal, the clinician for a triage flag, the hiring manager for a candidate rejection, finance for a payment above the ceiling.
Cadence is split between real-time and periodic. Real-time: mandatory-sign-off actions are blocked until the named reviewer approves — the WhatsApp-to-CRM auto-reply does not send, the rejection email does not fire. Periodic: human-on-the-loop tiers get a sampling review on a fixed rhythm — weekly for high-volume routing, monthly for outcome and bias drift — so silent failures surface before they compound.
This is where the manual reality of UAE operations bites. The pain you are automating is WhatsApp threads, shared inboxes, and spreadsheet handoffs — and that is exactly where unreviewed AI actions disappear. The approval workflow has to live inside those tools, in English and Arabic where the customer-facing decision is bilingual, or reviewers route around it.
Every mandatory-sign-off action produces an override record whether the human agrees with the model or not: the AI's proposed output, the inputs and retrieval sources behind it, the reviewer's identity, the decision (approve, modify, reject), the reason, and the timestamp. The record exists so that a later question — from a data subject, a board, or a regulator — can be answered without forensic reconstruction.
This ties directly to PDPL Article 18-style and DIFC Regulation 10-aware expectations around decisions taken solely by automated processing that produce a significant effect on a person. Those frames anticipate a meaningful human review and a person's right to a real explanation. A durable override record is the operational evidence that the review actually happened — it does not, on its own, make you compliant, and it is not legal advice.
Build the workflow so the records are a byproduct of doing the work, not a separate logging chore. When the reviewer approves inside the tool they already use, the record writes itself; when approval lives in a side document, it rots. The reviewer-and-cadence matrix, the escalation taxonomy, and the override log are the three artefacts a governance review asks for first.
The control layer for everything AI is doing inside your business — one screen for workflows, approvals, logs, costs, and the executive summary.
Replace the manual WhatsApp-to-CRM-to-spreadsheet shuffle with governed automations your team can see, approve, and audit.
Build logs, working systems, and field notes from running a portfolio of AI ventures. Sent weekly, never more.