Breach Settlement Notice and Claims UI in Figma

Quick answer

Breach settlement notice and victim compensation claims UI gives affected individuals a clear, legally compliant path to file for court-approved remedies—cash payments, extended monitoring, or identity restoration—without confusing enrollment with remediation offers or eligibility verification. Design a settlement notice landing page synced to court-approved copy, claims filing wizard with attestation and proof upload, status tracker for submitted claims, and admin review queue for settlement administrators. Connect to notice FAQ, regulatory archive, individual notification, and privacy request queue. Start from the Figma guides hub and pair with forms, file upload, and Dev Mode handoff.

Who this is for

Product designers building court-supervised settlement portals—not generic marketing landing pages.
Legal and privacy teams coordinating with settlement administrators, claims processors, and comms on notice language.
Support and call center leads who need claim status lookup parity with agent scripts.

Settlement notice landing page

SettlementNoticePage — Settlement SET-992 · Incident VIN-992 · Notice version SN-992-v1 · Court approved
├── Header: Important notice about a data privacy settlement · Do not ignore
├── Plain-language summary:
│   ├── What happened (public-safe) · Who may be included · What you may receive
│   ├── Deadline: Submit claims by 2027-02-15 · Opt-out deadline 2026-11-15
│   └── This is not a bill · You will not be charged for filing
├── Your options (mutually exclusive where required):
│   ├── [ File a claim ] — Cash payment, extended monitoring, or both per settlement class
│   ├── [ Opt out ] — Preserve right to sue individually · Requires attestation
│   └── [ Object to settlement ] — Rare path · Link to court instructions PDF
├── Eligibility overview:
│   ├── Included: Users in IND-441 cohort between dates X–Y
│   ├── Excluded: Employees covered by separate program · Deceased estates process
│   └── Link [eligibility portal](/designing-breach-victim-eligibility-verification-portal-ui-in-figma/) for account-specific check
├── Documents: Long-form notice PDF · Claim form PDF · Court order excerpt
├── FAQ blocks: Reuse [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/) NL-* where aligned
└── Footer: Settlement administrator contact · No legal advice disclaimer · [Trust center](/designing-trust-center-and-security-documentation-ui-in-figma/)

Element	Purpose
Court-approved version stamp	SN-* version must match legal repository
Deadline prominence	Missing deadline is the top support driver
Option clarity	Claim vs opt-out vs object are legally distinct
No legal advice banner	Standard disclaimer on every page

Verdict: The notice page is immutable legal copy—design CMS or component locks so comms cannot edit settlement terms without legal workflow.

Claims filing wizard

ClaimsWizard — Settlement SET-992 · Step 2 of 5 · Confirm eligibility
├── Step 1: Read notice summary ✓ · Acknowledged SN-992-v1 · Timestamp recorded
├── Step 2: Confirm eligibility (current):
│   ├── Enter notice code OR sign in · Pre-fill from [eligibility session](/designing-breach-victim-eligibility-verification-portal-ui-in-figma/)
│   ├── Attestation checkbox: "I was a [product] user during the class period"
│   ├── Identity fields: Name, address, email · Last 4 of account ID · Not full SSN unless court requires
│   └── Ineligible result → Explain why · Link FAQ · No appeal in UI without admin queue
├── Step 3: Select remedy:
│   ├── Option A: Cash payment (estimated $X–$Y · actual amount after pro-rata)
│   ├── Option B: Extended monitoring (24 months) · Routes to [remediation vendor](/designing-breach-remediation-offers-and-credit-monitoring-enrollment-ui-in-figma/)
│   ├── Option C: Both (if settlement allows)
│   └── Option D: Identity restoration credit (lump sum for third-party services)
├── Step 4: Proof upload (if required for enhanced tier):
│   ├── Document types: Breach notice email, bank statement showing fraud, medical bills (category-specific)
│   ├── [File upload UI](/designing-file-upload-and-drag-drop-ui-in-figma/) · Max 5 files · PDF/JPG · Virus scan pending state
│   └── Optional: "I have no additional proof" for standard tier only
├── Step 5: Review and submit:
│   ├── Summary of selections · Electronic signature · Perjury attestation language (legal-provided)
│   ├── Claim ID CLM-992-88421 generated · Confirmation email · Printable receipt
│   └── Status: Submitted · Pending administrator review
└── Progress: [Stepper UI](/designing-progress-indicators-and-steppers-in-figma/) · Save and resume within 30 days

