The hardest part of document review is not reading. It is knowing which document to read.
That distinction sounds obvious until you watch a junior lawyer spend forty minutes carefully annotating a contract that has nothing to do with the problem — while the clause that matters sits three files away, unchecked. What was missing was not diligence. It was triage.
Document analysis exercises are one of the most transferable formats in legal training. The same underlying structure — a set of documents, a specific question, a decision to make — works for due diligence, disclosure review, regulatory compliance, contract negotiation and a dozen other contexts. Built well, a single exercise can be reused across cohorts, adapted for different practice areas, and scaled without significant additional authoring time. Here is how we build them on BeSavvy.

The first stage places the student in front of a set of documents and asks one well-defined question: which of these is relevant to the problem?
The documents do not need to be complete. Two or three pages per contract is enough — long enough to require genuine reading, short enough to keep the exercise focused. What matters is that each extract contains enough real drafting for the student to engage with it as they would the genuine article, and that the full set includes both relevant and irrelevant documents. The noise is part of the exercise. Knowing which files to ignore is as important as knowing which ones to open.
For the change of control exercise we built recently, the question was: which of these twelve contracts contains a provision that could block completion? The answer required reading across all twelve, recognising what a change of control clause looks like in varied drafting contexts, and prioritising the highest-risk ones for escalation.
An AI mentor sits alongside throughout to discuss the student's reasoning. Why this contract rather than that one? What does the consequence of this particular trigger mean for the deal timeline? The conversation is where the judgement is built.
Once the student has identified the relevant documents, the exercise can go a level deeper. A single document is brought into focus — and within it, problems are embedded.
These might be drafting errors, missing definitions, conflicting provisions or commercially unreasonable terms. The student reads through, identifies the zones of concern, and either proposes a solution or works through one with the AI mentor. The interaction is direct: find the problem, discuss the fix.

This second stage trains something different from the first.
Both skills matter; few training programmes build both within the same exercise.