Are electronic signatures valid?

Yes. Electronic signatures are legally binding under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted. Ensure intent, consent, attribution, and record retention are clear to satisfy the four-part legal test for e-signatures.

When do you need a consumer disclosure?

If the form is consumer-facing for financial, healthcare, or government benefits, provide the ESIGN consumer disclosure and obtain affirmative consent to electronic records as required by 15 U.S.C. §7001(c).

How should I verify signer identity?

Use email verification for low-risk transactions; employ SMS codes, knowledge-based authentication, or higher-assurance methods for sensitive data. Document the authentication method in the audit trail.

Do I need a BAA for health information?

Yes. When collecting protected health information, a Business Associate Agreement is required under HIPAA to ensure the eSignature provider meets safeguards and record-retention obligations.

What file formats are supported?

Use PDF or DOCX for form templates; PDF is preferred for final signed copies. Ensure the platform preserves an audit trail and returns ISO-compatible signed PDFs for long-term storage.

How to correct a submitted form?

If errors are found, issue a corrected form or amendment and obtain a new signature. Maintain both versions with clear retention notes to support audits and potential disputes.

Electronic Signature
Templates
Miscellaneous
Client Information Request

Client Information Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Client Information Request

Recitals

WHEREAS, Service Provider and Client intend to commence a professional relationship under which Service Provider will provide certain services to Client as described in this Client Information Request and the accompanying engagement terms; and

WHEREAS, Client is submitting information requested by Service Provider to allow Service Provider to evaluate requirements, prepare a proposal, perform agreed services, and comply with applicable administrative, billing, and regulatory obligations; and

WHEREAS, the parties intend that the information provided herein become part of the engagement documentation and that certain provisions governing the parties' relationship be acknowledged and agreed prior to commencement of services.

Client Details

Client Name Business Name (if different) Business Address

Primary Contact

Title

Email

Phone

Taxpayer Identification Number (EIN/SSN) Entity Type (check all that apply)

Individual Sole Proprietor Corporation LLC Partnership Non-Profit

Service Provider Details

Service Provider Name Provider Address

Service Request

Primary Services Requested Project Description / Objectives

Scope of Work

The parties intend that the detailed scope of services be set forth below. Service Provider will perform the services described below in a professional manner consistent with industry standards. Any material changes to scope will be documented in writing and signed by both parties.

Payment Terms

Client agrees to pay Service Provider as set forth below. All fees are due in accordance with the schedule provided and late payments are subject to the stated late fee.

Estimated Contract Amount Payment Schedule Preferred Payment Method

Check ACH Wire Credit Card

Late Payment Fee

Term and Termination

This engagement will commence on the Start Date and, unless earlier terminated in accordance with this section, will continue until the End Date or completion of the Scope of Work, whichever occurs later.

Start Date:

End Date:

Termination Notice Period (days)

Either party may terminate this engagement for material breach if the other party fails to cure such breach within the notice period above following receipt of written notice specifying the breach. Termination rights for insolvency, illegality, or nonpayment are reserved as provided by law.

Confidentiality

Each party will hold in confidence all nonpublic information disclosed by the other party that is designated as confidential or that a reasonable person would understand to be confidential given the nature of the information and the circumstances of disclosure. Confidential information does not include information that is or becomes publicly available through no fault of the receiving party, that was known to the receiving party prior to disclosure, or that is independently developed.

Client acknowledges and agrees to confidentiality obligations

I acknowledge and agree

Governing Law; Dispute Resolution

This Agreement and any disputes arising out of or relating to the relationship formed by this document shall be governed by the laws of the state identified below without regard to conflict of law principles. The parties agree to attempt good-faith negotiation prior to initiating any litigation.

Governing Law State

Entire Agreement

This Client Information Request, together with any engagement letter or signed proposal executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

Representations and Acknowledgements

Client represents that the information provided in this form is true, complete and accurate to the best of Client's knowledge. Client acknowledges that Service Provider may rely on this information in performing services and setting fees, and that changes to provided information must be communicated promptly in writing.

Authorization

By signing below, the parties confirm that the information provided is accurate and that they accept the terms and conditions set forth in this Client Information Request and the related engagement documentation.

Client:

By:

Date:

Service Provider:

By:

Date:

What a Client Information Request Is and when it’s used

A Client Information Request is a standardized form used to collect essential details about a client or counterparty before starting a professional relationship or a transaction. Typical uses include onboarding new customers, gathering identification and tax data, documenting billing and contact details, and recording signatures for authorization. The form centralizes names, addresses, tax identification numbers, contact methods, service or product requirements, and any compliance attestations the organization requires. Properly completed Client Information Requests reduce rework, improve recordkeeping, and establish the baseline data needed for billing, regulatory checks, and contract formation.

Why sending a clear Client Information Request matters

A concise, well-structured Client Information Request speeds onboarding, limits missing or incorrect data, and creates an auditable record that supports tax reporting, KYC checks, and contract execution. It clarifies responsibilities and preserves evidence of consent and attribution for electronic signatures under U.S. law.

Who typically issues or completes this request

Organizations that onboard clients, vendors, or contractors routinely use this form to centralize required data before work begins.

Accounting and finance teams that need correct taxpayer identification and payment instructions for 1099 or vendor setup
Sales and account teams collecting billing, decision-maker, and contact details to prepare proposals and contracts
Human resources or staffing units gathering personal and employment eligibility data for new hires or contractors

Core parts to include in a professional Client Information Request

