We Handed Copilot Notebooks a Fake Lawsuit. It Briefed the Case in 15 Minutes.

Six documents went into a Copilot Notebook. Fifteen minutes later we had a chronological case timeline, a clause-by-clause map of contract violations to evidence, and ten deposition questions grounded in specific dates and file transfers.

That is the result. Here is the experiment, and why we think Notebooks is the most underrated Copilot feature for anyone whose job involves a pile of documents and a deadline.

The scenario is familiar to every lawyer: you get staffed on a new case or deal, someone hands you a stack of contracts, memos, correspondence, and expert reports, and says know this by Wednesday. So you read everything, highlight, cross-reference, and try to hold the whole picture in your head. Around hour six you are buried in tabs and sticky notes, trying to remember which document mentioned the date that connects to the clause in the other agreement. Consultants, analysts, project managers, and compliance officers all live some version of the same problem: multiple sources that have to be understood together, and synthesis that takes forever.

Why a notebook beats tenant-wide Copilot Chat#

Regular Copilot Chat in Microsoft 365 pulls from your entire tenant: emails, files, Teams chats, the whole universe of organizational data. Powerful, but noisy. It is asking a question in a stadium full of people; you might get a useful answer, but a lot of background chatter competes for attention.

Copilot Notebooks flips that model. You curate exactly what Copilot works with. Create a focused workspace, drag in specific files (Word docs, Excel spreadsheets, PDFs, PowerPoints, meeting notes, even OneNote pages), and when you ask a question, Copilot only uses what is in the notebook.

No random emails from 2019 bleeding into results. No hallucinations from a forgotten SharePoint site. Every answer traces back to a document you put there. Think of it as a project brain: Copilot gets exactly the context the task needs, bounded by your choices. The sweet spot is a collection of related documents you need to understand as a connected picture, not as individual files.

The test: a trade secret lawsuit in six documents#

To put Notebooks through its paces, we built a realistic scenario: a fictional trade secret lawsuit in which a small software startup sues a larger competitor and its former CTO for stealing proprietary technology. A classic David-versus-Goliath IP dispute, exactly the kind of case where a new associate gets handed a document pile and told to get up to speed fast.

We created six documents matching what a real case file would contain:

1. Client intake memo with the allegations, witness list, preliminary legal assessment, and estimated damages.
2. Employment agreement the former CTO signed, including non-compete, NDA, confidentiality obligations, and invention assignment clauses.
3. IT forensic audit report showing 3.4 GB of data transferred to a personal Dropbox account in the weeks before the CTO resigned, plus details on a secure deletion tool he ran the day before quitting.
4. Technical comparison analysis with a feature-by-feature breakdown of the startup's product versus the competitor's suspiciously similar new product, including a development timeline analysis.
5. Email chain of seven key communications telling the story chronologically, from the resignation through the discovery of the data theft to the competitor pitching the startup's own customers.
6. Competitor's marketing materials, including product announcements, a technical whitepaper, and a customer migration guide containing the startup's proprietary API endpoints and customer-specific configurations.

Adding all six to a notebook took about 30 seconds. Then the prompting started.

Three prompts, three deliverables#

The full case download#

The prompt: "I'm a new associate onboarding to this case. Based on all the documents in this notebook, give me a comprehensive case summary. Include: a chronological timeline of key events, the strongest evidence for each claim, the key witnesses and their significance, and any cross-references between documents that strengthen the case."

Copilot built a timeline by pulling dates from across all six documents: the suspicious email from the competitor six days before the first data transfer, the transfer dates from the forensic audit, the resignation, the competitor hire, the product launch, the customer solicitation. No single document contains that full timeline. Copilot assembled it by reading all six simultaneously.

It also identified the strongest evidence and explained why each piece matters, connecting facts rather than listing them: the forensic logs prove what was taken, the technical comparison proves the competitor could not have built the product independently, and the marketing materials prove they are using proprietary information they should not have. Then it cross-referenced the employment agreement against the actual events, mapping specific contract clauses to specific violations with supporting evidence for each.

That kind of synthesis takes hours manually. Copilot did it in about 20 seconds.

Contract-to-violation mapping#

The prompt: "Based on the employment agreement and the forensic audit findings, list every specific contractual provision that was violated, the evidence supporting each violation, and which document the evidence comes from."

This is the task that normally eats a first-year associate's afternoon. Copilot mapped every relevant clause (confidentiality, non-compete, non-solicitation, return of materials) to specific evidence from the forensic report, the technical analysis, and the competitor's marketing materials. Each violation came with the date, the document source, and the supporting data point. Not summarization: structured analysis across multiple documents, which is exactly what makes case onboarding slow when done by hand.

Deposition prep#

The prompt: "Draft the top 10 questions I should prepare for the deposition of the former CTO, based on the evidence across all documents."

This output impressed us most. The questions were not generic. They were grounded in the actual evidence: specific dates from the forensic audit, specific files that were transferred, specific details from the competitor's marketing materials that could only have come from proprietary sources.

Would an experienced litigator refine them? Absolutely. But as a starting point that gets a new associate 80 percent of the way there, it saves hours.

The audio overview is a real commute feature#

Notebooks includes an Audio Overview that generates a podcast-style summary of everything in your notebook. Driving to the office before a 9 AM case meeting? Instead of reading six documents, you listen to a ten-minute synthesis. It does not replace reading the actual files, but as a first-pass orientation it genuinely works.

What to know before you rely on it#

Getting the best results comes down to three habits:

• Be specific. "Summarize this" is weak. "Build a chronological timeline of key events with the source document for each date" is strong. The more specific the ask, the better the output.
• Curate the inputs. Add the files that matter for the task. Do not throw in 50 documents and hope Copilot finds the signal. Treat the notebook like a research folder.
• Share it. Notebooks and their references persist and can be shared, so a colleague picks up where you left off and the notebook becomes the shared knowledge base for the case, deal, or project.

And the limitations, as of April 2026:

• Licensing. You need a Microsoft 365 Copilot license. Notebooks is not available in base E3 or E5 plans.
• Indexing delay. New references take about 10 minutes to fully index. Add your files, grab a coffee, then start prompting.
• Numbers are not the strong suit. Complex spreadsheets with many tabs and heavy numerical data underperform. Notebooks does best with text-heavy content: Word docs, PDFs, memos, emails. Primarily numerical analysis belongs in other tools.
• Reference cap. The first 100 references are used for grounding. Plenty for most scenarios, but do not upload an entire SharePoint library.

Notebooks is not trying to replace the attorney's judgment, the analyst's expertise, or the consultant's experience. It eliminates the tedious assembly work, the reading and cross-referencing and note-taking, so you get to the thinking faster. Pick a case, a deal, a project, or a compliance review. Drop the files in. Ask a hard question. We think you will be surprised at what it finds when it can see across all your sources at once.