{"schemaVersion":"0.1","generatedAt":"2026-10-09T19:35:37.105Z","entry":{"knowledgeKey":"human-in-the-loop-automation","kind":"question","entityKey":"integration","locale":"en","primaryQuestion":"How can we automate checks in a review process while people keep authority over the decision?","questionVariants":[{"question":"What is human-in-the-loop automation?"},{"question":"Do we have to replace our review process to use MeshQu?"},{"question":"Which checks can a rule or an agent do, and which need a person?"},{"question":"Who makes the final call in an automated review?"}],"title":"Human-in-the-loop automation with MeshQu","answer":"Human-in-the-loop automation means automating the checks in a review process while people keep authority over the decisions that matter. With MeshQu you start with one decision in the process you already have and make what must be true, the evidence and who decides explicit. Then you automate checks one at a time. Each assessment is recorded against the same policy version, so automating a check does not change what the decision was judged against.","explanation":"Some checks need a person and some don’t. A person checks: someone confirms a document or a fact and records what they found. A rule checks: a system checks the same thing the same way, every time. An agent helps: it gathers and summarises the evidence for a person or a rule. A person decides: when a rule can’t settle it, a reviewer makes the call and records why. A review can move from manual to assisted, connected and agentic, where agents handle routine cases within the authority they are granted and exceptions and reserved outcomes go to people. At every stage what must be true, the evidence requirements and the authority stay the same, and so does the record. Each recorded assessment has a signed Decision Receipt, and reviews and approvals are linked records alongside it. An assessment recorded from a manual form produces the same kind of signed receipt as one recorded through the API.","applications":[{"value":"Start with one decision in an existing review process and make what must be true, the evidence and who decides explicit."},{"value":"Move a repeatable check from a person to a rule or an agent without changing what the case is judged against."},{"value":"Keep reviewer judgement, overrides and approvals as linked records beside each assessment."}],"limitations":[{"value":"MeshQu returns a verdict; your systems control the action and route cases to people."},{"value":"Who acted at each step is recorded as your systems supply it. The actor identifier is not authenticated by MeshQu."},{"value":"A recorded review shows who decided and why. It is not proof that the decision was correct."},{"value":"The supplier onboarding review on the page is illustrative, not a customer deployment."},{"value":"MeshQu is currently available for research, evaluation and design-partner deployments. Production availability and support commitments are agreed per engagement."}],"nextStep":{"label":"Map a decision","href":"https://www.meshqu.com/#model-a-decision"},"claims":[{"claimKey":"start-with-existing-process","statement":"You can start with one decision inside an existing review process rather than replacing the process.","qualification":"Manual capture is documented as a way to record human decisions before any upstream system is integrated."},{"claimKey":"same-policy-any-checker","statement":"Each assessment is recorded against the same policy version, so automating one check later does not change what the decision was judged against.","qualification":"Manual and API-recorded assessments produce the same kind of signed receipt. Whether a given check is automated is a choice for your team and your systems."},{"claimKey":"verdict-advisory","statement":"MeshQu returns a verdict and the calling application acts on it. MeshQu does not block, allow or modify the operation.","qualification":"Routing a case to a person is something your systems do with the verdict."},{"claimKey":"outcomes-recorded","statement":"What happened after a verdict, such as a reviewer accepting, overriding or escalating it, can be recorded as the decision’s outcome.","qualification":"One outcome per decision, immutable once recorded. The person recorded is as your systems supply them."}],"statementKind":"illustrative-example","availability":"limited-pilot","evidenceStrength":"source-reported","publicSources":[{"title":"MeshQu docs — Manual checks","url":"https://docs.meshqu.com/guides/manual-checks","context":"Recording human-operated decisions through a policy-derived form, producing the same kind of signed receipt as the API."},{"title":"MeshQu docs — Integration patterns","url":"https://docs.meshqu.com/guides/integration-patterns","context":"The calling application owns enforcement; MeshQu returns the verdict."},{"title":"MeshQu docs — Concepts overview","url":"https://docs.meshqu.com/concepts/overview","context":"Decision outcomes (accepted, overridden, escalated) recorded after a verdict."}],"revision":"7481eed54df10dea14a842f013d51607a9befe14174b64769421ee5e0d725539","updatedAt":"2026-10-09T11:39:37.405Z","canonicalUrl":"https://www.meshqu.com/human-in-the-loop-automation","related":[{"key":"what-meshqu-does","url":"https://www.meshqu.com/knowledge/what-meshqu-does.json"},{"key":"actor-identity","url":"https://www.meshqu.com/knowledge/actor-identity.json"},{"key":"decision-receipts","url":"https://www.meshqu.com/knowledge/decision-receipts.json"},{"key":"policy-application","url":"https://www.meshqu.com/knowledge/policy-application.json"}]}}