Post-LOI diligence should make the acquisition easier to judge, not simply make the data room larger. Every important request needs a reason, every conclusion needs support, and every unresolved issue needs an owner and a decision point. A folder marked complete is not the same as a risk understood.
The starting point is the preliminary review. Carry forward the facts and open questions that informed the proposal instead of creating a second, disconnected investigation. The buyer should be able to see what has changed since the initial assessment and whether the operating plan still makes sense.
This article accompanies Module 4: Post-LOI diligence. It explains how to organize findings, including what a quality-of-earnings review contributes and what it does not establish.
Organize the work around four evidence areas
Financial review examines the support for reported results, earnings adjustments, cash timing, and related financial questions. Commercial review considers customers, demand, order history, and the basis for expecting revenue to continue. Operational review considers the people, processes, assets, and costs needed to run the business. Legal review addresses rights, obligations, documents, and required permissions.
These areas connect without becoming interchangeable. A customer contract may matter to the commercial view of future revenue and to counsel's assessment of transfer restrictions. A production role may matter to continuity and to the cost of the buyer's operating plan. Assign the specialist questions to the appropriate advisers rather than making the deal tracker appear to resolve them.
The buyer's job is to keep the decision coherent across those reviews. If financial analysis assumes a customer remains, commercial evidence should support that assumption. If the operating plan assumes access to the current premises, the legal work cannot leave the right to occupy them as an unnoticed footnote.
Understand what quality of earnings produces
Quality of earnings, usually shortened to QoE, examines underlying earnings, their drivers, and support for proposed adjustments. Financial due-diligence professionals perform the review and document findings for the buyer and advisers. Its scope depends on the engagement and the business, so the buyer should understand what was and was not examined.
A QoE review is not an audit, a valuation, or a guarantee of future performance. RSM distinguishes financial statement audits from quality-of-earnings analysis as separate engagements with different purposes and procedures. That distinction matters when deciding what confidence a report can support.
Working-capital and debt-related analyses are related financial-diligence workstreams, not alternative names for QoE. They can interact with the earnings review, but they answer different questions. Keep their conclusions labeled so that an earnings adjustment is not confused with a contractual adjustment to the amount paid at closing.
Follow Cedar's consulting adjustment from claim to finding
Cedar Workshop is the fictional example carried forward from Module 3. It reports $1 million of EBITDA. The seller proposes adding back $120,000 of consulting expense. The review supports $40,000 for a one-time project, while $80,000 relates to work the business still needs.
The supported adjustment produces $1.04 million before other checks. It does not prove that this is the only relevant adjustment or that $1.04 million is cash available to the buyer. The important change is that the initial claim now has a documented basis and a limit.
| Review item | Cedar's illustrative record |
|---|---|
| Claim | $120,000 of consulting expense should be added back |
| Supporting evidence | The review distinguishes a one-time project from ongoing work |
| Supported adjustment | $40,000 |
| Earnings after this adjustment | $1,000,000 + $40,000 = $1,040,000, before other checks |
| Remaining question | What other findings and operating costs affect the buyer's assumptions? |
Preserve both the seller's proposal and the supported result. Replacing the original number without a record makes it harder to explain why the buyer's view changed. A concise findings row keeps the discussion focused on evidence rather than making the change look like an unexplained negotiating move.
Keep historical earnings separate from the buyer's plan
Suppose Cedar's owner performs work the buyer will need someone else to do. That raises an operating question: who will take responsibility, when will they start, and what will it cost? It should not automatically be treated as another historical QoE adjustment without the appropriate professional assessment.
The distinction is useful even when both questions affect the acquisition model. One asks what the historical earnings analysis supports. The other asks how the company would operate under a particular ownership plan. Keep the inputs separate, then show how the buyer has considered both.
For example, a completed consulting project and a proposed new management hire are not the same kind of item. The first may support a historical adjustment in the example. The second is a future operating assumption. Calling both “normalization” can hide the difference and make the proposal harder to explain.
A supported finding becomes an input to the proposal. It does not establish the agreed purchase price.
Write requests that are possible to complete
“Confirm revenue quality” is a broad objective, not a workable document request. A more useful request specifies the information, period, reason, and responsible person. The initial list can identify monthly revenue by customer for a defined period, with an explanation that the buyer is investigating concentration and changes in repeat work.
The request tracker should distinguish requested, received, under review, follow-up required, and resolved. “Received” is a delivery status. “Resolved” means the question has been assessed and its disposition recorded. The document may have arrived while the answer remains unclear.
Give each follow-up a due point related to the process. If an issue affects the proposal, it should not drift into a general post-close list. If the next answer requires specialist judgment, record the adviser review rather than setting an arbitrary internal deadline that assumes the conclusion.
Keep a findings log beside the document list
A document list tracks what arrived. A findings log explains what the review means. For every material issue, record the claim, source, conclusion, limitation, decision affected, accountable person, and next action. The two records can link to each other without becoming the same thing.
Cedar's consulting adjustment is one findings row. Customer continuity is another. Owner responsibilities need their own row. Premises permission should remain separate because it cannot be solved merely by establishing earnings. This separation prevents a favorable conclusion in one area from making unrelated open issues look resolved.
Use plain-language statuses. “Further evidence required” is more useful than a green icon beside an unexplained score. “Buyer accepts this commercial risk, subject to adviser review of the documents” is different from “permission obtained.” A status should describe what actually happened, not the team's preferred outcome.
Run a decision review before advancing
At the end of a review cycle, ask what changed, what remains open, and what action follows. Some findings lead to another request. Others change the operating assumptions, inform a revised proposal, require legal treatment, or justify pausing. No single outcome applies to every finding.
The supported consulting adjustment can inform the buyer's earnings input for pricing. It does not automatically reduce a price already agreed. Missing premises permission can require a legal and practical resolution; a lower price does not obtain permission. These examples illustrate why findings need decisions, not just numeric scores.
Tools can help organize documents and flag inconsistencies. They cannot turn an ambiguous invoice, incomplete agreement, or missing schedule into a reliable professional conclusion. Keep source access and human review visible in the record. The most useful automation shortens the search for evidence while preserving the question being answered.
Carry the evidence into pricing without losing its limits
The output of Module 4 is a clearer set of supported findings and unresolved questions. Module 5 uses those findings to explain a buyer's price position and the proposed payment components. Negotiation still determines what the parties accept.
Watch Module 4, then continue with how supported earnings inform an acquisition purchase price. Keep Cedar's review row beside the calculation: it is the evidence behind the number, not a separate piece of paperwork.
General buyer-side education. The Cedar figures are illustrative. Qualified advisers remain responsible for transaction-specific accounting, legal, tax, valuation, financing, and regulatory conclusions.