Overview#
A commission of investigation needs to manage strands, hearings, privilege decisions, disclosure recipients, pseudonymised witness material, and consent impact assessments without allowing one team to see another team's protected work. The Commission of Investigation Case Workspace module brings those workflows together in a clearance-aware case environment.
The workspace is designed for public inquiries, statutory investigations, sensitive reviews, and multi-party legal processes where every action must be explainable. Users can prepare hearings, export schedules, track disclosure access, manage privilege logs, separate strands with Chinese-wall controls, and record consent impacts while preserving a complete audit trail.
Key Features#
-
Clearance-Aware Case Workspace: Case tabs, documents, hearings, strands, and disclosure records respect each user's commission role and case clearance.
-
Strand Isolation: Chinese-wall controls separate sensitive strands so legal, investigative, and administrative teams can collaborate without unnecessary cross-contamination.
-
Hearing Management: Hearing schedules, participants, preparation status, and room details can be managed from the case workspace and exported for calendar coordination.
-
Privilege Log Export: Privilege decisions, claim status, reviewers, and supporting notes can be exported to spreadsheet formats for legal review and disclosure management.
-
Disclosure Recipient Tracking: Recipient access, delivery status, acknowledgement, and download activity are recorded for defensible disclosure oversight.
-
Consent Impact Assessment: Teams can document consent implications before using sensitive material in hearing, disclosure, or publication workflows.
-
Pseudonymisation Support: Witness, subject, and third-party identifiers can be pseudonymised for disclosure preparation while preserving the protected source record.
-
Full Access Audit: Workspace reads, exports, hearing changes, privilege updates, and recipient access events are recorded for compliance review.
Use Cases#
- Public inquiry case management where hearings, evidence, strands, and disclosure activity need to be coordinated across legal and investigative teams.
- Sensitive strand separation where material connected to one witness group, agency, or allegation must not leak into another team's workspace.
- Privilege review where legal teams need a defensible log of claims, decisions, reviewers, and export history.
- Disclosure recipient governance where external parties receive controlled access and the commission must know who viewed what and when.
- Consent assessment where teams evaluate whether sensitive evidence can be used, shared, or published under the commission's mandate.
- Pseudonymised publication preparation where identifying details must be controlled before hearing packs, reports, or public extracts are produced.
Integration#
The module connects commission case records, evidence management, hearing scheduling, disclosure packaging, privilege review, pseudonymisation, recipient access tracking, and audit reporting. It is designed to expose the operational workflow while keeping protected APIs, data models, and internal case-enforcement logic private.
Open Standards#
- iCalendar (RFC 5545): Hearing schedules can be exported in a portable calendar format for coordination with legal teams and external participants.
- Office Open XML / XLSX (ISO/IEC 29500): Privilege logs and structured review exports can be shared using the standard spreadsheet format commonly used in legal workflows.
- W3C PROV-DM: Disclosure, hearing, privilege, consent, and pseudonymisation actions can be represented as provenance events.
- GDPR (EU Regulation 2016/679): Data minimisation, lawful basis, transparency, subject rights, and accountability inform consent and pseudonymisation workflows.
- ISO 8601: Hearing dates, disclosure events, recipient access, and assessment records use consistent date and time formatting.
- RFC 3161 Time-Stamp Protocol: Disclosure packages and finalised logs can be timestamped for independent proof of production time.
- SHA-256 (FIPS 180-4): Exports, disclosure bundles, and evidence references can be hashed for integrity verification.
- WCAG 2.2: Hearing preparation, tabbed workspace navigation, export controls, and review interfaces support accessible workflows.
Security and Compliance#
The workspace applies clearance, strand isolation, recipient controls, and audit logging before displaying sensitive commission material. Exports inherit the review status and access boundaries of their source records, and disclosure access remains traceable after material leaves the immediate workspace.
Last Reviewed: 2026-06-25 Last Updated: 2026-06-25