Legal Practice Management
The date changed. The old date is still on the file.
A custom practice system built around one matter — who owns it, what is due and on whose instruction, which version is current, and what the record still refuses to claim on its own.
MF-2048Commercial agreement review
Next deadline
Response draft
Filed externally
No confirmation
Only an external confirmation can establish this.
Legal outcome
Recorded only from an authoritative source
Never derived from the matter state.
Conflict search2 matches · Cleared by the firm
Next22 Sep · A. Rao
The client asked for longer, so the deadline is 22 September — and 18 September is still on the file. Old values do not disappear.ILLUSTRATIVE INTERFACE · SAMPLE DATA
Enquiry and engagement
An enquiry is not a client, and a client is not an open matter
Three different records with three different obligations. The firm decides where each line is crossed, and the software’s job is to make the decision explicit rather than to make it automatically.
The enquiry
A relationship, not yet work.
Who asked, what about, where they came from and who is following up — a CRM record with its own purpose.
The firm’s decision
A person, on the record.
Conflicts reviewed, terms agreed, engagement confirmed. Nothing opens a matter except somebody deciding it should.
The matter file
The operating record.
MF-2048, with an owner, a practice area, deadlines that carry sources, and documents that carry versions.
Conflict search
A search compares names and related parties against the firm’s own records and shows what it found. Two matches is a prompt to look; zero matches is a search result. Neither is a professional clearance — the firm applies its own conflict policy and records the decision against a name.
Where enquiries come from — a CRM, a website form, a referral, a phone call — is a scoping decision. We confirm what each source can expose before defining the connection.
What is legal practice management software?
Software that runs a practice’s matters: the intake and engagement decision that opens one, the matter’s owner and team, the deadlines and events with their sources, the documents and their versions and review states, what is visible to the client and what is not, and the handoffs to whichever systems bill, communicate or file. It is an operating record, not a source of legal advice.
Why "matter" rather than "case"?
Because most legal work is not litigation. The category treats case management as the litigation-leaning half — court tracking, client files, billable hours — while matter covers all legal work, including advisory, transactional, corporate and contract work. A practice doing agreements and corporate work should not have to describe them as cases to use the system.
When does an enquiry become a matter?
When the firm says it does. Conflicts are reviewed, terms are agreed, and somebody records that an engagement has been confirmed — and only then does a matter file open with an owner and a number. The system makes that moment explicit and attributable rather than letting an enquiry drift into being treated as work.
Does no conflict-search match mean the matter is cleared?
No. A search reports what it found in the records it can see. Professional conflict clearance is a judgement the firm makes under its own policy and obligations, and the record stores that decision with the name of whoever made it. Software that turned an empty search result into a clearance would be making a professional determination it has no standing to make.
Deadlines
A date on its own is not defensible three months later
What is due, when it was decided, what it was based on, and who recorded it. When the date moves, the previous one stays exactly where it was — because the question that gets asked later is never only "when is it due".
The system records deadlines and their sources. It does not calculate statutory limitation periods, apply court rules, or compute jurisdiction-specific dates — those depend on facts and law the practice owns, and software that quietly guessed them would be the most dangerous thing on this page.
Can a deadline change without losing the previous one?
That is the design. The current date is the newest entry in a history that only grows, and every entry keeps what it was based on and who recorded it. A changed deadline is a new line, never an edit — so the file can still show what was due, when it moved and why, long after everybody has forgotten.
Can the software calculate court deadlines automatically?
No, not by default, and we would be careful about any system that says it can. Limitation periods and court-rule calculations depend on jurisdiction, procedure and the facts of the matter. The system records the date the practice sets, what it was based on and who set it. Where a firm has genuinely fixed internal rules, those can be scoped and configured — as the firm’s rules, applied consistently.
Can hearings, meetings and other matter events be tracked?
Yes — a matter event is deliberately broader than a hearing, because most matters do not have hearings. A filing deadline, a client review, a transaction milestone, a counterparty response and a court date are all events with a date, a source and an owner, held on the same record.
Documents
A document in the file is not a document that was filed
It can be drafted, revised, internally reviewed and approved by the client, and none of that is evidence that anybody outside the firm has received it. Only a confirmation from outside can establish that, and until one exists the record says what the document actually is.
What the firm can see
Document state
Approved draft
Versions
v3Client comments incorporated15 Sep
v2Internal edits13 Sep
v1Initial draft12 Sep
Filed is reachable only when a confirmation from outside the firm is recorded against the matter. Where a court, registry or counterparty system exposes a suitable interface and access is authorised, that connection is confirmed before it is scoped — it is never assumed.
Does uploading a document mean it has been filed?
No, and collapsing the two is how a practice discovers a filing was never made. Being in the matter file, internally reviewed and client-approved are all internal facts. Filed is an external fact that only an external confirmation can establish, so the state cannot reach it without one.
Can documents be versioned?
Yes, and earlier versions stay. Version three being current does not make it the only version — version one and version two remain on the matter with their dates and what changed, because the question later is usually what the draft said before, not what it says now.
Can it connect to court or e-filing platforms, or to e-signature?
Where those systems expose a suitable interface and the practice is authorised to use it, a connection is confirmed for feasibility before it is scoped — never listed as included capability. And an e-signature is the provider’s confirmation, not a legal opinion: whether a signed document is enforceable depends on the provider, the document, the jurisdiction and the circumstances, which is the practice’s call and not the software’s.
Internal and shared
One matter, two audiences, and visibility is a decision
A matter file holds working notes, drafts and internal reasoning alongside the things a client should see. Nothing crosses that line because of where it is stored — it crosses because somebody decided it should.
Access, permissions, sharing and retention controls support the practice’s own confidentiality model. Whether a communication or document is privileged depends on the actual legal and professional circumstances — that is a matter of law, not a setting in software.
Is everything in a matter visible to the client?
No, and it should not be. Internal notes, working drafts and matter reasoning stay inside the firm; requests, approved documents and whatever progress the practice chooses to surface can be shared. Visibility is an explicit state on each item rather than a consequence of where it happens to be stored.
Does the software create or guarantee privilege or confidentiality?
No. It provides authentication, permissions, controlled sharing, retention and a history of who did what — controls that support a practice’s confidentiality model. Whether particular information is privileged is determined by law and professional circumstance, and no software can confer that status.
Can clients get a portal?
A controlled client-facing surface can show the selected information the firm decides to share — matter progress, requests, approved documents. It is a view onto part of this record, never the record itself, and what appears there is chosen deliberately rather than mirrored automatically.
Closing a matter
Closed is an operational state. It is not a verdict.
A matter can close because the work finished, the transaction completed, the client withdrew, or it moved to another firm. None of those is won, lost or successful, and an operating record that inferred one would be putting words in a lawyer’s mouth.
What closing means here
Legal outcome
Recorded only from an authoritative source
Recorded only from an authoritative source. Never derived from the matter state.
Closed is not deleted. History, documents, permissions and the record of who did what survive closure, because the questions that arrive afterwards are usually about what happened, not about what is happening.
Does closing a matter mean the case was won?
No. Closing records that the practice has stopped working the matter — because the work finished, a transaction completed, the client withdrew or it transferred elsewhere. Won, lost, settled and approved are legal conclusions that come from an authoritative source and are recorded as such, never inferred from an operational status.
Does the system score matters or predict outcomes?
No. There is no success probability, no case-strength score and no predictive analytics on this page or in the Product. Those would dress up a guess as an assessment, and in a legal practice that is worse than having no number at all.
What happens to a matter after it closes?
It stays. Closed is not deleted — history, documents, permissions and the audit of who did what survive, under whatever retention the firm and its jurisdiction require. We do not invent universal retention rules; the practice sets the policy and the system applies it.
Where it sits
The practice runs the matter. Everything else is somebody else’s job.
Legal work touches a relationship system, a client-facing surface, a billing workflow, external authorities and the law itself. Naming each of them is what keeps the operating record honest about the one thing it does own.
CRM wins and holds the relationship. This operates the matter.
What is the difference between legal practice management and a CRM?
A CRM owns the relationship — enquiries, sources, follow-up, the pipeline that turns a prospect into a client. Legal practice management owns the work once the firm has agreed to do it: the matter, its team, its deadlines and their sources, its documents and versions, and its closure. They connect at engagement confirmation, and neither is a substitute for the other.
Can AI summarise matter information or give legal advice?
Summarising matter notes, retrieving approved internal knowledge or suggesting tasks from a document can be scoped, with the output reviewed by a person before it is relied on. Legal advice, strategy, conflict determinations, privilege calls, deadline calculations and outcome predictions are not things we will build a machine to do — they are professional judgements that belong to a qualified lawyer.
Can client funds or trust accounting be managed?
No. Client money, trust and escrow accounting are regulated obligations with jurisdiction-specific rules and audit requirements, and this Product does not claim them. It can hold matter time, expense and fee context and hand it to billing; anything touching client funds belongs to systems and professionals built for it.
Is this the same as a legal research tool?
No. Legal research covers statutes, judgements, authority and citation — a different category with different sources. This holds what the practice did on a matter. Where a firm uses a research provider, integrating it is a scoped piece of work against that provider’s interface.
Connect · migrate · choose
Most practices should use an established platform.
Mature legal practice management products handle standard matter, time, billing and document workflows, come with the email, calendar and document integrations firms depend on, and deploy quickly. If your way of working fits one, that is the better purchase, and it is the one we will point you at.
Use an established platform when
- Standard matter, time and billing workflows already fit how you work.
- Legal billing is mature or complex and you need it out of the box.
- Email, calendar, document and e-signature integrations matter and already exist there.
- You need to be running in weeks with vendor support behind it.
- Security and retention requirements map cleanly onto an established provider.
Build custom when
- The matter workflow is genuinely unusual and the tools force daily workarounds.
- Several internal or proprietary systems have to agree about one matter.
- The separation between internal work and what a client sees needs to be exact.
- A bounded custom layer beside an existing platform is the honest answer.
- The client or internal experience is part of how the practice differentiates.
The clearest signal is a practice keeping a parallel spreadsheet of deadlines because nobody trusts the ones in the system.
We check what each current system can export before defining the migration. Client and matter data moves only where the practice is authorised to move it, historical deadlines and document metadata arrive as a record of what a previous system held rather than as re-verified fact, and anything that does not reconcile is listed rather than silently imported. Email archives, filing histories and every historical version are rarely fully exportable, and we say so before the project rather than after it.
Legal data is sensitive and much of it is held under obligations the practice carries. Authentication, roles, permissions, controlled sharing, retention, deletion and a history of who did what are scoped around those actual obligations. We claim no certification, accreditation or regulatory approval the work has not earned.
Does every law firm need custom software?
No, and most do not. Established practice management platforms are mature, integrate widely and deploy quickly, and for a firm working in a fairly standard way one of them is the better answer. Custom earns its place when the matter workflow cannot be expressed in one, when several systems must agree about a single matter, when the internal-versus-client boundary has to be exact, or when a bounded layer beside an existing platform is genuinely the right shape.
Can multiple practice areas or offices use one system?
Yes, where scoped: offices, practice areas, teams, matters, clients, permissions and templates can be separated with authorised central views across them. What that does not automatically include is cross-jurisdiction compliance, consolidated trust accounting or universal legal rules — each is its own decision and its own scope.
Can time and billing context be tracked?
A matter can carry time entries, expenses and fee context — duration, person, matter, description, billable state — and hand them to whatever raises the invoice. It is deliberately not a billing product, and it does not touch trust accounting, tax compliance, settlement or the general ledger.
Can existing client and matter data migrate?
Clients, matters, owners, deadlines, events, document metadata and time records can be mapped and loaded, and we check first what each current system can export. Data moves only where the practice is authorised to move it, and email archives, filing histories and complete version trails are rarely fully exportable — which we say before the project rather than after it.
Who owns the system and the data?
The practice does. Source-code access, hosting, data ownership, exports, backups, handover and any third-party dependencies are defined in the project scope rather than assumed, and the data is exportable.
What determines the cost and timeline?
How many practice areas and matter types, how many users and offices and how tightly permissions must be enforced, how much of intake and conflict review the system carries, how deadlines and events are modelled, how far the document lifecycle goes, whether there is a client portal and what it may show, which integrations are real, and how much history migrates.
Selected work
Records, states and the interfaces people operate them in
A matter file is a structured record with derived state, provenance on its fields and a controlled boundary between internal and shared. These are three builds where exactly that discipline was the deliverable.
Questions
Legal practice systems, answered
What does legal practice management software do?
It runs a practice’s matters: the engagement decision that opens one, its owner and team, its deadlines and events with their sources, its documents and versions and review states, what the client can see, and the handoffs to whatever bills or communicates. It is an operating record, not a source of legal advice.
What is the difference between matter management and case management?
Case management leans towards litigation — court dates, client files, billable hours. Matter management covers all legal work, including advisory, transactional and corporate. This Product uses matter because most legal work is not a case.
Is this a CRM?
No. A CRM owns the enquiry and the relationship before an engagement exists. This owns the work after the firm agrees to do it. They connect at engagement confirmation.
Can a deadline be changed without losing the earlier one?
Yes — that is the design. The current date is the newest entry in a history that only grows, and every entry keeps what it was based on and who recorded it. A change is a new line, never an edit.
Does it calculate court deadlines automatically?
No. Limitation periods and court-rule calculations depend on jurisdiction, procedure and the facts. The system records the date the practice sets, its source and its owner; firm-specific rules can be configured as the firm’s rules.
Does uploading a document mean it was filed?
No. Being in the matter file, internally reviewed and client-approved are internal facts. Filed is external, and only a recorded confirmation from outside the firm can establish it.
Does closing a matter mean it was won?
No. Closing means the practice stopped working it. Won, lost and settled are legal conclusions recorded from an authoritative source, never inferred from an operational state.
Can AI give legal advice or predict outcomes?
No. Summarisation, approved knowledge retrieval and task suggestions can be scoped with human review. Legal advice, strategy, conflict determinations, privilege calls and outcome predictions belong to a qualified lawyer, and we will not build a machine to imitate them.
Should we build custom or use an established platform?
Use an established platform if standard matter, time and billing workflows fit and you need mature integrations — that is most firms. Build when the workflow cannot be expressed, when several systems must agree about one matter, or when a bounded layer beside an existing platform is the right shape.
Start
Bring one matter, and the deadline nobody could explain
The fastest way to scope a practice build is a real matter with real friction in it. Bring one file, and the date somebody had to reconstruct from email.
- What kinds of matter you run, and how differently each one behaves.
- How a deadline gets set today, and who would know why it moved.
- Where documents live, and how you know which version is current.
- What a client can see, and how that is decided.
- What you would keep of your current tools, and what your team works around.