Home › Insights › The Pre-Filing Evidence Map: How Much Review Rule 11 Expects

The Pre-Filing Evidence Map: How Much Review Rule 11 Expects

A lawyer

Quick Answer

Rule 11 does not require reading every document a client hands over. It requires a reasonable inquiry: each factual allegation tied to at least one reviewed document, or openly flagged as needing discovery.

That record is the Pre-Filing Evidence Map. It changes the question. Small firms ask what review costs per gigabyte on a small civil case. The better question is what review costs per allegation, and which allegation can wait for discovery.

Did this answer your question?

Key Points

  • Rule 11(b)(3), published by Cornell's Legal Information Institute, lets an unconfirmed factual allegation stand if it is "specifically so identified" as likely to need discovery.
  • Relevant e-Discovery's analysis puts AI-assisted review at cents per document, against dollars per document and roughly $19K per gigabyte for manual review.
  • Under Rule 11(c)(2), a sanctions motion cannot be filed if the challenged contention is withdrawn or corrected within 21 days of service.
Three things litigators believe about Rule 11 review. Myth or fact?
Call each one, then see how other readers called it.
1 A sanctions motion cannot be filed if the challenged allegation is corrected within 21 days of service.
2 Rule 11 requires reading every document the client provides before you sign.
3 Rule 11 also governs your later discovery responses and objections.
A lawyer's desk with a laptop full of client emails, a phone, a hard drive and a draft complaint beside a one-page worksheet

Before filing, the client's files arrive all at once; the signer needs to know which allegations they actually support.

The files arrive before the complaint does. A client hands over a laptop, a phone, a shared drive and years of email, and the lawyer already has a filing date circled. The questions that follow are practical ones. What does processing and review cost per gigabyte on a small civil case? Can a solo litigator facing thousands of emails and chats afford AI document review at all? How does a small firm Bates-number and produce documents defensibly without paying a litigation support vendor?

Rule 11 asks something narrower first. Was your look at the facts reasonable for the time and the material you had?

This article answers that with one working document. A Pre-Filing Evidence Map is a one-page record that ties each factual allegation in a draft complaint to at least one client document the signer actually reviewed, or flags the allegation as likely to need discovery. It does not require reading everything. It requires knowing which rows rest on paper and which rest on hope.

The procedure for sanctioning a lawyer is its own field. The Villanova Law Review gave the procedural mechanics of Rule 11 attorney sanctions dedicated treatment, apart from the standard of conduct itself. I stay with the standard here: what the signature certifies, what a reasonable look costs a small firm, and how each row of the map gets built, checked and dated by the person who signs.

Start with the signature, because everything else on the page hangs from it.

Every pleading filed in federal court must be signed by at least one attorney of record, in the attorney's own name. That signature is a promise about facts. It is made by one person, usually late, usually with a client's hard drive still copying in the next room.

The client wants the complaint filed. The drive holds more than anyone will read before the deadline. The lawyer knows this. The question underneath is simple and rarely answered in writing: how much of it did I have to read?

Rule 11 has carried that weight for a long time. The Villanova Law Review gave a full article in Volume 34 to the procedure of sanctioning attorneys under the rule, separate from the standard itself. Critics of the 1983 amendment warned that it would chill valid claims and breed fee fights unrelated to the merits. Supporters called it a cure for litigation abuse.

Neither side gave the signer a worksheet.

What follows is one. I call it the Pre-Filing Evidence Map, and it starts with the text of the certification you make when you sign.

Can you build the map on your own client's collection?

Yes. Bring a messy collection and a hard question, and watch Relevant e-Discovery read, code and cite your own evidence instead of someone else's case study.

It runs in your cloud, under your keys. You sign the complaint. The map shows why you could.

Book a working session on your matter

What does Rule 11(b)(3) actually certify when you sign?

Your signature certifies that each factual contention has evidentiary support, or likely will after discovery, based on an inquiry reasonable under the circumstances. Volume read is not the test.

