The other day, I found myself reading a report about Robert Brockman, a “software executive charged in the largest-ever tax case against a U.S. individual.” He is accused of “using a complex trust structure in the Caribbean to hide $2 billion in income over two decades.” The main focus of the story was the request by Brockman’s lawyers to move his case from San Francisco to Houston, where he is undergoing medical treatment to deal with progressive dementia.
But what caught my eye was the revelation that during an earlier court hearing in the case, “defense lawyer Neal Stephens said the case against Brockman involves 22 million pages of documents.” Two thoughts popped into my brain. The first was a question. How many other cases involving one taxpayer, if any, involved 22 million pages of documents or more? I tried to research the question, and though I found references to court cases and to other disputes not involving litigation that involved “millions of pages” of documents, none provided enough information to determine if “millions” meant three million or 10 million or 50 million. Many of these situations involved multiple parties, and very few, if any, were tax cases. I ignored references to matters such as property tax records maintained by governments that consisted of millions of pages because those databases related to tens of thousands and hundreds of thousands, if not a few million, taxpayers. So it’s unclear whether 22 million pages is a record.
The second thought that occurred to me was an observation. For those who find the idea of finding relevant tax law in the Internal Revenue Code, an effort simplified by the combination of search tools and digital technology, imagine being tasked with reading 22 million pages of documents in a tax case. No one person can do that in the applicable time frame. It takes a team. Yet it also requires someone to coordinate that team and to find ways to connect relevant information discovered by different team members in order to construct a chronology, a summary, or some other guide that is useful for the judicial proceedings.
Why am I confident no one person can read the 22 million pages within the time constraints of the litigation? The first step is to determine how many words are on 22 million pages. That is difficult because some of the pages might contain pictures, charts, graphs, or similar non-word material. It also is difficult because the margins, spacing, font size, and other characteristics of the material is unknown. The general rule of thumb is that a single-spaced page holds 500 words and a double spaced page holds 250 words. So, using 375 words per page as a rough benchmark, 22 million pages would contain 8.25 billion words. The second step is to determine how long it takes to read 8.25 billion words. As I wrote in So How Long Does It Take to Read the Internal Revenue Code?, “the answer depends on how fast a person reads. The average person reads roughly 200 to 250 words per minute. Note that it’s one thing to read, and a totally different thing to understand. Someone trying to understand written text might need to read more slowly, or to go back and reread some or all of the text.” Considering reading the material, and setting aside understanding, analyzing, interpreting, summarizing, or comparing the material to other information, it would take 41.25 million minutes, or 687,500 hours, to read 22 million pages. Reading for 12 hours a day, for 365 days, would require 157 years. Allowing time for understanding, analyzing, and otherwise absorbing the impact of the material would require many more years.
And some think reading the Internal Revenue Code, cover to cover, which I have done, is a horrendous undertaking. There probably are, however, a few people who enjoy reading long books, including those that consist of multiple volumes. If you need a list of suggested titles, check out this List of Longest Novels, on which War and Peace comes in at 32nd. And, no, the Internal Revenue Code isn’t on the list though it would be, near the bottom, if it were a novel, which it isn’t.