Settlement Litigation Discovery DSQ Export UI

Quick answer

Discovery UI exports ARC-* archive packages for litigation and regulatory subpoenas—without giving opposing counsel a live admin console. Design DSQ- discovery requests* with matter-scoped search, RED-DSQ- redaction*, load-file generation (DAT/OPT or JSON), and guest counsel portals (USR-GST-*) that expire on a court-ordered timeline. Every export needs chain-of-custody (COC-DSQ-*) tied to forensic evidence patterns and HLD- legal hold* overlays that block DST-* destruction while discovery is active. Start from the Figma guides hub and pair with compliance exports, team roles, and audit log visibility.

Who this is for

Product designers building settlement archive consoles that legal teams use for e-discovery—not claimant self-service.
Settlement counsel and e-discovery vendors requesting scoped PKG-* exports with defensible chain of custody.
Legal ops and compliance placing HLD-* on archive scope when follow-on litigation references the original breach settlement.

Discovery lifecycle overview

DiscoveryProgram — DSQ-992-001 · matter_id: MAT-2026-441 · Status: Scoping
├── Triggers:
│   ├── Follow-on class action cites SET-992 disbursement records
│   ├── Regulatory subpoena for PAY-* and reconciliation ([FIN-*](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/))
│   ├── Criminal investigation into fraud ([FRA-*](/designing-breach-settlement-duplicate-claim-detection-and-fraud-prevention-ui-in-figma/))
│   └── Internal litigation after [post-incident review](/designing-post-incident-review-and-root-cause-analysis-ui-in-figma/)
├── ID namespace:
│   ├── DSQ-* (discovery request) · SCOPE-* (custodian scope definition)
│   ├── COC-DSQ-* (chain of custody event) · EXP-DSQ-* (production export)
│   ├── RED-DSQ-* (redaction overlay) · LDF-* (load file bundle)
│   ├── USR-GST-* (guest counsel user) · TOK-GST-* (time-boxed access)
│   └── LOG-DSQ-* (discovery audit · separate from LOG-ARC-*)
├── Scope dimensions (SCOPE-*):
│   ├── Date range · CLM-* / PAY-* ID lists
│   ├── Record classes: claims · payments · QA FIND-* · call recordings
│   ├── PKG-* versions · hash verification required
│   └── Exclusions: unrelated settlements · sealed exhibits
├── Production workflow:
│   ├── Legal defines SCOPE-* → admin approves
│   ├── Search ARC-* index → preview hit counts
│   ├── RED-DSQ-* privilege · PII of non-parties
│   ├── EXP-DSQ-* job → LDF-* + native files
│   ├── COC-DSQ-* seal · checksum · custodian sign-off
│   └── Guest portal or secure physical media tracking
├── Holds:
│   ├── Auto HLD-* on SCOPE-* when DSQ-* active
│   ├── Blocks DST-* on overlapping RET-*
│   └── Release only when matter closed + counsel cert
└── Outcomes:
    ├── Defensible production for court
    ├── LOG-DSQ-* + LOG-ARC-* correlated audit
    └── Guest access revoked · TOK-GST-* expired

DSQ state	Internal legal	Guest USR-GST-*
Draft scope	Build SCOPE-*	No access
Approved	Preview counts	Invite pending
In production	Monitor EXP-DSQ-*	Wait
Delivered	Download LDF-*	View-only portal
Closed	Archive COC-DSQ-*	TOK-GST-* revoked

Verdict: Discovery exports are productions—not DSAR responses. Scope, redaction, and custody must be explicit.

DSQ-* request intake and SCOPE-* builder UI