Include distinct sections to collect identity, contact, tax, payment, compliance, and authorization data so reviewers can find and verify information quickly.

Client Identity

Full legal name, business entity type, and DBA if applicable. Use the exact legal entity to match tax records and contracts; mismatches can delay payments.

Contact Details

Primary mailing address, physical address if different, phone number, and email. Specify whether P.O. boxes are acceptable for legal notices.

Tax Information

TIN/SSN or EIN and W-9 request status. Accurate TINs prevent backup withholding and ensure correct information returns to the IRS.

Payment Instructions

Preferred payment method, ACH routing and account numbers or remit address for checks. Indicate any billing contacts and invoice delivery preferences.

Compliance Statements

Data privacy and consent checkboxes, HIPAA authorization if health data is present, and representation statements for sanctions and adverse ownership.

Authorization

Signature block, printed name, title, and effective date. State who is authorized to sign and whether a notarization or witness is required.

Step-by-step: collecting client information with minimal back-and-forth

Use a simple, linear workflow so each required item is captured and verified before moving to the next step.

01

Prepare the form: Pre-fill known fields and highlight required items.
02

Send to contact: Deliver by email or secure link with clear instructions.
03

Verify returned data: Check TINs, addresses, and signatory authority.
04

Record and file: Store completed form with audit metadata and retention tags.

Typical routing for a completed Client Information Request

Define roles and automated routing to reduce manual handoffs and ensure the right teams receive verified data.

Intake: Form sent to client for completion.
Review: Internal reviewer checks for completeness.
Authorize: Authorized signer approves and signs.
Archive: Signed copy stored in records with audit trail.

Configuring an online workflow for this request

Map form fields to responsible parties and choose authentication levels to match regulatory needs.

Field	Configuration
Required Fields	Mark TIN, legal name, signature as required
Authentication	Email verification by default; SMS or KBA for higher assurance
Routing Rules	Send to finance after signature for vendor setup
Retention Tag	Apply retention policy and access controls

Delivery and technical options for sharing the request

Choose distribution channels and integrations that match your security and recordkeeping needs.

Email Link: Simple, low-friction delivery
Embedded Form: Host on secure portal
API Integration: Automate with CRM or ERP

Integrations with CRM, cloud storage, and accounting systems reduce duplicate data entry and centralize completed records.

Timing considerations and common deadlines

Be mindful of tax and reporting timelines that depend on when information is received and verified.

W-9 Provisioning:

Provide W-9 upon payer request; no fixed federal deadline

1099 Reporting:

Forms to recipients due Jan 31; IRS filing dates follow same timing

I-9 Retention:

Retain three years after hire or one year after termination, whichever later

HIPAA Authorizations:

Obtain before collecting protected health information

Client Onboarding SLA:

Set an internal completion target (for example, 7 business days)

Frequent mistakes that delay processing

Submitting an incorrect or mismatched TIN that triggers backup withholding and requires re-submission
Using informal or nickname variations of legal entity names that do not match IRS records or contracts
Not specifying signatory authority, resulting in unsigned or invalid approvals
Failing to apply proper authentication for sensitive data, increasing audit and compliance risk

Regulatory and operational risks to watch for

Backup Withholding: 24% withholding if TIN is incorrect

I-9 Fines: $281–$2,789 per violation

Information Return Penalties: $60–$660+ per incorrect 1099

HIPAA Exposure: Breach penalties and corrective action

Contract Invalidity: Incorrect signer authority can void agreements

Operational Delay: Missed deadlines and payment holdbacks

eSignature vendor comparison for handling Client Information Requests

Compare common plan attributes that affect how you collect and store client information electronically; signNow is listed first for parity with platform details.

	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	7-day free trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Real-world examples of Client Information Request use

Organizations across industries use standardized intake forms to accelerate onboarding and maintain compliance.

Optica Ventures LLC

Optica needed a simple intake flow for investors and partners

"The interface is simple and easy-to-use"
Optica reported fewer follow-ups and faster execution after centralizing client intake with an eSignature-enabled workflow.

Fertility Centers of Illinois

A healthcare provider required secure online intake that respected patient privacy

"the API has been great"
The organization emphasized compliance and responsiveness, noting improved intake accuracy and ease of integration with back-office systems.

Frequently asked questions about Client Information Requests

Answers to common questions about validity, electronic signatures, data retention, and integration with back-office systems.

Need help? Contact support

Are electronic signatures valid?
Yes. Electronic signatures are legally binding under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted. Ensure intent, consent, attribution, and record retention are clear to satisfy the four-part legal test for e-signatures.
When do you need a consumer disclosure?
If the form is consumer-facing for financial, healthcare, or government benefits, provide the ESIGN consumer disclosure and obtain affirmative consent to electronic records as required by 15 U.S.C. §7001(c).
How should I verify signer identity?
Use email verification for low-risk transactions; employ SMS codes, knowledge-based authentication, or higher-assurance methods for sensitive data. Document the authentication method in the audit trail.
Do I need a BAA for health information?
Yes. When collecting protected health information, a Business Associate Agreement is required under HIPAA to ensure the eSignature provider meets safeguards and record-retention obligations.
What file formats are supported?
Use PDF or DOCX for form templates; PDF is preferred for final signed copies. Ensure the platform preserves an audit trail and returns ISO-compatible signed PDFs for long-term storage.
How to correct a submitted form?
If errors are found, issue a corrected form or amendment and obtain a new signature. Maintain both versions with clear retention notes to support audits and potential disputes.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now