Litigation Support Software: Options and Limits 2026

What is Litigation Support Software

Litigation support software collects, reviews, organises or presents evidence in a dispute. General practice management covers a firm’s business operations, including billing and client administration. Buying the latter does not automatically supply a discovery review workflow.

Apply the same criteria to each category, while asking what the output actually proves.

Category	Data Inputs and Review Workflow	Security and Australian Hosting	Court Outputs	Pricing and Support
eDiscovery and document review	Email, native files and PDFs; processing, relevance coding and privilege decisions	Relativity aiR and Everlaw have Australian hosting options; assess AI processing and support access separately	Productions with document identifiers, redactions and export metadata	Relativity has pay-as-you-go and term commitments; Everlaw charges by hosted data; specialist support can add cost
Matter management	Matter details, tasks, invoices and working documents; owners track deadlines and spend	Xakia permits Australian Azure hosting; LawVu has regional stacks and separate AI processing arrangements	Matter status and budget reports support administration	Xakia uses user subscriptions; LawVu quotes by users and capabilities; both provide support
Court books and chronologies	Selected documents and dated facts; indexing, pagination and source links	Bundledocs permits Australian storage; Litigation Ready identifies Sydney servers for Australian use	Indexed bundles and source-linked timelines	Bundledocs has subscription and quoted business options; Litigation Ready uses annual user subscriptions
Financial analysis	Bank-statement PDFs or extracted transactions; account consolidation and transfer analysis	Software requires its own IT assessment; a service engagement must resolve handling arrangements	Schedules and findings with source references support financial evidence preparation	Software licences fund team-operated analysis; FinTrace quotes per matter and delivers the analysis

The product descriptions below rest on published vendor documentation. The comparison concerns features and delivery models, with no measured performance ranking.

Document Review Software and eDiscovery Platforms

Document review software helps lawyers decide which documents answer the issues in a dispute and which attract privilege. An eDiscovery platform also handles stages before and after review. Buying an end-to-end platform can avoid repeatedly moving evidence between tools.

An eDiscovery workflow starts with preservation and collection from relevant custodians and systems. Processing extracts text and metadata, identifies duplicates and prepares searchable records. Lawyers then review relevance and privilege, apply redactions and export a production in the agreed format.

Review Platforms by Operating Model

Relativity aiR, formerly RelativityOne, suits teams needing a configurable collection-to-production workflow with dedicated review administration. Its documentation covers legal holds, collection, processing and production. Australian hosting is available. Relativity’s pricing page describes pay-as-you-go licensing or term commitments and global support.

Everlaw combines review and production with Storybuilder for facts, timelines and testimony. Its hosted-data pricing includes user licences, processing and productions. Everlaw’s data-processing terms identify a Sydney hosting region. Its subprocessor list distinguishes that storage from other AI and support processing locations.

Reveal suits organisations that need control over the infrastructure as well as review functionality. Its Private Deployment runs in customer-controlled cloud or on-premises environments. Review assignments, redaction and production are documented capabilities. Its security information identifies ISO 27001 and SOC 2 Type 2 certifications.

A private Reveal deployment lets the organisation choose Australian infrastructure, with operational responsibility for that environment. Its deployment documentation sets technical requirements, while sales and support arrangements require a scoped enterprise proposal. Location control alone does not replace access controls or disaster recovery.

Litigation Ready has search, annotations and document sharing for prepared PDFs. A native email collection with metadata and production specifications needs the deeper processing capabilities of an eDiscovery platform. These are different operating tiers, not a ranking by accuracy.

Cloud software as a service puts infrastructure maintenance with the vendor. On-premises deployment puts more responsibility on your IT team. Australian data residency must cover storage, backups and processing, including AI services. Overseas support access also needs a decision under the matter’s confidentiality obligations.

Technology-Assisted Review

Technology-assisted review uses reviewers’ relevance decisions to train a system that prioritises further documents. It differs from asking a generative AI system to summarise a bundle. The review protocol must define the population, validation method and treatment of privilege.

Australian courts have accepted this approach in large matters. The Victorian Supreme Court’s discussion of McConnell Dowell Constructors v Santam [2016] VSC 734 describes predictive coding protocols agreed through a special referee. Its technology practice note recognises technology-assisted review for reasonable searches in larger cases. Court orders and the particular discovery obligation still govern the process.

Litigation Management Software