DiscoveryRequest — DSQ-992-001 · requested_by: Settlement Counsel · priority: High
├── Matter metadata:
│   ├── Case caption · court · docket number
│   ├── Opposing counsel contact · protective order ref
│   ├── Related SET-* · ARC-992-001 link
│   └── Link existing HLD-* or create new overlay
├── SCOPE-* builder:
│   ├── Visual custodian map (PKG-* sections as checkboxes)
│   ├── Query builder: CLM-* prefix · PAY-* date range · FIND-* severity
│   ├── Estimated volume · cost projection (optional admin tile)
│   ├── Privilege log placeholder flag
│   └── Conflict check: overlapping DSQ-* on same PKG-*
├── Approval chain:
│   ├── Settlement admin · general counsel · optional court order upload
│   ├── Dual approval for full PKG-* export
│   └── Break-glass reason if scope exceeds standard playbooks
├── Pre-flight checks:
│   ├── PKG-* hash integrity ([archive verification](/designing-breach-settlement-archive-and-long-term-record-retention-ui-in-figma/))
│   ├── No active packaging job
│   ├── HLD-* applied to scope
│   └── RET-* / DST-* blocked in UI with explanation
└── Outputs:
    ├── DSQ-* ID assigned · SLA for production date
    └── Notify e-discovery vendor integration webhook ([webhooks UI](/designing-webhooks-and-event-subscriptions-ui-in-figma/))

Use accordions for advanced SCOPE-* filters and progress steppers for approval stages.

EXP-DSQ-* production job and LDF-* load file UI

ProductionJob — EXP-DSQ-992-001-A · dsq_id: DSQ-992-001 · Status: Redaction review
├── Job dashboard:
│   ├── Progress: extract · redact · package · checksum
│   ├── Document count · Bates range preview (SET992-000001)
│   ├── Error queue: corrupt files · password-protected PDFs
│   └── Pause / resume · legal hold on job if scope dispute
├── RED-DSQ-* review workspace:
│   ├── Document viewer with redaction tools
│   ├── Privilege tag · confidential · highly confidential
│   ├── Third-party PII auto-suggest ([content classification](/designing-content-classification-and-sensitivity-labels-ui-in-figma/))
│   ├── Bulk apply redaction reasons
│   └── Privilege log auto-populate from tags
├── LDF-* bundle config:
│   ├── Format: Relativity DAT · Concordance · JSON manifest
│   ├── Native vs text-only · OCR status column
│   ├── Metadata fields: CLM-* · PAY-* · LOG-* timestamps
│   └── Encryption password delivery channel (out-of-band)
├── COC-DSQ-* custody events:
│   ├── Custodian: who ran export · when · from which system
│   ├── SHA-256 of LDF-* · individual file hashes
│   ├── Transfer method: SFTP · encrypted drive · guest portal
│   └── Recipient acknowledgment capture
└── Delivery:
    ├── Internal download (role-gated)
    ├── Guest portal publish (USR-GST-*)
    └── [Compliance export](/designing-compliance-exports-and-legal-hold-ui-in-figma/) copy for regulator if parallel subpoena

Align Bates numbering and metadata with forensic evidence chain of custody—reviewers should recognize the same event model.

Guest counsel portal (USR-GST-*) UI

GuestCounselPortal — USR-GST-MORRIS-001 · dsq_id: DSQ-992-001 · expires: 2026-12-01
├── Access controls:
│   ├── TOK-GST-* magic link · MFA required ([2FA UI](/designing-two-factor-authentication-and-security-settings-ui-in-figma/))
│   ├── IP allowlist optional ([enterprise pattern](/designing-ip-allowlist-and-network-restrictions-ui-in-figma/))
│   ├── View-only · no download unless order permits
│   └── Session timeout aggressive ([session UI](/designing-session-timeout-and-re-authentication-ui-in-figma/))
├── Browse experience:
│   ├── Search within production only · not full ARC-*
│   ├── Filter by Bates · doc type · date
│   ├── Watermarked preview · print disabled
│   └── Request additional SCOPE-* (workflow back to DSQ-*)
├── Activity:
│   ├── LOG-DSQ-* every view · export attempt
│   ├── Anomaly: bulk scrape → alert [security alerting](/designing-security-alerting-rules-and-notification-routing-ui-in-figma/)
│   └── Auto-revoke at expiry · extension requires approval
└── Offboarding:
    ├── Revoke TOK-GST-* · email confirmation
    └── COC-DSQ-* "access terminated" event

