Settlement Tier Objection UI

Quick answer

Tier objection UI is how claimants and administrators contest CLM-POA- outcomes without corrupting WAVE- batches.** Design OBJ-TIER- dispute records*, CHL-AWD- review workspaces* that compare intake answers, documents, and RULE-POA-* evaluation traces, and REDET-POA- re-determination runs* that output revised EST-AWD-* before counsel payout approval. Every open OBJ-TIER-* should place HOLD-DISB-* on the claim, optionally move funds into contested escrow, and write LOG-OBJ-* for court monitor reporting. Without this UI, tier fights collapse into generic appeals with no POA version context, shortfall RED-PR-* math uses stale FIN-AWD-*, and call center agents improvise explanations. Start from the Figma guides hub and pair with plan of allocation, document upload, deficiency cure, and status portal.

Who this is for

Product designers separating “I disagree with my tier” from fraud, identity, or eligibility appeals.
Claims administrators adjudicating OBJ-TIER-* with POA-* traceability instead of spreadsheet overrides.
Class counsel approving tier upgrades/downgrades that change fund liability before tranche release.

Tier objection lifecycle overview

TierObjection — OBJ-TIER-8841 · CLM-4412 · POA-992 · Status: CHL-AWD review
├── Entry points:
│   ├── Claimant portal · “Dispute tier” from [status portal](/designing-breach-settlement-claim-status-portal-and-claimant-dashboard-ui-in-figma/)
│   ├── Admin flag · confidence low on CLM-POA-*
│   ├── [Document upload](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/) triggers re-tier suggestion
│   ├── [Fraud hold](/designing-breach-settlement-duplicate-claim-detection-and-fraud-prevention-ui-in-figma/) cleared · tier re-open
│   └── Counsel-initiated · court order amend to POA-*
├── ID namespace:
│   ├── OBJ-TIER-* (objection case root)
│   ├── CHL-AWD-* (challenge review session)
│   ├── REDET-POA-* (re-determination job)
│   ├── HOLD-DISB-* · RESV-CONT-* (payment holds)
│   ├── LOG-OBJ-* · APP-TIER-* (audit + counsel lock)
│   └── NTF-TIER-* (determination letter to claimant)
├── Evidence bundle:
│   ├── Snapshot CLM-POA-* at filing time · POA version id
│   ├── RULE-POA-* evaluation JSON · inputs/outputs
│   ├── New docs · amended intake answers
│   ├── Admin notes · reason codes REASON-OBJ-*
│   └── Prior OBJ-TIER-* history · no duplicate open cases
├── Outcomes:
│   ├── Uphold · close OBJ-TIER-* · release HOLD-DISB-*
│   ├── Upgrade tier · new EST-AWD-* · may trigger DEF-FUND-*
│   ├── Downgrade tier · NTF-TIER-* · claimant confirm window
│   ├── Split issue · tier OK · route eligibility to appeals
│   └── Escalate · special master · freeze REDET-POA-*
└── Downstream:
    ├── [Subclass allocation](/designing-breach-settlement-subclass-allocation-and-pro-rata-distribution-ui-in-figma/) refresh
    ├── [Distribution schedule](/designing-breach-settlement-distribution-schedule-and-tranche-disbursement-planning-ui-in-figma/) re-simulate
    └── [Post-disbursement QA](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/) sample OBJ-TIER-* cohort

OBJ-TIER-* state	Disbursement	Claimant sees
Draft	Unchanged	Hidden
Open	HOLD-DISB-* active	“Tier under review”
Pending docs	Hold continues	Deficiency-style checklist
CHL-AWD- review*	Hold	Estimated timeline
Resolved uphold	Release hold	Original tier + explanation
Resolved change	New FIN-AWD-* path	Itemized before/after

Verdict: Never apply tier changes silently on open OBJ-TIER-— every REDET-POA- needs LOG-OBJ- and visible NTF-TIER-.**

Claimant dispute intake UI

DisputeTierForm — OBJ-TIER-8841 · step 2 of 4
├── Context panel (read-only):
│   ├── Current tier label · EST-AWD-* · POA summary link
│   ├── “What proof satisfied” · doc list DOC-*
│   ├── POA version · not legal advice disclaimer
│   └── Link [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/) tier definitions
├── Dispute reason (required):
│   ├── Wrong harm band · wrong SUB-*
│   ├── Missing credit for uploaded proof
│   ├── Plan misapplied · cite FAQ section
│   ├── Data entry error · admin path
│   └── Other · free text min length
├── New evidence:
│   ├── [File upload](/designing-file-upload-and-drag-drop-ui-in-figma/) · type tags
│   ├── Optional amended answers · diff vs original intake
│   └── Attestation checkbox · penalties for false claims
├── Expectations:
│   ├── SLA for review · business days not court days
│   ├── Hold on payment while open
│   └── Cannot file duplicate OBJ-TIER-* for same POA version
└── Submit:
    ├── Create OBJ-TIER-* · LOG-OBJ-CREATE-*
    ├── Email confirmation · case id
    └── Portal status → Open

Use forms with explicit error states when a claim already has open disputes on overlapping grounds.

