figma guide

Designing breach settlement court monitor and special master reporting UI in Figma: MON-* dashboards, RPT-* periodic reports, and compliance attestations

Design breach settlement court monitor and special master reporting UI in Figma with MON-* monitor dashboards, RPT-* periodic reports, compliance attestations, and read-only court-facing views.

Published
Updated
Sep 03, 2026
Read time
8 min
Level
Intermediate

Quick answer

Court monitor reporting UI gives judges and special masters settlement health in one place—not quarterly PDF dumps that contradict the admin console. Design MON- monitor dashboards* with read-only KPIs, RPT- periodic reports* generated on a court schedule, and compliance attestations that tie to auditor finding responses and final accounting. Monitors see claim volumes, disbursement rates, open exceptions, and remediation aging—without edit access to CLM-* or PAY-*. Connect to external auditor portal, fund reconciliation, regulatory correspondence, and trust center patterns. Start from the Figma guides hub and pair with tables, SLA dashboards, and Dev Mode handoff.


Who this is for

  • Product designers building settlement administrator portals where court-appointed monitors or special masters need ongoing visibility.
  • Settlement administrators preparing RPT-* packages on court-ordered cadence without manual spreadsheet assembly.
  • Class counsel and court monitors reviewing settlement progress, open remediation, and certification readiness before closure hearings.

Monitor engagement lifecycle overview

