Designing breach settlement opt-out and class member exclusion UI in Figma: deadlines, attestation, and administrator confirmation

Quick answer

Breach settlement opt-out UI lets class members exclude themselves before the deadline—preserving their right to sue independently while forfeiting settlement benefits. Design a deadline-driven opt-out wizard with plain-language consequences, legal attestation and identity verification, OPT- confirmation and printable receipt*, and an administrator opt-out registry that blocks future CLM-* filing attempts. Connect to settlement notice and claims, notice FAQ, eligibility portal, and regulatory archive. Start from the Figma guides hub and pair with forms, progress steppers, and Dev Mode handoff.

---

Who this is for

• Product designers building pre-claims exclusion flows—not generic account deletion or marketing unsubscribe.
• Settlement administrators and legal counsel who need auditable opt-out records before the court-approved deadline.
• Support and call center leads who must explain opt-out vs claim filing without giving legal advice.

---

Opt-out vs claim filing: entry routing

Users arriving from notice FAQ or settlement mail need a clear fork before they start either flow:

SettlementDecisionRouter — Settlement SET-992 · Notice SN-992-v1 · Choose your path
├── Header: You may be part of this settlement · Deadline: 2027-06-15
├── Option cards (mutually exclusive after deadline):
│   ├── [ File a claim ] → CLM-* wizard · Receive settlement benefits if approved
│   ├── [ Opt out of the settlement ] → OPT-* wizard · Keep right to sue · No settlement payment
│   └── [ Do nothing ] → Info panel only · May receive default remedy or nothing per court order
├── Comparison table (below cards):
│   ├── Opt out: Cannot file CLM-* later · Cannot appeal settlement terms as class member
│   ├── Claim: Bound by settlement if approved · Cannot sue separately for covered claims
│   └── Do nothing: Outcome defined in notice · Link to SN-992 full text PDF
├── Legal disclaimer: "This page does not provide legal advice" · Link attorney referral if offered
└── Already opted out? Lookup by OPT-* or email · Resend confirmation only (no undo)

Element	Purpose
Side-by-side comparison	Reduces accidental opt-outs from users who wanted cash payment
Do-nothing explainer	Court orders vary—some default members in unless they opt out
No undo after submit	Legal requirement—confirmation must state permanence
Shared SET- and SN- IDs**	Same namespace as claims UI

Verdict: Route before identity collection—users should understand consequences before submitting PII.

---

Opt-out wizard (victim-facing)

OptOutWizard — Settlement SET-992 · Step 2 of 4 · Confirm you understand the consequences
├── Progress: Identity → Consequences → Attestation → Confirmation
├── Consequences panel (plain language, legal-reviewed):
│   ├── You will NOT receive settlement payment or monitoring benefits
│   ├── You MAY pursue your own lawsuit against defendants (subject to statutes of limitation)
│   ├── You CANNOT file a claim (CLM-*) after opt-out is processed
│   └── You CANNOT participate in [appeals](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/) of this settlement
├── Identity verification:
│   ├── Pre-fill from [eligibility portal](/designing-breach-victim-eligibility-verification-portal-ui-in-figma/) if session exists
│   ├── Name, email, mailing address, last-four SSN or account ID per notice
│   └── [Email OTP](/designing-email-verification-and-otp-ui-in-figma/) or mailed PIN for high-risk settlements
├── Attestation checkboxes (all required):
│   ├── "I understand I am giving up settlement benefits"
│   ├── "I have read the opt-out instructions in notice SN-992-v1"
│   ├── "I am not acting on behalf of a deceased class member" (or separate flow)
│   └── Electronic signature · Full legal name · Date
├── Submit → Processing: OPT-992-44102 issued
└── Confirmation page: Download PDF · Print mailing label for postal opt-out parity

Design consequence copy as scannable bullets—not a wall of legal text. Link full notice PDF from regulatory archive.

---

Opt-out confirmation and lookup

OptOutConfirmation — OPT-992-44102 · Processed · Settlement SET-992
├── Status badge: Opt-out recorded · Effective date · Cannot be reversed
├── Receipt details: Name · Address hash · Submission timestamp · Notice version SN-992-v1
├── Download: Opt-out confirmation PDF · Court-filed exclusion list reference (when available)
├── What happens next:
│   ├── You will not receive claim filing reminders
│   ├── Your email removed from claims campaign segments only—not marketing unless separate consent
│   └── Contact administrator with OPT-* for status questions
├── Lookup form (return visits): OPT-* or email + OTP · Resend confirmation email
└── Blocked action banner if user tries CLM-* URL: "You opted out on 2027-03-12 · OPT-992-44102"

Share OPT- lookup* with call center scripts—agents must see the same blocked-claim state as the portal.

---

Administrator opt-out registry (internal)

