In M&A diligence, there's a timing pattern that experienced corporate attorneys recognize but rarely discuss directly: the clause that matters most is discovered toward the end of the review period, not the beginning. Call it the four-day problem — though in practice the exact day depends on the scope of the room. The name captures the underlying dynamic: high-risk, non-standard provisions tend to surface late in the review window, at precisely the moment when the deal team has the least flexibility to act on what they've found.
This isn't random. There's a structural explanation for why material clauses cluster at the tail end of diligence. Understanding that structure is the first step toward doing something about it.
How Diligence Review Time Gets Spent
The distribution of review effort in a standard M&A diligence process follows a predictable pattern. Day one is orientation: reviewing the data room index, categorizing documents, assigning review tasks across the team. Day two and early day three focus on the documents that appear highest-priority by name or category — the main customer contracts, the material vendor agreements, employment agreements for key executives, the corporate organizational documents, the financial statements.
These are the expected-to-be-important documents, and they usually get the most careful reading. The problem is that risk doesn't distribute proportionally to document prominence. A 200-page data room for a mid-market transaction will typically contain 40 to 50 contracts that are individually unremarkable — maintenance agreements, platform subscriptions, professional services arrangements — that cumulatively represent significant operational dependencies. Those documents tend to get reviewed later, faster, and with less attention to non-standard provisions.
The four-day problem is the convergence of two forces: review fatigue and depth-of-review gradient. As the review period progresses, the team is working faster to close out the remaining documents. At the same time, the documents they're reviewing are the ones that got deprioritized earlier — often because they appeared less important, which means they're less familiar to the reviewers, which means non-standard provisions are harder to catch quickly.
The Cost Structure of Late Discovery
When a material clause is discovered on day one, it creates a negotiation conversation. When it's discovered on day four — or after signing — it creates a different kind of problem entirely.
Pricing adjustment leverage shifts
A non-standard indemnity carve-out, a consent requirement that's broader than market, an automatic renewal with a short termination window — any of these can be price-relevant if discovered early. Discovered late, the acquirer's options narrow. Renegotiating the purchase price after LOI based on a newly discovered provision is possible but difficult. The seller's leverage in that conversation is that the buyer has already publicly signaled intent, the deal team's momentum is pointed toward close, and backing out based on a provision in a $300,000 vendor contract looks disproportionate.
Closing conditions and timeline exposure
Third-party consents triggered by change-of-control provisions have to be obtained before close. If a consent requirement is discovered with two weeks until closing, the risk is that the counterparty — now aware that they hold a closing condition — uses that leverage to renegotiate. Consent fees, pricing adjustments, and term extensions all become more likely the later a consent requirement surfaces. We've seen situations where a consent process that should have taken a week stretched to three weeks because the counterparty's commercial team got involved once they understood the transaction context.
Post-close operational risk
The clauses that are missed entirely — not flagged late, but not flagged at all — become post-close problems. An unnoticed auto-renewal in a key vendor contract can lock an acquirer into pricing terms they would have renegotiated had they known. An IP ownership gap in a target's software development agreements can cloud title to technology that was part of the deal's valuation thesis. These aren't abstract risks; they're the kinds of issues that surface during post-close integration and generate the friction that makes integrations harder than they look at closing.
Why Standard Process Doesn't Solve It
The obvious response to the four-day problem is to start earlier or hire more reviewers. Both help at the margins. Neither addresses the underlying structure.
Starting earlier often just extends the same review pattern over a longer timeline. If the first three days focus on the high-prominence documents and the tail of the review covers the lower-priority contracts, adding two days at the front doesn't necessarily change which documents get the careful reading. It may just mean that the review team spends more time on the prominent documents and runs the same depth gradient on everything else.
More reviewers increases bandwidth but creates coordination overhead and consistency risk. If six associates are reviewing contracts independently and a non-standard provision appears in a document that none of them are cross-referencing, the flag still doesn't get made.
We're not saying that larger teams or longer timelines are bad approaches — they're often the right call. What we're saying is that they don't solve the root cause, which is that the standard diligence process doesn't systematically surface non-standard provisions regardless of where in the document stack they appear.
What Changes When the Tail Gets Flagged First
The most effective mitigation is changing the review sequencing — specifically, generating an early-stage flag list that covers the full document population before deep reading begins. When you know on day one that document 47 of 200 contains a provision that merits closer attention, the review schedule can be structured to address that document at the right depth, at the right time.
This is the core idea behind how we built Undwrlyft's first-pass review. The goal isn't to replace attorney judgment about what a clause means or how to negotiate around it. The goal is to make sure that the clause gets in front of an attorney at a point in the timeline when there's still room to do something about it. A flag on day one that says "document 47 contains non-standard indemnification language and a potential change-of-control trigger in Section 14.3" is not legal analysis — it's routing. It's making sure the document gets to the right person at the right time in the review process.
The four-day problem doesn't fully disappear, but it changes character. Instead of a late-breaking discovery that creates time pressure, it becomes an expected output of first-pass review that the deal team can plan around. That's a different kind of problem — a manageable one.
What to Do Before You Have Better Tools
Practically, there are adjustments to the standard diligence process that reduce late-discovery risk without requiring a different workflow:
- Index review with triage questions. Before diving into document review, spend an hour reviewing the data room index specifically to identify documents that could contain consent requirements, non-standard indemnification, or IP ownership provisions — regardless of their apparent priority level. Flag those for earlier review.
- Reverse the standard depth gradient for small contracts. High-value contracts almost always get careful attention. Systematically schedule detailed review of low-value contracts with operational dependencies (software platforms, key vendors, IP-adjacent agreements) earlier in the review window.
- Build the consent log on day one. Create a working document that tracks every contract that might require third-party consent on a change of control, and update it throughout the review. This forces the team to think about the consent question across the full document population rather than contract by contract.
None of these are new ideas. They're practices that careful M&A teams already use. The four-day problem persists because implementing them consistently under deal-timeline pressure is genuinely difficult. The value of a first-pass extraction layer is that it makes the discipline automatic rather than aspirational.