Case structure
Matters hold the record: subjects, facts, notes, files, tasks, messages, reports, timelines, and operational activity.
Platform / Knox
One operating layer for the case, the record, and the work.
Knox brings casework, documents, messages, tasks, schedules, reports, client access, and live collaboration into one controlled platform. It is built for teams that need the work to stay connected from intake through delivery.
Platform Brief
Built to keep serious work from scattering.
Case-based operations break down when facts live in one system, files in another, messages in another, reports somewhere else, and client updates in a separate channel. Knox creates a single operating surface where the record, the workflow, and the people remain connected.
Operating Architecture
The platform carries the structure of the work.
Knox is organized around the way operational teams actually move: matters are opened, facts are captured, documents are reviewed, tasks are assigned, deadlines are tracked, reports are produced, and clients receive controlled visibility.
Role access
Admins, investigators, clients, contacts, and team members see only what their role and assignment allow.
Work movement
Tasks, status changes, schedules, messages, reviews, and document handling stay close to the matters they affect.
Output control
Reports, packets, summaries, exhibits, updates, and client-ready deliverables can be produced from structured work.
01 / Operations Desk
The working surface opens with the work in view.
The Operations Desk gives users an immediate read on active matters, priority work, recent messages, uploaded documents, open tasks, and live presence. It is the platform’s control surface.
- Role-aware dashboard visibility
- Priority queues and recent matter activity
- Live Office access from the operating surface
02 / Case Workspace
Each matter carries its own operating record.
The case workspace keeps facts, subjects, documents, tasks, notes, communications, timeline movement, reporting, and client visibility tied to the matter instead of scattered across separate tools.
- Case overview, timeline, tasks, files, and reporting
- Permission-aware access by role and assignment
- Operational history connected to the matter
03 / Document Control
Files remain part of the record.
Uploads, metadata, review status, notes, tags, matter grouping, and document activity remain inside the same environment as the case they support.
- Document library by matter and category
- Review state, notes, tags, and file metadata
- Reduced reliance on disconnected file-sharing systems
04 / Timeline
The movement of the matter remains visible.
Knox captures operational activity as the matter develops: document uploads, messages, task completion, notes, schedule changes, report work, and other case-level actions.
- Case activity presented as an operational timeline
- Document, message, task, note, and event visibility
- Better reconstruction of what happened and when
05 / Scheduling
Deadlines and meetings stay operational.
Scheduling belongs close to the case. Knox keeps calendar events, meetings, reminders, invitations, and matter-linked deadlines inside the same controlled environment as the work.
- Case-linked calendar activity
- Meetings and events connected to matter context
- Operational continuity while users schedule work
06 / Resources
Support resources stay close to the workspace.
Court links, jurisdictional destinations, saved references, and frequently used support resources can live inside Knox so users spend less time leaving the operating surface.
- Court links and saved legal resources
- Federal, state, and jurisdictional destinations
- Useful for legal, investigative, and compliance teams
Control Layer
The platform is built around controlled access.
Knox is not a shared folder with a dashboard placed over it. It is a controlled operating environment where users, matters, files, messages, schedules, reports, and client access are governed by role and context.
01
Role separation
Internal users, clients, contacts, administrators, and assigned
team members operate with different visibility and authority.
02
Matter context
Information is organized around matters, not scattered across
unrelated tools, inboxes, folders, and conversations.
03
Client visibility
Clients and outside contacts can receive controlled access without
entering the internal operating surface.
04
Deployment flexibility
Knox can support branded, white-label, hosted, or extended
deployments depending on the operating requirement.
Engage
Put the work inside one controlled operating layer.
Knox gives operational teams a platform for cases, documents, schedules, reports, client access, live collaboration, and the record behind the work.
Contact Aerellus