Design remedy selection with radio groups and plain-language benefit descriptions—court documents often use terms victims do not recognize.

Opt-out and objection flows

OptOutFlow — Settlement SET-992 · Preserve individual lawsuit rights
├── Entry: Separate path from claims · Prominent on notice page
├── Required fields: Name, address, account identifier, signature
├── Attestation: "I exclude myself from the settlement class"
├── Confirmation: Opt-out ID OPT-992-1204 · Mail confirmation option for users without email
├── Deadline enforcement: Hard stop after 2026-11-15 · Friendly error + court contact
└── No retroactive opt-out in UI after deadline — direct to administrator phone

ObjectionFlow — Settlement SET-992 · Challenge fairness of settlement
├── Link to court filing instructions · Do not build full objection form unless legal requires
├── Capture interest registration only: Name, email, "I intend to object"
└── Route to [regulatory archive](/designing-regulatory-authority-correspondence-and-breach-filing-archive-ui-in-figma/) document repository

Verdict: Opt-out UI needs equal visual weight to claim filing— burying opt-out links creates class-action approval risk.

Claims status tracker

ClaimStatusTracker — CLM-992-88421 · Submitted 2026-08-22 · Status: Under review
├── Status stepper: Submitted → Under review → Approved / Denied → Payment issued
├── Current detail:
│   ├── "We are verifying your eligibility with settlement records"
│   ├── Expected update: Within 60 days of claim deadline
│   └── No payment amount until pro-rata calculation complete
├── User actions:
│   ├── Upload additional proof (if requested) · Request deadline shown
│   ├── Update mailing address for check · [Address book UI](/designing-saved-addresses-and-address-book-ui-in-figma/)
│   └── Contact administrator · Pre-fill CLM-* reference
├── Denied state:
│   ├── Reason code (plain language) · Appeal instructions PDF
│   └── Link [privacy queue](/designing-privacy-request-queue-and-case-management-ui-in-figma/) for data disputes
├── Approved + paid:
│   ├── Payment method: Check mailed · ACH · PayPal (per settlement)
│   ├── Issued date · Reference number · Tax reporting note if applicable
│   └── Monitoring remedy: Handoff link to [enrollment hub](/designing-breach-remediation-offers-and-credit-monitoring-enrollment-ui-in-figma/)
└── Call center parity: Agent lookup by CLM-* shows same status enum

Status	Show victim	Hide
Under review	Generic processing message	Other claimants’ data, pro-rata math
Approved	Expected payment window	Final dollar until issued
Denied	Reason category, appeal path	Internal reviewer notes

Administrator review queue (internal)

ClaimsAdminQueue — Settlement SET-992 · 1,247 submitted · 892 pending review
├── Filters: Status · Remedy type · Proof required · Fraud flag · Cohort
├── Claim row: CLM-* · Name (masked) · Submitted date · Remedy · Risk score
├── Review panel:
│   ├── Eligibility match: IND-441 cohort ✓ · Duplicate CLM-* check
│   ├── Proof documents · Zoom viewer · Approve / Request more / Deny
│   ├── Deny reason codes (legal-approved list) · Required comment for audit
│   └── Bulk export for payment processor · [Compliance exports](/designing-compliance-exports-and-legal-hold-ui-in-figma/)
├── Fraud signals: Multiple claims same address · Velocity · Known bad proof hashes
└── Audit log: reviewer_id · action · timestamp · claim_version

Internal UI is a variant set of victim-facing components—same CLM-* IDs, different field visibility.