Litigation management software tracks responsibility for a dispute: deadlines, tasks, budgets, external counsel costs and reports to the business. It helps in-house counsel see which matters need attention. A review platform answers a different question about the documents inside a matter.

Xakia has matter and task tracking, dispute management, budgets and reporting. Its vendor case studies include Australian in-house teams, including Cancer Council Queensland. Xakia’s trust centre permits Australian hosting. Subscription plans use per-user pricing, with support included and some capabilities dependent on the plan.

LawVu combines matter intake and documents with reporting, with spend management in its broader offering. Its plans use quoted pricing based on users and capabilities. Regional hosting choices and round-the-clock support are documented. LawVu’s billing-guidelines AI documentation specifies European processing for Australian customers, showing why storage location and AI processing need separate assessment.

Litigation document management software keeps working files organised with permissions and version history. Xakia’s document management includes version control and integrations with iManage and NetDocuments on specified plans. That filing workflow does not itself establish a complete discovery search or a privilege decision.

Use matter management for deadline and cost control. Use an eDiscovery platform where document-level coding, production metadata and review audit trails drive the dispute. Integrations can connect the systems, but a shared matter name does not mean both hold the same evidence history.

Evidence Management Software and Court Book Tools

Evidence management software keeps exhibits identifiable and accessible. Court book tools assemble selected material into an indexed, paginated bundle for a hearing. They work on the documents the legal team selects, after relevance and privilege decisions.

Bundledocs creates bundles with sections, an index and page numbering. Its security page permits Australian Azure storage and describes encryption in transit and at rest. It has a cloud subscription model, quoted business options and an on-premises version. Training material is available online.

Litigation Ready combines document sharing with court books, indexing and annotations. Its feature pages also describe a chronology tool with links to source documents. Australian users’ servers are in Sydney, according to its security knowledge base. Annual user subscriptions include support, with administration training on firm plans.

For an electronic Federal Court book, apply GPN-eBOOKS. It requires searchable, copyable text and correct landscape orientation. The judge’s chambers specify the format: a separate index with relative links to attachments, or one PDF with bookmarks and internal relative links.

The applicable format controls sequential pagination, index entries and document bookmarks. Match displayed page numbers with other supplied versions and bookmark affidavit annexures as required. GPN-TECH also governs planning technology for the proceeding. A vendor’s court-ready label does not replace these requirements or the judge’s directions.

Legal chronology software builds a dated fact timeline with the source documents beside each entry. Litigation Ready and Everlaw’s Storybuilder cover this work. Australian provider Adio documents using Everlaw for discovery and trial work. Distinguish the document’s date from the event it records, and identify disputed facts within the chronology.

The court book preparation guide explains the preparation workflow beyond the choice of software.

AI Litigation Support Software

AI tools in litigation support summarise documents and help draft chronologies. Review teams also use them to prioritise documents. Relativity describes AI review, privilege and case-strategy products. Everlaw describes first-pass coding suggestions and matter-wide questions. Litigation Ready includes document summaries and source-linked chronology features in its published offering.

Advanced uses still need a named human decision.

AI Use	Useful Output	Human Check
Cluster a large production by topic	Groups of related documents for review allocation	A review lead checks coverage and samples documents outside the clusters
Compare witness accounts	Candidate inconsistencies with source passages	A lawyer checks the complete passage, context and whether the accounts address the same event
First-pass privilege review	Documents flagged for privilege assessment	A lawyer makes the privilege decision and checks attachments and communication chains
Draft a chronology	Proposed events with document references	The matter lawyer confirms event dates, sources and the distinction between fact and inference

The NSW Supreme Court’s SC Gen 23 permits preparatory tasks such as chronologies and document summaries subject to confidentiality controls. It prohibits AI-generated witness evidence and AI rephrasing of that evidence. The note requires verification of authorities and evidence references in submissions, beyond using AI alone.

SC Gen 23 generally requires prior leave for AI preparation of expert-report content. Specific pre-filing reports have a separate leave procedure. In the Federal Court, GPN-AI requires the responsible person to confirm factual support, authorities and chronology accuracy. It also specifies disclosure when AI summarises or analyses information relied on by a witness, among other evidentiary uses.

The AI practice note guide explains the court-specific rules. The legal AI tools comparison covers research and drafting tools beyond this evidence-handling workflow.

Where Software Stops: Financial Evidence