MonitorEngagement — MON-992-001 · Role: Special Master · Status: Active · Next RPT due: 2026-10-01
├── Triggers:
│   ├── Court order appointing special master or monitor
│   ├── Settlement plan requires quarterly status reports
│   ├── Pre-[final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/) certification hearing
│   ├── Material [RSP-* remediation](/designing-breach-settlement-external-auditor-finding-response-and-remediation-ui-in-figma/) must be reported
│   └── Class counsel requests monitor access for oversight
├── ID namespace:
│   ├── MON-* (monitor engagement) · USR-MON-* (monitor user)
│   ├── RPT-* (periodic report) · ATT-MON-* (monitor attestation)
│   ├── KPI-* (dashboard metric snapshot) · EXH-* (court exhibit draft)
│   └── LOG-MON-* (monitor activity · same pattern as [AUD-EXT LOG-*](/designing-breach-settlement-external-auditor-access-and-read-only-review-portal-ui-in-figma/))
├── Access model:
│   ├── Read-only dashboard — aggregated metrics · no claimant PII bulk export
│   ├── Scoped drill-down — sample CLM-* redacted · linked QA-* / RSP-*
│   ├── Report generation — admin publishes RPT-* · monitor comments
│   └── Time-boxed or standing — per court order · MFA required
├── Cadence:
│   ├── Monthly / quarterly / milestone-based RPT-*
│   ├── Auto-reminder to admin 14 days before due
│   ├── Overdue RPT-* flags on MON-* dashboard (admin-only shame banner)
│   └── Ad hoc EXH-* for hearings
└── Outcomes:
    ├── RPT-* filed with court · EXH-* attached to docket
    ├── Monitor attestation on [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
    └── Engagement closed at settlement wind-down
MON stateAdmin seesMonitor sees
DraftScope · cadence configNothing
ActiveRPT-* due dates · KPI freshnessLive dashboard
Report pendingDraft RPT-* for reviewComment period
FiledCourt filing confirmationHistorical RPT-* archive
ClosedLOG-MON-* archiveAccess revoked

Verdict: RPT- numbers must match admin console KPIs—never hand-built spreadsheets that diverge from production data.*


MON-* dashboard and KPI-* metrics UI

MonitorDashboard — MON-992-001 · settlement_id: SET-992 · period: Q3 2026
├── Header strip:
│   ├── Settlement name · plan version · monitor role label
│   ├── Last data refresh_at · "As of" timestamp (critical for trust)
│   ├── Open exceptions count (RSP-* · VAR-* · overdue REM-*)
│   └── Next RPT-* due · link to draft if in progress
├── KPI tiles (aggregated · no PII):
│   ├── Claims: submitted · approved · denied · pending · % complete
│   ├── Disbursements: total paid · batch count · avg days claim-to-pay
│   ├── Fund: escrow balance · [reconciliation](/designing-breach-settlement-fund-reconciliation-and-bank-matching-ui-in-figma/) status · UCF balance
│   ├── Quality: open FIND-* · QA error rate · [clawback](/designing-breach-settlement-clawback-and-overpayment-recovery-ui-in-figma/) recovery rate
│   ├── Remediation: open RSP-* · overdue REM-* · material findings count
│   └── Contact center: call volume · avg handle time (from [call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) metrics)
├── Trend charts:
│   ├── Claims approved per week · disbursement $ per batch
│   ├── Exception aging · remediation closure rate
│   └── Compare to plan milestones (vertical markers)
├── Drill-down (scoped · redacted):
│   ├── Click KPI → filtered table (counts · IDs masked)
│   ├── Sample CLM-* summary: CLM-992-***** · status · award tier only
│   ├── Link to read-only [QA campaign](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/) ERR-* rollup
│   └── Link to open RSP-* summary (no EVD-* download unless scoped)
└── Alerts panel:
    ├── Material finding open >30 days
    ├── Reconciliation period not closed
    ├── Disbursement batch without post-QA
    └── Configurable thresholds from court order

Pair dashboard layout with SLA reporting patterns—monitors expect uptime-style clarity on settlement throughput.


RPT-* periodic report builder and filing UI

PeriodicReport — RPT-992-Q3-2026 · mon_id: MON-992-001 · Status: Monitor review
├── Report setup:
│   ├── rpt_id (RPT-*) · mon_id · period_start · period_end
│   ├── template_enum (quarterly_status · pre_final_accounting · ad_hoc_hearing)
│   ├── court_docket_ref · filing_deadline_at
│   └── auto_sections[] vs manual_narrative_sections[]
├── Auto-generated sections (from KPI-* snapshots):
│   ├── Executive summary bullets (editable by admin · tracked changes)
│   ├── Claims and disbursement tables (frozen at snapshot_at)
│   ├── Fund reconciliation summary for period
│   ├── QA and audit status ([QA-*](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/) · [AUD-EXT-*](/designing-breach-settlement-external-auditor-access-and-read-only-review-portal-ui-in-figma/))
│   ├── Open remediation appendix ([RSP-*](/designing-breach-settlement-external-auditor-finding-response-and-remediation-ui-in-figma/) · REM-* status)
│   └── Exception list with aging
├── Manual narrative blocks:
│   ├── Admin-authored prose per section · character limit optional
│   ├── Monitor comment threads per section (USR-MON-*)
│   ├── Resolve comments before "Ready to file"
│   └── Version history · diff between RPT-* drafts
├── Review workflow:
│   ├── Draft → Admin internal review → Monitor review → Ready to file → Filed
│   ├── Monitor can request revision (returns to Draft with comments)
│   ├── Counsel optional sign-off gate on pre-final templates
│   └── ATT-MON-* optional "Reviewed without objection" checkbox
├── Filing outputs:
│   ├── PDF with exhibit numbering (EXH-* refs)
│   ├── CSV exhibits behind separate PKG-* if court allows
│   ├── filing_confirmed_at · docket_upload_ref
│   └── Archive in [regulatory correspondence](/designing-regulatory-authority-correspondence-and-breach-filing-archive-ui-in-figma/)
RPT templateTypical court timingMust include
quarterly_statusEvery 90 daysKPI trends · open exceptions
pre_final_accounting60 days before closureFull fund · QA · RSP-* closure
ad_hoc_hearingHearing date − N daysSpecific EXH-* topic

USR-MON-* access, attestation, and comparison to auditor portal

MonitorUser — USR-MON-992-001 · mon_id: MON-992-001 · role: Special Master
├── Access parallels [USR-EXT-*](/designing-breach-settlement-external-auditor-access-and-read-only-review-portal-ui-in-figma/) but broader read:
│   ├── Dashboard always on · RPT-* comment rights
│   ├── No REM-* edit · no PAY-* trigger · no CLM-* approve
│   ├── Optional EXH-* draft comment · not edit admin data
│   └── MFA · session timeout · LOG-MON-* all views
├── ATT-MON-* attestation types:
│   ├── RPT reviewed · objections noted (comment ref)
│   ├── Pre-final accounting readiness (checklist)
│   ├── Remediation adequacy (links RSP-* closed)
│   └── Final closure recommendation (optional)
└── Wind-down:
    ├── MON-* closed at settlement archive
    ├── USR-MON-* revoked · RPT-* archive read-only for admin
    └── LOG-MON-* retained per [retention policy](/designing-data-retention-policies-and-auto-deletion-ui-in-figma/)

Comparison: court monitor vs adjacent oversight UI

SurfacePrimary audienceCadenceThis UI adds
External auditor AUD-EXT-*Audit firmEngagement-basedOngoing court reporting
RSP-* remediationAdmin + counselEvent-drivenMonitor visibility rollup
Final accountingCourt filingOncePeriodic RPT-* leading up
Status pagePublic claimantsIncidentConfidential court metrics
Trust centerCustomersStaticLive settlement ops KPIs

Handoff checklist (Dev Mode)

  • MonitorEngagement — mon_id (MON-*), settlement_id, role_enum, rpt_cadence_enum, scope_enum, status_enum.
  • MonitorUser — usr_mon_id (USR-MON-*), mon_id, mfa_enrolled_bool, status_enum.
  • DashboardSnapshot — kpi_id (KPI-*), mon_id, snapshot_at, metrics_json, refresh_source.
  • PeriodicReport — rpt_id (RPT-*), mon_id, period_start, period_end, template_enum, status_enum, filing_ref.
  • ReportSection — section_id, rpt_id, section_type_enum, content_ref, auto_generated_bool.
  • MonitorAttestation — att_mon_id (ATT-MON-*), rpt_id or mon_id, type_enum, signed_at.
  • MonitorActivityLog — log_mon_id (LOG-MON-*), usr_mon_id, action_enum, timestamp.

Common mistakes

MistakeWhy it hurtsFix
Manual Excel RPT-*Numbers disagree with systemAuto KPI-* snapshots
Monitor gets admin roleEdit liabilityUSR-MON-* read + comment only
PII in RPT-* PDFPrivacy violationAggregates · redacted samples
Stale dashboard refresh_atCourt mistrustShow “As of” · auto-refresh SLA
No RPT-* version historyDispute what was filedDraft versions · diff
Skip remediation in reportIncomplete pictureRSP-* appendix required
Same portal as claimantsWrong audienceSeparate MON-* route
No filing confirmationAudit gapfiling_confirmed_at + docket ref
Monitor comments via emailLost threadIn-app RPT-* comment threads
Close MON-* before archiveLost oversight historyRetain RPT-* read-only

  1. Define MON- scope from court order* — cadence, KPI list, drill-down depth.
  2. Prototype dashboard with KPI tiles, trends, and redacted drill-down tables.
  3. Build RPT- template* with auto sections from KPI-* plus editable narrative.
  4. Add monitor review loop — comments, revision, ATT-MON-* optional sign-off.
  5. Filing export with EXH-* numbering and regulatory archive storage.
  6. Tie pre-final RPT- to final accounting* certification checklist.

FAQ

Special master vs external auditor?

MON- is ongoing oversight + RPT-** · AUD-EXT-* is scoped engagement · May both exist · Separate USR-* types.

Monitor needs individual CLM-* names?

Redact per plan · Break-glass with counsel approval · LOG-MON-* · Usually status counts suffice.

RPT-* due date missed?

Admin overdue banner · Escalation to counsel · Document reason in next RPT-* narrative.

Monitor disputes RSP-* closure?

Comment on RPT-* · May require re-open REM-* · ATT-MON-* “objection noted.”

Public access to settlement stats?

Not this UI — use notice FAQ for claimants · MON-* is court-confidential.

KPI definitions change mid-settlement?

Version kpi_schema · RPT-* footnote · Do not restate prior periods silently.


Next steps

Share on X

§ Keep reading

Related guides.