As a small team exploring the intersection of litigation and LegalTech we began with a simple question: when AI helps prepare legal work how does a lawyer actually verify what it produced and how is that verification recorded?
Generative AI has made it remarkably easy to produce a first draft, find authorities and assemble legal material. But the work does not end when the draft is generated. Before something reaches a client, a court or a senior reviewer someone still has to ask a more fundamental question: can we stand behind what this document says?
A draft can cite a case that does not exist. It can cite a real case with the wrong citation. A quotation can read as authoritative without appearing in the judgment. And perhaps most difficult of all the authority may be genuine, correctly named and correctly reported yet still not support the proposition it is cited for. Ordinary citation checking cannot catch that last problem. The question is no longer simply “does this case exist?” but “what does the source actually say and does it support what this draft asks the reader to believe?”
This distinction is becoming increasingly important. In Pooja Ramesh Singh v. Jammu and Kashmir Bank Ltd. 2026 INSC 668 the Supreme Court dealt with reliance on non-existent fake and hallucinated AI-generated material presented as precedent. While recognising AI as an assistive tool the Court asserted total and absolute human control over adjudication with a human in the loop at every stage. More recently on 2 September 2026 Vijay Ghanshyam Gadiya v. Union of India 2026 INSC 947 brought the issue into even sharper focus. The Court found that some authorities relied upon were non-existent or carried fake citations while others existed but did not lay down the propositions attributed to them. The Court set aside the High Court order and the ₹425.27 crore penalty order and remitted the matter for fresh adjudication.
For us these developments point to a simple distinction at the centre of LiTL: a source being found is not the same as a source being verified.
LiTL — Lawyer in the Loop is built around that gap. It provides a structured verification layer for AI-assisted legal work. It brings the relevant source and the proposition being relied upon into the same workflow and leaves the final assessment where it belongs — with the lawyer.
The lawyer can Confirm, Correct, Reject or Leave Unresolved. Each decision becomes part of a verification record showing what was identified, what was located, what was reviewed, what was changed and what remains open.
We deliberately treat Unresolved as a legitimate outcome. A source may be unavailable, a passage may require deeper reading or an issue may need to be taken to a senior. A system that forces every item into a resolved state may produce a cleaner report but not necessarily a truer one.
LiTL does not certify that a document is legally correct and it does not turn “source found” into “verified.” It preserves the boundary between what the system found, what the source contains and what the lawyer decided.
The Supreme Court’s Draft Regulations for Use of Artificial Intelligence in Courts 2026 envisage that a Court may require disclosure of the AI system used, the extent of its assistance and the steps taken to verify its output. LiTL is designed with this direction in mind. It makes the verification process visible, reviewable and capable of leaving a record.
Not AI versus the lawyer. AI evidence for the lawyer.
Product Note: LiTL is currently presented as a fully interactive verification workflow. Documents can be processed through the verification workflow, relevant sources can be fetched and reviewed alongside the draft, and a verification report is generated from the recorded review. We are continuing to refine the product and expand its broader workflow capabilities.