Designing breach settlement hold release notifications and claimant payment timeline UI in Figma: NOTIF-HOLD-*, ETA-PAY-*, and portal timeline sync

Quick answer

Hold release notification UI must mirror server-side GATE-PAY-* truth—not marketing “your payment is coming” blasts. Design NOTIF-HOLD- templates* (placed, released, still blocked) with plain-language mappings from REASON-HOLD-* codes, ETA-PAY- timeline steps* on the status portal that align with WAVE-EXPORT-* states, and SYNC-TML-* rules so email, SMS, and portal never disagree. When HOLD-DISB-* clears, notify only if GATE-PAY- still allows* and the next tranche is scheduled in distribution planning; if award restatement reopens holds, send NOTIF-REST-* before NOTIF-HOLD-REL-*. Without this UI, claimants celebrate a release email while fraud holds still block, call center scripts contradict the portal, and regulators see optimistic ETAs during appeal stays. Start from the Figma guides hub and pair with notice FAQ, email OTP, and notification preferences.

---

Who this is for

• Product designers owning claimant comms across email, SMS, and portal.
• Operations leads aligning call center scripts with automated messages.
• Engineers implementing event-driven NOTIF-* with idempotency keys.

---

NOTIF-HOLD-* event model

NotificationEvent — NOTIF-HOLD-REL-8821 · CLM-4412 · Channel: email+sms
├── Trigger:
│   ├── HOLD-DISB-* → Released · source LOG-REL-*
│   ├── GATE-PAY-* recalc · must be Allow
│   └── No active STY-APP-* program stay
├── Template variants:
│   ├── NOTIF-HOLD-PLACED-* · why blocked · next action link
│   ├── NOTIF-HOLD-REL-* · hold cleared · ETA-PAY-* step advance
│   ├── NOTIF-HOLD-STILL-* · partial release · other holds remain
│   └── NOTIF-REST-* · [restatement](/designing-breach-settlement-award-restatement-and-fin-awd-version-history-ui-in-figma/) changed amount
├── ID namespace:
│   ├── NOTIF-HOLD-* (outbound message)
│   ├── ETA-PAY-* (timeline node)
│   ├── COPY-HOLD-* (plain language snippet)
│   ├── SYNC-TML-* (portal sync job)
│   └── LOG-NOTIF-* (delivery + open)
└── Consent:
    ├── [Notification prefs](/designing-notification-preferences-and-communication-settings-ui-in-figma/)
    └── SMS opt-in · separate from marketing

Event	Portal timeline	Call center script id
Hold placed	Red step + action CTA	SCR-HOLD-PLACED
Hold released	Yellow “processing”	SCR-HOLD-REL
Export uploaded	Blue “sent to bank”	SCR-EXPORT-UP
Paid / check mailed	Green complete	SCR-PAID

Verdict: Do not send NOTIF-HOLD-REL- on manual override alone*— require GATE-PAY Allow in the same transaction.

---

ETA-PAY-* timeline UI (claimant portal)

PaymentTimeline — CLM-4412 · ETA-PAY-7 active step
├── Steps (typical):
│   1. Claim received · [settlement claims](/designing-breach-settlement-notice-and-victim-compensation-claims-ui-in-figma/)
│   2. Under review · holds / [deficiency](/designing-breach-settlement-deficiency-notice-and-claim-cure-ui-in-figma/)
│   3. Award finalized · [VER-AWD-*](/designing-breach-settlement-award-restatement-and-fin-awd-version-history-ui-in-figma/)
│   4. Scheduled for payment · [tranche](/designing-breach-settlement-distribution-schedule-and-tranche-disbursement-planning-ui-in-figma/)
│   5. Processing · [export uploaded](/designing-breach-settlement-payment-file-generation-and-nacha-preview-ui-in-figma/)
│   6. Complete · [disbursement](/designing-breach-settlement-payment-disbursement-and-payout-tracking-ui-in-figma/)
├── Subcopy rules:
│   ├── Active hold · show top COPY-HOLD-* · link to cure action
│   ├── Multiple holds · “2 items need attention”
│   ├── No false dates · show ranges or “next tranche window”
│   └── Intl · link [foreign payment FAQ](/designing-breach-settlement-foreign-claimant-and-international-payment-ui-in-figma/)
└── Components:
    ├── [Progress stepper](/designing-progress-indicators-and-steppers-in-figma/) · desktop
    ├── [Vertical timeline](/designing-order-history-and-order-tracking-ui-in-figma/) · mobile
    └── [Badges](/designing-badges-and-chips-in-figma-status-tags-and-handoff/) · hold severity

Use empty states when no holds but award pending, and toasts only for in-session portal updates—not replacement for email.

---

Plain-language COPY-HOLD-* mapping

REASON-HOLD-* (internal)	COPY-HOLD-* (claimant)	Suggested action
IDV-*	Identity verification needed	Step-up flow
DEF-NOT-*	Missing documents	Document upload
OBJ-TIER-*	Award under review	Read-only wait
LIEN-PEND-*	Third-party claim	Contact support
REST-ACK-*	Updated award amount	Acknowledge restatement
STY-APP-*	Program-wide delay	Notice FAQ

Recommended: counsel approves COPY-HOLD-* strings before launch— version in admin UI like privacy notice changelog.

---

Comparison: notification channels

Channel	Best for	Avoid
Email	Detail + links	PII in subject line
SMS	Short ETA change	Full account numbers
Portal	Source of truth	Sending before SYNC-TML-*
Mail	Check reissue	Duplicating portal steps

---

Common mistakes

1. NOTIF-HOLD-REL- before WAVE-EXPORT- exists**— claimants expect money in 24h.
2. Different dates in email vs portal— missing SYNC-TML-* job after export.
3. Legal jargon in COPY-HOLD-*— drives call center volume.
4. No NOTIF-HOLD-STILL- when one of multiple holds clears*— false celebration.
5. Ignoring returned payment auto-notify— timeline stuck on “complete.”

---

Recommended workflow

1. Publish COPY-HOLD- catalog* · link to REASON-HOLD-* · counsel sign-off.
2. Wire events from HOLD-DISB-* and GATE-PAY-* · idempotent NOTIF keys.
3. Design ETA-PAY- steps* · map to export/disbursement backend states.
4. Run SYNC-TML-* after every batch status change.
5. Train call center · SCR-* ids match portal step labels exactly.

---

FAQ

Should we email on every hold placement?

Yes for hard holds affecting payment— but batch digest if >3 micro-holds same day.

ETA date ranges vs exact dates?

Use ranges until bank confirm— exact dates only after disbursement tracking settlement.

Appeal stay lifted— notify all claimants?

Program banner + optional NOTIF-STY-LIFT-*— do not imply individual pay date until tranche scheduled.

Developer handoff?

Document event → NOTIF template → ETA step matrix— Dev Mode checklist.

Accessibility?

Timeline steps need text labels beyond color— pair with accessibility plugins review.

---

Next steps

• Design breach settlement disbursement hold release and payment gate UI in Figma — when release is real
• Design breach settlement payment file generation and NACHA preview UI in Figma — processing step copy
• Design breach settlement claim status portal and claimant dashboard UI in Figma — dashboard shell
• Design breach settlement call center and agent script UI in Figma — script parity
• Design notification preferences and communication settings UI in Figma — opt-in/out