Breach Settlement Cy Pres UI in Figma

Quick answer

Breach settlement residual fund UI handles money left after claims, disbursements, and escheatment—often routed to cy pres beneficiaries under court supervision. Design a residual balance dashboard tied to SET-* escrow, a beneficiary proposal and scoring workflow for counsel and administrators, and public comment or objection windows before court approval. Connect to final accounting, unclaimed funds, settlement notice, 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 cy pres and residual allocation flows—not generic nonprofit donation checkout.
Settlement administrators and class counsel preparing beneficiary proposals for court review.
Communications teams publishing objection-period notices on notice FAQ pages.

Residual fund lifecycle overview

ResidualFundLifecycle — SET-992 · Residual balance: $892,114 · Status: Proposal draft
├── Sources of residual (sum to RES-* total):
│   ├── Unclaimed after [disbursement](/designing-breach-settlement-payment-disbursement-and-payout-tracking-ui-in-figma/) and [escheatment](/designing-breach-settlement-unclaimed-funds-and-escheatment-ui-in-figma/)
│   ├── Denied claims pool return (per court order)
│   ├── Rounding and minimum-payment thresholds
│   ├── Monitoring remedy unused credits
│   └── Escrow interest (if not allocated to class)
├── ID namespace:
│   ├── RES-* (residual pool) · BEN-* (beneficiary org) · CYP-* (cy pres proposal)
│   └── PAY-RES-* (beneficiary disbursement) separate from class PAY-*
├── Status progression:
│   ├── Accruing → Proposal draft → Public comment → Court review → Approved → Disbursed → Closed
│   └── Feeds [final accounting FIN-*](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/) residual line
└── Not the same as state escheat—RES-* stays in settlement until court directs

Stage	Administrator sees	Public / class sees
Accruing	Running residual total	Not published
Proposal draft	BEN-* shortlist and allocation %	—
Public comment	Submitted comments queue	Comment form on notice site
Court review	CYP-* filing package	Read-only proposal summary
Approved	RES batch disbursement	Press / FAQ update
Closed	Zero RES balance	Link in closure notice

Verdict: RES- balance is live until court approval*—show accrual updates in admin UI but hide specific beneficiary names until proposal is filed.

Residual balance dashboard (administrator)

