Self-Exclusion Enrollment Form

This form enrolls a patron in a voluntary self-exclusion program and records the minimum information needed to verify identity, set the exclusion period, and document consent. It is designed to create a clear audit trail for program administrators. Use it when a person is choosing to restrict access to a venue, property, or service under an established exclusion policy.

The patron should complete the identification and consent fields, and an authorized program administrator should review the submission for completeness and identity match. If your process requires witness verification or a staff reviewer, that role should be defined in the workflow before rollout. The form should not be used as a general intake form by front-line staff without clear authorization.

It is typically submitted once per enrollment event, with a new form required if the patron changes the exclusion period or re-enrolls after expiration. If your program allows renewals, use a separate renewal process rather than editing the original record without an audit trail. That keeps the record clear and easier to enforce.

Collect only the fields needed to identify the patron, confirm consent, and administer the exclusion period. Use the minimum-necessary principle and avoid collecting unnecessary PII such as full government ID numbers, date of birth details beyond what is needed, or unrelated personal history. If your policy allows anonymous inquiry before enrollment, keep that separate from the signed enrollment record.

If your program uses a patron photo for verification, the form should include explicit consent and a clear explanation of how the image will be used and stored. Supporting documents should be limited to what is required to confirm identity or eligibility, and the field should be optional unless your policy requires it. Avoid collecting extra documents by default because that increases privacy risk and review burden.

Use a controlled field such as a dropdown or radio group for standard exclusion periods, with an 'other' option that reveals a conditional text field for custom terms. This reduces entry errors and makes the record easier to review. The effective date should be a date picker so the enrollment timeline is unambiguous.

The submission should trigger a review step, confirmation of the selected exclusion period, and storage of the signed record in an audit trail. The patron should receive a clear confirmation of whether the enrollment is pending review or active immediately, depending on your policy. If the program includes enforcement steps, those should be documented separately from the enrollment form.

You can tailor the program notice, exclusion period options, supporting document requirements, and acknowledgment language to match the governing policy. Add conditional logic for venue-specific rules, such as different access restrictions or regional program terms. Keep the core identity, consent, and signature fields intact so the record remains enforceable and consistent.

A structured form reduces missing fields, inconsistent wording, and unclear consent language that often happen with ad-hoc paper intake. It also makes it easier to enforce required vs optional fields, capture a reliable signature, and preserve an audit trail. That matters when the record may need to be reviewed later by compliance, legal, or program staff.