best legal intake softwareTest the Difficult File, Not the Demo

The best legal intake software is the product that carries one of your firm's real, difficult inquiries from first contact to an attorney-ready record with the least hidden repair work. Test it with missing documents, conflicting facts, a duplicate person, an unknown answer, and a follow-up correction. Then inspect the sources, review gates, security controls, export, and full operating cost.

Define the job before comparing products

Begin with one case type. Write down the questions, documents, parties, dates, consent records, and approvals that the firm expects. Identify which information is required at first contact and which can wait until a later stage. Name the person who owns each exception.

That written path becomes the evaluation script. It prevents a comparison from collapsing into a feature count. Two products may both offer forms, document uploads, and reminders while producing very different work for staff after submission.

Create a small demonstration file with representative problems:

• a partially completed questionnaire
• a person who may already exist in the system
• one answer marked unknown
• one question left unanswered
• a poor-quality document scan
• two sources that give different dates
• a later correction from a follow-up call
• a document that contains sensitive information

Use synthetic or properly authorized information. Ask every vendor to use the same file and carry it through the same intake stages.

Follow the matter through the entire demonstration

The useful part of a demonstration begins after the prospect presses submit. Watch where the documents go, how the intake team finds incomplete work, and what the lawyer receives before making a decision.

Case-type configuration

Ask whether the firm can configure questions, expected documents, roles, stages, and review gates by case type. A mass tort inquiry, an employment dispute, and a consumer arbitration matter should not be forced into the same generic fields.

Look for conditional questions that have an operational purpose. A follow-up question should appear because an earlier answer created a need for it. The system should preserve the fact that a question was skipped by logic, answered as unknown, or left unanswered.

Source-linked facts

Ask the demonstrator to open the source behind an important value. A reviewer should be able to move from a proposed date or name to the questionnaire answer, call segment, document page, or passage that supplied it.

Then introduce a conflicting source. The software should retain both values and present the conflict for review. Replacing the first value without history makes the record look cleaner while removing the evidence needed to understand it.

Exception work

Open the queues for missing information, contradictory values, likely duplicates, failed uploads, and low-confidence extraction. Check whether each exception has an owner, an age, and a clear action. A general notification feed does not provide the same operational control.

Ask what happens when no rule applies. The safe result is a stopped record with enough context for a person to decide what comes next. A completed field should never stand in for legal judgment.

Matter creation

Carry an approved intake into the case management system. The claimant, parties, documents, source links, notes, corrections, consent history, tasks, and review history should travel forward without staff entering the same information again.

Check the actual integration behavior. A product may advertise an integration while transferring only contact fields or attaching one flattened PDF. Ask which objects move, which remain behind, how errors appear, and who repairs a failed transfer.

Confirm the human decision boundary

Intake staff and software can collect and prepare information. The firm's lawyers or authorized personnel retain conflict decisions, engagement, qualification standards, legal conclusions, filing, and advice.

The ABA Standing Committee's summary of Formal Opinion 506 states that trained and supervised nonlawyers may assist with specified prospective-client intake tasks while the prospective client remains able to communicate with a lawyer about the agreement and scope. A software evaluation should therefore cover supervision, escalation, and access to a lawyer, not only task completion.

Technology competence also belongs in the review. Comment 8 to ABA Model Rule 1.1 points lawyers to the benefits and risks associated with relevant technology. Ask who at the firm will understand configuration changes, monitor exceptions, approve new uses, and respond when the software behaves differently from the documented process.

Review security and information governance

Legal intake can hold identity details, health records, financial information, dispute narratives, and communications from people the firm has not yet accepted as clients. Security review should match the sensitivity of that information and the firm's legal obligations.

Request written answers about:

• encryption in transit and at rest
• role-based access and administrator privileges
• authentication options and access review
• audit history for viewing, editing, exporting, and deletion
• data location, retention, backup, and deletion
• subprocessors and third-party AI services
• incident notification and response terms
• testing, vulnerability handling, and service continuity
• ownership and permitted use of firm and prospect data

ABA Model Rule 1.6 includes a duty to make reasonable efforts to prevent unauthorized access to or disclosure of information relating to representation. Applicable state rules and privacy laws may impose other requirements. Firm counsel should decide the standard that applies.

The NIST Cybersecurity Framework 2.0 gives organizations a common set of cybersecurity outcomes for governance, identification, protection, detection, response, and recovery. It can help a firm turn broad security questions into a documented current state, target state, and gap list for each provider.

Price the operating model, not the subscription

Put the costs that staff and lawyers will experience beside the quoted fee. Request pricing and limits for setup, case-type configuration, seats, storage, document volume, communications, AI use, support, integrations, third-party services, data migration, export, and custom work.

Then estimate the work the product leaves behind:

• staff correction and re-entry
• attorney re-screening
• failed integration repair
• manual document classification
• duplicate cleanup
• report reconciliation
• configuration maintenance
• security and vendor review

Use your demonstration file to measure this work. A lower subscription can be more expensive to operate if staff repeatedly rebuild the intake before review.

Test export before signing

Ask for a complete export from the demonstration environment. Inspect whether it includes structured fields, documents, relationships, source locations, notes, tasks, status history, consent records, audit events, and configuration. Confirm the file formats and the work required to use them elsewhere.

Also read the contract for data return, deletion timing, export fees, termination assistance, service changes, and access after termination. A promise that the firm owns its data says little about whether the firm can retrieve a usable record.

Use a scored decision record

Score every product against the same observable tests. Weight the criteria according to the firm's matter types and risk, then record the evidence behind each score.

Evaluation area	Evidence to retain
Case-type fit	Configured workflow and question logic
Source traceability	Demonstrated path from fact to source
Exception handling	Queues, ownership, age, and escalation
Human review	Enforced legal decision gates
Matter creation	Field, document, history, and error mapping
Security	Written controls, terms, and review findings
Cost	Subscription, limits, services, and repair work
Portability	Complete test export and contract terms

Record unanswered vendor questions as unanswered. Do not convert them into assumptions. Keep true unknowns separate, such as future document volume that the firm cannot yet estimate. That distinction makes the final comparison easier to defend and revisit.

The selected software should make the difficult parts of intake visible. It should preserve the source behind each material fact, give exceptions to named people, carry the approved record forward, and leave legal judgment with the firm.

Book a demo →