Record classes
Record classes remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.
- Connected source records
- Named review authority
- Visible exceptions
Data Retention
Data Retention Requires Defined Record Authority
Evaluate retention, archive, legal-hold, deletion, export, provider, and customer responsibilities for each relevant record class and deployed service.
Defined record classes Named authority Visible lifecycle Provider boundaries
Operational Scope
What to examine in data retention.
Each capability should be evaluated against the firm's real records, permissions, review duties, and failure conditions.
Retention authority
Retention authority remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.
- Connected source records
- Named review authority
- Visible exceptions
Archive and hold
Archive and hold remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.
- Connected source records
- Named review authority
- Visible exceptions
Deletion evidence
Deletion evidence remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.
- Connected source records
- Named review authority
- Visible exceptions
Controlled Workflow
Move from source evidence to an accountable outcome.
The exact configuration depends on the firm's operating model, enabled workspaces, data, and assigned authorities.
Define scope
Confirm the relevant matters, records, people, roles, branches, and decision boundaries before work starts.
Connect evidence
Attach the source records and context needed to understand, review, and reconcile the work.
Review exceptions
Route incomplete, conflicting, unavailable, or permission-restricted states to the responsible person.
Record the outcome
Preserve the accepted result, remaining exceptions, responsible authority, and next action.
Evidence Boundary
Treat product evidence as scoped evidence.
Trust and security statements must be tested against current deployment evidence. This page does not certify legal compliance, universal control coverage, a provider, a data location, or an operational outcome.
Navigation and client input never grant access; the relevant tenant, branch, matter, record, and capability must be re-authorised.
Loading, empty, unavailable, permission-denied, failed, and retryable outcomes must remain distinguishable from success.
Software can organise evidence and workflow, but professional, regulatory, accounting, and operational decisions remain with authorised people.
Confirm the deployed environment, enabled providers, configured controls, and supported data before relying on a capability.
Data Retention FAQ
Frequently Asked Questions
Practical questions about data retention, authority, evidence, and product scope.
What does Lexuno mean by data retention?
Evaluate retention, archive, legal-hold, deletion, export, provider, and customer responsibilities for each relevant record class and deployed service.
Does this page promise that every workflow is enabled for every firm?
No. Availability and behavior depend on the current product release, plan, configuration, permissions, providers, and the firm's accepted operating model.
How should a firm evaluate this capability?
Use representative records and end-to-end scenarios, including empty, permission-denied, provider-unavailable, failed, exception, and reconciliation states.
Does Lexuno replace professional advice or accountable review?
No. Lexuno provides operational software. Legal, regulatory, accounting, security, and professional decisions remain separate responsibilities.
How should access be verified?
Test the exact tenant, branch, matter, record, role, and capability boundaries server-side. Visible navigation alone is not authorisation evidence.
Evaluate data retention against your real operating model.
Use representative workflows and request current product evidence for the scope that matters to your firm.