Settlement Deficiency Notice & Cure UI

Quick answer

Deficiency notice UI tells claimants exactly what is wrong with a settlement claim and gives them a fair window to fix it—before automatic denial. Design DEF- deficiency records* tied to CLM-* claims, CURE- cure periods* with visible deadlines, and claimant-facing fix flows that map each deficiency code to a specific form field or document upload. Admins see deficiency queues with reason codes, cure countdowns, and bulk reminder actions; claimants see plain-language “action required” banners—not legal jargon alone. Connect to settlement claims, document upload, amendments, status portal, and disputes. Start from the Figma guides hub and pair with forms, alerts, and Dev Mode handoff.

Who this is for

Product designers building settlement claim review consoles and claimant portals where incomplete claims need correction—not instant rejection.
Claims administrators who issue deficiency notices under court-approved plans with fixed cure periods.
Class counsel who need audit-ready DEF-* trails showing what was missing, when the claimant was notified, and whether cure was met.

Deficiency lifecycle overview

DeficiencyFlow — DEF-992-0041 · CLM-992-44102 · Status: Cure active (12 days left)
├── Triggers (reviewer or rules engine):
│   ├── Missing required field (SSN last4 · signature · attestation)
│   ├── [Document upload](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/) incomplete or illegible
│   ├── Eligibility proof insufficient vs [eligibility portal](/designing-breach-victim-eligibility-verification-portal-ui-in-figma/) bar
│   ├── Payee/bank data invalid before [disbursement](/designing-breach-settlement-payment-disbursement-and-payout-tracking-ui-in-figma/)
│   ├── [Minor/guardian](/designing-breach-settlement-minor-claimant-and-guardian-designation-ui-in-figma/) docs missing
│   └── Duplicate field mismatch vs [fraud rules](/designing-breach-settlement-duplicate-claim-detection-and-fraud-prevention-ui-in-figma/) (soft deficiency, not FRD-*)
├── ID namespace:
│   ├── DEF-* (deficiency notice) · CURE-* (cure period instance)
│   ├── CLM-* (claim) · DOC-* (requested evidence)
│   └── AUD-* (notice sent · cure opened · cured · expired)
├── Outcomes:
│   ├── Cured → Claim returns to approval queue
│   ├── Expired → Denied with appeal path to [disputes](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/)
│   ├── Withdrawn → Claimant abandons
│   └── Escalated → Manual review after partial cure
└── Claimant messaging: What is missing + deadline + one CTA to fix

Deficiency type	Admin sees	Claimant sees	Fix surface
Missing signature	def_code: SIG_MISSING	”Sign your claim to continue”	E-sign step
Illegible ID scan	def_code: DOC_UNREADABLE	”Upload a clearer photo”	File upload
Wrong eligibility proof	def_code: ELIG_INSUFFICIENT	”Show you were affected between [dates]“	Proof upload + attestation
Invalid bank routing	def_code: PAY_INVALID	”Fix payment details”	Payment methods
Incomplete guardian packet	def_code: GUARDIAN_DOCS	”Guardian paperwork required”	Guardian forms

Verdict: Every DEF- must list specific fix actions—not a generic “your claim is incomplete” dead end.*

DEF-* record structure and admin queue

DeficiencyRecord — DEF-992-0041 · clm_id: CLM-992-44102 · cure_id: CURE-992-0041
├── Core fields:
│   ├── def_id (DEF-*) · clm_id · reviewer_id
│   ├── deficiency_codes[] (enum · multiple allowed)
│   ├── deficiency_notes_internal (counsel-only)
│   ├── deficiency_message_claimant (plain language template)
│   ├── cure_deadline_at · cure_days_granted (from plan)
│   └── status: draft · sent · cure_active · cured · expired · withdrawn
├── Admin queue columns:
│   ├── DEF-* · CLM-* · Claimant · Codes · Cure days left · Channel sent
│   ├── Resubmission count · Partial cure flag
│   └── Assigned reviewer · Escalation tier
├── Bulk actions:
│   ├── Send reminder (email/SMS/mail) · Extend cure (supervisor)
│   ├── Batch expire on deadline · Export for counsel
│   └── Convert to [dispute](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/) if contested
└── Filters: def_code · cure_status · amount band · foreign · minor

Use tables for the ops queue and a detail panel showing DEF-* ↔ CLM-* field-level mapping—reviewers should see which form fields triggered each code.

Claimant cure flow (portal)

CureWizard — CLM-992-44102 · DEF-992-0041 · Step 1 of 2
├── Entry points:
│   ├── Email/SMS: "Action required by [date]"
│   ├── [Status portal](/designing-breach-settlement-claim-status-portal-and-claimant-dashboard-ui-in-figma/) banner with countdown
│   └── [Call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) sends signed ACT-* link
├── Step 1 — Understand deficiencies:
│   ├── Checklist of items (not paragraph of legalese)
│   ├── Each item: icon · plain title · "Fix this" anchor
│   ├── Cure deadline prominent · timezone-aware
│   └── Link to [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/) for definitions
├── Step 2 — Fix each item inline:
│   ├── Field-level errors tied to def_code
│   ├── [Document re-upload](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/) with quality hints
│   ├── [Amendment](/designing-breach-settlement-claim-amendment-and-correction-ui-in-figma/) preview before submit
│   └── Block submit until all DEF codes addressed
└── Post-submit:
    ├── Status → "Under review" · Cure clock paused or reset per plan
    ├── Confirmation email with DEF-* reference
    └── No duplicate CLM-* creation

