Can attendees sign electronically?

Yes. Electronic signatures meet enforceability tests when they show intent, consent to transact electronically, attribution, and reliable record retention as described in the ESIGN Act (15 U.S.C. ch. 96) and UETA (1999).

Is notarization required for registrations?

Generally no for standard registrations; notarization is only necessary when a specific legal instrument requires it. Check local venue, permit, or vendor contract terms for exceptions.

How should refunds be handled?

Define refund windows and procedures in the form terms. Keep records of approvals, transaction IDs, and communication; this documentation helps resolve chargebacks and consumer disputes.

What if a registrant provides incorrect TINs?

For vendor payments, incorrect TINs can trigger backup withholding at 24% and IRS penalty risk. Use validated W-9 collection processes and correct errors promptly to avoid IRC §6721 consequences.

How do I export attendee data?

Most platforms export CSV or PDF. Include fields for name, contact, ticket type, payment status, and consent flags so reconciliation and check-in are straightforward.

How long must records be kept?

Follow federal baselines such as IRS three-year rules (IRC §6501(a)) and HIPAA six-year retention (45 CFR §164.530(j)); adjust for state or industry-specific longer periods.

Electronic Signature
Templates
Miscellaneous
Chicago Event Registration Form

Chicago Event Registration Form

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

CHICAGO EVENT REGISTRATION FORM

This Registration Agreement (the Agreement) is entered into by and between Event Organizer: and Registrant: for participation in the event identified below. The Organizer and Registrant are each a Party and collectively the Parties.

WHEREAS

WHEREAS, the Event Organizer conducts professional and public events in Chicago and will host the event described herein (the Event); and

WHEREAS, the Registrant desires to register for the Event and to obtain the services, access, and materials described in this Agreement subject to the terms and payment provisions set forth below.

EVENT DETAILS

Event Name:

Event Date: Venue:

City: State:

REGISTRANT INFORMATION

Full Legal Name Organization / Company (if applicable) Email Phone Address

SCOPE OF WORK / ACCESS

The Organizer agrees to provide the Registrant with access to the Event, scheduled sessions, materials, and meals as designated in the ticket(s) purchased. The Organizer's obligations include reasonable event organization, venue access, name badge, and any paid conference materials. Specific services, speaker access, exhibitor access, or sponsorship deliverables will be described below:

TICKET & PAYMENT SELECTION

Ticket Type (check one): General Admission VIP Student

Number of Tickets Total Fee (USD) Deposit Amount Balance Due By Payment Method Payment Reference / Transaction ID

PAYMENT TERMS

Registrant agrees to pay the Total Fee in accordance with the schedule above. Late payments shall incur a late fee of on the outstanding balance, calculated monthly. Failure by Registrant to pay amounts when due permits Organizer to suspend access, cancel registration, and recover collection costs and reasonable attorneys' fees.

TERM AND TERMINATION

Term Start Date: Term End Date:

Either Party may terminate this Agreement for material breach by the other Party if the breach remains uncured for days following written notice. Organizer may terminate without liability for reasons of public safety, force majeure, or venue closure; in such events Organizer will refund paid fees pro rata or offer reasonable alternatives.

CONFIDENTIALITY

Each Party shall keep confidential any non-public information disclosed in connection with this Agreement and shall not disclose such information except to its employees, agents, or contractors who have a need to know and who are bound by confidentiality obligations no less protective than those set forth herein. Information that is or becomes public through no fault of the receiving Party, or that is lawfully received from a third party, is not confidential.

Registrant acknowledges confidentiality terms I acknowledge and will comply with the confidentiality obligations described above.

WAIVER, RELEASE & CONDUCT

Registrant acknowledges that attendance at live events involves inherent risks. Registrant releases Organizer and its agents from liability for personal injury, property damage, loss, or theft arising from participation, except to the extent resulting from Organizer's gross negligence or willful misconduct. Registrant agrees to abide by venue rules and Organizer's code of conduct and understands that Organizer may remove Registrant for noncompliance without refund.

Registrant acceptance of waiver and conduct terms I accept the waiver, release, and conduct terms set forth above.

PHOTO AND MEDIA RELEASE

Registrant grants Organizer the right to photograph and record sessions and to use such photographs, audio, and video for promotional and archival purposes without further compensation, unless Registrant checks below refusing consent.

Photo release I consent to being photographed and recorded for promotional and archival use.

CANCELLATION & REFUND POLICY

Cancellation by Registrant more than 30 days prior to the Event receives a full refund minus any non-refundable processing fees. Cancellations 30 days or fewer prior to the Event may be subject to partial refunds or no refund as set by Organizer. Refunds will be processed to the original payment method within a reasonable time after approval.