Before signing a complaint built on a client's ESI (electronically stored information, meaning the emails, chats and files the client hands over), work through three checks:

  1. List every factual allegation the complaint makes, one per line.
  2. For each one, find at least one client document you have actually reviewed that supports it.
  3. Where no reviewed document exists, decide whether the pleading will specifically identify that allegation as likely to have support after discovery.

Federal Rule of Civil Procedure 11(b) contains four certifications, and the third one governs facts. The text published by Cornell's Legal Information Institute says factual contentions must "have evidentiary support or, if specifically so identified, will likely have evidentiary support after a reasonable opportunity for further investigation or discovery." The duty attaches when a paper is presented, "whether by signing, filing, submitting, or later advocating it." The 1983 Advisory Committee note called the reasonableness standard "more stringent than the original good-faith formula."

Picture the moment the rule was written for. A client sets a drive on the desk. Inside are years of email, chat exports, spreadsheets nobody has opened since they were saved. The limitations period runs out in weeks. The lawyer who signs is the one who answers for what the complaint says.

The common assumption is that a careful lawyer reads everything before signing. The rule does not say that. It asks what inquiry was reasonable, and it leaves room for allegations that are honestly flagged as needing discovery.

The stakes were never small. Writing in the Buffalo Law Review in 1989, Carl W. Tobias read the amended rule as one that "essentially requires that judges impose sanctions on lawyers and parties who fail to conduct reasonable inquiries before filing court papers." Separate law review work has studied how the Seventh Circuit applied Rule 11 sanctions, and how courts handled the procedure for sanctioning attorneys. Across the 5 sources drawn on here, none sets a page count or a percentage of documents a signer must read.

Cost sits underneath all of it. At Relevant e-Discovery, our analysis of review economics puts AI-assisted review at cents per document, against dollars per document and roughly $19K per gigabyte for manual review. Reading every page is expensive. It is also not what the signature promises.

The same question is now arriving from a different direction, as judges and bars ask whether courts will require a human to oversee AI document review. Either way, the signer stays responsible. Which leaves the harder question for the next section: how much reading is reasonable when the drive holds more than anyone can open before the deadline.

If a client hands you a mountain of ESI, how much must you read before you sign?

When the committee that toughened Rule 11 in 1983 described what makes a prefiling inquiry reasonable, its list said nothing about how many documents a lawyer must read.

The fear of having to read everything has a real source. In its 1983 note, the Advisory Committee admitted that "in practice Rule 11 has not been effective in deterring abuses." It swapped the old "good ground to support" language for a reasonableness test it called "more stringent than the original good-faith formula," expecting that "a greater range of circumstances will trigger its violation."

Yet the same note tied a reasonable inquiry to the circumstances, and one factor it named, reliance on a client for the facts, describes the large ESI handoff almost exactly. The words "such factors as" leave the list open, but none of the named factors counts documents read.

The stricter standard caused a fight. Writing in the Buffalo Law Review in 1989, Carl Tobias said the amendment "may well have engendered more controversy than any other revision" since the Federal Rules were first adopted. Critics attacked it "for chilling valid claims," and he argued that civil rights plaintiffs and their lawyers paid the price. In 1988, U.S. District Judge William Schwarzer had proposed that courts judge violations by how reasonable the prefiling inquiry was and leave the merits aside. Tobias found many of his ideas "cogent" but preferred curtailed enforcement, repeal or amendment.

YearWhat happened to the standard
1937The original rule combines two former Equity Rules on counsel's signature and on scandal and impertinence
1983"Good ground to support" gives way to reasonableness under the circumstances (effective Aug. 1, 1983)
1988 to 1989Schwarzer and Tobias debate whether courts should focus on the prefiling inquiry and how hard enforcement falls on civil rights cases
1993Contentions needing discovery can be specifically identified (effective Dec. 1, 1993)

The 1993 revision gave relief to the lawyer facing a mountain of files, with limits. The committee acknowledged that a litigant "may have good reason to believe that a fact is true or false but may need discovery." Even so, flagging a contention does not relieve anyone of "an appropriate investigation into the facts that is reasonable under the circumstances," and "it is not a license" to make claims "without any factual basis or justification." The flag also expires. If support does not turn up after a reasonable chance at discovery, the party "has a duty under the rule not to persist with that contention."

