# Contract Approval Checklist

Use this checklist when comparing e-signature, proposal, and document workflow software. The goal is not just to collect signatures; it is to make the path from draft to approval to signed record clear, controlled, and easy for buyers.

## 1. Workflow context

- What documents need signatures: sales contracts, proposals, NDAs, HR forms, vendor agreements, order forms, change orders, renewals?
- Who owns templates?
- Who can send documents externally?
- Which documents require approval before sending?
- Where should signed documents be stored?
- Which CRM, accounting, HR, or file-storage tools must connect?

## 2. Approval and template control

- Can templates be locked by owner/team?
- Can pricing/legal/commercial clauses require approval?
- Can approval routing vary by deal size, region, contract type, or customer segment?
- Are redlines, comments, and versions visible enough for the team?
- Can admins audit who changed templates and when?

## 3. Signer experience

- Can external signers complete without creating an account?
- Does the signing flow work well on mobile?
- Are reminders, expiries, and signing order configurable?
- Is the final PDF clear, complete, and easy to download?
- Can internal users see bottlenecks without chasing manually?

## 4. Security and evidence

- Does the vendor provide audit trails for each document?
- Are SSO, MFA, role-based permissions, and admin logs available where needed?
- What evidence is available for SOC 2, ISO 27001, GDPR, data retention, and subprocessors?
- Can signed documents be exported if the vendor is replaced?
- What happens to data after contract termination?

## 5. Decision record

| Decision item | Notes |
|---|---|
| Preferred vendor |  |
| Primary workflow |  |
| Required integrations |  |
| Approval owner |  |
| Template owner |  |
| Accepted risks |  |
| Review date |  |

