Settlement Plan of Allocation UI

Quick answer

Plan of allocation UI is the authoritative bridge between court-approved settlement text and every FIN-AWD- in software—not a PDF stored in a shared drive.* Design POA- versioned plan records*, AWD-CHART- award matrices* (tier rows × proof columns × subclass columns), and CLM-POA- mapping rules* that drive claims intake, subclass assignment, deficiency cure, and counsel payout approval. Every POA-* change requires LOG-POA-* audit, APP-POA- counsel lock*, and downstream invalidation of stale ALLOC-PR-* previews. Without this UI, intake questions drift from the fairness order, tier fights flood disputes, and shortfall reductions lack a defensible baseline. Start from the Figma guides hub and pair with fairness hearing, settlement notice, document upload, and court monitor reporting.

Who this is for

Product designers configuring settlement plans as structured data instead of static legal PDFs.
Claims administrators translating POA-* tiers into intake forms and auto-tier suggestions.
Class counsel publishing POA-* versions that match the operative settlement agreement.

Plan of allocation lifecycle overview

AllocationPlan — POA-992 · version 4.0 · Status: Locked for production
├── Artifacts:
│   ├── Court order PDF · exhibit cross-refs EXH-POA-*
│   ├── Plain-language summary for [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/)
│   ├── AWD-CHART-* matrix · SUB-* columns · proof requirements
│   ├── Caps: MAX-CLM-* · MIN-TIER-* · stacking rules
│   └── Effective dates · supersedes POA-991
├── ID namespace:
│   ├── POA-* (plan version root)
│   ├── TIER-* (award tier row)
│   ├── AWD-CHART-* (matrix id)
│   ├── RULE-POA-* (eligibility rule expression)
│   ├── CLM-POA-* (computed tier on claim)
│   ├── LOG-POA-* · APP-POA-* (change control)
│   └── DIFF-POA-* (amendment delta vs prior)
├── Mapping pipeline:
│   ├── Intake answers → RULE-POA-* evaluation
│   ├── [Documents](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/) → proof tier upgrade/downgrade
│   ├── [Subclass](/designing-breach-settlement-subclass-allocation-and-pro-rata-distribution-ui-in-figma/) → column filter on AWD-CHART-*
│   ├── Admin override · dual approval · reason code
│   └── Output: EST-AWD-* → FIN-AWD-* after approval
├── Governance:
│   ├── Draft POA-* in sandbox · no production CLM-* writes
│   ├── Counsel APP-POA-* · publish · bump LOG-POA-*
│   ├── Invalidate stale simulations · [ALLOC-PR-*](/designing-breach-settlement-subclass-allocation-and-pro-rata-distribution-ui-in-figma/)
│   └── Notify ops if [supplemental notice](/designing-breach-settlement-supplemental-notice-and-renotice-campaign-ui-in-figma/) required
└── Outcomes:
    ├── Single source of truth for tier math
    ├── Traceable CLM-POA-* for audits
    └── Fairness objections cite POA version not spreadsheet

POA-* state	Intake	Existing CLM-*
Draft	Hidden	Unaffected
Published	Uses new rules	Grandfather flag optional
Locked	Read-only config	Amend via correction UI only
Superseded	Redirect to new POA-*	Migration job POA-MIG-*

Verdict: POA- must not be editable by claims processors without LOG-POA-— tier changes are legal events, not support tickets.**

AWD-CHART-* matrix editor UI

AwardChart — AWD-CHART-992-CORE · dimensions: 6 tiers × 4 proof levels × 3 SUB-*
├── Row types (TIER-*):
│   ├── Flat dollar · e.g. TIER-A $125
│   ├── Tiered escalation · TIER-B1/B2 by harm band
│   ├── Percent of loss · capped MAX-CLM-*
│   └── In-kind benefit · links [remediation offers](/designing-breach-remediation-offers-and-credit-monitoring-enrollment-ui-in-figma/)
├── Columns:
│   ├── SUB-* from class definition
│   ├── Proof level: self-cert · doc required · enhanced audit
│   └── State carve-out · optional column
├── Cell rules:
│   ├── Amount or formula reference FORM-POA-*
│   ├── Mutually exclusive tiers · priority order
│   ├── Stack forbidden unless RULE-POA-* allows
│   └── Display string for claimant portal (not internal codes)
├── Validation:
│   ├── No orphan TIER-* without FAQ definition
│   ├── Sum worst-case liability vs fund · flag DEF-FUND-* risk
│   ├── Cross-check [opt-out](/designing-breach-settlement-opt-out-and-class-member-exclusion-ui-in-figma/) excluded SUB-*
│   └── Export court exhibit · match PDF exhibit numbering
└── Handoff:
    ├── Dev: RULE-POA-* JSON schema · test vectors
    ├── QA: golden CLM-* fixtures per TIER-*
    └── Legal: sign-off checkbox on APP-POA-*

Use tables for matrix layout and badges for proof-level requirements on intake previews.

