Can this form be signed electronically?

Yes. Electronic execution is enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the signature demonstrates intent, consent, attribution, and retention. Exceptions like wills or certain court filings still require paper or different procedures.

What authentication should I use?

Choose authentication proportional to risk: email for low-risk, SMS or knowledge-based verification for higher assurance, and ID credential analysis for regulated transactions. Stronger methods reduce fraud risk and support legal defensibility in disputes involving signature attribution.

Are notarization or witnesses required?

Generally, a Client Information Request Form does not require notarization or witnesses unless it contains a power of attorney, deed, or other notarized instrument. Remote Online Notarization is permitted in many states with identity proofing and audio-video recordkeeping requirements.

How long should we retain completed forms?

Retention depends on purpose: retain active files through the contract term plus three years; follow IRS minimums of three years for tax records (IRC §6501(a)); and retain healthcare records six years per 45 CFR §164.530(j). Check state variations.

What if client refuses to provide TIN?

If a client refuses to provide a correct TIN, require them to complete Form W-9 or document the refusal. Failure to obtain a TIN may trigger 24% backup withholding and exposure to penalties under IRC §6721 for incorrect reporting.

Can we collect PHI on this form?

You may collect PHI only when necessary and with proper patient authorization or a permitted purpose. Use HIPAA-compliant processes, execute a BAA with any eSignature vendor handling PHI, and retain records six years per 45 CFR §164.530(j).

Electronic Signature
Templates
Miscellaneous
Client Information Request Form

Client Information Request Form

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

CLIENT INFORMATION REQUEST FORM

Purpose and Authorization

This Client Information Request Form (the "Form") is submitted to collect information necessary for the Service Provider to evaluate, propose and, where applicable, enter into services with the Client. The Client certifies that the information provided is true, complete and accurate to the best of the Client's knowledge and authorizes the Service Provider to verify such information where reasonable and necessary.

WHEREAS

WHEREAS, Client Name: (the "Client") seeks to obtain proposals and information from the Service Provider; and

WHEREAS, Service Provider Name: (the "Service Provider") requires certain client data to prepare a scope of work and proposed agreement; and

WHEREAS, the parties intend that information provided on this Form be relied upon for preparing engagement terms and any related General Business Agreement.

Client Contact Information

Business / Organization Name Primary Contact Name

Phone

Email

Primary Address Tax Identification (if applicable)

Service Requirements and Scope

Brief description of requested services and objectives. Provide sufficient detail to allow preparation of a Scope of Work and fee proposal.

Payment Terms (For Proposed Engagement)

Proposed Total Fee Amount:

Payment Schedule (describe milestones, deposits, retainers)

Late Payment Fee (if not otherwise agreed):

Term and Termination

Proposed Engagement Start Date: Proposed Engagement End Date (if applicable):

Termination Notice Period (mutual): days. In addition to any contractual termination provisions, either party may terminate for material breach following failure to cure within the notice period.

Confidentiality

The parties acknowledge that certain information exchanged in connection with proposals and engagement may be confidential. The receiving party shall protect confidential information with at least the same degree of care it uses for its own confidential information, but no less than reasonable care. Confidential information excludes information that is or becomes generally known through no breach, is already known to the receiving party, or is independently developed. Any disclosure required by law shall be made only after prompt notice to the disclosing party to permit protective measures.

Representations and Certifications

By submitting this Form, Client certifies that the information provided is true, accurate and complete. Client authorizes the Service Provider to rely on the information for preparing proposals, scopes of work, cost estimates and any related contractual documents. Client agrees to promptly notify the Service Provider in writing of any material change to the information furnished.

Consent to verification of information and references

Governing Law and Entire Agreement

Governing Law: The laws of the state of shall govern any disputes arising from this Form and any ensuing engagement documents, without regard to conflict of laws principles.

Entire Agreement: This Form, and any subsequent written engagement agreement executed by the parties, contains the entire understanding between the parties with respect to the matters described herein and supersedes all prior discussions and agreements, whether written or oral, relating to such matters.

Additional Details

Preferred Method of Communication Notes or Special Requirements

Signatures

Client (Printed Name):

By:

Date:

Service Provider (Printed Name):

By:

Date:

What the Client Information Request Form Is

The Client Information Request Form is a standardized document used to collect essential identifying, contact, and project-related data from a client at the start of a professional engagement. It centralizes details such as full legal name, tax identification, mailing and service addresses, authorized contacts, billing and payment preferences, and any compliance-related disclosures. Organizations use it to confirm identity, set communication expectations, and gather documents required for onboarding, billing, or regulatory compliance. Accurate responses reduce follow-up, support timely invoicing, and establish a clear record for the engagement.

Why Standardize Client Intake with a Request Form

A Client Information Request Form streamlines onboarding, reduces administrative errors, and documents client consent and authority. By collecting standardized data up front, organizations reduce processing time, improve billing accuracy, and create an auditable record that supports compliance with ESIGN, UETA, and industry-specific regulations.

Who Typically Completes the Form

Common users include account managers, intake teams, and compliance officers who need verified client details before services, billing, or regulatory review.

Law firms collecting client intake data and conflict checks at onboarding.
Accounting and finance teams requiring taxpayer identification for billing and reporting.
Healthcare providers capturing patient identifiers and consent information for records and billing.

The form also supports operations, finance, and legal teams by centralizing authoritative client data used across billing, contracts, and regulatory processes.

Core Elements Every Professional Form Should Include

Essential elements to include when designing a professional Client Information Request Form for reliable data capture, regulatory compliance, and streamlined processing across teams.

Identification

Include full legal name, aliases, date of birth for individuals, and registered entity name for organizations. Capture government ID number and expiration where required to support identity verification and anti-fraud checks.

Contact Info