The note also sets how much support is enough. The certification concerns evidentiary support for the allegation, "not that the party will prevail." Losing at summary judgment "does not necessarily mean" a party lacked support, and evidence enough to defeat a summary judgment motion counts as sufficient. The lawyer's job, then, is to find support for each allegation, and that does not require reading every file.

"The court is expected to avoid using the wisdom of hindsight and should test the signer's conduct by inquiring what was reasonable to believe at the time the pleading, motion, or other paper was submitted."

Advisory Committee note to Federal Rule of Civil Procedure 11

When an inquiry is challenged, the court asks what you had in front of you on the day you signed. A dated record linking each allegation to its document answers that question directly. We build review software whose outputs link back to the exact exhibit they came from, so we have a stake in this reading. The rule also protects you: a signer need not disclose privileged communications or work product to show that the signing was substantially justified.

The consequences are real. Absent exceptional circumstances, the firm is held jointly responsible for its lawyers' violations. Sanctions are limited to what deters repetition. A motion cannot be filed if the challenged contention is withdrawn or corrected within 21 days of service, and that window is most useful when you can see which contention rested on what.

Through each revision and the debate around it, the court's question has stayed tied to the single allegation and the moment you signed. The size of a collection enters only indirectly, through the time you had and what the client gave you. A large ESI set matters for what it lets you support, allegation by allegation, on the day you sign.

  • For every factual allegation, record which reviewed document supports it and the date you reviewed it, so the record answers the question a court will ask: what was reasonable to believe at signing.
  • Where support depends on discovery, identify that contention specifically in the pleading, and still write down the investigation you did, because a flag does not replace a reasonable inquiry.
  • Write down the circumstances behind your inquiry: how much time you had, what the client supplied and what you relied on it for.
  • Put a recheck date on each flagged contention. If discovery does not produce support after a reasonable opportunity, stop advocating it.
  • If you are served with a sanctions motion, use your record to find the specific contention to withdraw or correct within the 21-day safe harbor.

How we checked this

We read the text of Rule 11, its amendment history and the Advisory Committee notes published by Cornell's Legal Information Institute, plus the published summary of Carl Tobias's 1989 article, which responds to Judge Schwarzer's 1988 commentary. This section uses no figures from our own data. The description of source-linked outputs is our own product claim. Committee notes show what the drafters intended. They cannot show how individual courts or circuits apply the standard today. Tobias's article covers the first half-decade under the 1983 version and reflects the debate of that era, not current enforcement. We sell AI review software, so we have a commercial interest in a per-allegation, source-linked approach. Still unknown: none of the sources we read discusses large ESI sets directly, and we found no ruling on how much weight a court gives a source-linked record of prefiling review.

  1. Federal Rule of Civil Procedure 11, rule text and Advisory Committee notes, Legal Information Institute, retrieved November 20, 2026.
  2. Carl W. Tobias, Rule 11 and Civil Rights Litigation, 37 Buffalo Law Review 485 (1989), UR Scholarship Repository.
  3. Relevant e-Discovery, product description of source-linked review outputs, 2026.

How can a small firm reduce the cost of pre-filing document review?

Review less, and review on purpose. A solo or small firm on one messy matter needs enterprise-grade defensibility at small-matter economics, not a full read of every file.

The trouble starts with the collection itself. A client who has lived inside a dispute for a long time does not hand over a tidy folder. They hand over everything. Email threads that branch and branch again. Chat exports with no subject lines. Spreadsheets named "final," then "final2." Somewhere in there is the document that proves the allegation the whole complaint leans on. Most of the rest is noise.

The economics of reading all of it are punishing. The per-document gap between manual and AI-assisted review, set out in the previous section, means a full manual pass can cost more than the claim is worth. Enterprise platforms solve the volume problem, but they were built for large teams. Relevant e-Discovery was built to be operable and affordable for a solo or small firm on a single messy matter, the exact segment Relativity and Everlaw price out and cannot serve without an administrator.