A searchable statement bundle helps you find a document. Financial analysis establishes how the transactions fit together across the supplied accounts. Text search or document coding alone cannot establish genuine, complete bank records, trace transfers or produce an explained financial schedule.

Some platforms add bank-statement extraction and summaries, including Litigation Ready. Compare the actual output with the task you need done. Document-review functionality alone does not establish forensic analysis, and software cannot authenticate a statement merely because it can read it.

FinTrace saves lawyers and forensic accountants hours of statement review by delivering the analysis as a service. In one recent matter, roughly 50 hours of estimated manual lawyer work was delivered in about 10 hours. The service processes thousands of PDFs through staged extraction, source-grounding checks and independent reviews.

The output includes a searchable Excel ledger and a clear findings report. Suspicious transactions are flagged, with transfers followed across related accounts and currencies. Every finding cites the original PDF filename and page, so the supporting evidence is already at hand.

Criterion	Team-Operated Financial Software	FinTrace Per-Matter Service
Inputs	The formats and preparation steps supported by the selected product	Statement PDFs as held, including scans and mixed order
Review workflow	Your team operates the software and owns analysis decisions	Staged extraction, source-grounding checks and independent reviews produce the analysis
Security and hosting	Assess the product’s processing locations, access controls and retention	Resolve data handling within the service engagement before statement transfer
Output for financial evidence	Depends on export fields and analysis your team performs	Categorised ledger and readable findings with PDF filename and page references
Pricing model	Licence or subscription, plus staff time and implementation	Written quote using a fixed base fee plus per-page scope
Support and court explanation	Vendor support concerns software; the analyst explains the work	Service delivery supplies source-backed analysis; any expert opinion comes from the instructed expert

FinTrace performs the same statement-analysis work at a fraction of the cost of manual review or engaging a forensic accountant for that stage. Forensic accountants also use FinTrace directly, freeing their time for interpretation and wider specialist work. Request a matter assessment with a matter outline and timeframe. Include approximate page and account counts. Statements follow assessment and acceptance of the written quote.

The person giving expert evidence must explain their own opinion and reasoning under the applicable court rules.

In the illustrative regulator matter, the review platform handles correspondence, relevance and privilege across the 40,000-document production. FinTrace handles the financial statements and returns findings with their supporting evidence. The legal team can then select exhibits and instruct an expert on any opinion the case needs.

Use the bank statement analysis software comparison for a closer assessment of financial tools. The litigation support service guide explains the service deliverables.

Questions to Settle Before Buying Litigation Software

Settle the work volume and required output with your intended software users before you buy. A subscription that solves matter reporting can leave a production-review problem untouched.

Record your answers before committing the budget.

• Separate annual matter volume from the largest likely production. Record native-file types, custodians and expected hosted data, alongside PDF page counts.
• Complete the IT security review. Identify permissions, single sign-on, audit records, retention and export rights before ingesting confidential material.
• Specify the required data residency across storage, backups, AI processing and support access. Tie that specification to confidentiality orders and organisational policy.
• Map integrations to actual work. Decide which system owns the matter record, document versions and production identifiers.
• Calculate total cost over three years. Include licences, hosted data, implementation, training, review administration, archive charges and exit exports.
• Name support coverage for an Australian hearing. Distinguish local assistance from a global support promise, and specify response arrangements during trial.

US guides to litigation software for attorneys often assume US discovery rules and production conventions. Australian discovery depends on the court, proceeding and orders. Use the software’s functions, but set the review protocol and production format for your Australian matter.

For a document-heavy investigation, prioritise a review platform with the required processing and production workflow. Scope financial statement analysis by the ledger and report your lawyers or forensic accountants need.

Timeline Software for Evidence

Choose timeline software that keeps each event connected to its evidence and preserves uncertainty about when it happened. A presentation timeline and a working legal chronology solve different problems. Your working record needs review notes and consistent updates before it becomes a hearing exhibit.

Everlaw’s Storybuilder Fact timelines connect facts to evidence and related facts. Its documented date fields accept a range and an approximate-date marker. Descriptions carry context, while Story permissions distinguish viewing from editing. CSV export provides a timeline outside the hosted workspace. Those features suit a team already reviewing its evidence in Everlaw.

Litigation Ready’s published chronology workflow generates a response from selected matter documents and saves it in recent sessions. It exports CSV or DOCX for offline use. Its feature documentation describes source-linked events and review of the generated chronology. A lawyer must resolve uncertain dates and disputed events before using the resulting chronology.

