Signature Request

1---2name: signature-request3description: Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.4argument-hint: "<document or contract to send>"5---6 7# /signature-request -- E-Signature Routing8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Prepare a document for electronic signature — verify completeness, set signing order, and route for execution.12 13**Important**: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.14 15## Usage16 17```18/signature-request $ARGUMENTS19```20 21Prepare for signature: @$122 23## Workflow24 25### Step 1: Accept the Document26 27Accept the document in any format:28- **File upload**: PDF, DOCX29- **URL**: Link to a document in ~~cloud storage or ~~CLM30- **Reference**: "The Acme Corp MSA we finalized yesterday"31 32### Step 2: Pre-Signature Checklist33 34Before routing for signature, verify:35 36```markdown37## Pre-Signature Checklist38 39- [ ] Document is in final, agreed form (no open redlines)40- [ ] All exhibits and schedules are attached41- [ ] Correct legal entity names on signature blocks42- [ ] Dates are correct or left blank for execution date43- [ ] Signature blocks match the authorized signers44- [ ] Any required internal approvals have been obtained45- [ ] Document has been reviewed by appropriate counsel46```47 48### Step 3: Configure Signing49 50Gather signing details:51- **Signers**: Who needs to sign? (names, emails, titles)52- **Signing order**: Sequential or parallel?53- **Internal approval**: Does anyone need to approve before the counterparty signs?54- **CC recipients**: Who should receive a copy of the executed document?55 56### Step 4: Route for Signature57 58**If ~~e-signature is connected:**59- Create the signature envelope/request60- Set signing fields and order61- Add any required initials or date fields62- Send for signature63 64**If not connected:**65- Generate a signing instruction document66- Provide the document formatted for wet signature or manual e-sign67- List all signers with contact information68 69## Output70 71```markdown72## Signature Request: [Document Title]73 74### Document Details75- **Type**: [MSA / NDA / SOW / Amendment / etc.]76- **Parties**: [Party A] and [Party B]77- **Pages**: [X]78 79### Pre-Signature Check: [PASS / ISSUES FOUND]80[List any issues that need attention before sending]81 82### Signing Configuration83| Order | Signer | Email | Role |84|-------|--------|-------|------|85| 1 | [Name] | [email] | [Party A Authorized Signatory] |86| 2 | [Name] | [email] | [Party B Authorized Signatory] |87 88### CC Recipients89- [Name] — [email]90 91### Status92[Sent for signature / Ready to send / Issues to resolve first]93 94### Next Steps95- [What to expect after sending]96- [Expected turnaround time]97- [Follow-up if not signed within X days]98```99 100## Tips101 1021. **Check entity names carefully** — The most common signing error is incorrect legal entity names.1032. **Verify authority** — Make sure each signer is authorized to bind their organization.1043. **Keep a copy** — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.