E-Signature Status Chasing

Poll an e-signature provider's API for envelope status and send polite nudges to counterparties or internal owners who have not yet signed. Sending new envelopes is out of scope for this skill.

When to use

• A contract, NDA (non-disclosure agreement), or other document has been sent out for signature and needs periodic status checks.
• One or more signers on an envelope have not completed signing after a set number of days.
• Legal or deal-desk staff need a recurring nudge cadence without manually checking the e-signature portal.
• A signed envelope needs to be flagged to counsel for final confirmation, not summarized or interpreted.

Tools

• http-get
• send-email
• schedule-task

Playbook

1. Use schedule-task to set up a recurring check (for example, daily) against the target envelope or list of pending envelopes.
2. On each run, call http-get against the e-signature provider's REST API to fetch envelope status, e.g. GET https://api.esignprovider.com/v2.1/accounts/{accountId}/envelopes/{envelopeId} (or the equivalent list endpoint for bulk polling). Auth is injected by the org's Integration row for this host — never ask for, echo, or hardcode credentials.
3. Parse the response for each recipient's signing status (sent, delivered, completed, declined). Identify signers still in "sent" or "delivered" state past the agreed grace period.
4. For each non-signer past the grace period, use send-email to send a brief, polite reminder referencing the envelope subject and due date — never include the contract text itself, only the fact that a signature is pending.
5. If a recipient has "declined" or the envelope shows an error/void status, do not attempt to resolve it yourself — use send-email to notify the internal envelope owner and flag it for a licensed human's attention.
6. When all signers show "completed," send a completion notice to the internal owner via send-email stating the envelope is fully executed; do not summarize or interpret contract terms in this notice.
7. If the provider API returns 401/403 or no Integration row exists for the host, stop polling, do not retry silently, and message a human via send-email naming the service and the scopes needed.
8. Every status summary or nudge email you generate must include the line: "Not legal advice — attorney review required."
9. Never send communications to counterparties' outside counsel or to regulators; nudges are limited to the counterparty's designated signer and internal stakeholders only.

Failure modes

• Treating a "declined" or expired envelope as routine and continuing to nudge instead of escalating to a human.
• Including contract clauses, negotiated terms, or attachment content in a reminder email instead of just a status pointer.
• Polling too frequently and creating nudge fatigue, or missing an expired envelope because schedule-task was never renewed.
• Losing the audit trail by not keeping the "not legal advice" disclosure on every outbound status message.

Done when

• Every signer's status has been checked against the provider API and non-signers past the grace period have received exactly one nudge per cycle.
• Any declined, voided, or error-state envelope has been escalated to a human with the disclosure note attached.
• Fully executed envelopes have been reported to the internal owner without any attempt to summarize or interpret the underlying contract.