EMERGENCY & ACCESSIBILITY

Emergency Contact Name Emergency Contact Phone Dietary Restrictions or Allergies Accessibility or Special Requirements

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, ticket terms, and schedules, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous discussions, negotiations, and agreements, whether oral or written. Any modification must be in writing and executed by both Parties.

ADDITIONAL PROVISIONS

If any provision of this Agreement is determined to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither Party may assign this Agreement without the prior written consent of the other, except that Organizer may assign to an affiliate or successor in connection with a transfer of its business.

Registrant:

By:

Date:

Event Organizer:

By:

Date:

What the Chicago Event Registration Form Is and When It’s Used

The Chicago Event Registration Form collects attendee information, session selections, payment authorization, and consent statements for events held in Chicago. It centralizes contact details, ticket type, emergency and accessibility needs, and any required waivers or liability acknowledgments so organizers can manage attendance, enforce capacity limits, and comply with recordkeeping obligations for permits, vendor payments, or public-safety reviews.

Why a Standardized Registration Form Matters

A clear registration form reduces processing errors, supports consistent customer communications, and documents consent and payment terms. For electronic execution, legal equivalence is governed by the ESIGN Act (15 U.S.C. ch. 96) and UETA (1999), which together permit enforceable electronic signatures in most U.S. jurisdictions.

Who Typically Completes or Manages This Form

Event organizers and administrative staff prepare and distribute the form; attendees complete it to register and consent. Organizers centralize responses for check-in and reporting.

Event organizers and planners responsible for guest lists, capacity, and vendor coordination.
Attendees or registrants providing contact, payment, and emergency information for participation.
Vendors, speakers, and sponsors submitting certificates, contact data, or billing instructions.

Authorized Signers and Role Examples

Event Manager

The Event Manager is the individual designated to finalize registration terms, authorize refunds, and sign vendor contracts on behalf of the host organization. This person should be an employee or an officer with documented authority to bind the organization.

Authorized Signer

An Authorized Signer is a named representative (organizer, executive, or procurement officer) who completes payment authorization, signs waivers or venue agreements, and verifies attendee lists for official records.

Step-by-Step: How to Complete the Registration Form

Follow these steps to prepare, distribute, and collect a legally enforceable registration form for an event in Chicago.

01

Prepare form: Define fields, payment terms, and waiver language.
02

Distribute: Send secure links or embed the form on the event site.
03

Collect responses: Monitor submissions and payment confirmations.
04

Confirm attendance: Issue tickets and update the check-in roster.

Submission Workflow and Where Records Go

The typical routing captures registration data, processes payment, issues confirmation, and exports an attendee list for on-site check-in.

Capture data: Form records saved to organizer account or CRM.
Process payment: Payment gateway handles charges and receipts.
Send confirmation: Automated email with ticket and instructions.
Export list: CSV or PDF roster used at event check-in.

Common Online Configuration Settings

Configure fields and authentication to match event risk and compliance needs; use conditional logic for waivers or restricted sessions.

Field	Configuration
Auto-fill	Map to CRM fields to reduce duplicate entry.
Conditional logic	Show waiver fields when premium sessions are selected.
Authentication	Use email link or SMS code for signer verification.
Reminders	Schedule email reminders for unpaid or incomplete registrations.

Technical Requirements and Integrations

Ensure the form platform supports required integrations, file formats, and signer authentication before launch.

Integrations: Salesforce, Google Workspace, NetSuite and similar systems supported.
File formats: Accepts PDF, DOCX, and exports to CSV for reporting.
Authentication: Email, SMS code, or knowledge-based checks available.

Essential Elements of a Professional Registration Form

Include clear contact fields, payment capture, waivers, accessibility options, and exportable data to support operational, legal, and reporting needs.

Contact capture

Collect full name, email, and phone in discrete fields to ensure reliable confirmations and emergency contact reachability; validate formats to reduce bouncebacks and missed communications.

Session selection

Provide selectable sessions with capacity controls and conditional questions for restricted tracks so organizers can manage attendance by time slot and resource allocation.

Payment collection

Integrate a PCI-compliant gateway for ticket payments; record transaction IDs and timestamps for reconciliation and refund processing.

Waivers and consents

Present liability waivers and photo/recording consents clearly and capture an explicit signature or checkbox acknowledging agreement for legal clarity.

Accessibility options

Include fields for accommodation requests and accessibility needs so planners can provide required services and comply with local ordinances.

Data export

Enable CSV/PDF exports of attendee lists and payment summaries for on-site check-in, reporting, and accounting reconciliation.

Security and Compliance Basics

In-transit encryption: TLS 1.2/1.3

At-rest encryption: AES-256