Prototype mobile-first cure flows—many claimants fix deficiencies on phones. Use progress steppers when multiple deficiency items exist.

CURE-* deadline, reminders, and expiration

CurePeriod — CURE-992-0041 · def_id: DEF-992-0041 · Deadline: 2026-09-15
├── Reminder schedule (configurable):
│   ├── T-14 days: first email + portal banner
│   ├── T-7 days: SMS optional (consent-gated)
│   ├── T-3 days: urgent banner + [toast](/designing-toasts-and-snackbars-in-figma/) on login
│   └── T-0: auto-expire or grace window per plan
├── Extension rules:
│   ├── Supervisor EXT-* with reason · max one extension common
│   ├── [Call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) cannot extend without role
│   └── AUD-* logs every extension
├── Expiration UX:
│   ├── Claimant: "Cure period ended" + appeal CTA if plan allows
│   ├── Admin: CLM-* → denied_deficiency_expired
│   └── Counsel report: DEF-* cured vs expired rates
└── Partial cure:
    ├── Some codes fixed · others open → split DEF-* or sub-status
    └── Reviewer re-notifies for remaining codes only

Design countdown components that match flash sale timers patterns but use calm urgency—not ecommerce pressure language.

Comparison: deficiency UI vs adjacent settlement surfaces

Surface	Focus	This UI adds
Settlement claims	Initial filing	Fix incomplete submissions
Amendments	Voluntary corrections	Admin-required fixes with deadline
Disputes	Contest denial	Pre-denial cure window
Document upload	Evidence storage	Targeted re-upload requests
Status portal	Progress view	Action-required deficiency banners

Handoff checklist (Dev Mode)

DeficiencyRecord — def_id (DEF-*), clm_id, deficiency_codes[], cure_deadline_at, status_enum, claimant_message_key.
CurePeriod — cure_id (CURE-*), def_id, started_at, deadline_at, extension_count, status_enum.
DeficiencyBanner — clm_id, def_id, days_remaining, cta_href, dismissible (false).
CureWizard — def_codes[], field_fix_map{}, step_index, submit_blocked_until_complete.
AdminDeficiencyQueue — sortable columns[], reminder_action_enums[], partial_cure_indicator.

Common mistakes

Mistake	Why it hurts	Fix
Generic “incomplete claim” message	Support flood · abandonment	Per-code plain language + fix CTA
No visible cure deadline	Due process risk	Countdown on portal and emails
Legalese-only notice PDF	Claimants ignore	Portal checklist mirrors PDF
Multiple DEF-* without merge	Conflicting instructions	Consolidate open deficiencies
Cure expires without reminder series	Unfair denial	T-14/T-7/T-3 reminder schedule
Allow fixes after expire without appeal	Dead end	Link to disputes
Deficiency for FRD-* fraud	Wrong workflow	Route fraud to FRD-* hold
Re-upload without quality guidance	Repeat DEF-* loop	Show photo tips on DOC_* codes
Admin edits claimant data silently	Audit gap	Claimant confirms via cure submit
No AUD-* on notice send	Counsel discovery gap	Log channel + timestamp

Recommended workflow

Catalog deficiency codes from the settlement plan (signature, eligibility, payment, guardian, etc.).
Design admin DEF- queue* with cure countdown and bulk reminder actions.
Prototype claimant cure wizard mapping each code to a specific fix surface.
Connect status portal banners to active CURE-* with signed deep links.
Define reminder schedule and extension rules with counsel and operations.
Export cured vs expired metrics for final accounting and plan compliance reports.

FAQ

Multiple deficiencies on one claim?

Single DEF- with codes[] array* · Cure wizard checklist · One deadline unless plan splits by category.

Claimant cures after deadline but before admin processes expire?

Grace buffer common (24–72h) · Status cured_late for reviewer discretion · Do not auto-deny on clock alone without batch job.

Minor/guardian deficiency notices?

Send to guardian contact only · Never expose minor PII in email subject · Guardian cure wizard variant.

Deficiency vs identity re-verification?

DEF- = missing claim data* · IDV- = prove identity* · Do not mix queues · IDV may follow cured claim if risk fires.

Partial document cure?

Mark individual DOC- satisfied* · Keep DEF-* open for remaining codes · Show progress (2 of 3 fixed).

Next steps

Design breach settlement notice and victim compensation claims UI in Figma — Initial CLM-* filing
Design breach settlement claim document upload and evidence management UI in Figma — Targeted re-uploads
Design breach settlement claims dispute and appeals UI in Figma — Post-expiration appeals
Design breach settlement claim status portal and claimant dashboard UI in Figma — Action-required banners
Design inline alerts and banners in Figma — Cure countdown messaging

Designing breach settlement deficiency notice and claim cure UI in Figma: DEF-* notices, CURE-* deadlines, and resubmission flows