Skip to content
Lintel

2026-09-17

What ‘grounded’ should mean for AI on legal text

‘Grounded’ is used loosely in AI products. For contracts it should mean something specific and checkable.

General information, not legal advice.

Language models write fluent answers whether or not they have the facts. On casual questions that is an inconvenience. On contract text it is a risk, because a confident, wrong statement about a time limit can steer a decision. “Grounded” has become a common label for products that try to avoid this. The word is only useful if it means something specific.

A working definition#

For legal and contractual text, a grounded answer should satisfy four conditions.

1. It is drawn from identified source text. The answer is built from passages in the project’s own documents, not from the model’s general memory of what contracts usually say.

2. It cites those passages precisely. Each claim in the answer points to a clause and page, so a reader can open the source and check. A general reference to “the contract” is not a citation.

3. It stays within what the sources say. If the passage says “14 days”, the answer says 14 days. It does not round, generalise or add a consequence that the text does not state.

4. It declines when the sources do not support an answer. “Not found in these documents” is a correct and valuable response. A system that never says it cannot answer is not grounded.

Why the fourth condition is the hard one#

It is easy to make a system cite something. It is harder to make it recognise that nothing relevant was found. Retrieval always returns the nearest passages, even when none is on point, and a model will happily write an answer around them. Good design checks whether the retrieved material actually supports the question, and prefers silence to a plausible guess.

A practical consequence is that the decline path should be tested as carefully as the answer path. Questions the documents cannot answer are part of any evaluation set.

Scope is part of grounding#

Answers should be limited to the documents of the project being asked about. Mixing in material from other projects or other customers is both a confidentiality problem and a correctness problem: another contract’s clause is not this contract’s clause. Retrieval scoped to the project, with strict tenant separation, is a precondition for trust.

Version matters too. If an amendment changes a clause, the answer should reflect the version that applies and, where useful, show that it was amended.

Provenance for extracted fields#

The same principle applies beyond chat. When software extracts an obligation from a clause, each field, such as the trigger, the period and the consequence, should carry its source page and text span. A confidence score helps route uncertain items to a person. It should be treated as a routing signal, not a promise of correctness. We do not think a single accuracy percentage is a meaningful claim for varied contracts, and we do not publish one.

Humans remain responsible#

Grounding reduces one kind of error. It does not turn software into a lawyer. Clauses have to be interpreted in context, and the right reading can depend on facts and law that are not in the text. Outputs should therefore be labelled as decision support, reviewed by qualified people and never sent externally without approval.

A checklist for evaluating a product#

  • Can I click from every statement to the exact source passage?
  • Does it ever say “not found”? Ask a question you know the documents cannot answer.
  • Is retrieval limited to my project?
  • Does it show which version of a clause it used?
  • Are extracted fields shown with their source and a way to correct them?
  • Is anything sent outside my organisation without my approval?

If the answers are yes, “grounded” is more than a label.

Lintel’s Grounded Copilot is designed around these conditions and is in early access. In the sample console you can try one question that returns a citation and one that honestly returns “Not found in these documents.”

General information, not legal advice. Back to resources

Start with one contract.

Join early access, or book a walkthrough and we will show you how a single agreement becomes a live register.