The Problem With Large Case Files Is Not Size Alone. It Is Fragmentation.

A lot of firms blame large case files for being too big.

That is the easy explanation. It is also the lazy one.

Size creates weight. Fragmentation creates confusion. And confusion is what actually slows review, weakens confidence, and makes big PI files dangerous to handle manually. The real problem is not that the file has thousands of pages. It is that the useful story is broken apart across scattered, repeated, and poorly aligned material that does not hold together on its own.

That is why two files with similar page counts can create completely different levels of pain. One is large. The other is fractured.

Page count is obvious. Fragmentation is what does the damage.

Page count gets blamed because it is visible. Anyone can look at a file and say, “This is huge.”

But volume alone does not explain why review bogs down. What makes a case hard is when the timeline is split across providers, the same event shows up differently in multiple places, key details are buried in unrelated sections, and the reviewer has to keep deciding what belongs together and what does not.

That is fragmentation.

And fragmentation is far more destructive than size because it attacks continuity. Once continuity breaks, the reviewer stops moving through the case and starts manually rebuilding it.

Fragmentation turns review into reconstruction

This is where firms quietly lose control of the file.

A reviewer is no longer just absorbing information. They are trying to reconstruct order from disorder. They are matching dates, linking events, resolving overlap, spotting duplication, and figuring out whether a detail is new, repeated, contradictory, or simply out of place.

That work is slower than reading because it demands judgment at every turn.

A large but coherent file can still be worked through. A fragmented one keeps interrupting the reviewer’s understanding. It forces them to stop, re-check, compare, and second-guess. That is why fragmented files feel heavier than they look. The burden is not just more material. It is weaker continuity.

Weak continuity makes every answer more fragile

This is the part firms should take seriously.

When continuity is broken, even basic answers get less stable. Treatment sequence becomes harder to pin down. Gaps become easier to miss. Cause and effect get blurrier. Supporting facts are harder to validate. The team may still reach the right conclusion, but it takes more effort and comes with less confidence.

That fragility matters.

Because in PI work, weak continuity does not just waste time. It creates risk. The more the file forces people to piece the case together manually, the more the review depends on memory, persistence, and individual sharpness holding up under pressure.

That is not a reliable operating model. That is a gamble.

Big files become dangerous when they stop holding together

This is the distinction firms need to get right.

A file is not difficult just because it is large. It becomes difficult when its internal coherence falls apart. Once the facts are scattered, duplicated, and poorly aligned, the case stops presenting itself clearly. The team has to manufacture clarity by hand.

That is where review gets slower. That is where confidence weakens. That is where important details become easier to miss.

The takeaway is simple: if your team still treats page count as the main problem, you are measuring the file like an amateur. Size matters. Fragmentation is what actually breaks the review.