Matter Management Software Requirements for Legal Practices

Matter management software should represent the practice's working record, not simply replace a shared drive with a web form. A disputes matter may contain opponents, counsel, courts, witnesses, experts, undertakings and procedural deadlines; an advisory matter may involve related entities, changing instructions, approvals and deliverables. Both need a durable link between the accepted instruction, the people allowed to act, the work performed, documents relied upon and financial treatment. Requirements therefore begin with the legal and operational lifecycle. A feature list assembled from product demonstrations tends to miss the controls that become important when a conflict, invoice or historical decision must be reconstructed.

Model the matter as a governed record

A matter needs a stable identifier, responsible office and lawyer, work type, client relationship, jurisdiction, status, opening date and applicable terms. Those fields should be effective-dated where responsibility or classification can change. Status is not enough to describe lifecycle: intake, conflict clearance, engagement, active work, dormancy, closure and destruction each have preconditions and permitted actions. Reopening should retain the previous closure decision rather than overwrite it. Custom fields are useful for specialised practices, but uncontrolled additions produce inconsistent reports and hidden mandatory data. Define a core schema, governed extensions and validation rules based on matter type, while retaining who changed each material value and why.

Parties are entities, roles and relationships

The same organisation or person can be a client in one matter, an opponent in another and a related party elsewhere. Store an entity once where identity can be established, then assign matter-specific roles with dates and context. Names require aliases, former names, trading styles and transliterations. Corporate relationships such as parent, subsidiary, beneficial owner and director should be explicit rather than buried in notes, because they affect conflict searches. A party record also contains sensitive personal and contact data, so broad access is not justified merely because the matter title is visible. Duplicate detection needs a review workflow; automatically merging similar names can combine unrelated people and disclose restricted relationships.

Conflict checking is a decision process

A search box is only one part of conflicts. Intake must collect prospective clients, opponents, related entities, key individuals and the nature of the proposed work before confidential detail spreads. Searching should cover aliases and relationships while distinguishing exact identity from a possible match. Results require disposition: who reviewed the candidate, what evidence was considered, whether a waiver or information barrier applies, who approved acceptance and which conditions remain. The system should preserve the search population and decision as at the time of clearance. Re-running against today's names is useful monitoring, but it cannot prove what was checked when the instruction was accepted.

• Record every party as an entity with aliases, then attach dated roles to individual matters.
• Retain conflict queries, candidate matches, reviewer decisions, waivers and acceptance conditions.
• Make matter access inherit from explicit teams and barriers rather than broad organisational groups.
• Link time, documents, deadlines, expenses and bills to the same stable matter identifier.
• Treat closure and destruction as approved workflows with visible holds and unresolved obligations.

Permissions must express ethical boundaries

Role-based access by department is too coarse for restricted matters. Access may depend on an explicit matter team, an information barrier, a need-to-know group or a client-imposed condition. Search results, notifications, recent-item lists, document previews and analytics must apply the same rule as the matter page; leaking a title or party name through a secondary index is still disclosure. Privileged administrators need tightly defined support paths and audited elevation rather than permanent universal visibility. When someone joins or leaves a team, changes must propagate to document stores, exports and search indexes. Permission tests should cover derived artefacts such as email attachments and generated billing narratives, not just canonical records.

Time capture needs provenance and correction

Time entries connect work performed to profitability, client bills and sometimes recoverable costs. Capture the worker, matter, activity, date, duration, narrative, rate context and source without silently converting a timer into a final entry. Narratives may need privilege review or client-specific coding. Edits after submission should preserve the original, editor, reason and approval; billed entries require a controlled adjustment rather than mutation. Mobile and offline capture must resolve duplicate submissions and matter closure cleanly. Targets and reminders can improve completion, but the requirement is an accurate, reviewable record. Surveillance-style activity inference creates noisy evidence and does not replace professional judgement about what work was billable.

Documents need versions, not filename conventions

A legal document record should distinguish a logical document from its versions, renditions and attachments. Each version needs an author, timestamp, source and immutable content hash, while check-out or co-authoring rules prevent accidental forks. Email filing should retain message headers and relationships between the message and attachments. Search requires extracted text, metadata and security trimming, with clear treatment for scanned material and encrypted files. Final, filed, executed and superseded are controlled states rather than words appended to filenames. Links should resolve to the authorised record or a specific frozen version, depending on context, so a citation in advice cannot silently point to later drafting.

The document of record is the version that can be identified, authorised and reproduced, not the file whose name happens to contain the word final.

Disputes require chronology and deadline discipline

Litigation work introduces events with sources, dependencies and consequences. A chronology entry should link to the document or testimony supporting it and separate asserted dates from confirmed dates. Court deadlines need jurisdiction-aware rules, source orders, responsible owners, reminders and recorded completion. Automatic calculations can assist but should expose the rule and permit authorised review rather than present a date without derivation. Tasks, hearings, limitation dates and undertakings are different obligations and should not share an undifferentiated calendar model. Changes to a hearing or order must retain the previous date and notification trail, because later review may depend on when the team learned that a deadline moved.

Advisory work needs scope and deliverable control

For advisory practices, scope can change through emails, calls and supplementary instructions. Record the accepted scope, assumptions, client decision-makers, dependencies and agreed deliverables alongside later variations. Advice should identify its status, audience, jurisdiction and the facts on which it relied. Reusable precedents need their own ownership and review lifecycle; copying an old matter's document can carry obsolete clauses or client information. Matter templates can initialise phases and checklists, but they should not conceal which steps were completed, waived or considered inapplicable. The system should make departures visible while allowing professional judgement, rather than forcing every instruction through a single rigid process.

Money, trust and billing remain connected but distinct

Matter management often exchanges data with accounting rather than becoming the ledger. Client and matter identifiers, time, expenses, fee arrangements and billing status need controlled interfaces. Trust or client money requires jurisdiction-specific ledger controls, authorisation and reconciliation that a generic matter balance cannot provide. Rate changes should be effective-dated, and a bill should retain the rates, narratives, tax treatment and approval used when it was issued. Write-offs, transfers and credit notes need reasons and links to accounting entries. Integration failures must be visible and replayable; silently dropping a time entry or creating duplicate disbursements undermines both the bill and the matter history.

Retention begins at creation

Retention cannot be added at closure if records lack classification, ownership and hold status. Define which emails, drafts, notes, recordings and exports form part of the file, and distinguish operational convenience copies from records. Closure should verify final billing, client money, undertakings, original documents, future dates and responsible approval. The resulting retention schedule may depend on matter type, jurisdiction, client terms and the age or capacity of a party. Legal holds suspend eligible destruction without changing the underlying schedule. When destruction becomes due, produce a reviewable population, obtain approval, delete from searchable and derivative stores, and retain evidence of disposition without retaining the destroyed substance.

Test complete matter histories

Acceptance testing should follow realistic histories: prospective instruction, ambiguous party match, conditional clearance, team changes, document drafting, time correction, scope variation, billing, closure, hold and eventual disposition. Include restricted matters, merged party candidates, failed integrations and reopened work. Verify that audit history answers who knew, changed and approved what at the relevant time. Migration deserves the same approach; folder counts and row totals do not prove that document versions, party roles or barriers survived. A sound implementation gives the practice one coherent matter record while preserving the boundaries between legal judgement, document evidence, financial accounting and records governance.