ResidualDashboard — SET-992 · RES-992 · Balance: $892,114 · Last updated: 2028-01-02
├── Accrual breakdown (chart + table):
│   ├── Unclaimed class payments: $612,400
│   ├── Post-escheat remainder (returned to fund): $0
│   ├── Denied-claim pool: $198,200
│   ├── Rounding residue: $41,514
│   ├── Unused monitoring credits: $40,000
│   └── Escrow interest: $0
├── Projection vs court cap:
│   ├── Court max cy pres: 100% of residual · Min to class re-distribution: 0%
│   └── Alert if accrual exceeds expected model from claims actuary
├── Links:
│   ├── Drill to CLM-* / PAY-* / UCF-* rows contributing to each bucket
│   ├── [ Start cy pres proposal ] when wind-down gate met
│   └── Block if open material VAR-* from [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
└── Export: Residual accrual CSV for counsel · Date-stamped snapshot RES-992-SNAP-04

Use badges for accrual source types—finance filters by bucket quickly.

Cy pres beneficiary proposal workflow

CyPresProposal — CYP-992-v1 · RES-992 · $892,114 · Status: Draft · 3 beneficiaries
├── Step 1 — Eligibility criteria (court order driven):
│   ├── Geographic nexus: US · CA weighted
│   ├── Mission alignment: Consumer privacy · Identity theft prevention
│   ├── Cannot be: Defendant, counsel, or administrator affiliated
│   └── 501(c)(3) verification · W-9 on file
├── Step 2 — Beneficiary shortlist (BEN-* records):
│   ├── BEN-992-01 · Privacy Rights Clearinghouse · Score: 92 · Proposed: 60%
│   ├── BEN-992-02 · Local legal aid (CA) · Score: 88 · Proposed: 30%
│   └── BEN-992-03 · Cybersecurity education nonprofit · Score: 85 · Proposed: 10%
├── Scoring matrix (transparent in UI):
│   ├── Nexus to class harm · Track record · Overhead ratio · Duplication with other settlements
│   └── Counsel notes per row · Required for export
├── Step 3 — Allocation validation:
│   ├── Percentages sum to 100% · Dollar amounts sum to RES balance ± $0.01
│   ├── Minimum disbursement per BEN-* (avoid $50 checks to nonprofits)
│   └── Alternative: Single beneficiary with court justification field
├── Step 4 — Filing package preview:
│   ├── Proposal narrative PDF · Beneficiary org charts · Letters of intent
│   └── Link to [regulatory archive](/designing-regulatory-authority-correspondence-and-breach-filing-archive-ui-in-figma/) on submit
└── Versioning: CYP-992-v2 if court returns for revision—never overwrite v1

Design scoring as visible columns, not hidden backend logic—counsel must explain choices in court.

Public comment and objection period UI

Many courts require notice before cy pres approval:

PublicCommentPortal — SET-992 · CYP-992-v1 · Comment period ends 2028-02-15
├── Read-only proposal summary:
│   ├── Total residual: $892,114 · Beneficiary names and proposed splits
│   ├── Rationale excerpt from CYP-* narrative (plain language)
│   └── Full PDF download · Case number · Court hearing date if scheduled
├── Comment form:
│   ├── Name · Email · Relationship to settlement (class member / org / public)
│   ├── Comment type: Support · Objection · Alternative beneficiary suggestion
│   ├── Text area · Optional attachment (PDF only · size cap)
│   └── [Email verification](/designing-email-verification-and-otp-ui-in-figma/) for class members
├── Admin moderation queue:
│   ├── COM-* IDs · Flag duplicates · Redact PII before court exhibit export
│   ├── Response not required in UI—counsel handles offline
│   └── Export bundle for court: All comments + summary stats
└── FAQ link from [notice landing page](/designing-breach-faq-and-notice-landing-page-ui-in-figma/)

Element	Purpose
Fixed comment deadline	Countdown banner—same pattern as opt-out deadline
No voting UI	Court decides—not popularity contest unless order requires
Separate from CLM- portal*	Avoids confusing claim status with cy pres comments

Beneficiary disbursement (post-approval)

BeneficiaryDisbursement — RES batch RES-PAY-992 · 3 BEN-* · Total: $892,114 · Approved 2028-03-20
├── Per beneficiary row:
│   ├── BEN-992-01 · $535,268 · ACH to verified account · W-9 confirmed
│   ├── Status: Pending → Sent → Confirmed · PAY-RES-* ID
│   └── Receipt: Thank-you letter template · Public recognition opt-in
├── Finance controls:
│   ├── Dual approval over threshold · Same as class [disbursement](/designing-breach-settlement-payment-disbursement-and-payout-tracking-ui-in-figma/)
│   ├── Wire vs ACH per org preference · No check to invalid address
│   └── 1099 reporting flag for tax team
├── Closure tie-out:
│   ├── RES balance → $0 · Update [FIN-* report](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
│   └── Publish beneficiary thank-you on [trust center](/designing-trust-center-and-security-documentation-ui-in-figma/) if brand allows
└── Audit: cyp_proposal_id · ben_id · pay_res_id · court_order_ref · confirmed_at

PAY-RES- namespace* separates nonprofit payouts from class member PAY-*—critical for reporting and support lookup.

Comparison: residual fund vs adjacent surfaces

Surface	Focus	This UI adds
Unclaimed funds	Individual dormant PAY-*	Aggregate remainder after escheat cycle
Final accounting	Ledger closure	RES-* line and CYP-* appendix
Opt-out	Class member exclusion	Unrelated—do not merge flows
Notice FAQ	General settlement info	Cy pres comment period banner
Vendor risk	Security reviews	Optional BEN-* diligence checklist

Handoff checklist (Dev Mode)

ResidualDashboard — settlement_id (SET-), res_pool_id (RES-), balance, accrual_buckets[]{source_code, amount}, last_snapshot_id, projection_alert_bool.
CyPresProposal — cyp_proposal_id (CYP-*), version, res_pool_id, total_amount, beneficiaries[]{ben_id, name, proposed_pct, proposed_amount, score, counsel_note}, validation_errors[].
BeneficiaryRecord — ben_id (BEN-*), org_name, ein, w9_status, nexus_score, affiliation_flags[], payment_method_ref.
PublicCommentPortal — settlement_id, cyp_proposal_id, comment_deadline, comment_form_fields, com_id (COM-*) on submit.
BeneficiaryDisbursement — res_pay_batch_id, cyp_proposal_id, rows[]{ben_id, pay_res_id, amount, status_enum}, court_order_ref, fin_report_line_ref.

Common mistakes

Mistake	Why it hurts	Fix
Treat residual as escheat	Wrong legal path	RES-* separate from ESC-*
Hide beneficiary names until too late	Comment period useless	Publish summary at comment open
Class PAY-* workflow for nonprofits	Wrong tax and approval rules	PAY-RES-* with W-9 gate
No public comment when court requires	Filing rejected	Comment portal tied to CYP-* version
Editable CYP-* after court filing	Integrity failure	Versioned proposals
Single beneficiary without narrative	Court denial	Required justification field
Residual accrual stale in FIN-*	Balance mismatch	Live RES-* link until closure
Merge cy pres FAQ with claim FAQ	User confusion	Separate anchor on notice page

Recommended workflow

Legal defines cy pres criteria and comment requirements from settlement order before design.
Build residual dashboard accrual buckets linked to existing CLM-* / PAY-* / UCF-* data.
Design CYP- proposal wizard* with scoring matrix and allocation validation.
Add public comment portal on notice site—sync deadline with progress indicators.
Implement PAY-RES- disbursement* with finance dual approval before FIN-* sign-off.
Archive CYP- and court order* to regulatory archive.

FAQ

Can residual go back to class members?

Only if court order allows re-distribution—UI needs alternate CYP-* template “Return to class pro rata” with CLM-* eligibility rules.

What if no comments are submitted?

Still show empty comment period with “Period closed · No comments received” in admin export—proves notice was offered.

How is residual different from unclaimed funds?

Unclaimed funds are individual PAY- failures* tracked as UCF-*; residual is the aggregate pool after all individual resolution attempts and escheat cycles complete.

Do beneficiaries get portal access?

Optional BEN- login for W-9 upload and payment status*—separate auth from class member accounts.

Mobile public comment?

Mobile-friendly comment form on notice site—most class members read FAQ on phones; proposal PDF is desktop download.

Next steps

Design breach settlement final accounting and court closure UI in Figma — FIN-* includes RES-* disposition line
Design breach settlement unclaimed funds and escheatment UI in Figma — individual dormancy before aggregate residual
Design breach FAQ and notice landing page UI in Figma — cy pres comment period banner
Design regulatory authority correspondence and breach filing archive UI in Figma — CYP-* court filings
Design trust center and security documentation UI in Figma — optional public beneficiary recognition

Designing breach settlement residual fund and cy pres allocation UI in Figma: leftover balances, beneficiary selection, and court approval workflows