Client Identity
Legal entity name, DBA, entity type, EIN or SSN, and registration jurisdiction so contracts reference the correct counterparty.
A clear manual reduces onboarding time, decreases errors from inconsistent data, and helps demonstrate compliance with recordkeeping obligations. It centralizes proof of consent and signature authority, supports secure electronic workflows, and streamlines recurring transactions across departments.
Typical users prepare this manual during client onboarding, contract execution, or account setup to ensure teams share a single source of truth.
Name, title, phone, and email for the person authorized to provide operational instructions. This contact coordinates onboarding, answers clarification requests, and receives notices related to performance or billing; they are not necessarily an authorized signer.
Individual(s) with legal authority to sign contracts and approve changes. Record job title, scope of signing authority, any signing limits, and whether a countersignature or witness is required by the client or state law.
Legal entity name, DBA, entity type, EIN or SSN, and registration jurisdiction so contracts reference the correct counterparty.
Operational, billing, legal, and emergency contacts with phone, email, and preferred communication channel for each role.
Authorized signers, their titles, signature limits, witness/notary requirements, and whether remote online notarization is allowed for the client.
Billing address, remit-to details, W-9 or W-8 status, invoicing rules, and backup withholding triggers when applicable.
Data classification, handling constraints, required encryption or access controls, and any required Business Associate Agreement for PHI.
Preferred eDelivery methods, archival location, retention periods, and escalation steps for disputed items.
| Field | Configuration |
|---|---|
| Auto-fill Rules | Map fields to CRM or ERP values for accuracy |
| Conditional Fields | Show fields only when relevant to reduce signer friction |
| Authentication | Choose email, SMS, or KBA depending on risk |
| Integrations | Push completed records to CRM or document repository |
Choose a platform that supports your required authentication methods, audit logging, and integrations to downstream systems.
Provide upon payer request; no fixed federal deadline
Delivered by January 31 each year
Recipient and IRS due by January 31
Form 1040 due April 15 (October 15 with extension)
Keep for three years after hire or one year after termination
Receive information and verify identity and tax data
Legal and finance review required fields and authority
Signatures collected with chosen authentication method
Store final manual with audit trail and access controls
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | Yes, 7-day trial | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.
The airSlate SignNow team has been exceptional, responsive, the API has been great, and we're extremely happy that we chose airSlate SignNow as a company.