Self-Exclusion Enrollment Form
Enroll a patron in a voluntary self-exclusion program with identity verification, exclusion period selection, photo upload, and signed acknowledgments. Use it to document consent, program scope, and enforcement details in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Gaming And Casinos · Hospitality · Regulated Entertainment · Public Sector
Overview
This Self-Exclusion Enrollment Form template is for documenting a patron’s voluntary request to be excluded from a venue, property, or program. It gathers the information needed to verify identity, define the exclusion period, capture a reference photo, and record the patron’s acknowledgment of the terms they are accepting.
Use it when your organization needs a consistent intake process for self-exclusion programs, especially in regulated environments where staff must recognize the patron and enforce the exclusion later. The template is useful for guest services, compliance, security, or responsible gaming teams that need a clear record of who enrolled, when the exclusion starts, and what areas or services it covers.
Do not use this form as a general customer feedback form or a broad incident report. It is also not the right template if you do not need identity verification or if your program does not require a photo, government ID reference, or signed acknowledgment. In those cases, remove unnecessary fields rather than collecting PII by default. The form should stay focused on the minimum necessary information, with clear required versus optional fields and a plain-language note explaining what happens after submission.
Standards & compliance context
- Collect only the PII needed to administer the self-exclusion program, in line with GDPR Article 5 data minimization principles.
- If the form is used in a regulated venue, keep an audit trail of submission, review, and acceptance actions so the enrollment can be verified later.
- Use clear consent and disclosure language before collecting identification details or a photo, especially when the data will be used for enforcement.
- If the program is tied to a public-facing intake process, make the form accessible and keyboard-friendly to support WCAG 2.1 AA expectations.
- Keep the acknowledgment language aligned with the actual exclusion rules, including whether the patron can revoke, extend, or renew the enrollment.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Program Notice
This section explains the program before any personal data is collected, so the patron can make an informed decision.
-
Self-Exclusion Program Notice
This form is used to enroll a patron in a voluntary self-exclusion program. Information collected will be used only to verify identity, administer the exclusion, and support compliance and audit trail requirements.
-
Consent to collect and use my personal information for self-exclusion administration
By checking this box, you consent to the collection and use of the personal information and photo provided on this form for identity verification, exclusion enforcement, and compliance recordkeeping.
-
I understand the self-exclusion terms and consequences
I understand that self-exclusion may restrict my access to gaming areas, promotions, and related services for the selected period, and that violations may result in removal or other actions permitted by program rules.
Patron Identification
These fields verify who is enrolling and give staff enough information to match the record later without collecting unnecessary PII.
- Full Name
-
Date of Birth
Used only for identity matching and age verification where required.
- Government ID Type
-
Government ID Last 4 Digits
Optional. Use only if needed to match the identity record.
-
Phone Number
Optional contact number for enrollment follow-up and confirmation.
-
Email Address
Optional email for confirmation and program communications.
Address and Contact Details
This section captures the minimum contact information needed for notices, follow-up, or record matching.
- Street Address
- City
- State / Province
- Postal Code
Exclusion Period
These fields define how long the exclusion lasts, when it starts, and where it applies.
- Exclusion Period
-
Requested Start Date
If not approved immediately, the effective date may be adjusted according to program rules.
- Scope of Exclusion
Identification Photo
A current photo helps staff recognize the patron during enforcement, so this section should be used only when your process requires it.
-
Current Photo
Upload a clear, recent photo of the patron. This will be used only for self-exclusion administration and enforcement.
-
Photo Taken Date
Optional. Helps confirm the photo is current.
Acknowledgment and Signature
This section records the patron’s agreement to the terms and creates the signed record needed for enforcement and audit purposes.
- I understand the exclusion may not be revoked before the end of the selected period, except as allowed by program rules
- I understand that property access, marketing contact, and account privileges may be restricted under the program
-
Patron Signature
Signature confirms the accuracy of the information provided and agreement to the self-exclusion terms.
- Signature Date
How to use this template
- 1. Configure the program notice, consent language, and acknowledgment text so the patron understands the exclusion terms before entering any personal data.
- 2. Set the patron identification fields to match your verification process, using the least amount of PII needed and marking only truly required fields as required.
- 3. Define the exclusion period options, start date rules, and program scope so the patron can select a valid term without free-text ambiguity.
- 4. Add the identification photo upload and photo taken date fields, and make sure staff know when a current photo is required versus when an existing image can be reused.
- 5. Route the completed submission to the correct reviewer or administrator, then record the signature, review outcome, and any follow-up enforcement steps in your audit trail.
Best practices
- Use progressive disclosure for any venue-specific or jurisdiction-specific terms so the patron only sees fields that apply to their enrollment.
- Keep government ID collection minimal by storing only the ID type and last four digits when full document details are not necessary.
- Use a date picker for date of birth, start date, photo taken date, and signature date rather than free-text entry.
- Make the program scope explicit, such as one property, one venue group, or all locations, so staff can enforce the exclusion consistently.
- Include a plain-language line that explains what happens after submission, including whether the enrollment is pending review or effective immediately.
- Require a current photo only when your enforcement process depends on visual identification, and avoid duplicate uploads when an existing image is already on file.
- Review the acknowledgment wording with compliance or legal staff before rollout so the terms match the actual program rules.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Self-Exclusion Enrollment Form used for?
This form is used to enroll a patron in a voluntary self-exclusion program and document the terms they agreed to. It captures identity verification, contact details, exclusion period, photo upload, and signed acknowledgments. The result is a clear record for program administration and enforcement.
Who should complete and process this form?
The patron should complete the form, with staff or a program administrator reviewing identity details and confirming the submission is complete. If your process allows assisted intake, staff can help explain the fields without changing the patron’s answers. Keep an audit trail of who reviewed and accepted the enrollment.
How often is this form used?
It is typically used once per enrollment, and again only if your program allows a new exclusion period or a fresh enrollment after a prior term ends. It is not a recurring check-in form. If your policy includes renewals or extensions, create a separate renewal workflow rather than overloading this form.
What information should be required versus optional?
Only require the fields needed to verify identity, enforce the exclusion, and contact the patron about the program. Use optional fields where local policy does not need the data, and avoid collecting extra PII that you will not use. This supports data minimization and reduces friction during intake.
Does this form need a photo and government ID?
If your program uses visual identification for enforcement, include both the photo upload and a government ID field with only the last four digits recorded when possible. If your policy does not require one of those items, remove it rather than collecting it by default. Keep the field types aligned to the data being captured.
How should the exclusion period be configured?
Use a controlled exclusion period field, such as a select list or date-based duration, so the patron cannot enter ambiguous terms. Pair it with a start date and clear program scope so there is no confusion about when the exclusion begins and where it applies. If your program has multiple durations, use conditional logic to show only the valid options.
What happens after the patron submits the form?
The submission should route to the program administrator or compliance reviewer for verification, recordkeeping, and any required enforcement steps. The patron should see a confirmation message that explains whether the enrollment is pending review or immediately accepted. If applicable, store the submission in an audit trail and notify the relevant locations or systems.
Can this template be customized for different venues or jurisdictions?
Yes. You can adjust the program scope, exclusion period options, contact fields, and acknowledgment language to match a casino, gaming venue, or other regulated setting. If local rules require different disclosures or retention practices, update the template before rollout and have legal or compliance review the final version.
How is this better than collecting the information informally?
A structured form reduces missing fields, inconsistent wording, and unclear consent language. It also creates a cleaner record for staff, which is important when the program must be enforced later. Informal intake often leaves gaps in identity verification, dates, or acknowledgments that are hard to fix after the fact.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
Reduce recruiting pipeline friction with faster sourcing, scheduling, and comp benchmarking to hire top talent before competitors do.
-
MangoApps 2026 Winter Release adds native shift scheduling, structural AI for surveys and wikis, and a redesigned search—unifying frontline operations in one...
-
Small team strategies to win big clients with collaboration, transparency, and agility—without enterprise overhead.
Ready to use this template?
Get started with MangoApps and use Self-Exclusion Enrollment Form with your team — pricing built for small business.
