Identity
Collect full legal name, date of birth, government ID type and number, issuing country or state, and expiration date. Include instructions to match the name exactly as shown on the presented ID to avoid processing delays.
A Passenger Registration Form centralizes passenger data for operational efficiency, safety, and compliance. Accurate records speed boarding, enable emergency response, and support contact-tracing or regulatory reporting. Electronic capture reduces manual errors and simplifies retention under applicable recordkeeping laws.
Organizations and staff who handle passenger movement complete or request Passenger Registration Forms for operational, safety, and legal purposes.
Roles using the data include front-line staff, dispatch, safety coordinators, and compliance teams that depend on timely, accurate form entries.
Responsible for verifying collected data, cross-checking IDs, ensuring forms meet regulatory and internal policy standards, and maintaining manifests. They coordinate with safety and legal teams when special assistance or health declarations are present and oversee data retention schedules.
Provides accurate legal name, date of birth, government ID number or passport, contact and emergency information, and discloses relevant medical needs. Accuracy affects boarding, liability, and potential backup withholding if taxpayer identification is requested for payment or taxation purposes.
| Field | Configuration |
|---|---|
| Authentication | Email link; SMS OTP; optional KBA |
| Signature Type | E-signature or drawn signature field |
| Conditional Logic | Show medical fields only when needed |
| Storage | Encrypted storage with retention policy |
| Integrations | Connect to CRM, ERP, or cloud storage |
Use eSubmission to reduce handling; select a platform supporting PDF, DOCX, and mobile signing.
Collect full legal name, date of birth, government ID type and number, issuing country or state, and expiration date. Include instructions to match the name exactly as shown on the presented ID to avoid processing delays.
Provide primary phone number, email address, and mailing address; request preferred contact method and permission to send SMS or email notifications. Clearly explain data use for contact-tracing and emergency alerts.
Offer checkboxes for mobility assistance, allergies, medication needs, and space for brief explanations. Include confidentiality notice and indicate whether medical info is required for boarding or only for safety planning.
Collect emergency contact name, relationship, and phone number. Recommend two contacts and clarify whether the passenger authorizes release of information in an emergency situation.
Include ESIGN consumer disclosure when collecting e-signatures, a privacy consent statement for data use, and an affirmation that provided information is accurate to the best of the passenger's knowledge.
Provide signature field, printed name, and MM/DD/YYYY date fields. If notarization or witness is required, include separate sections and instructions for in-person or RON workflows.
Export signed forms as flattened, audit-stamped PDFs compatible with ISO 32000 standards. Include embedded audit trails and signer metadata so records are admissible and tamper-evident for compliance reviews.
Bulk export passenger lists and contact fields in CSV or Excel formats for operational reporting, manifest uploads, batch communications, and integrations with scheduling or CRM systems.
Provide a clean, single-page printable layout for on-site registration or backup paper collection, including clear field labels and space for manual initials and notary stamps.
Store completed forms in encrypted archives with retention tagging, role-based access controls, and easy export for audits, incident investigations, and legal hold processes.
Collect completed form before boarding or at check-in.
Retention begins on date of signing or trip date.
Retain RON session recordings per state notary requirements.
Keep records accessible for audits for required federal periods.
Allow passengers to update contact info up to departure where feasible.
| Document Type | Passenger Registration Form | Liability Waiver |
|---|---|---|
| Primary purpose | passenger data | risk release |
| Required fields | identification, contact | scope, risks, consideration |
| Signature legal effect | operational record | contractual release |
| Notarization typical | rare | sometimes required |
| 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 | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | No cap | No cap | No cap |
Form collection window opens when bookings begin.
Identity and data checks completed before final manifest.
Create final passenger manifest and distribute to crew.
Store signed records with audit trail; apply retention policy.