Compare Chronology Records and Exports

Criterion	Everlaw Storybuilder	Litigation Ready
Sources and review notes	Facts link to evidence, with descriptions for context	Generated chronologies use selected matter documents; review the event and its source
Partial or uncertain dates	Date ranges and an approximate-date marker are documented	Preserve the source’s uncertainty when reviewing generated dates
Consistent updates	Edit facts within the shared Story and export a new version	Review saved results and distinguish later exports from the earlier chronology
Access controls	Story View, Edit and Full Access permissions govern collaboration	Apply the matter’s document-access arrangements to the chronology workflow
Offline handling	CSV is an export from the hosted workspace	CSV and DOCX exports support offline use

An offline export is a separate copy. Record its version and restrict who receives it, because later platform edits will not change a file already sent to counsel. Keep the working chronology’s event identifiers consistent so corrections can be followed into each export.

A fictional case illustrates the date check. A letter describes a payment during the preceding week but gives no exact day. Record the supported period and attach the letter’s reference. Keep a review note explaining the uncertainty. A platform that forces an exact day would require a clear uncertainty field or a different chronology format.

For manual creation, the separate browser timeline maker lets you build a chronology without selecting an evidence-review platform. Choose the shared platform when permissions and source-linked collaboration drive the matter. Use a manual chronology when the team needs a controlled record it will maintain itself.

Redaction Software for Financial Productions

Redaction software must remove protected content from the released file, including its searchable text and image content. A black rectangle over an account identifier can leave the underlying value extractable. The legal team must first decide which material the disclosure obligation permits or requires it to withhold.

Adobe Acrobat Pro documents text and image redaction followed by Apply. Its desktop workflow includes sanitisation before saving a separate output. Adobe’s search-and-redact function handles repeated terms across PDFs, while sanitisation addresses hidden information. Use these operations on working copies held in the approved document environment.

Foxit PDF Editor Pro is another documented desktop option. Its manual describes permanent text and image removal, search-and-redact across files and redaction profiles for repeated terms. Separate hidden-data commands address metadata and attachments. Its Australian support contact is listed with the user guide. Select the desktop edition and supported operating system when comparing it with Acrobat Pro.

Compare Redaction Controls

Control	Adobe Acrobat Pro	Foxit PDF Editor Pro
Visible content	Mark text or images, then apply redactions	Mark text or images, then apply redactions
Hidden content	Sanitize removes hidden information from the output	Sanitize Document or selective hidden-information removal addresses metadata, attachments and other hidden content
Bulk work	Search-and-redact identifies repeated text across PDFs	Search-and-redact covers multiple files and supports reusable redaction profiles
Extraction after export	Test the saved PDF’s search, copy and text extraction	Apply the same test to the saved PDF
Logs and version control	Keep a matter log of reasons, operator, checks and released version	Keep the same matter log and connect it to the saved output
Local versus hosted processing	The documented desktop procedure saves to a chosen location	The documented desktop procedure saves a redacted output file

Desktop processing gives the team control over the working file’s location. Cloud synchronisation, AI features and any hosted conversion are separate processing decisions. Approve those settings under the matter’s confidentiality requirements. Retain the log separately from the sanitised production so removing metadata does not remove the record of the redaction decision.

A Fictional Financial-Production Trial

Use a synthetic statement to test the workflow before processing confidential evidence. In this fictional example, the legal team has authorised removal of an account identifier while retaining the transactions.

1. Preserve the original synthetic statement and make a working copy. Record the source identifier and intended output version.
2. Mark every authorised occurrence of the account identifier, including any occurrence in a scanned image. Apply the redactions and sanitise the output’s hidden information.
3. Save a separate PDF and reopen that saved file. Search for the identifier, copy nearby text and extract the text into a separate file. The identifier must be absent from each result.
4. Inspect attachments, metadata and hidden content. Check that the remaining transaction evidence is readable and that sanitisation has preserved the required production format.
5. Record the output version, operator and test results in the matter log. Release only the checked version under the approved disclosure scope.

If the identifier remains in extracted text or an attachment, withhold the output and correct the removal before repeating the checks. For a manual browser workflow, use the existing redact PDF tool. The tool handles technical removal. The lawyer retains responsibility for the disclosure decision and the version released.