Audit trail: Timestamps and IP logs

Access controls: Role-based permissions

HIPAA support: BAA available

PCI support: Payment data handling

Common Errors to Avoid When Preparing the Form

Using free-text for critical fields leads to inconsistent records and extra manual cleanup during import or reporting.
Not validating email or phone formats causes failed confirmations and increases no-shows or administrative follow-up.
Omitting explicit consent language for waivers or recordings can create legal exposure and complicate dispute resolution.
Failing to test mobile and desktop flows results in lost registrations from users on phones or tablets.

Potential Legal and Financial Risks

Data breach fines: Regulatory penalties and remediation costs

HIPAA violations: Civil penalties for PHI mishandling

Tax reporting: IRC §6721 penalties for incorrect information returns

Consumer disputes: Refund or chargeback liabilities

Venue liability: Overcapacity or safety incidents exposure

Contract breaches: Vendor or sponsorship dispute costs

Key Timing Considerations for Registrations

Set and publish clear cutoffs, payment deadlines, and confirmation windows so registrants and staff share the same expectations.

Registration cutoff:

Close online registration at a fixed date/time before the event.

Payment deadline:

Require payment at time of registration or within a defined invoice period.

Confirmation delivery:

Send ticket and instructions within 24 hours of successful registration.

Cancellation window:

Define refund eligibility cutoff (for example, 14 days before event).

Post-event follow-up:

Allow 30 days for surveys, reimbursements, or final reporting.

Key Milestones and Processing Stages

Track milestone stages from form design to archival so stakeholders know when each action is completed and who owns it.

01

Draft form

Design fields, consents, and payment logic before testing.

02

Publish and distribute

Make the live form available through secure links or your website.

03

Collect and reconcile

Monitor submissions, confirm payments, and resolve failed transactions.

04

Close and archive

Finalize attendee lists and store records per retention policy.

Typical eSignature Pricing and Feature Comparison

Common vendor pricing and feature availability for eSignature platforms used to collect registrations and payments; signNow is listed first for comparison.

	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 trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

How Organizations Use This Form in Practice

Real-world examples show common implementation patterns for event registration forms at mid-size organizations.

Martin Properties — Tim Martin, Founder

Tim Martin streamlined open-house registration to reduce manual sign-in.

Used real-time confirmations and mobile check-in.
The approach reduced on-site lines and ensured accurate contact capture for follow-up while preserving necessary disclosure and venue liability language.

Fertility Centers of Illinois — John Butler, Founder

John Butler implemented a secure consent flow for patient education events.

Required explicit consent and contact verification.
This ensured HIPAA-aware handling of attendee information and consistent audit trails for medical outreach while simplifying post-event reporting.

Practical Tips for Accurate and Efficient Completion

Apply these operational practices to reduce errors, improve throughput, and support compliant recordkeeping.

Validate contact fields

Enforce email and phone validation, present inline error messages, and require confirmation for high-value registrations to prevent failed communications and reduce no-shows.

Use conditional questions

Show follow-up fields only when relevant (dietary needs, session prerequisites) to keep the form concise and reduce respondent fatigue.

Test mobile flows

Simulate registration on common devices and browsers to ensure payment and signature capture work reliably for mobile users.

Record audit trail

Capture timestamps, IP addresses, and consent records for electronic signatures to support enforceability and dispute resolution.

Frequently Asked Questions About the Chicago Event Registration Form

Answers to common questions about electronic signatures, notarization, retention, and distribution for event registration forms.

Need help? Contact support

Can attendees sign electronically?
Yes. Electronic signatures meet enforceability tests when they show intent, consent to transact electronically, attribution, and reliable record retention as described in the ESIGN Act (15 U.S.C. ch. 96) and UETA (1999).
Is notarization required for registrations?
Generally no for standard registrations; notarization is only necessary when a specific legal instrument requires it. Check local venue, permit, or vendor contract terms for exceptions.
How should refunds be handled?
Define refund windows and procedures in the form terms. Keep records of approvals, transaction IDs, and communication; this documentation helps resolve chargebacks and consumer disputes.
What if a registrant provides incorrect TINs?
For vendor payments, incorrect TINs can trigger backup withholding at 24% and IRS penalty risk. Use validated W-9 collection processes and correct errors promptly to avoid IRC §6721 consequences.
How do I export attendee data?
Most platforms export CSV or PDF. Include fields for name, contact, ticket type, payment status, and consent flags so reconciliation and check-in are straightforward.
How long must records be kept?
Follow federal baselines such as IRS three-year rules (IRC §6501(a)) and HIPAA six-year retention (45 CFR §164.530(j)); adjust for state or industry-specific longer periods.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now