Is an electronic signature valid?

Yes. Electronic signatures are legally valid in the U.S. under the ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided intent, consent, attribution, and record retention requirements are met.

Do I need a paper disclosure for electronic consent?

For consumer-facing financial or healthcare records, ESIGN requires a consumer disclosure and an ability to withdraw consent; follow 15 U.S.C. §7001(c) procedures when sending electronic receipts or tax acknowledgments.

How should I correct an error on a submitted form?

Document corrections with a dated amendment or new submission, keep the original, and log who made the change; retain both versions for the retention period.

What are required retention periods?

Keep tax-related records at least 3 years (IRC §6501(a)); HIPAA-related records 6 years (45 CFR §164.530(j)); longer state or industry rules may apply.

Can supporters withdraw consent to communications?

Yes. Provide an easy method to withdraw consent and record the request; maintain proof of the withdrawal for compliance and audit.

What steps reduce data breach risk?

Limit stored PII, use encrypted transport and storage (TLS and AES-256), restrict access, and use vendors with SOC 2/ISO 27001 certifications.

Electronic Signature
Templates
Miscellaneous
Supporter Information Form

Supporter Information Form

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

SUPPORTER INFORMATION FORM AND SUPPORT AGREEMENT

This Supporter Information Form and Support Agreement (the Agreement) is entered into on between:

Supporter Name: Organization Name:

WHEREAS

WHEREAS, Supporter desires to provide financial and/or in‑kind support to Organization for the purpose of advancing Organization's lawful charitable and programmatic activities; and

WHEREAS, Organization desires to accept such support on the terms set forth herein and to collect certain information from Supporter to document the relationship, payment arrangements, and any applicable reporting or recognition; and

WHEREAS, the parties intend this Agreement to memorialize the Supporter information, pledge terms, confidentiality obligations, and governance provisions applicable to their relationship.

SUPPORTER CONTACT INFORMATION

Primary Contact Mailing Address

Email

Phone

Supporter Type Individual Organization

SCOPE OF SUPPORT

Supporter agrees to provide the support described below. Supporter shall complete the scope and description fields to make clear the nature of the support and any restrictions or designations.

Scope of Support (describe activities, program designation, restrictions, and any deliverables)

PAYMENT TERMS

Supporter hereby pledges the following amount and accepts the payment schedule and late fee provisions set forth below.

Pledge Amount (USD) Payment Schedule (installments, dates, or one-time) Late Payment Fee

Payment Method: Check Credit Card Bank Transfer

Authorization for recurring payments or automatic charges (if applicable)

TERM AND TERMINATION

This Agreement commences on the Start Date set forth below and continues until the End Date unless earlier terminated in accordance with this section.

Start Date

End Date

Notice Period for Termination (days)

Either party may terminate this Agreement for any reason upon written notice to the other party in accordance with the notice period above. Termination shall not relieve Supporter of obligations to pay amounts due for support already incurred or irrevocably committed by Organization prior to the effective date of termination.

CONFIDENTIALITY

For the purposes of this Agreement, "Confidential Information" means nonpublic information disclosed by either party that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. Each party shall hold Confidential Information in confidence and shall not disclose or use such information except as necessary to fulfill its obligations under this Agreement or as required by law. Confidentiality obligations do not apply to information that is or becomes public through no fault of the receiving party, is independently developed, or is received from a third party without restriction.

Publicity Consent: Supporter consents to Organization using Supporter name, logo, and gift amount for recognition and fundraising purposes unless Supporter indicates objection below.

I consent to recognition/publicity I prefer to remain anonymous

OTHER PROVISIONS

Governing Law: This Agreement shall be governed by and construed in accordance with the laws of the state of , without regard to conflict of laws principles.

Entire Agreement: This Agreement, together with any attachments or addenda signed by both 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.

Amendment: Any amendment to this Agreement must be in writing and signed by authorized representatives of both parties.

SUPPORTER CERTIFICATIONS AND AUTHORIZATIONS

By signing below, Supporter certifies that the information provided in this form is true and accurate, that Supporter has the authority to enter into this Agreement and to authorize payments where indicated, and that Supporter understands and agrees to the terms set forth herein.

Tax Receipt Requested: Yes No

Emergency Contact Name Emergency Contact Phone

Preferred Method of Communication: Email Phone Mail

Supporter Name:

By:

Date:

Organization Representative:

By:

Date:

What the Supporter Information Form Is and when it's used

A Supporter Information Form collects contact details, permission choices, and transaction data from individuals who support an organization financially or by volunteer action. Typical items include legal name, mailing and email addresses, preferred contact channels, donation amount or pledge, payment method, and any required tax or gift acknowledgment language. For organizations, the form documents consent for communications, opt-in preferences under TCPA/CAN-SPAM considerations, and the information needed to issue receipts and comply with reporting obligations. It can be delivered on paper or electronically and integrated into donor management systems.

Why a clear Supporter Information Form matters

A complete, well-structured form reduces errors, speeds donor processing, and documents consent for communications and tax receipts. It also centralizes the data needed for acknowledgments, annual reporting, and retention compliance.

Who typically completes or manages this form

Clear role assignment (who collects, who verifies, who stores) helps preserve data integrity and legal compliance across fundraising channels.

