Quick answer: A seller manages diligence by running it like a project. One person receives every buyer request, logs it in a tracker with a responder and a promised date, and routes answers through the M&A advisor and counsel before release. Sensitive documents are released in stages, every question and answer is recorded in a log, and the business keeps hitting its numbers. Fast, consistent answers protect price because delay and contradiction give a buyer reasons to doubt the earnings.
Key points
- Diligence is a project with a coordinator, a tracker and a log. Answers given ad hoc, from memory, contradict each other, and contradiction reads as risk.
- One channel in and one channel out. Every request enters a single tracker, and every answer leaves through a single reviewed path.
- Release information in stages. Financial and legal basics go first, and customer names, pricing and individual pay go late, to the buyer that has earned them.
- The business must keep performing. Monthly results during diligence are read as evidence about the forecast, and a weak month gives the buyer a reason to reopen the price.
Diligence run as a project, with named roles
Diligence is the verification stage between the letter of intent and the signed purchase agreement, and a seller manages it best as a project with a small team. The decision rule is that few people can speak for the company, every statement they make can be supported in writing, and nobody answers the buyer except through the coordinator. The seller’s due diligence checklist lists what buyers ask for. The question here is how the asking and answering is run.
| Role | What it does | What it avoids |
|---|---|---|
| Owner | Decides on sensitive disclosures, speaks to the buyer on strategy and people, keeps running the business | Answering document requests directly or off the record |
| Coordinator | Receives every request, logs it, assigns a responder, chases, checks each answer for consistency before it leaves | Making judgment calls on sensitive items without the advisor and counsel |
| M&A advisor | Triages and narrows requests, reviews answers, holds the call with the buyer’s lead, keeps the timetable | Drafting legal positions or tax conclusions |
| Attorney | Reviews contracts, litigation and privileged material, prepares the disclosure schedules for the purchase agreement | Managing the daily flow of financial requests |
| Outside accountant | Answers financial and tax questions and supports the reconciliation of the numbers to the buyer’s report | Presenting adjustments the schedule does not support |
| Responders | Supply facts from operations, HR, IT and finance to the coordinator | Replying to the buyer directly |
The owner is deliberately not the first responder. The coordinator is usually the controller or finance lead, or a manager who knows where the records live. The role is a real job for the duration of diligence, and it works only if the coordinator carries the owner’s authority to chase colleagues.
From the buyer’s request list to the seller’s tracker
The buyer’s request list arrives as a spreadsheet or inside the data room, and it is usually long and full of overlaps, because the buyer’s accountants, attorneys and operating advisors each send their own. A seller who answers line by line receives the same question several times. The coordinator and the advisor convert the lists into one tracker.
- Consolidate. Merge duplicate requests from different advisors into one row and note who asked.
- Triage. Mark what gates price (earnings, working capital, customers, change-of-control terms), what is standard and what is low value.
- Assign. Give each row one responder and a promised date that the responder has agreed to.
- Narrow. Where a request asks for every document of a kind, offer a summary or a defined sample, and say why.
- Review. Nothing leaves before the coordinator checks it against what the buyer has already been told, and the advisor or attorney reviews anything sensitive.
- Log. Record the answer and the documents, and update the room.
Illustrative example: A tracker with three sample rows
The columns matter more than the rows. Each request gets one row, one responder and one promised date, and the status column is what the weekly call reads from.
| Ref | Request | Area | Priority | Responder | Promised | Status | Release rule |
|---|---|---|---|---|---|---|---|
| F-014 | Monthly trial balances for the full prior year | Financial | Gates price | Controller | Friday | Answered, in the room | All approved buyers |
| C-007 | Contracts with the largest customers | Customers | Gates price | Operations lead | Next Wednesday | With counsel for redaction | Names masked until exclusivity |
| P-022 | Employee list with pay | People | Standard | HR lead | Following Monday | Open | By role only, names held back |
A second tab holds the Q&A log, one row per question, with the date asked, who asked it, who answered, the written answer and the documents attached. A weekly rhythm keeps both current: the coordinator sends the status on Monday, the advisor holds one call with the buyer’s lead midweek to settle priorities, and answers go out in a single reviewed batch before the weekend. The references, dates and rows are invented to show the structure and are not a standard.
The tracker doubles as the agenda for the weekly call, and it records which items are waiting on the buyer. That record matters when the exclusivity period is running down, a point developed in the guide to exclusivity and no-shop provisions.
Response discipline: speed, consistency and a written record
- Acknowledge quickly, answer completely. A request acknowledged the same day with a promised date reads as control. A silent request reads as something being held back.
- Keep the dates promised. A missed date does more damage than a slow answer that was honestly dated, so promise less and deliver on time.
- Keep one version of every fact. The CIM, the data room, the Q&A log and anything said on a call should agree. When a figure changes, say that it changed and why.
- Put answers in writing. A verbal explanation on a call is followed by a written note in the log, so that both sides remember the same answer.
- Correct mistakes at once. An error volunteered is a detail. An error found by the buyer becomes a doubt about the rest of the package.
- Disclose known problems early. A known issue goes to the buyer with its explanation and documents before the buyer’s accountants reach it. The guide to red flags buyers find shows what they look for.
Response-time targets stay qualitative. Priority items are answered before the next scheduled call, standard items go out in the weekly batch, and anything that needs a third party is flagged with the reason and a revised date.
Staged disclosure and sensitive requests
Information is released in stages as the buyer’s commitment rises. Before the letter of intent the buyer has the CIM and summary financials. After it, the buyer receives detailed financial records and contract summaries with names masked. Customer names, pricing, supplier terms and individual pay come last, to the buyer under exclusivity and sometimes only to its advisors. Items needed for signing, such as disclosure schedules and third-party consents, come at the end. The data room guide covers folders and permissions, and the release column of the tracker records which stage each item belongs to.
Sensitive requests need a rule so that each one is not debated afresh. The usual tools are redaction, aggregation, a summary with the documents open to advisors only, and a folder restricted to outside counsel. When the buyer is a competitor, a clean team is added: a small group that sees competitively sensitive data and reports its conclusions without the underlying detail. What a competing buyer may see before closing is a question for the seller’s attorney. Customer calls are a stage of their own, covered in customer diligence.
Keeping the business on plan while diligence runs
Buyers read monthly results during diligence as evidence about the forecast. A weak month gives them a reason to reopen the price, and a strong month rarely raises it. The owner’s calendar should therefore protect the business: the owner runs operations, the coordinator runs diligence, and a short weekly check-in connects the two. The monthly close stays on its normal schedule, and the owner reviews the numbers the buyer watches, such as revenue, gross margin, backlog and receivables, before the buyer sees them. If a month misses, the owner tells the buyer first and gives the reason.
Practices that distort working capital, such as pushing collections or stretching payables, are reversed by the working capital adjustment and noticed along the way. Deferring hiring, maintenance or marketing to lift a month is noticed as well.
Fatigue, momentum and requests that stray
Diligence consumes people who have day jobs. Fatigue shows up as slow answers and then careless ones, and careless answers are the ones that contradict each other. The advisor protects the team by batching requests into a weekly delivery, absorbing follow-up calls and asking the buyer to rank what it still needs. A short list of open items with a date beside each keeps momentum, and the guide to why business sales fall apart describes what happens when momentum is lost.
Requests that stray beyond what the letter of intent contemplated, such as new areas of work or the same item asked again in a different form, are raised by the advisor with the buyer’s lead and not answered in silence. The tracker shows what was asked and when. If the price is reopened, the guide to retrades after the LOI describes the response, and the whole sequence of review is set out in the guide to due diligence in a business sale.
Frequently asked questions
Who should be the point of contact for diligence requests?
One person who knows where the records live and can reach the owner quickly, often the controller, finance lead or a trusted manager, with the M&A advisor reviewing answers before they go out. The owner should not be the first responder, because the owner’s time belongs to the business and answers given from memory are the ones most likely to contradict a document.
How quickly should a seller answer diligence requests?
Acknowledge each request promptly and give a firm date for the answer. Items that decide price, such as earnings records and customer contracts, come first. Predictability matters more than raw speed: a missed promised date does more damage than a slower answer that was honestly dated. Anything waiting on a third party should be flagged with the reason.
What should a seller do when a buyer asks for customer names or pricing?
Treat it as a staged release. Early on, share aggregated or masked data. After the letter of intent, customer-level detail can go to the buyer under exclusivity, sometimes to its advisors only. If the buyer is a competitor, a clean team limits who sees the detail. The seller’s attorney advises on what a competing buyer may see.
How does a seller keep running the business during diligence?
By separating the jobs. The owner runs operations, and a coordinator runs diligence. A short weekly check-in connects them, the monthly close stays on schedule, and the owner reviews the numbers the buyer watches before the buyer sees them. If a month misses, the owner tells the buyer first and explains why.
Should answers to buyer questions be given verbally or in writing?
In writing, or confirmed in writing after a call. A verbal explanation leaves each side with its own memory of what was said, and differences surface later as disputes. A Q&A log that records the question, the answer, the date and the supporting documents gives both sides one record and lets the seller correct an error quickly.
Preparing a company for sale or a buyer's diligence?
The Impetus Group offers fractional investment banking support, including earnings normalization, financial projections, CIM preparation and help navigating buyer diligence, with an engagement scoped to what the business needs.
Related guides
- Due Diligence Checklist for Sellers: What Buyers Ask For and Why: A checklist of the documents and answers buyers request in diligence on a company sale, grouped by area, with the reason each request is made.
- Virtual Data Room for Selling a Business: Structure, Staging and Access: How to build and run a virtual data room for selling a business: folder index, staged access by bidder, masking, the question log, audit trail and version control.
- Why Business Sales Fall Apart: Causes, Warning Signs and How to Prevent Each: Business sales fail through diligence surprises, price gaps, owner fatigue, financing, lost customers and legal problems. See warning signs and prevention for each.
- Exclusivity and No-Shop Provisions in a Business Sale: Length, Terms and Trade-Offs: Exclusivity bars a seller from talking to other buyers after a letter of intent. See what a no-shop restricts, how long it should run and what to ask in return.
- Sell-Side Quality of Earnings Report: Scope, Timing and How to Use It: What a sell-side quality of earnings report covers, when an owner should commission it, who should perform it and how to use it in the CIM and with buyers.
- Quality of Earnings Findings That Reduce Price and How to Pre-Empt Them: The quality of earnings findings that most often lower a sale price, such as rejected add-backs and cut-off errors, with how each appears and how to pre-empt it.
This guide is general education. It is not a valuation opinion, appraisal, investment advice, or legal or tax advice. How these guides are made.