Comparison: settlement claims vs adjacent surfaces

Surface	Focus	This UI adds
Remediation offers	Free services from company	Court-supervised cash and optional remedies
Eligibility portal	Affected / not affected	Legal claim filing and opt-out
Notice FAQ	Public Q&A	Binding notice and deadline enforcement
Regulatory archive	Authority filings	Court-approved notice versions (SN-*)
Identity restoration	Active fraud response	Settlement-funded restoration credits

Handoff checklist (Dev Mode)

SettlementNotice — settlement_id (SET-), incident_id (VIN-), notice_version (SN-*), court_approval_date, claim_deadline, optout_deadline, locale.
ClaimsWizard — step_index, session_id, notice_acknowledged_at, attestation_text_id, save_resume_token.
ClaimSubmission — claim_id (CLM-*), settlement_id, remedy_enum[], proof_document_ids[], signature_timestamp, ip_audit_ref.
OptOutSubmission — optout_id (OPT-*), settlement_id, attestation_text_id, confirmation_delivery_method.
ClaimStatus — claim_id, status_enum, status_history[], payment_ref, denial_reason_code, appeal_doc_url.
AdminReview — claim_id, reviewer_id, action_enum, comment, fraud_flags[], export_batch_id.
RemedyHandoff — claim_id, monitoring_offer_id (MON-*), enrollment_prefill_token.
LegalCopyBlocks — SN-* version, attestation_paragraph_ids[], perjury_language_id.

Common mistakes

Mistake	Why it hurts	Fix
Combine remediation enrollment with settlement claim	Users think they filed for cash when they only got monitoring	Separate SET-* and REM-* flows with cross-links
Editable settlement terms in CMS	Legal non-compliance	Lock SN-* blocks; version bump workflow only
Hide opt-out below fold	Class certification challenge	Equal prominence with claim CTA
Show estimated payment as guaranteed	Fraud expectations	”Estimated range · final after pro-rata”
Full SSN on standard tier	Unnecessary PII collection	Last 4 + notice code unless court order requires
No save-and-resume on long wizard	Abandonment before deadline	30-day session token
Different claim status in portal vs phone	Support chaos	Shared CLM-* enum in call center UI
Missing proof upload virus-scan state	Users submit twice	Pending → Accepted → Rejected states

Recommended workflow

Legal delivers SN- copy blocks* before any visual design—wizard steps map to court form sections.
Reuse eligibility session from verification portal to reduce duplicate identity collection.
Design opt-out and claim as parallel entry points from notice page—not nested menus.
Build admin queue as internal variant of claim detail components.
Sync CLM- lookup* with call center scripts before notice mail date.
Archive submitted claim metadata (redacted) to compliance exports per settlement administrator requirements.

FAQ

Can someone file both a settlement claim and opt out?

No—these are mutually exclusive. UI must block opt-out if CLM-* already submitted and vice versa, with clear error copy.

What if the user already enrolled in free monitoring?

Settlement extended monitoring remedy may stack or replace—state explicitly in Step 3 with legal-approved language; link existing ENR-* status.

How do we handle deceased class members?

Design separate estate representative flow or administrator-only process—do not force standard wizard without legal spec.

Are claim amounts shown before approval?

Show ranges only if court notice allows—never display final pro-rata amount until payment issued.

Mobile filing support?

Mobile-first wizard—many users open settlement emails on phones. Use progress steppers and single-column proof upload.

Next steps

Design breach FAQ and notice landing page UI in Figma — public FAQ aligned with settlement notice
Design breach victim eligibility verification portal UI in Figma — pre-fill claims with verified cohort
Design breach remediation offers and credit monitoring enrollment UI in Figma — monitoring remedy handoff after claim approval
Design breach identity restoration and fraud alert UI in Figma — restoration credits from settlement
Design regulatory authority correspondence and breach filing archive UI in Figma — court notice version repository

Designing breach settlement notice and victim compensation claims UI in Figma: class notices, proof upload, and claims admin