Cost is only half of it. The other half is what the law actually weighs.

The 1983 Advisory Committee note to Rule 11, reproduced by Cornell's Legal Information Institute, lists factors that shape a reasonable inquiry:

  • How much time was available for investigation before signing.
  • Whether the signer had to rely on the client for the underlying facts.
  • Whether the paper rested on a plausible view of the law, and whether the signer depended on forwarding counsel or another member of the bar.

Read those factors next to a client's hard drive. Time is short. The client is the only source of the facts. Nothing there demands a page-by-page reading. The note also tells courts to avoid "the wisdom of hindsight" and to test "what was reasonable to believe at the time" the paper was submitted.

A brief aside, because I think it matters. I would rather defend a narrow review I can show than a broad one I can only describe. A lawyer who says "I went through the documents" has a sentence. A lawyer who can point to the document behind each allegation has a record.

So the cost question turns into a targeting question. If you know which allegations you must support, you know which documents you must find. You do not need most of the drive to sign. You need the right pages, and proof you read them. The idea that a bigger document set always means a longer review falls apart once review starts from the complaint rather than the collection.

That shift, from reading the pile to answering the pleading, is where the map begins.

What is a Pre-Filing Evidence Map, and what goes on it?

A Pre-Filing Evidence Map is a one-page record tying each factual allegation to a reviewed client document, or flagging it for discovery, so the signer can verify every link before filing.

The map has one row per allegation. Nothing more is needed to start. Each row answers a plain question: what did I read that lets me say this?

ColumnWhat it recordsWhy it matters at signing
Complaint paragraphThe paragraph number of the factual allegationKeeps the map in the same order as the pleading
AllegationThe fact asserted, in a few wordsSeparates factual contentions from legal ones
Supporting documentA document ID or Bates number for at least one reviewed sourceShows the support existed before the signature
StatusSupported, or flagged as likely to need discoveryMatches the two paths the rule allows for facts
Verified by and dateThe attorney who opened the document and whenFixes what was known at the time of filing

Look at the last column first. It is the one most lawyers skip. A map that lists documents nobody opened is a guess dressed up as a record. The attorney's verification is what turns a search result into an inquiry.

That is where source-linked review earns its place. At Relevant e-Discovery, our approach is that every answer traces to its source: outputs link back to the exact exhibit they came from, so an attorney can one-click verify before filing. That is the structural answer to the Mata v. Avianca sanctions risk, where unverified output reached a court. In practice, the supporting document column fills itself with links, and the verification column stays the lawyer's job.

Two further properties keep the map honest.

  • The originals cannot drift. Our platform keeps immutable originals with content hashing, append-only audit trails and documented chain of custody, behind a fail-closed privilege gate on production. If the inquiry is challenged, the document behind row 1 is the same document it was on filing day.
  • The collection stays in your control. Processing runs single-tenant, or inside your own AWS account under your own keys, with no vendor retention and no model training. Building the map does not hand privileged material to anyone.

Privilege deserves its own thought before any of this begins. Some client documents will be privileged, and they may be the best support you have. The map can cite them by ID without disclosing their contents, and designing a privilege gate so privileged ESI never reaches review covers how to keep them fenced off from anything that leaves the firm.

Enterprise platforms supply the defensible spine of Bates numbers, privilege and chain of custody. Newer AI tools supply cited questions and answers. The map needs both at once. A row with a link but no custody record is fragile. A row with custody but no link is slow.

The harder rows are the ones with an empty supporting document column, and what you write in the status column next to them.

What should you do before signing your next complaint?

Build the map before you sign. One row per allegation, each tied to a reviewed document or honestly flagged for discovery, dated and verified by the lawyer who signs.

Rule 11 never asked anyone to read the whole drive. It asked for an inquiry reasonable under the circumstances, and it let the signer name what still needs discovery. The map is just that inquiry, written down.

