Required Forms and Waivers

HubIRL uses required forms to enforce event readiness and legal/compliance workflows.

Mental Model

• Community creates reusable templates.
• Event attaches templates or custom forms.
• Event publishes form versions.
• Ticket holder and guests sign required forms.
• Scanner enforces completion at check-in.

Organizer Setup Flow

1. Create community-level templates in hub admin documents.
2. Attach templates (or create custom forms) in event admin documents.
3. Mark each document as required or optional.
4. Publish versions before event day.
5. If re-sign is required on a new version, attendees must sign again.

Ticket Holder Flow

1. Open your ticket.
2. Open the forms/documents section.
3. Sign all required items.
4. Return to ticket and verify readiness state.

Guest Flow

1. Ticket owner or admin sends guest signing link.
2. Guest opens secure link and signs without full app access.
3. Completion status syncs into ticket readiness.
4. Scanner checks owner and guest completion for required items.

Event-Day Enforcement

Scanner checks required forms before normal validation.

If forms are missing:

• attendee/guest signs first, then re-scan, or
• authorized operator uses explicit override where policy allows.

Override Rules

• OWNER and ADMIN can override.
• Event staff can override only with explicit OVERRIDE_CONSENT.
• Overrides should be controlled exception handling, not default workflow.

Common Failure Cases

”I signed but still blocked”

• Check if a newer form version now requires re-sign.
• Check whether a guest on the same ticket still has pending required forms.

”Guest cannot open signing link”

• Regenerate and resend the guest link.
• Confirm guest is tied to the correct attendee record.

”Scanner says documents required”

• Use scanner pending-doc details.
• Resolve signer-by-signer and re-scan.

Related Guides

• Events and Tickets
• Roles and Permissions
• Troubleshooting