OptOutRegistry — Settlement SET-992 · 4,821 OPT-* records · Deadline: 2027-06-15
├── Ingestion sources: Portal wizard · Postal mail scan · Call center assisted entry
├── Row: OPT-* · Name · Email · Address hash · Source · Processed date · SN-* version
├── Pre-deadline actions:
│   ├── Batch export to court · Exclusion list filing · Duplicate detection
│   ├── Merge duplicate OPT-* (same person, two submissions) · Audit comment required
│   └── Flag late submissions · Auto-reject after deadline with template response
├── Cross-check panel:
│   ├── If CLM-* exists for same identity → Conflict queue · Legal review
│   ├── If OPT-* after CLM-* approved → Rare · Escalate immediately
│   └── Sync exclusion flag to claims database before claim deadline closes
├── Metrics: Daily opt-out rate · Source breakdown · Duplicate rate · Late rejection count
└── Audit log: opt_id · action · operator_id · court_filing_ref · timestamp

Internal UI must block CLM- creation* at API level when OPT-* is active—not just hide the claim button.

---

Postal and assisted opt-out parity

Not all class members use the portal. Design variants for:

Channel	UI requirement
Printable mail-in form	Same fields as wizard · Barcode encoding OPT-* pre-print area · PDF from confirmation page
Call center assisted	Agent read-back script · Dual attestation · OPT-* issued while caller on line
Legal representative	Separate attestation for attorney filing on behalf of client · POA upload optional
Deceased class member	Do not allow simple opt-out wizard · Route to estate representative flow with legal gate

Use file upload patterns for mailed form batch ingestion in admin registry.

---

Comparison: opt-out vs adjacent surfaces

Surface	Focus	This UI adds
Settlement claims	Receive benefits	Explicit exclusion from class
Claims dispute / appeal	Post-denial recovery	Not available after OPT-*
Eligibility portal	Am I included?	Permanent exclusion action
Privacy settings	Data rights	Separate from legal class action rights
Notice FAQ	Public information	Actionable opt-out entry point

---

Handoff checklist (Dev Mode)

• SettlementDecisionRouter — settlement_id (SET-), notice_version (SN-), opt_out_deadline, claim_deadline, user_session_state.
• OptOutWizard — opt_id (OPT-*), settlement_id, step_index, identity_fields[], attestation_ids[], signature_text, submitted_at.
• OptOutConfirmation — opt_id, status_enum, effective_date, confirmation_pdf_url, court_filing_ref, blocked_claim_reason.
• OptOutLookup — lookup_key (OPT-* or email), otp_verified, resend_allowed.
• OptOutRegistry — settlement_id, opt_id, source_enum, duplicate_of_opt_id, conflict_clm_id, court_export_batch_id.
• ClaimBlockBanner — opt_id, opt_date, redirect_url, support_contact_ref.

---

Common mistakes

Mistake	Why it hurts	Fix
Hide opt-out behind account login only	Excludes class members without accounts	Guest opt-out with identity verification
Allow opt-out after claim approved	Legal invalidation of settlement	Hard block once CLM-* reaches Approved
Confuse with marketing unsubscribe	Users think they opted out of settlement	Separate copy and confirmation IDs
No deadline countdown	Missed exclusion window	Prominent countdown on router and wizard
Soft-block claim filing in UI only	Duplicate CLM-* via API	Server-side OPT-* gate
Missing postal parity	Disparate impact claims	Printable form matching wizard fields
Promise lawsuit outcomes	UPL risk	”May pursue” language only
Different OPT-* status on phone vs portal	Support chaos	Shared enum in call center UI

---

Recommended workflow

1. Legal delivers opt-out deadline, attestation text, and consequence language before wireframes.
2. Design decision router first—wizard and registry inherit SET-* and SN-* context.
3. Build OPT- confirmation and CLM- block** as paired components before launch.
4. Sync OPT- registry* with claims database exclusion flag before claim deadline.
5. Test call center assisted flow with agent scripts before notice mail date.
6. Archive OPT- batch exports* to compliance exports per court filing requirements.

---

FAQ

Can users opt out after filing a claim?

Only before claim is finalized—once CLM-* is submitted, legal may treat opt-out as withdrawn claim instead. Follow counsel’s state machine exactly.

What if someone opts out by mistake?

No self-service undo—direct to administrator contact. Some settlements allow narrow reversal windows before court filing; do not build unless legal specifies.

Should opt-out require the same proof as claims?

Often lighter—notice mailed to address may suffice. Match verification tier to court order, not claims fraud threshold.

How do opted-out users appear in reporting?

Excluded from CLM- and PAY- metrics** but counted in OPT-* registry exports. Separate dashboard tile for administrators.

Mobile opt-out support?

Mobile-first wizard—notice links open on phones. Large attestation checkboxes and progress stepper for multi-step clarity.

---

Next steps

• Design breach settlement notice and victim compensation claims UI in Figma — the path users skip when opting out
• Design breach FAQ and notice landing page UI in Figma — public entry to opt-out vs claim decision
• Design breach settlement claims dispute and appeals UI in Figma — unavailable after OPT-* confirmation
• Design breach call center and agent script UI in Figma — assisted opt-out and OPT-* lookup
• Design regulatory authority correspondence and breach filing archive UI in Figma — court-filed exclusion list storage