Choosing a Legal Case Management System: A Buyer's Checklist
Selecting a legal case management system is a decision that a law firm will live with for years. The software will hold the firm's matters, client records, documents, deadlines and billing history, and every fee earner and member of staff will use it daily. A poor choice produces a long tail of costs: re-entry of data, workarounds, resistance from staff, security exposure and, in the worst case, a migration to a different product after the firm has already invested heavily in the first. A sound choice is largely the product of discipline in the selection process rather than of any particular feature list.
This article offers a structured checklist for evaluating a legal case management system. It begins with the firm's own requirements, because a buyer who has not written down what the firm needs will be guided by the vendor's demonstration instead. It then addresses functionality, security and confidentiality, data migration, integration, pricing models, support and the contract, and the conduct of a proper trial. Where a point depends on the law or professional rules of a particular jurisdiction, the reader should consult those rules, as the software cannot discharge professional obligations on the firm's behalf.
The checklist is intended for solo practitioners, small and mid-sized firms and in-house or public sector legal teams. It does not recommend any product. Its purpose is to enable the practitioner to question any product, including the one that the firm eventually chooses, on the points that matter.
Start with the firm's own requirements
Before looking at any product, the firm should document how it works now and where the work is going wrong. The exercise need not be elaborate. The principal, a senior fee earner and the person who manages administration should each describe the life of a typical matter from the first enquiry to the final bill and the closing of the file, and should identify the points at which time is lost, information is duplicated, deadlines are at risk or errors occur.
Questions to answer before any demonstration
Which practice areas does the firm handle, and do they have particular workflow needs, such as court deadlines in litigation, completion statements in conveyancing, or contract lifecycle tracking in commercial work?
How many people will use the system, and in what roles: attorneys, paralegals, administrators, accounting staff, and, perhaps, external collaborators and clients?
What are the largest sources of wasted time today: searching for documents, re-keying client details, chasing approvals, preparing bills, or reconciling accounts?
What are the firm's mandatory obligations that technology must support: conflict checking, client money accounting, limitation tracking, retention of records, and data protection?
What must the system be able to do from the first day, and what can wait?
The answers should be turned into a requirements list in three categories: essential, important and desirable. The list becomes the scoring sheet against which every candidate system is assessed. It also protects the firm from being drawn to impressive features that it will never use.
Functionality that matters for legal work
The term legal case management system is used loosely, and products vary from simple matter lists to comprehensive platforms combining case management, document management, billing and client communication. The following areas should be assessed on their substance, by asking the vendor to demonstrate each using the firm's own scenarios, and not only by reading a feature table.
Matter and client management
The system should allow a matter to be opened quickly with the right data, linked to one or more clients and related parties, and organised by practice area. Look for configurable matter types, custom fields, a clear matter status, and a single view that shows the parties, documents, tasks, deadlines, time and billing for a matter. Check how the system handles related matters, such as a client with several files, and how it records opposing parties and their representatives for conflict checking.
Conflict checking
A conflict check is only as good as the data searched and the search method. Test whether the system searches all clients, related parties, opposing parties and former clients, whether it recognises variations of names, and whether the results are recorded on the matter file. Ask whether a conflict search can be run before a matter is opened, so that the firm does not create a record for a client it cannot accept.
Documents and templates
Assess how documents are stored, versioned, searched and secured. Check whether documents can be assembled from templates populated by matter data, whether emails can be saved to the matter easily, and whether the system maintains a version history. For firms with significant commercial work, a contract repository with clause and date tracking, and reminders for renewal and expiry, may be an essential requirement.
Tasks, diary and deadlines
The diary function is the firm's safeguard against missed limitation periods and court deadlines. Evaluate how deadlines are created, whether they can be generated from rule-based or template-based sequences, how reminders reach the responsible person, and how the system escalates an overdue task. Ask what happens when a fee earner leaves the firm or is absent: can their tasks be reassigned in bulk, and is there a record of who did what?
Time recording and billing
The system should support the firm's billing methods, whether hourly, fixed fee, staged or contingent. Check that time entries can be captured with minimal friction, including by timer and on a mobile device, that narratives can be edited before billing, that disbursements are recorded and attributed, that invoices can be generated in the firm's format and that payments are tracked against invoices.
Client money accounting
If the system includes trust or client account features, test them with the specific rules of the firm's regulator in mind. The software must separate client funds from office funds, maintain client ledgers, record transfers with authority, produce the reports that the rules require and make reconciliation straightforward. A system that does not support the firm's accounting rules should not be used to record client money, regardless of its other features. If the system does not offer client accounting, the firm should confirm that it integrates properly with whatever does.
Client portal and e-signature
A client portal can reduce routine enquiries by allowing clients to see the status of a matter, exchange documents securely and sign documents electronically. Consider whether the portal is simple enough for non-technical clients, whether access is controlled by matter, and whether e-signatures produced by the system are suitable for the categories of document the firm handles. The firm must be satisfied as to the legal effect of electronic signatures under the law of its own jurisdiction for each document type, since some instruments require particular formalities.
Reporting
Management reporting should answer the questions a principal actually asks: work in progress, unbilled time, billed and collected fees by fee earner, ageing of receivables, matter profitability, caseload by status, and matters with no recent activity. Request a demonstration using realistic data, and check whether reports can be exported.
Security, confidentiality and data protection
A legal case management system holds privileged and confidential information. The firm remains responsible for it, and the choice of system must be one that the principal could explain to a regulator, a client or an insurer. The vendor should answer the following questions in writing.
Where is the data stored, in which country, and may the vendor move it? Some jurisdictions or clients restrict the transfer of personal data abroad, and some firms have contractual undertakings about it.
How is data encrypted in transit and at rest?
How is access controlled? Look for individual user accounts, role-based permissions, the ability to restrict a matter to named users, multi-factor authentication and session controls.
Is there an audit trail showing who accessed, changed or deleted records?
How are backups made, how often, where are they kept, and how quickly can the firm's data be restored?
What is the vendor's process for notifying customers of a security incident, and within what time?
Who at the vendor can access the firm's data, under what conditions, and is that access logged?
What happens to the data when the contract ends: in what format can it be exported, within what time, and when is it deleted from the vendor's systems?
The firm should be cautious about assertions of certification or compliance. If a vendor claims that its service meets a recognised standard, the firm should ask for the documentation that supports the claim and for the scope of the certification, and should not treat a logo on a website as evidence. Equally, the absence of a certification does not of itself mean that a product is insecure; what matters is the substance of the controls and the vendor's willingness to describe them in the contract.
The data processing terms should be reviewed by a lawyer. They should identify the vendor as a processor acting on the firm's instructions, restrict the use of data to providing the service, impose confidentiality obligations on the vendor's personnel, address sub-processors and set out the vendor's duties on breach and on termination.
Data migration and implementation
Many firms underestimate the effort of moving from existing records to a new system. Migration is the stage at which projects are delayed and relationships with vendors become strained, so it should be explored in detail before signature.
Inventory the existing data. List the sources: spreadsheets, a previous system, shared drives, email folders, paper files, accounting software. Estimate the volume and the quality of each.
Decide what to migrate. Not every historical record needs to be moved. Many firms migrate open matters in full, closed matters in summary, and retain the archive in a secure repository for the retention period.
Ask the vendor what it will do and what the firm must do. Does the vendor provide import tools or a migration service, and at what cost? What formats are accepted? Who is responsible for cleansing duplicates and correcting errors?
Plan a trial migration. Test with a sample of matters, check the results with the fee earners who know the files, and correct the mapping before migrating the remainder.
Plan the cut-over. Decide the date, the freeze on new entries in the old system, and the fallback plan if the migration fails.
Train the users. Training should be role-specific, scheduled before go-live and repeated after the first month, when users know what they do not understand.
A realistic implementation plan names an owner within the firm, usually a principal or practice manager with authority to make decisions, and allocates time for the work. A system imposed on staff without involvement or training will be used inconsistently, and the firm will not obtain the benefit it paid for.
Integration and portability
The firm already uses email, calendars, accounting software and document formats, and the new system should work with them. Ask which integrations are supported natively and which require third-party connectors, and test the integrations that matter most, particularly email filing and calendar synchronisation.
Portability is the counterpart to integration. A system that keeps the firm's data in a form that cannot be exported, or that charges heavily for export, creates a dependency that the firm should avoid. Ask for a sample export of a dataset, and check that it contains the matter details, documents with their folder structure, notes, time entries and billing history in a usable form. Confirm in the contract that the firm owns its data and may retrieve it on demand and on termination.
Understanding pricing models
Pricing for legal software is commonly structured per user per month, per firm, by tier of features, by storage, or by a combination. The headline price is rarely the whole cost, and the firm should model the total cost of ownership over a period of at least three years.
Pricing element | Question to ask |
|---|---|
Licence or subscription | Is the price per user, per firm or by feature tier? What happens to the price as the firm adds staff? |
Implementation and migration | Is there a set-up fee, and is data migration included or separately charged? |
Training | Is training included, and for how many sessions or users? |
Add-on modules | Are billing, client portal, e-signature, document assembly or reporting priced separately? |
Storage and usage | Is there a cap on storage, documents or signatures, with overage charges? |
Support | Is support included, and at what service levels? |
Price changes | Is there a cap on annual increases, and what notice must be given? |
Exit | Is there a charge for data export or for final-month access? |
Per-user pricing compared with per-firm pricing
Per-user pricing is the most common model, and it has a structural consequence: every additional user raises the cost, so firms are tempted to limit access to the system to save money. That can be counterproductive, because an administrator, a part-time paralegal or a consultant who cannot log in will work outside the system, and the firm's records become incomplete. Per-firm pricing with unlimited users removes the incentive to restrict access and makes cost more predictable as the firm grows.
The following is illustrative arithmetic only, and not market data. Suppose a firm of four attorneys, three paralegals and two administrators is offered a per-user plan at a monthly price of 30 units per user. Nine users would cost 270 units a month, or 3,240 units a year. If the firm then adds a part-time bookkeeper and two junior paralegals, twelve users would cost 360 units a month, or 4,320 units a year, an increase of 1,080 units. Under a per-firm plan priced at, say, 250 units a month, the cost for nine or twelve users would be the same, 3,000 units a year. The firm should substitute actual quotations, since the break-even point between the two models depends on the firm's size and the real prices offered, and a very small firm may find a per-user plan cheaper.
Support, reliability and the vendor
The software is only part of the offering. The firm depends on the vendor for support, uptime, development and continuity, and should assess those on evidence.
Support. What channels are available, in which hours and time zones, and what response times does the vendor commit to? Does support include help with configuration, or only technical faults?
Availability. What availability does the vendor commit to, how is downtime measured and communicated, and what remedy does the firm have if the commitment is missed?
Roadmap and stability. How often is the product updated, how are changes communicated, and can the firm influence development?
Vendor stability. How long has the vendor operated, and what arrangements exist if it ceases to trade? A data escrow or export commitment is relevant here.
References. Ask for contacts at firms of similar size and practice mix, and speak to them. Ask what they wish they had known before buying.
Running a proper trial
A demonstration shows the product at its best. A trial shows how it behaves in the firm's hands. Request a trial with the firm's own data, or a realistic sample, and design it as a test with defined tasks and criteria.
Choose two or three typical matters from different practice areas and set them up in each candidate system.
Assign a group of testers that includes a sceptic, a junior user and an administrator, not only the principal.
Have each tester complete a prescribed set of tasks: opening a matter with a conflict check, saving an email, drafting a document from a template, recording time, setting a deadline, generating an invoice and sharing a document with a client.
Score each task against the requirements list, recording the time taken and the difficulties encountered.
Test the export function, and test the support channel by raising a genuine question.
Review the scores and the testers' qualitative comments together, and weigh essential requirements more heavily than desirable ones.
Contract terms to examine
The contract allocates the risks of the relationship, and a lawyer should read it with the care they would give a client's commercial agreement. Particular attention should be given to the following terms.
Term and renewal. Is the commitment monthly or annual? Does it renew automatically, and on what notice may the firm terminate?
Service levels and remedies. Are availability and support commitments binding, and what credits or termination rights follow a failure?
Data ownership, confidentiality and processing. Is it clear that the firm owns the data and that the vendor may use it only to provide the service?
Security obligations and incident notification.
Limitation of liability. Vendors commonly cap liability at fees paid, and the firm should consider whether the cap is acceptable given the sensitivity of the data. Check whether data breach is excluded from the cap or carved out.
Intellectual property. The firm's templates and content should remain the firm's.
Termination and exit. The firm should be able to export all data in a usable format on termination for any reason, within a stated period and at no excessive cost.
Governing law and jurisdiction. Consider whether disputes would be resolved in a forum that is practical for the firm.
Practical next steps
Write the requirements list in three categories, with input from fee earners and administrators, and attach a weight to each essential item.
Identify the firm's regulatory constraints on client money, record retention, confidentiality and the location of data, and make them pass or fail criteria.
Shortlist no more than three systems, and send each a written questionnaire covering security, data location, export, pricing and support.
Obtain full written pricing, including implementation, storage, add-ons and renewal terms, and prepare a three-year cost comparison.
Run a structured trial with real scenarios and a mixed group of testers, and score the results.
Speak to reference customers of similar size.
Have the contract and data processing terms reviewed before signature, and negotiate exit and incident terms in particular.
Prepare the migration and training plan, name an internal owner and set the go-live date.
How the right system supports the firm
A well-chosen system gives a firm a single, searchable and auditable record of every matter, and reduces the administrative effort that diverts fee earners from legal work. Legalytech is a cloud practice management platform that brings matters, clients, documents, a contract repository, a client portal, e-signature and billing into one environment, and the checklist above is intended to be applied to it as rigorously as to any other candidate.
This article is provided for general information only and does not constitute legal advice. Practitioners should consult the rules of their own jurisdiction and regulator.
Comments