# Agentic Document Signing with Human Approval

A system pattern in which agents prepare and validate signing packs while humans retain authority over template approval and legally significant sends.

Published: 2026-07-26
Canonical: https://darrylwong.me/posts/agentic-document-signing-human-approval
Topics: Agentic Workflows, Document Signing, Human-in-the-Loop, Technical Build Notes

## Automate preparation, not signing authority

An agent can ingest a source document, create a signing template, assign roles, place fields, validate the layout, and prepare a review link. It should not independently decide that a document is legally ready to send.

The signing platform remains the system of record for documents, templates, fields, submitters, submissions, review state, authorization, and audit events. Chat memory or agent notes must not become a parallel source of signing truth.

## Enforce review across every send path

Agent-created or agent-edited templates should be pending by default. The review gate must be enforced server-side across the user interface, regular APIs, agent APIs, MCP tools, background jobs, scripts, and resend paths. A warning in the interface or prompt is not sufficient.

Any change to the source document, submitters, roles, fields, or layout invalidates approval. Template approval and send approval remain separate human decisions.

## Bind approval to the exact action

Immediately before sending, the system should read back and validate the current approved revision. Page-numbering and field-coordinate contracts must be explicit, signer assignments must match, and the system should create an exact, short-lived preflight that can be consumed only once by an unchanged send.

Archived, changed, stale, pending, or replayed sends must fail closed. Ambiguous or post-send errors must not trigger automatic invitation retries because the external effect may already have occurred.

## Use an evidence ladder for delivery

A successful API response proves only that the signing platform accepted or queued an action. Durable provider evidence, sender-side handoff, recipient Inbox presence, opening, and signing are different states and require different evidence and operator language.

The durable pattern is a small agent adapter over the signing application, with credentials held in the runtime secret store and sanitized metadata returned to the agent. Authorization, review state, preflight consumption, send blocking, replay protection, and audit enforcement remain platform properties.

The living guide uses DocuSeal as a reference implementation and includes environment discovery, API and MCP contracts, required enforcement points, provider-evidence handling, regression tests, license considerations, and sanitized validation practices.

## Sources

- [Read the living document-signing guide](https://gist.github.com/oruenboi/9e907567e3fc4e7472f14a70a22ac926)
- [Self-host DocuSeal for production](https://gist.github.com/oruenboi/bd55d6c05b5dbedfa8855a570e8a1c5a)
- [Install the review-gated Codex plugin](https://gist.github.com/oruenboi/3654bc9438e96ce004bffe36abc2d7bd)