Skip to content

t1k:business:pandadoc-esign

FieldValue
Modulebase
Version0.12.1
Effortlow
Tools—

Keywords: archive, assign fields, audit trail, CC recipient, countersign, create document, create from markdown, create from template, document status, docusign alternative, e-signature, esign, pandadoc, reassign signer, recipient, send for signature, send msa, send nda, send sow, sign contract, signature, signer, signing order, signing status, void

/t1k:business:pandadoc-esign
create <file.md> | from-template <name> | assign-fields [doc-id] | recipients [doc-id] | send [doc-id] | status [doc-id] | content [doc-id] | audit [doc-id] | lifecycle <complete|void|decline|archive> [doc-id] | templates

Drive the PandaDoc e-signature platform from Claude Code through the pandadoc MCP server. This is the create-to-executed half of the contract pipeline — it picks up where t1k:business:contract (render to PDF/DOCX) leaves off and carries a contract all the way through signing, tracking, and filing.

draft (.md) → contract render → .pdf / .docx → pandadoc create → edit draft → GATE → send → track → signed/
  1. The pandadoc MCP server is registered (https://mcp.pandadoc.com/v1/mcp, HTTP transport).
  2. Authenticate once: run /mcp, select pandadoc, complete the browser OAuth login with your existing PandaDoc account. Status must read connected before any operation below.
  3. Tools surface as mcp__pandadoc__* and are deferred — load them first with ToolSearch(query="pandadoc").

Grouped by stage. One row per operation; the governing tool is named.

OperationWhat it doesTool
Create from MarkdownTurn a rendered .md contract into a draft; variables = sender-filled, fields = recipient-filled.documents_create_from_markdown
Create from templateStamp a draft off a workspace template, mapping recipients/tokens/fields by role.documents_create

⚡ Signature fields — ALWAYS ship a signable doc (READ FIRST)

Section titled “⚡ Signature fields — ALWAYS ship a signable doc (READ FIRST)”

A document created via MCP MUST come out signable — signature fields placed AND bound to each signer. Creating recipients alone is NOT enough: a recipient with no assigned field is a CC (view-only) and cannot sign — the counterparty opens it and sees no Sign button. This IS fully doable through the MCP; do not fall back to the UI.

Two things to check before every create:

  • <br> inside a table cell stalls the document permanently — the doc sits in Uploaded forever, never reaching Error. GFM tables and in-cell [[fields]] are both fine; only the break kills it. GFM has no in-cell line break, so emit one table row per line instead, and assert '<br>' not in markdown before every create.
  • Condensing prose must never drop or lift a material term. A condensed render must stay legally equivalent to the full .docx SSOT. Every liability cap / sub-cap (especially an IP-infringement sub-cap that re-caps the indemnity — e.g. §15.4), IP & indemnity carve-out, refund / payment / non-refundable term, and governing-law clause must survive verbatim-in-effect. Before create, diff the render’s liability section (§15) and IP/indemnity sections (§12/§14) against the full .docx — a render that removes a cap the full document keeps hands the counterparty a right the negotiated contract never granted, in the document they actually sign. Stop and restore it. (Real hit: a render dropped an IP-infringement sub-cap, leaving the provider’s liability uncapped in the signable document.)

Author the markdown from the source contract — keep its layout and every | table, signer fields lowercase, one per line outside a table. Full 5-step recipe (create → poll → assign fields → verify), the stall symptoms, and the earlier size/tables misdiagnosis that a de-table fix only appeared to cure: references/document-lifecycle.md.

OperationWhat it doesTool
Update draftRename, re-tag, set variable tokens / field values, update named blocks.documents_update
Assign fieldsBind/reassign/unassign signature & input fields to recipients by UUID.documents_fields_assign
Add CCAdd a non-signing observer (needs an existing contact). ⚠ Prefer naming the observer in the create call — one added afterwards lands on a later signing_order and stays silent until signing completes. See references/recipients.md.recipients_add_cc
Edit recipientCorrect one signer’s details in place (same person).recipients_edit
Reassign signerHand a signing slot to a different contact; transfers their fields.recipients_reassign
Delete recipientRemove a recipient (signers Draft-only).recipients_delete

⛔ HARD GATE — NEVER send without the user’s explicit, per-send approval. Sending a PandaDoc document transmits it to the counterparty for signature — an outward-facing, hard-to-reverse action. You MUST show the user the document title + full recipient list and get an explicit “yes, send” for that specific document, every time. No standing approval, no “the user said send earlier”, no inferring intent. When unsure, leave it in draft. This is enforced mechanically by the pandadoc-send-gate PreToolUse hook (forces a human approval prompt on documents_send and any documents_status_change → sent); never attempt to work around it.

OperationWhat it doesTool
SendTransmit the draft to recipients for signature. Requires explicit per-send user approval (hook-enforced).documents_send

List, Search, Status, Details, Metadata / Summary. Tool names + exact behavior in references/tracking-status-audit.md.

Content download, Audit trail. Tool names + exact behavior in references/tracking-status-audit.md.

Change status, Archive. Tool names + exact behavior in references/tracking-status-audit.md.

DocOpen when you need to…
references/document-lifecycle.mdCreate from Markdown, edit a draft, assign fields, or force a terminal status — the full signature-field binding recipe, variable-vs-field rules, async UPLOADED→DRAFT gate.
references/recipients.mdManage signers, CC, signing order, or swap/correct a person after creation.
references/tracking-status-audit.mdFind documents, poll status, pull the executed content + audit trail, or force a terminal lifecycle state (complete/void/decline/archive).

Workflow — send a contract for signature

Section titled “Workflow — send a contract for signature”
  1. Render first. Ensure a final .pdf/.md exists; if only a .md draft exists, render/finalize it (t1k:business:contract).
  2. Discover tools. ToolSearch(query="pandadoc") → load the create/edit/send/track tools.
  3. Resolve recipients. Confirm signer name + email + role + signing order (and your counter-signer). Pull from authoritative records — never guess an email.
  4. Create the draft — from Markdown (documents_create_from_markdown) or template (documents_create, after templates_details_get). Creation is async: poll documents_status_get until DRAFT before any edit.
  5. Edit the draft — run the FINALIZATION CHECKLIST (every item, every time). A draft is only “ready” when ALL of these hold (verify with documents_details_get):
    • Signers invited = at least one field bound to each signer via documents_fields_assign. Creating a recipient with role: Client is NOT enough — a recipient with no assigned field stays CC and cannot sign. Assigning the field is what promotes CC → signer.
    • CC recipients added for every observer who should receive the doc (legal, COO, intro partner) — mirror the negotiation email’s Cc unless told otherwise.
    • EVERY recipient — signers AND CCs — is at signing_order: 1 unless the user explicitly asked for a sequential flow. signing_order gates email delivery, not just signing sequence: nobody at order N is emailed until order N-1 completes. A CC parked at order 2 receives NOTHING at send time. Verify with documents_details_get that no recipient sits above order 1. This is unfixable after send — see the signing-order gotcha below.
    • Date(s) filled — set [Effective.Date] and any sender date token (documents_update tokens, or hardcode the agreed date in the text). Never leave a blank effective date.
    • Signature-block Name/Title are static text (you know the signatories) — only Date + Signature are recipient fields.
    • Map it — record the PandaDoc doc ID + URL in the counterparty’s repo README / data-room file (see Document mapping below).
  6. GATE — confirm before sending. Show title + recipient list + send-or-draft choice. Default to leaving it in draft unless the user explicitly says send.
  7. Send (documents_send) only on explicit go-ahead.
  8. Track. Poll documents_status_get / documents_details_get for viewed/signed.
  9. File the executed copy. On completed (2), pull documents_content_get + documents_audit_trail_get into the counterparty’s signed/ folder and record the signature date.

Document mapping (bi-directional SSOT — never skip)

Section titled “Document mapping (bi-directional SSOT — never skip)”

Every PandaDoc document MUST be cross-linked with the repo record it came from, in both directions, at create time:

  • Repo → PandaDoc: in the counterparty’s README.md (or data-room file), record the PandaDoc doc ID + URL + current status + the source .md it was built from. Example line: **PandaDoc:** \` — (status: draft, built from `outgoing/.md`)`.
  • PandaDoc → repo: name the document so the counterparty + round are obvious, and keep the source .md as the editable SSOT (PandaDoc markdown is a render target, not the master).
  • On recreate: if you rebuild a draft (new doc ID — e.g. to add signature fields the first pass lacked), update the README to the new ID and documents_archive the superseded draft so the repo never points at a dead or duplicate PandaDoc. One live doc per agreement round.
  • t1k:business:contract — renders Markdown → PDF/DOCX (run BEFORE this skill).
  • t1k:business:contract-review — adversarial clause review (run BEFORE sending).
  • This skill — create → edit → send → track → file the executed record (the final stage).