Development Teams — collect donor contact details, gift intent, and tax receipt info for recordkeeping and stewardship.
Event Volunteers — register attendees, record volunteer preferences, and capture emergency contact information.
Individual Supporters — provide legal name, address, contact consent, and payment authorization for donations.

Core sections to include in a professional form

Design the form so each section maps to a downstream process: identification, contact, consent, payment, receipt issuance, and privacy disclosures.

Supporter Identity

Full legal name and any organization name; required for tax receipts and verifying matching records in donor databases.

Contact Details

Mailing address, email, and phone with clear formatting instructions so receipts and notices reach the correct recipient.

Donation Details

Gift amount, pledge schedule, payment method, and designation (restricted vs. unrestricted) to ensure proper accounting and acknowledgment.

Consent & Preferences

Clear opt-in/opt-out choices for email, SMS, and mail; document consent to electronic records where consumer disclosure is required.

Acknowledgment

Language for tax acknowledgment and a block indicating whether the organization provided goods or services in exchange for the gift.

Signature Block

Signature and date fields for the supporter, plus fields for staff verification and payment authorization where applicable.

Step-by-step: completing and processing the form

Follow a consistent sequence to collect, verify, and record supporter data to minimize delays and legal exposure.

01

Capture: Collect supporter details and consent at point of interaction.
02

Verify: Confirm contact info and payment method before finalizing.
03

Authorize: Obtain signature or e-signature and date the form.
04

Record: Store form in donor system and issue acknowledgment or receipt.

Configuring an online workflow for this form

Map form fields to donor CRM fields and set validation rules to reduce manual corrections.

Field Mapping	Map Full Name, Email, Address to matching CRM fields for one-click import.
Required Fields	Mark name, email, donation amount, and consent as required to prevent incomplete submissions.
Validation Rules	Validate email format and ZIP codes; reject invalid payment tokens automatically.
Notifications	Trigger email receipts to the supporter and an internal alert to finance on large gifts.
Audit Trail	Enable timestamps and user attribution for every change to the record.

Where completed forms should be sent and stored

Define routing so each completed form is delivered to the right system and person without manual handoffs.

Donor CRM: Primary storage for contact and giving history; enable automatic import.
Finance: Send payment confirmations and gift details for reconciliation.
Acknowledgment: Generate and deliver tax receipts within required timelines.
Records Archive: Store a signed copy in secure long-term archive for compliance.

Technical considerations for digital delivery and signing

Ensure integrations (CRM, Google Workspace, Box, NetSuite) and secure transport (TLS) are configured so signed forms route automatically and remain auditable.

File Formats: PDF and DOCX accepted for upload and signed output.
Integrations: Connectors to CRM and cloud storage are essential.
Authentication: Support email link or SMS code signer authentication.

Essential data elements to collect and protect

Legal Name: Full legal name

Contact Info: Email, phone, address

Payment Data: Last four digits or token

Consent Record: Opt-in status

Tax Details: TIN or donor ID

Signature: Signed consent or e-sign

Common mistakes to avoid when creating the form

Collecting incomplete addresses or partial names, which leads to failed mailings and inability to match donor records.
Failing to obtain explicit consent for electronic communications, risking TCPA or CAN-SPAM noncompliance and donor complaints.
Storing full payment card data outside PCI-compliant systems, creating security and regulatory exposure for the organization.
Not mapping fields to CRM or accounting systems, causing duplicate entries and reconciliation delays.

Legal and financial risks of incorrect or incomplete forms

TCPA Exposure: Risk of statutory damages for unsolicited calls/texts

CAN-SPAM Violations: Potential fines for noncompliant commercial emails

Data Breach Liability: Costs from unauthorized access to supporter data

Charity Registration Fines: State penalties for failing to register for solicitations

Incorrect Receipts: IRS issues for inadequate gift acknowledgments

Retention Failures: Regulatory disputes from missing records

Comparing eSignature options for collecting supporter information

Platform choice affects cost, compliance features, and throughput. signNow appears first for neutral comparison against common alternatives.

	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 by plan	Varies by plan	Varies by plan

Frequently asked questions about the Supporter Information Form

Answers to common operational and legal questions when collecting supporter data and signatures.

Need help? Contact support

Is an electronic signature valid?
Yes. Electronic signatures are legally valid in the U.S. under the ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided intent, consent, attribution, and record retention requirements are met.
Do I need a paper disclosure for electronic consent?
For consumer-facing financial or healthcare records, ESIGN requires a consumer disclosure and an ability to withdraw consent; follow 15 U.S.C. §7001(c) procedures when sending electronic receipts or tax acknowledgments.
How should I correct an error on a submitted form?
Document corrections with a dated amendment or new submission, keep the original, and log who made the change; retain both versions for the retention period.
What are required retention periods?
Keep tax-related records at least 3 years (IRC §6501(a)); HIPAA-related records 6 years (45 CFR §164.530(j)); longer state or industry rules may apply.
Can supporters withdraw consent to communications?
Yes. Provide an easy method to withdraw consent and record the request; maintain proof of the withdrawal for compliance and audit.
What steps reduce data breach risk?
Limit stored PII, use encrypted transport and storage (TLS and AES-256), restrict access, and use vendors with SOC 2/ISO 27001 certifications.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now