CHL-AWD-* admin review workspace

ChallengeReview — CHL-AWD-220 · OBJ-TIER-8841 · assignee: Tier Specialist
├── Split view:
│   ├── Left: intake timeline · Q-A* answers · overrides LOG-POA-OVERRIDE-*
│   ├── Center: RULE-POA-* trace · which rule fired · failed branches
│   ├── Right: AWD-CHART-* cell highlight · TIER-* row · proof column
│   └── Bottom: document viewer · redaction for PII
├── Actions:
│   ├── Request additional docs · DEF-OBJ-* deficiency path
│   ├── Run REDET-POA-* simulation · compare EST-AWD PRE/POST
│   ├── Recommend uphold / upgrade / downgrade · reason code
│   ├── Escalate to counsel · lock edits
│   └── Merge duplicate OBJ-TIER-* · LOG-OBJ-MERGE-*
├── Counsel queue:
│   ├── APP-TIER-* required if award delta > threshold
│   ├── Fund impact widget · links DEF-FUND-* preview
│   └── Batch approve low-risk doc upgrades only
└── Handoff:
    ├── Dev: immutable OBJ-TIER-* event log
    ├── QA: fixtures per REASON-OBJ-* code
    └── Legal: export packet for [fairness hearing](/designing-breach-settlement-fairness-hearing-and-class-objection-ui-in-figma/) if systemic

Pair tables for side-by-side PRE/POST awards and badges for hold states on the claim header.

REDET-POA-* re-determination and fund impact

Scenario	REDET-POA-* behavior	Fund UX
Single claim upgrade	Re-run RULE-POA-* on new inputs	Flag if batch WAVE-* affected
Mass POA bug fix	Batch REDET-POA-* job	Block WAVE-* until complete
Court order tier change	POA-* bump + migrate CLM-*	Supplemental notice
Downgrade after fraud clear	NTF-TIER-* + confirm window	Reduce RESV-CONT-*
Split subclass column	SUB-* filter change on chart	Re-run subclass allocation

When aggregate liability increases, surface SIM-SHORT-* link to shortfall UI before counsel APP-TIER-* on large batches.

Comparison: tier dispute vs general appeal

Dimension	OBJ-TIER-*	General appeal
Scope	CLM-POA-* / AWD-CHART-*	Eligibility, exclusion, fraud
Evidence	POA rules + docs	Broader record
SLA	Shorter · payment blocked	May allow provisional pay
Counsel	APP-TIER-* on material delta	APP-APPEAL-*
Escrow	RESV-CONT-* tier slice	Full claim reserve

Recommended: route portal users through a decision tree so tier math disputes never land in the wrong queue.

Common mistakes

Letting processors edit TIER- without OBJ-TIER-**— breaks audit and duplicates amendment paths.
Re-running REDET-POA- against wrong POA version*— compare LOG-POA-* snapshot at OBJ-TIER-* open.
Releasing HOLD-DISB- before NTF-TIER- sends**— claimants see payment before explanation.
Ignoring DEF-FUND- when batch upgrades approve*— tranche over-commitment.
Showing internal RULE-POA- codes to claimants*— use plain-language tier summaries from POA-*.

Recommended workflow

Expose “Dispute tier” only after CLM-POA- published* · snapshot POA version on OBJ-TIER-* create.
Auto HOLD-DISB-* · optional RESV-CONT-* if payment was imminent.
Adjudicate in CHL-AWD-* · run REDET-POA-* · counsel APP-TIER-* when needed.
Send NTF-TIER-* · update status portal · release hold.
Report OBJ-TIER- volumes in final accounting* and court monitor dashboards.

FAQ

Is OBJ-TIER-* the same as claims dispute and appeals?

No— OBJ-TIER- is POA-scoped tier math.* Eligibility or exclusion fights stay in the appeals module with cross-links.

Can claimants object after payment?

Yes, but route to clawback workflows if FIN-AWD-* already sent; OBJ-TIER-* may still run for record.

Provisional pay during OBJ-TIER-*?

Usually block— if plan allows interim pay, tie to provisional payment UI with explicit tier disclaimer.

Systemic tier errors?

Open batch REDET-POA-* · freeze WAVE-* · coordinate supplemental notice.

Developer handoff?

Export OBJ-TIER- state machine + RULE-POA- trace viewer**— see Dev Mode checklist.

Tier objection during fairness hearing?

Freeze mass REDET-POA-* until order; allow individual OBJ-TIER-* only if plan permits pre-effective date.

Next steps

Design breach settlement plan of allocation and award chart UI in Figma — POA-* source for CLM-POA-*
Design breach settlement contested claim escrow and dispute reserve UI in Figma — holds during OBJ-TIER-*
Design breach settlement claims dispute and appeals UI in Figma — non-tier appeals
Design breach settlement counsel review and payout approval UI in Figma — APP-TIER-* gates
Design breach settlement fund shortfall and pro rata reduction UI in Figma — when upgrades widen DEF-FUND-*

Designing breach settlement tier objection and award challenge UI in Figma: OBJ-TIER-* disputes, CHL-AWD-* review, and POA-* re-determination