For Florida law firms

DocuSign / e-signature (scoped)

firm lane · Connector

Current availability

StagedBuilt and dormant until a firm turns it on: DOCUSIGN_BASE_URL · ACCOUNT_ID · ACCESS_TOKEN.

Where it lives: /api/esign/send
What unlocks it: a firm admin

Status is evaluated against this deployment's configuration by the capability-status service at build time; the catalogue's facts were last reviewed on the date shown.

Capabilities

StagedSend a document for electronic signature only where the signing-path register allows it: wills and codicils, revocable trusts, powers of attorney, health care surrogate designations and living wills are refused the provider path with the statute's own reason (§§ 732.502, 732.522, 736.0403, 709.2105, 765.202, 765.302) and are signed at the supervised ceremony; administration documents, engagement agreements and other firm documents may go (master plan Phase 15, M-1507).
StagedEvery send first shows a receipt card for the exact stored document (its bytes' SHA-256), its class and every signer; the envelope is bound to those, and only that single-use, ten-minute receipt sends it.
StagedThe provider's events move an envelope through one door: completed only when every bound signer completed (otherwise partial); a signer the provider changed or one missing puts it to the firm's review; declined and voided are final; a stale or repeated event changes nothing; a document whose stored bytes changed after sending is marked. Every event is kept.
StagedOn completion the executed copy — every document signed, with the provider's certificate of completion, as one PDF — is stored on the matter with its SHA-256, and the firm opens it through a short-lived link.

Limits

Dormant until the firm's DocuSign credentials; wet ink and the supervised ceremony work today.
Completed means every signer signed through the provider — never a review of whether the document was validly executed. Counsel's sign-off on the register is an owner gate, not yet recorded.

What EstateDraftFL refuses

Reason code	HTTP	What it means
class-required	400	The send names no signing class — the register is applied before anything is sent.
out-of-scope	409	The register refuses the provider path for this instrument; the message gives the statute's reason.
document-required	400	An envelope carries the exact stored bytes the receipt names — attach the stored document.
document-changed	409	The stored bytes differ from the document's recorded hash — nothing was sent.
approval-required	428	The send was called without a receipt's token.
approval-stale	409	The document changed after the receipt was shown.
approval-args-changed	409	The class or the signers differ from the confirmed receipt.
recipient-invalid	400	A signer's address failed validation, or two signers share one — no override exists.
not-completed	409	Only a completed envelope has an executed copy.

Evidence

src/lib/esign-events.test.ts
src/lib/esign-scope.test.ts
scripts/connector-audit-esign.ts
docs/connectors/esign-AUDIT.md
docs/connectors/esign-SCOPE.md
supabase/migrations/20261002120000_phase15_esign.sql

Last reviewed 2026-10-02

← All surfaces