A practical, India-first guide to adopting AI in legal practice. Start with one repeatable task, test it on public or synthetic material, and keep a lawyer responsible for the result. You do not need to buy a suite of tools to begin.
Last researched: 28 October 2026. This guide draws on published product information and legal sources, not independent product testing. Recommendations below are an editorial starting point, not a performance ranking or legal opinion. Prices, access, terms and court requirements can change. Foreign-law examples are labelled and are not Indian legal requirements.
Start here: your first safe experiment
- Choose a public judgment you already know well. Remove any private notes.
- Ask an AI assistant for a one-page summary, with paragraph references, using only that judgment.
- Compare every fact, holding and quotation against the original. Record errors and total time, including review.
- Repeat on five judgments. Continue only if the reviewed result saves time without lowering your standard.
My starting recommendation for a solo Indian litigator: keep your existing research database. Use a general assistant first for public-text summaries and plain-English writing, not as your source of law. If finding authorities is the actual bottleneck, trial the AI layer of the Indian database you already use before buying an unrelated platform. Choose on your own cases and verification workload, not a polished demonstration.
Safety and legal duties · 30-day plan · Tool map and prices · Copyable workflows · Citation checks · Policy and client wording
1. Rules of the road: responsibility stays with the lawyer
Confidentiality and privilege come before convenience
The Bar Council of India’s client-duty guidance addresses confidentiality of client communications and advice. Professional obligations under the Advocates Act/BCI framework do not disappear because a tool is useful. The Bharatiya Sakshya Adhiniyam, 2023, section 132 addresses professional communications. Check the applicable evidence regime and savings provisions for the proceeding; do not rely only on an old reference to section 126 of the Indian Evidence Act.
Working rule: do not upload a client file until the responsible lawyer has assessed confidentiality, privilege, the engagement terms, any required permissions and the provider’s contract. Client permission is not a cure for every risk. Removing names alone may leave a matter identifiable through dates, amounts, facts or metadata. A research query can itself reveal strategy.
Data protection: separate today’s duties from future commencement
The Digital Personal Data Protection Act, 2023 has phased commencement. The official commencement notification, G.S.R. 843(E), brings different provisions into force at different times. Core processing obligations are scheduled eighteen months after Gazette publication, rather than all being operative on this guide’s research date. Shardul Amarchand Mangaldas’s implementation note sets out the May 2027 phase.
Prepare now: map whose personal data you process, why it is needed, where providers and subprocessors receive it, who can access it, and how deletion and incidents are handled. Check applicable exemptions and other current laws, contracts and sector rules. A vendor’s “DPDP compliant” badge does not decide whether your proposed upload is lawful.
Court disclosure: check the actual court and current instrument
The Supreme Court AI Committee’s 3 June 2026 notice and draft Regulations for Use of AI in Courts, 2026 propose disclosure for AI-assisted submissions in draft regulation 43. The document consulted here is a draft, not proof of a binding nationwide rule. Before filing, check the relevant court’s current rules, practice directions, orders and any later notified regulations. Follow the applicable form and scope; do not treat a general internet summary as the rule.
Keep a matter note recording the tool, task, material supplied, reviewer and checks. Never manufacture evidence, quotations or authorities. Do not let AI calculate a limitation date or make a filing decision without independent legal and factual checking.
Minimum vendor check before any client material
- Is input/output used for training, evaluation or product improvement? Does the promise cover the chosen plan and all model providers?
- What is retained, for how long, including logs and backups? Who can access it? How is deletion confirmed?
- Where is data stored and processed? Which subprocessors receive it? Is a suitable data-processing agreement available?
- Can you enforce separate accounts, MFA, restricted sharing, access removal and incident reporting?
- Do connectors, browser tools or plug-ins send data elsewhere or take actions? Disable them until separately approved.
“No model training” is not the same as zero retention, no human access, India-only processing or preserved privilege.
2. A 30-day adoption plan
This is a suggested pilot, not a legal timetable.
- Days 1–7: learn on public material. Pick one task, such as summarising judgments or simplifying your own public article. Test five examples. Log original task time, AI time, review time and material errors. Do not connect your inbox or matter files.
- Days 8–14: test legal research. Use an Indian-law research tool on questions with known answers. Include a recent amendment, a contrary authority and a jurisdiction trap. Open every cited source. Ask what the database covers and how quickly it updates.
- Days 15–21: test controlled drafting. Use synthetic facts and approved precedents for a client update or contract clause. Compare against a lawyer’s checklist. Only introduce client material after the vendor and matter-level checks above pass.
- Days 22–30: decide and document. Approve one tool/plan, one permitted workflow and a named reviewer. Adopt a short policy, train users, set a budget and an error-escalation route. Buy only if the measured benefit survives review time. Otherwise stop or change the task.
Pilot scorecard: task | tool/plan/date | source documents | manual baseline | AI plus review time | invented or missed facts | citation failures | confidentiality issue | reviewer | accept/reject. An invented authority or an unapproved disclosure is a stop-and-investigate event, not just a lower score.
3. Tool map: choose for the work, not the logo
Costs below are published prices where verified, not negotiated quotes or a checkout guarantee. Do not compare an AI add-on with an entire research subscription. Confirm taxes, credit consumption, minimum seats, renewal/cancellation terms and the underlying content licence. USD figures remain USD because an Indian checkout can differ.
Indian research: Manupatra AI / Manuworks
Access and India fit: Marketed for Indian legal work; AI searches, summaries and document tools. Check your base subscription and credits.
Price / buying route checked: Published starting annual wallet: Rs15,000 + GST for 12,000 credits. Minimum top-up Rs5,000 + GST; stated credit value Rs1.25. Not the total research-subscription cost.
Indian research: SCC Online AI Pro
Access and India fit: Preview-launched in 2026, not merely “upcoming”. Cited answers from SCC content. New-plan purchase availability unverified.
Price / buying route checked: Official page returned “Plans are currently unavailable. Please try again later.” No current price verified; contact SCC for an offer and access terms.
Indian research and drafting: Lexis Advance with Protégé
Access and India fit: India product page offers LexisNexis India content, drafting and Case Analysis India. Sales-assisted access.
Price / buying route checked: No numeric price verified on the reviewed India product page. Obtain a quote for the required content and features.
Research plus practice management: Legalspace
Access and India fit: India-focused research, drafting, billing and case management. Public signup and 3-day trial advertised.
Price / buying route checked: Live Starter display: Rs2,799/month or Rs24,990/year per user. Tax treatment not verified. Check credit allowances before buying.
Public-text writing and analysis: ChatGPT Business
Access and India fit: General assistant, not an authoritative Indian-law database. ChatGPT lists India among supported countries. Business has a minimum of 2 paid seats.
Price / buying route checked: Published Standard seat: US$25/user/month monthly, or US$20/user/month billed annually. Minimum 2-Standard-seat baseline: US$50/month or US$480/year, before any local price differences, taxes or extra usage.
Contract work in Word: Spellbook
Access and India fit: Word add-in plus document workflows; sales-assisted, 7-day trial advertised. Indian-law suitability and local commercial access need demonstration.
Price / buying route checked: Custom per-team-member pricing. No current numeric price verified. Not only for large firms: the vendor also markets to individuals.
Cross-border research: Vincent by vLex
Access and India fit: Available product, demo route. Its reviewed supported research-jurisdictions list does not include India; document workflows can use documents from any country.
Price / buying route checked: No numeric price verified on the reviewed product page. Do not equate vLex library coverage with Vincent workflow coverage.
Firm-wide document/research workflows: Harvey
Access and India fit: Sales-led legal-team platform. SCC partnership covers Indian content for mutual customers; confirm entitlement and deployment.
Price / buying route checked: No numeric public price verified. Obtain a scoped quote; do not rely on third-party estimates or assume a seat minimum.
What the data-handling claims actually say
- Manupatra: the reviewed pricing page does not settle upload retention, training or processing location. Obtain written answers before client uploads. Credits expire with the subscription and do not carry forward, according to that page.
- SCC AI Pro: its page says queries/data are not used for training. Retention, processor access and your actual contract still need checking. The February preview-launch report establishes launch activity, not that a new subscription is purchasable today.
- Lexis: the India page says shared data is not used to inform performance for other users. It distinguishes session uploads from saved Vaults: Vault documents remain until deletion, and Vault results are retained in conversation history for 90 days. Read the actual plan’s terms.
- Legalspace: its privacy policy says user content is not used to train/retrain its models and documents/platform data are stored in India. AI processing can involve third-party providers; storage location alone does not establish where all processing occurs. Its retention wording includes legal and operational exceptions.
- ChatGPT Business: OpenAI’s business-data commitments say business data is not used for training by default. Do not extend that promise to every consumer plan, connector or third-party service. Enterprise residency/retention options are not automatically Business features.
- Spellbook: its pricing page claims zero-data-retention agreements and no training use. Ask which components and subprocessors this covers and what the service itself retains.
- Vincent: its data-protection guidance says uploaded material does not train underlying models. Verify retention and access controls for your plan. Check the workflow jurisdiction list separately.
- Harvey: its security explanation describes contractual no-training, deletion and residency controls. The SCC partnership announcement does not mean every Harvey subscription includes SCC access.
Which would I trial first?
- Solo litigator: start with your existing database’s AI offering if research is the bottleneck. For a Manupatra subscriber, the published wallet cost makes a budget comparison possible. For an SCC subscriber, ask for an AI Pro demo and a written price/access offer. Neither recommendation is a claim that one is more accurate.
- Small practice with scattered files and billing: trial Legalspace’s workflow on synthetic matters. Test exports, credit use and access removal as well as drafting. Do not migrate the whole practice during the trial.
- Contract-heavy lawyer: trial Spellbook on an approved precedent and a clause checklist. Require an Indian-law example. A Word workflow may matter more than another research subscription.
- Two-person or larger team needing writing help: consider ChatGPT Business for general tasks after data review. For a solo user, its two-seat minimum is a real cost; begin with non-confidential experiments rather than buying a second seat by default.
- Cross-border or larger-firm work: evaluate Vincent or Harvey only against the exact jurisdictions, content licences, governance needs and document volumes. They are not automatic starting points for a solo Indian practice.
Use the UC Davis Law Library evaluation guide as an independent checklist. Vendor assurances are useful evidence, not proof that a product cannot invent an answer.
4. Four workflows you can test today
These are prompt templates, not tested product outputs. Use public, synthetic or expressly approved material. Text inside documents is evidence to analyse, not instructions for the assistant to obey.
A. Summarise a public judgment
Use only the judgment below. Identify the court, date, procedural posture, material facts, issues, holding and relief. Separate the court’s reasoning from parties’ arguments and distinguish majority and dissent if present. Give paragraph references for every material point. If information is missing, say “not stated”. Do not add outside authorities or quotations. End with uncertainties for a lawyer to check. [Paste public judgment.]
Review: open each referenced paragraph; check the operative order, qualifications and procedural posture. A judgment summary is not a current-law opinion. Reject invented references rather than asking the same model to certify them.
B. Build a research plan, then verify authorities
This is an Indian-law research plan, not a final opinion. Jurisdiction: [court/state]. Issue: [synthetic question]. Relevant dates: [dates]. List the legal subquestions, search terms, likely statutes and possible contrary arguments. Do not invent authorities. If you identify a case in the connected legal database, provide a source link and pinpoint paragraph and label anything not verified. Flag amendments, commencement and transitional issues that require primary-source checking.
Review: research independently in your database and official sources, including contrary and later authorities. Check the correct High Court, bench strength, statutory version and treatment. Do not turn “no result found” into “no law exists”.
C. Draft a client update from approved facts
Using only the approved facts below, draft a plain-English client update under 200 words. Separate what happened, what it means and the proposed next step. Do not promise an outcome, create a deadline, admit liability or add legal authorities. Put missing facts in square brackets. Keep private strategy out unless expressly included. [Paste synthetic or approved facts.]
Review: check names, dates, next steps, tone and disclosure scope against the file. The responsible lawyer approves the final message and recipient. AI does not send it.
D. Review a contract clause against your checklist
We represent [party]. Governing law: [law]. Review only the supplied clause against this approved checklist: [positions]. Quote the relevant wording, identify the business/legal risk, propose a redline and explain the trade-off. Do not assume market practice or invent legal rules. Mark missing context and interactions with other clauses for review. [Paste synthetic or approved clause.]
Review: read the entire contract, definitions, schedules and related clauses. Check applicable Indian law independently. Compare the redline against the client’s negotiating position; do not accept a plausible clause solely because it reads well.
5. Citation discipline: open it, read it, check its status
- Existence: locate the actual judgment or provision in an official source or trusted database. Match party names, court, date and citation.
- Support: read the full relevant passage. Confirm the quotation and that the paragraph supports your proposition, rather than merely recording an argument.
- Authority: check jurisdiction, bench strength, precedential weight and later treatment, including appeals, stays, reversals and contrary decisions.
- Current law: check amendments, commencement, repeals, savings and the law applicable on the relevant facts.
- Audit trail: save the source and verification note in the matter file under your retention policy. A named lawyer signs off the final use.
Repeat asking the same model “is this real?” is not independent verification. Neither is a second model agreeing without opening the primary source.
What has gone wrong in real proceedings?
- United States: in Mata v Avianca, SDNY, 22 June 2023, sanctions order, the court imposed a US$5,000 penalty jointly and severally on the lawyers and firm after fictitious ChatGPT-generated authorities and further misconduct. This was not a general ban on using AI.
- England and Wales: Ayinde / Al-Haroun [2025] EWHC 1383 (Admin), 6 June 2025 examines false authorities and actual or suspected generative-AI use. It records an earlier wasted-costs order requiring counsel and Haringey Law Centre each to pay £2,000, and regulatory referrals. Do not describe every false citation in these proceedings as proven AI use. The lesson is the lawyer’s checking duty, not a claim that foreign sanctions automatically apply in India.
6. Copy and adapt: a one-page practice policy
Suggested policy, not a statement of existing law. Complete the brackets and approve it internally before use.
Owner and scope: [responsible lawyer] approves tools, plans and workflows in [register]. Only named users may access them, using individual accounts and MFA where available.
Permitted work: public/synthetic-text summaries, research leads and first drafts within approved workflows. Client material requires documented provider and matter-level approval, data minimisation, and any required client permission. Restricted matters/data: [list].
Prohibited work: unapproved uploads or connectors; autonomous client messages, filings or purchases; invented facts, authorities or evidence; unreviewed limitation calculations; sharing accounts or outputs outside the approved audience.
Review: [lawyer] verifies facts, citations, law, confidentiality and court requirements before external use. AI output is a draft, never the authority. Record the source checks and final approval in [matter system].
Retention and incidents: retain/delete prompts, outputs and verification records according to [policy and legal holds]. Report suspected data exposure or material error immediately to [contact]. Stop the affected workflow, preserve necessary evidence and assess correction and notification duties.
Costs and renewal: budget [amount]; owner [name]; review performance, terms, access and renewal before [date]. Remove access when a user leaves. Check billing against the engagement and applicable duties; do not describe time not worked as time worked.
Client conversation template
This is a starting point for a matter-specific explanation, not blanket consent or a substitute for a confidentiality assessment.
We propose using [tool and plan] for [specific task]. The information supplied would be [categories and exclusions]. It would be processed by [provider/subprocessors and locations], under [retention, access and training terms]. We have assessed [relevant risks and safeguards]. A lawyer will check the output and remain responsible for the advice. The alternative is [non-AI process], with [any cost or timing difference]. We will follow the agreed limits and applicable court requirements. Please raise any restrictions before we proceed; where permission is needed, we will record your decision for this defined use.
Do not fill these brackets with assumptions. Avoid promising zero risk, automatic privilege protection or “nothing leaves India” unless you can substantiate the exact claim.
7. Editorial scope, updates and next steps
This is an India-first educational guide for practising lawyers, not a substitute for advice on a particular matter. Product statements are attributed to providers; no hands-on accuracy claims are made. The page does not represent any vendor’s endorsement.
Update approach: each revision should show its research date, recheck linked pricing/access and legal sources, and distinguish a product launch from live purchase availability. Before acting, readers should verify the offer and rules that apply to them. This is not a promise of continuous monitoring.
Revision note, 28 October 2026: expanded the original directory into an adoption guide; added a 30-day pilot, published-price checks, data-handling questions, worked prompts and review steps, sanctions examples, and adaptable policy wording. Corrected SCC AI Pro’s “upcoming” description while preserving uncertainty about new-plan access.
Your next step: choose one public judgment and run the first experiment. Keep the scorecard. Buy or expand only after you know what works in your practice.