Best for: opposing counsel under protective order. Skip when: court requires physical production only—track in COC-DSQ-* without building browse UI.

Comparison: DSQ-* vs DSAR-ARC-* vs compliance export

Dimension	DSAR-ARC-*	DSQ-* (this pattern)	Compliance export
Requestor	Individual claimant	Counsel / regulator	Internal audit
Scope	One person’s records	Matter-defined bulk	Policy template
Redaction	RED-ARC-* third-party PII	RED-DSQ-* privilege + PII	Often full internal
Format	PDF + JSON portability	LDF-* + natives	CSV / audit pack
Guest access	Rare	USR-GST-* common	Never
Chain of custody	LOG-DSAR-ARC-*	COC-DSQ-* required	Standard audit log

HLD-* interaction and DST-* blocking UI

When DSQ-* is active, show hold overlay on archive retention UI:

HoldBanner — HLD-DSQ-992-001 · blocks: DST-* on PKG-992-claims · until: matter closed
├── Visible on RET-* schedule view
├── Explain: "Discovery DSQ-992-001 prevents destruction"
├── Link to DSQ-* detail · counsel contact
└── Release workflow: upload matter closure order → dual approval

Never allow silent DST-* while SCOPE-* overlaps—surface blocking reason in destruction UI pre-flight.

Common mistakes

Giving guest counsel full ARC- search* instead of scoped production—scope creep and PII exposure.
Skipping COC-DSQ-* because “it’s just a copy”— courts care about custody.
Same export for DSAR and DSQ— different redaction rules and formats.
No privilege log UI when RED-DSQ-* tags exist— incomplete production.
Forgotten TOK-GST- expiry*— opposing counsel retains access indefinitely.

Recommended workflow

Define DSQ- intake* with matter metadata and SCOPE-* builder on archive console.
Prototype EXP-DSQ- job* with RED-DSQ-* review and Bates preview.
Build LDF- config* panel for vendor format selection and metadata mapping.
Add COC-DSQ- timeline* component shared with forensic evidence UI.
Design USR-GST- portal* with watermark, MFA, and LOG-DSQ-* audit.
Wire HLD- blocking* on DST-* and document release workflow for matter closure.

FAQ

Opposing counsel wants live database access?

Deny by default · Offer scoped guest portal or staged productions · Document in COC-DSQ-*.

Multiple DSQ-* on same SET-992?

SCOPE- conflict checker* · dedupe productions · shared RED-DSQ-* where possible.

Subpoena to third-party cloud provider?

Internal DSQ- still tracks* what you produce · PKG-* hash proves what existed at archive time.

Sealed exhibits?

Separate EXP-DSQ- sealed* · USR-GST-* without browse · physical delivery COC-DSQ-*.

E-discovery vendor API?

Webhook + LDF- drop* · API keys UI for integration service account · not guest counsel.

After production, can we run DST-*?

Only when HLD-DSQ- released* · RET-* eligible · legal sign-off · link proof of deletion.

Next steps

Design breach settlement archive and long-term record retention UI in Figma — PKG-* source for DSQ-*
Design breach settlement archived DSAR and claimant access UI in Figma — Individual vs bulk export contrast
Design forensic evidence management and chain of custody UI in Figma — COC-DSQ-* patterns
Design compliance exports and legal hold UI in Figma — HLD-* enterprise baseline
Design regulatory authority correspondence and breach filing archive UI in Figma — Parallel regulator productions

Designing breach settlement litigation discovery and DSQ export UI in Figma: DSQ-* requests, guest counsel portals, and chain-of-custody handoff