A legal case intake workflow converts an incoming notice, claim, complaint, referral, or internal escalation into a controlled matter record. Its job is to make urgent facts visible without pretending that the first account is complete. A sound workflow preserves the source, records uncertainty, routes conflicts and deadlines to lawyers, and gives the team a practical first plan.
Intake is often where preventable problems begin. An attachment remains in one person's inbox. A date is copied without its qualifier. Two teams open duplicate matters. A business summary becomes accepted as fact. Structure helps, but only if it keeps a clear boundary between reported information, verified records, and legal analysis.
Before automating, outsourcing, or redesigning intake, measure the current process from receipt through accepted handoff. The legal AI ROI calculator can model volume, handling time, verification effort, adoption, and cost for that bounded workflow without treating theoretical speed as realised savings.
What information should a legal case intake workflow capture first?
Capture the original communication before rewriting it. Store the email, notice, pleading, order, call note, or referral with its received date, sender, attachments, and transmission context. Then create structured fields that point back to that source.
| Intake field | Practical purpose | Verification prompt |
|---|---|---|
| Matter name and identifier | Prevents duplicate or ambiguous records | Is this a new matter or part of an existing one? |
| Source and receipt date | Preserves provenance | Can the original communication be opened? |
| Parties and related entities | Supports conflicts and relationship mapping | Are names legal names, trade names, or allegations? |
| Forum and proceeding reference | Routes procedural review | Has the forum been confirmed from an official record? |
| Dates and stated deadlines | Enables urgent triage | Is each date sourced, calculated, or unverified? |
| Allegations and requested relief | Frames initial scope | Is this the sender's characterisation or a finding? |
| Custodians and systems | Starts preservation assessment | Who else or what system may hold records? |
| Owner and next action | Creates accountability | Who must act, by when, and on what basis? |
Do not force a neat narrative on incomplete material. Use “reported,” “alleged,” “to be confirmed,” and source citations where appropriate. Link early dated facts to an evidence-linked litigation chronology once reviewers can trace them.
How should conflicts and confidentiality be handled at intake?
Conflicts review should occur through the organisation's approved process before sensitive work expands. Capture enough party and relationship data for that review, including affiliates, key individuals, opponents, and other names supplied by the instruction. Do not circulate the intake more widely merely to obtain informal views.
Use role-based access from the beginning. A new matter can contain personal data, commercially sensitive material, privileged communications, allegations, or security information. Give access to people who need it for intake and review, then revise permissions when the team is confirmed.
A practical gate has three outcomes: cleared for opening, pending information or review, and declined or redirected. Preserve the decision record and avoid presenting a software status as a legal conclusion. For platform diligence, teams can examine Gotham's security page and assess configuration, contracts, and internal policy against their own requirements.
How do you identify and verify urgent dates?
Treat every incoming date as a candidate until its source and significance are checked. Keep the received timestamp, the date stated in the document, the event date, and any calculated date in separate fields. This avoids silently converting “within a stated period after service” into an unsupported calendar entry.
The Limitation Act, 1963 is a primary statutory source for limitation questions within its scope. The eCourts Services portal and the Supreme Court of India website provide official case and court information, subject to the status and limitations of each service. Counsel should confirm the current official record and the rules applicable to the forum.
Use a two-person or lawyer-approved deadline workflow:
- Save the source document and proof or context of receipt.
- Record the date exactly as stated, without calculation.
- Identify the event that may start time running.
- Assign counsel to determine the applicable rule and calculation.
- Record the calculated date, assumptions, source, reviewer, and review time.
- Add internal planning dates separately from legal deadlines.
- Recheck if service, filing status, forum, or facts change.
Automation can create reminders, but it should not invent the legal basis. A calendar entry without a source and reviewer is a prompt, not proof.
What does a useful intake triage look like?
Triage ranks operational attention. It does not decide the merits. A simple model considers time sensitivity, proceeding status, preservation urgency, financial or operational exposure, data sensitivity, senior stakeholder involvement, and information gaps. Each factor should have an owner and a next action.
| Triage question | If yes, route to |
|---|---|
| Is a filing, hearing, response, or service date stated? | Immediate lawyer deadline review |
| Could routine deletion affect relevant records? | Preservation assessment |
| Is there a cyber or data incident dimension? | Security, privacy, and legal response |
| Are senior employees, regulators, or multiple entities involved? | Conflicts, governance, and access review |
| Is the source incomplete or authenticity uncertain? | Verification and source acquisition |
| Does the matter overlap another open dispute? | Matter-linking and ownership review |
Every red flag should produce a named action rather than a dramatic label. “High risk” is less useful than “counsel to verify service and approve response plan.”
How should documents and early evidence be organised?
Keep originals or authoritative copies, assign stable identifiers, and separate raw intake material from working notes. Record who supplied each item, when it arrived, and whether it supersedes another version. Avoid renaming files in a way that destroys useful context. When OCR or extraction creates derivative text, retain the relationship to the source image or file.
Create an initial source register with document ID, title, date, sender or origin, custodian, format, access label, and review state. Grouping by issue can come later. Early overclassification encourages people to fit documents to a theory before the record is understood.
If the intake suggests a preservation need, open a dedicated decision path rather than assuming upload equals preservation. The Bharatiya Sakshya Adhiniyam, 2023 provides official statutory text relevant to electronic and digital records. Counsel should determine what the particular proceeding requires.
Gotham's document workflows, practice solutions, and litigation workflow materials can support an evaluation of source-linked intake. They do not replace the team's legal and records procedures.
How do you turn intake into a matter plan?
Close intake with a short, reviewable plan. It should state what is known, what remains alleged or uncertain, immediate deadlines, preservation decisions, responsible lawyers, document requests, stakeholder communications, budget or approval gates, and the next formal review.
A first-week operational checklist might include:
- matter identifier and duplicate check completed;
- conflicts decision recorded through the approved process;
- access group approved;
- original notice and attachments secured;
- dates entered with source and reviewer status;
- preservation trigger assessed;
- parties, custodians, systems, and external counsel mapped;
- initial chronology entries linked to sources;
- forum record checked through official channels;
- next actions assigned with owners; and
- client or business update format agreed.
The plan should change when the record changes. Keep prior decisions visible so the team can understand why scope, ownership, or priority moved.
Define an accepted-handoff gate
Intake is complete only when the receiving matter owner can act without reconstructing the first notice. Use this gate to distinguish a submitted form from an accepted matter record.
| Gate | Acceptance evidence | If missing |
|---|---|---|
| Source preserved | Original notice or referral and attachments open from the record | Return to intake owner and preserve the transmission context |
| Identity checked | Matter, parties, related entities, and duplicate search recorded | Hold opening or route the ambiguity for review |
| Conflicts routed | Approved conflicts status or a plainly marked pending decision | Restrict work and access under the organisation's procedure |
| Urgent dates reviewed | Source, calculation basis, reviewer, and internal planning dates are separate | Escalate immediately to the responsible lawyer |
| Preservation considered | Dated decision, owner, scope, or reason no action was taken | Open the preservation assessment path |
| Access approved | Named group and information classification recorded | Keep access at the minimum intake level |
| First plan assigned | Owner, next action, due time, and open questions visible | Do not mark the handoff accepted |
Record submitted at, accepted at, and returned at separately. That makes three useful measures possible: time waiting for missing information, time under legal review, and time from acceptance to first action. A single intake-cycle number hides which part of the workflow needs improvement.
For a pilot, sample ten recently closed intakes and ask whether each gate can be proved from the record. Count the missing evidence by gate, not only the number of forms completed. The result gives the team a concrete backlog for form design, routing, training, or system integration.
How can intake quality be measured without misleading metrics?
Review individual files for control quality rather than chasing a universal score. Ask whether the original source is present, urgent dates have legal review, conflicts and access gates are recorded, preservation was assessed, and open questions have owners. Sample handoffs: can a new team member understand the matter without relying on an undocumented conversation?
Watch for recurring exceptions such as duplicate matters, unsupported deadlines, missing attachments, unclear ownership, stale pending conflicts, or summaries without citations. These patterns identify workflow changes worth making. They do not prove legal performance or predict case outcomes.
A good legal case intake workflow gives the team a reliable starting point, not a false sense of completeness. Explore Gotham's litigation discovery workflow, review broader legal workflows, or talk to the team about a source-linked intake design.