CLM-POA-* determination and override UI

ClaimTierDetermination — CLM-POA-4412 · POA-992 · TIER-B2 · Status: Proposed
├── Auto evaluation:
│   ├── Intake Q-A12 → SUB-B · harm band “moderate”
│   ├── Documents DOC-884 · proof level 2
│   ├── RULE-POA-* match · EST-AWD-* $340
│   └── Confidence: high · no manual step required
├── Manual review queue:
│   ├── Low confidence · conflicting answers
│   ├── [Fraud signals](/designing-breach-settlement-duplicate-claim-detection-and-fraud-prevention-ui-in-figma/) · tier downgrade path
│   ├── [Deficiency](/designing-breach-settlement-deficiency-notice-and-claim-cure-ui-in-figma/) · missing proof for claimed tier
│   └── Override · supervisor + counsel · LOG-POA-OVERRIDE-*
├── Claimant portal:
│   ├── Show tier name · amount · what proof satisfied
│   ├── “How we calculated this” · FAQ + POA summary link
│   ├── Dispute tier · [appeals](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/)
│   └── Not final until APP-DISB-* path completes
└── Downstream:
    ├── [Subclass allocation](/designing-breach-settlement-subclass-allocation-and-pro-rata-distribution-ui-in-figma/) uses TIER-* + SUB-*
    ├── [Contested reserve](/designing-breach-settlement-contested-claim-escrow-and-dispute-reserve-ui-in-figma/) on tier fights
    └── [Shortfall RED-PR-*](/designing-breach-settlement-fund-shortfall-and-pro-rata-reduction-ui-in-figma/) uses FIN-AWD-* baseline

Pair forms intake with deterministic copy from POA-* tooltips— avoid paraphrasing tiers in free text fields.

POA-* amendment and DIFF-POA-* UI

Change type	Typical trigger	UX requirement
Clarification	FAQ confusion	DIFF-POA-* highlights copy only
Tier amount	Court order amend	Grandfather or migrate CLM-*
New TIER-*	Supplemental notice	Renotice workflow
Rule logic fix	Bug · not legal change	LOG-POA-* + regression tests
Rollback	Wrong publish	Block disbursement until revert

Amendment wizard should force impact analysis: count CLM-* with changed EST-AWD-* before APP-POA-*.

Comparison: POA storage patterns

Pattern	Pros	Cons
Structured POA- in app*	Testable · portal sync	Upfront legal modeling
PDF-only	Fast launch	Tier drift · audit pain
Spreadsheet import	Counsel comfort	Version hell
Hybrid PDF + matrix	Best for court exhibits	Must keep EXH refs in sync

Recommended: hybrid with AWD-CHART- as system of record* and PDF as signed attachment.

Common mistakes

Intake questions not generated from RULE-POA-*— wrong tier defaults; support fixes do not scale.
Publishing POA- without invalidating ALLOC-PR- previews**— disbursement uses mixed tier baselines.
Internal TIER- codes on claimant portal*— drives call center volume.
Ignoring MAX-CLM- in chart editor*— fund model breaks before shortfall UI triggers.
Override without LOG-POA-OVERRIDE-*— external auditor findings.

Recommended workflow

Model POA- from settlement agreement* · build AWD-CHART-* with counsel · attach court PDF.
Generate intake + FAQ from POA-* · publish notice alignment check.
Lock POA- for production* · run golden CLM-* tests · train admin override paths.
On amendment · DIFF-POA-* · impact report · renotice if required · migrate CLM-POA-*.
Archive POA- versions in final accounting* with LOG-POA-* bundle.

FAQ

Can claimants see the full AWD-CHART-*?

Usually a summary table— full matrix is admin/counsel; portal shows applicable tier row only.

Multiple POA-* for subclasses?

One POA- root with SUB- filtered charts**— avoid duplicate conflicting TIER-* ids.

POA-* vs cy pres?

Cy pres is outbound allocation— POA-* defines claimant awards before residual routing.

Tier disputes during fairness hearing?

Freeze POA- publish* until order enters · use draft POA-* for simulation only.

Developer handoff for RULE-POA-*?

Export test vectors + schema— pair with Dev Mode checklist for rule engine UI states.

POA-* and tax 1099?

FIN-AWD- from CLM-POA-** is reporting basis— document in POA metadata.

Next steps

Design breach settlement notice and victim compensation claims UI in Figma — intake driven by POA-*
Design breach settlement subclass allocation and pro rata distribution UI in Figma — SUB-* × TIER-* intersection
Design breach settlement fund shortfall and pro rata reduction UI in Figma — when POA liability exceeds fund
Design breach settlement deficiency notice and claim cure UI in Figma — proof gaps vs AWD-CHART-*
Design breach settlement fairness hearing and class objection UI in Figma — POA approval context

Designing breach settlement plan of allocation and award chart UI in Figma: POA-* tiers, AWD-CHART-* matrices, and plan-to-claim mapping