Collect primary and secondary phone numbers, a professional email address, and a full mailing address. Note preferred contact method and any restrictions on electronic communication for regulatory compliance.

Tax & Billing

Record taxpayer identification (SSN or EIN), billing name, payment terms, and invoicing contact. Verify TIN accuracy to avoid backup withholding and delayed payments.

Authorization

Specify who can make decisions, sign agreements, and approve payments. Require documentation such as corporate resolutions or power of attorney for third-party signers.

Security

Describe access controls, encryption at rest and in transit, and any required multi-factor authentication. Note retention schedule and audit trail availability for compliance reviews.

Attachments

List required supporting documents, acceptable file formats, and size limits. Common requests include voided checks, W-9, certificates of incumbency, and government-issued photo ID.

Step-by-Step: From Request to Stored Record

Follow these steps to collect, verify, and process client information efficiently, minimize rework, and create a clear audit trail for compliance.

01

Gather Details: Collect full name, address, TIN, and contact info.
02

Verify Identity: Confirm ID and TIN; request supporting documents.
03

Authorize Signer: Obtain signed authority or corporate resolution as needed.
04

Record Retention: Store completed form with audit trail and access controls.

Recommended Online Workflow Settings

Configure an online workflow to collect and route Client Information Request Forms automatically, applying validation and conditional routing rules.

Field	Configuration
Authentication Method	Email link with optional SMS code or KBA for higher assurance.
Required Attachments	Specify file types (PDF, JPG) and maximum size; make fields required.
Conditional Routing	Send to compliance if high-risk answers; otherwise route to account manager.
Retention Policy	Auto-archive after recording; enforce access controls and encryption at rest.

Typical eSubmission Flow

This workflow shows how a Client Information Request Form moves from sender to signer, through verification, and into secure storage with an audit trail.

Upload: Sender uploads form and selects fields.
Assign: Add signer emails and set signing order.
Authenticate: Authenticate signer via email, SMS, or KBA.
Archive: Store signed PDF with audit report and access controls.

Platform and Integration Considerations

Choose distribution channels and authentication levels that match the risk and regulatory needs of the client data.

Delivery: Email invite, direct upload, or secure link.
Integrations: CRM, ERP, cloud storage integrations supported.
File Types: PDF, DOCX, and image uploads accepted.

Security and Compliance Baseline

Encryption in Transit: TLS 1.2 and 1.3 transport encryption

Encryption at Rest: AES-256 encryption for data at rest.

Certifications: SOC 2 Type II and ISO 27001

HIPAA: HIPAA compliant with BAA available

Legal Frameworks: ESIGN and UETA recognition for signatures

Audit Trail: Comprehensive logs: timestamps, IP, actions

Short Risks and Penalties at a Glance

Incorrect TIN: May trigger 24% backup withholding.

Missing Signatures: Contracts may be unenforceable.

Late Filing: Information return penalties under IRC §6721.

I-9 Violations: Civil fines $281–$2,789 per violation.

Privacy Breach: HIPAA exposure with six-year record retention.

Operational Delay: Missing data causes onboarding hold.

Common Preparation Mistakes to Avoid

Collecting incomplete or inconsistent client identifiers, such as abbreviated names or missing tax IDs, which leads to identity verification failures and additional document requests that slow onboarding.
Failing to verify authorized signer status or obtain corporate resolutions results in invalid authorizations and potential payment disputes that require legal clarification.
Requiring unnecessary fields or attachments without explaining purpose increases completion time and raises privacy concerns under HIPAA or state privacy laws for regulated data.
Using weak authentication or mailing signed PDFs without audit logs undermines legal defensibility and complicates dispute resolution over signature attribution.

Timelines, Deadlines, and Processing Expectations

When requesting client information, set clear deadlines for response, verification, and completion to avoid billing delays and regulatory lapses.

Response Timeframe:

Request response within 7–14 calendar days.

Verification Window:

Allow 3–5 business days for identity verification.

Form Completion:

Complete and sign before service start date.

Escalation:

Escalate incomplete responses after 15 days.

Reporting Deadlines:

Provide TINs for 1099 reporting by Jan 31.

Pricing and Feature Comparison for eSignature Providers

Comparison of basic per-user pricing and feature differences among popular eSignature vendors to help choose a compliant solution for the Client Information Request Form.

	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
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently Asked Questions and Practical Answers

Common questions and solutions for completing, validating, and securely storing the Client Information Request Form.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic execution is enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the signature demonstrates intent, consent, attribution, and retention. Exceptions like wills or certain court filings still require paper or different procedures.
What authentication should I use?
Choose authentication proportional to risk: email for low-risk, SMS or knowledge-based verification for higher assurance, and ID credential analysis for regulated transactions. Stronger methods reduce fraud risk and support legal defensibility in disputes involving signature attribution.
Are notarization or witnesses required?
Generally, a Client Information Request Form does not require notarization or witnesses unless it contains a power of attorney, deed, or other notarized instrument. Remote Online Notarization is permitted in many states with identity proofing and audio-video recordkeeping requirements.
How long should we retain completed forms?
Retention depends on purpose: retain active files through the contract term plus three years; follow IRS minimums of three years for tax records (IRC §6501(a)); and retain healthcare records six years per 45 CFR §164.530(j). Check state variations.
What if client refuses to provide TIN?
If a client refuses to provide a correct TIN, require them to complete Form W-9 or document the refusal. Failure to obtain a TIN may trigger 24% backup withholding and exposure to penalties under IRC §6721 for incorrect reporting.
Can we collect PHI on this form?
You may collect PHI only when necessary and with proper patient authorization or a permitted purpose. Use HIPAA-compliant processes, execute a BAA with any eSignature vendor handling PHI, and retain records six years per 45 CFR §164.530(j).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now