The record matters longer than people expect. The certification attaches again each time a paper is later advocated. A sample motion in limine invoking Rule 11, kept in the NIWAP Library at American University Washington College of Law, shows the rule surfacing well after the pleading stage.

My recommendation is plain. Start the map the day the client's collection arrives. Leave the empty rows empty. Then decide, row by row, which ones the complaint will flag, and which ones it should not plead at all.

Summarize This Article With AI

Open this article in your preferred AI engine for an instant summary.

Frequently Asked Questions

What else do lawyers ask about pre-filing review under Rule 11?

Most follow-up questions concern unconfirmed facts, privacy of the map, firm liability, verification and cost. Each has a direct answer in the rule's text or Relevant's own terms.

Can I plead a fact I have not confirmed yet?

Yes, if you say so. Rule 11(b)(3) allows a factual contention that "will likely have evidentiary support after a reasonable opportunity for further investigation or discovery," provided it is "specifically so identified." That is the flagged row on the map. Leave the label off, and the same sentence goes out certified as already supported by evidence you hold.

Do I have to hand my evidence map to the court?

Not as a matter of course. The 1983 Advisory Committee note says the rule "does not require a party or an attorney to disclose privileged communications or work product in order to show that the signing of the pleading, motion, or other paper is substantially justified." I would treat the map as work product, meaning material counsel prepares for the litigation, and guard it that way.

Who answers for the map if an associate built it?

The firm, usually. "Absent exceptional circumstances, a law firm must be held jointly responsible for a violation committed by its partner, associate, or employee," Rule 11(c)(1) says. The signature still belongs to one lawyer. So the verified-by column should name that lawyer, not whoever typed the row.

Does the complaint itself need to be verified?

Usually not. Under Rule 11(a), unless a rule or statute specifically states otherwise, a pleading need not be verified or accompanied by an affidavit. Some rules and statutes do require it. Check before you rely on the default.

What can a Rule 11 sanction actually include?

Whatever deters, and no more. Under Rule 11(c)(4), a sanction "must be limited to what suffices to deter repetition of the conduct or comparable conduct by others similarly situated." It may be a nonmonetary directive, an order to do or stop doing something, a penalty paid into court, or, on motion, part or all of the movant's reasonable attorney's fees. The order must describe the conduct and explain its basis.

What does Relevant e-Discovery charge, and how do I start?

The economics are demonstrable, not asserted. AI-assisted review runs at cents per document, against the manual review costs set out earlier, and the difference shows on your own matter. To see it, book through the Relevant e-Discovery contact page and bring the draft complaint, the client's files, and the allegation you trust least.

Written by

Michael

Kansky

Michael Kansky is a serial software entrepreneur who has spent more than two decades building and bootstrapping profitable SaaS and services companies.

Connect on LinkedIn

Read next

Photorealistic editorial scene of a small law firm conference table at dusk, a printed spreadsheet of search terms and hit counts marked up in red pen lying beside an open manila folder of stapled documents, aEdiscovery

Negotiating Search Terms With Opposing Counsel: A Hit-Report Ladder

Agree on search terms in measured rounds: run each proposed term, share the hit report, code a random sample of hits, calculate precision per term, and revise before signing anything.November 22, 202620 min read
Editorial photograph of a small law office at dusk: a litigatorEdiscovery

Offshore Document Review: The Privilege Risk Nobody Prices

Not on supervision alone. Offshore review saves labor, but a confidentiality agreement cannot verify where privileged files travel, which country's data law reaches them, or keep malpractice exposure off your firm.November 20, 202620 min read
A litigation attorney sits at a cluttered small-firm desk in warm late-afternoon window light, pen in hand, initialing a printed sampling checklistEdiscovery

Will Courts Require a Human to Oversee AI Document Review?

Yes, in practice: courts will not ban AI document review, but by 2027 a documented attorney checkpoint, recording who designed, sampled and approved the review, will likely decide whether it is defensible.November 20, 202621 min read

See it on your matter

Bring us a messy collection - mailboxes, scans, phones, recordings - and watch it become one searchable, defensible record.