Assign one accountable owner to every request, define what counts as complete, and keep one current tracker that records status, source location, version, reviewer, and next action. The owner is responsible for finding or explaining the item, not for making a legal judgment about disclosure. Start with a deal-specific request list, route financial and tax questions to the people who maintain those records, and ask qualified counsel to address legal scope, privilege, and redactions. Review each upload against the request, follow up on missing or unclear items, and finish with a documented owner sign-off. This creates accountability without pretending that a full checklist alone proves diligence is complete.
Start with a request list that matches the deal
A pre-sale request list is a control document, not a promise that every possible diligence question has been answered. Begin with the transaction context, the likely buyer questions, and the records the business actually maintains. A practical list can have categories for financial information, material contracts, customers and suppliers, employees, intellectual property, permits, disputes, insurance, assets, and corporate records. The American Bar Association describes diligence lists that cover contracts, financial statements, litigation, intellectual property, customer arrangements, employee arrangements and policies, and regulatory filings. [4]
Tailor the list to the business and proposed transaction. An asset sale may raise different questions from an equity sale. A regulated operation may need more careful review of licenses or approvals. A business with few employees may not need the same employee category as a larger employer. Do not copy a generic index and call it complete. Add a short purpose statement for each request so the owner understands what decision the record supports.
Define ownership as accountability, not expertise
Assign one primary owner to each request or tightly related request group. The owner might be the person who maintains the accounting records, manages contracts, handles people operations, or knows a particular operational process. A second person can be a backup, but a shared label such as “management” is not an accountable assignment. NIST describes document and records control in terms of requirements, roles, and responsibilities that keep records appropriately controlled and managed. [3]
Write the assignment so it is observable. For example, an owner may be responsible for locating the current customer agreement set, confirming the date range, listing known gaps, and sending the package for review. The owner is not automatically authorized to waive a request, interpret legal privilege, or decide whether a sensitive document should be disclosed. Those decisions should go to the business owner and, where appropriate, qualified legal counsel.
Give every row a useful definition of done
A status such as “uploaded” is not the same as complete. For each row, define the expected record, date range, entity or business unit, format, and any required explanation. Completion might mean that the current signed agreement and amendments are present, or that the owner has documented that no agreement exists and identified the operating arrangement instead. The standard should be specific enough that another reviewer can test it without asking what the owner meant.
Use a small status vocabulary. “Not started” means no work has been confirmed. “In progress” means the owner is locating or assembling material. “Ready for review” means the owner believes the response satisfies the request but a reviewer has not checked it. “Needs follow-up” means an item is missing, inconsistent, unreadable, outdated, or unclear. “Complete” should require both an acceptable response and a recorded check. Keep “not applicable” separate from “not found,” because they call for different follow-up.
Make the tracker the source of truth for the work
Maintain one current tracker rather than letting status live in email threads, personal notes, and folder names. Useful fields include request ID, category, description, primary owner, backup, status, source location, version or date, confidentiality note, reviewer, last request date, next action, and completion date. A source location should point to the controlled working copy or approved repository path, not merely say “shared drive.”
The IRS explains that businesses may use a recordkeeping system suited to their operations when it clearly shows income and expenses, and that supporting documents should be kept in an orderly and safe manner. [1] That guidance is not an M&A checklist, but its underlying discipline is useful: connect a summary record to the documents that support it. Keep the tracker itself versioned, restrict editing to designated users, and record material changes instead of silently replacing history.
Use a repeatable follow-up loop for missing items
When a response is missing or weak, send a precise follow-up to the owner. Identify the request, state what was received, explain the gap, and ask for a specific next action and date. “Please complete contracts” creates ambiguity. “The signed agreement is present, but the renewal amendment referenced in section 4 is missing. Please locate it or confirm who can explain its absence” gives the owner a testable task.
Escalate based on impact and elapsed time, not personal pressure. A repeated missing item affecting a material customer contract, a key license, a major liability, or a financial reconciliation deserves earlier attention than a low-risk administrative gap. Preserve the unanswered request and response in the tracker. If the business cannot locate a record, document the search performed, the reason it may not exist, and the person who can provide context. Do not create a replacement record that could be mistaken for an original.
Check the record, not just the filename
A completion check should compare the response with the request definition. Confirm that the document belongs to the correct entity, covers the requested period, includes referenced schedules and amendments, opens correctly, and is the current approved version. Compare important summaries with the underlying records. For example, a contract list should reconcile to the agreements supplied, and a revenue schedule should have a clear relationship to the books used to prepare it. The IRS identifies books, transaction summaries, and supporting documents as connected parts of recordkeeping. [2]
Use a reviewer who can recognize an obvious mismatch but do not treat a general review as legal, tax, or accounting advice. A reviewer can flag an unsigned agreement, an unexplained variance, a missing page, or an inconsistent date. The relevant specialist or counsel should decide what the issue means and what response is appropriate. Record the reviewer, date, result, and open question so the completion decision can be revisited.
Protect sensitive material while keeping the process usable
A request tracker often contains more sensitive information than a simple folder index because it records gaps, disputes, personnel matters, and access decisions. Use least-necessary access, separate especially sensitive categories where appropriate, and agree with counsel on handling privileged or restricted material before sharing it. Do not assume that putting a document in a particular folder makes it privileged, secure, or suitable for disclosure. Confidentiality duties and disclosure decisions depend on the facts, agreements, and applicable law.
Use neutral labels for access and review status. A note such as “counsel review required” is more useful than a conclusory claim that a document is privileged. Keep a clean distinction between the business record, the diligence response, and internal commentary about the response. If a tool with automated extraction or summarization is used, define the task, limit the source set, prevent unauthorized disclosure, and require a human to check the output against the original. Stop the pilot if access cannot be controlled, citations cannot be traced, or reviewers cannot reliably identify errors.
Run a final completion review before sharing
Before a buyer receives a response set, run a closure meeting or written review against the tracker. Look for rows marked complete without a source location, documents with conflicting versions, unexplained “not applicable” answers, and follow-ups with no owner. Confirm that each material exception has an explanation and an assigned decision-maker. The ABA notes that data-room work includes organizing folders, monitoring uploads, cataloguing completed requests, identifying missing documents, and maintaining reliable version control. [4]
The final question is not “Is every box green?” It is “Can the business explain what was provided, what was not found, what remains under review, and who approved the response?” Keep an exceptions log for unresolved issues. Where legal, tax, employment, regulatory, or accounting consequences may follow, ask the appropriate qualified adviser to review the issue. Jurisdiction, transaction structure, and the terms of the deal can change what must be provided and how it should be handled.
Turn the workflow into a repeatable owner practice
After the first review, improve the process without rewriting history. Note which requests were unclear, which records had no natural owner, and which recurring gaps should be addressed in ordinary operations. Assign ownership before the next request arrives. A simple monthly or quarterly check of important contracts, financial support, permits, employee records, and corporate approvals can make later diligence less dependent on memory. Retention periods vary by record type and jurisdiction, so do not replace a qualified adviser’s guidance with a generic calendar.
For business owners, Acquivo gives business owners the entire sell-side process an investment bank would run, as software, with no success fee. It is user-operated software, so the owner remains responsible for deciding what to collect, who may access it, which sources are reliable, and when qualified professionals should review an issue. Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. The useful implementation target is not automatic approval. It is a visible, reviewable chain from request to owner to source record to human completion check.
Key Points
- Assign one primary owner and an optional backup to every request, with legal and disclosure decisions routed to the appropriate qualified reviewer.
- Define complete in observable terms, including the expected date range, entity, version, supporting schedules, and explanation for not-found or not-applicable items.
- Keep one controlled tracker with status, source location, reviewer, next action, and completion evidence.
- Follow up with specific gap descriptions and document searches, responses, escalations, and unresolved exceptions.
- Use human review for material, sensitive, legal, tax, accounting, employment, and regulatory issues, and stop automated pilots when access or error checking is unreliable.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
- [1] Recordkeeping · Accessed
- [2] What kind of records should I keep · Accessed
- [3] Document and Records Control Program · Accessed
- [4] How to Navigate the Key Stages of an M&A Transaction · Accessed
Choose your next step
Acquivo is user-operated software. Owners and their professionals remain responsible for decisions, communications, and professional review.
Educational information, not individual legal, tax, or investment advice. Consult qualified professionals for your circumstances. Acquivo provides software, not representation or negotiation on your behalf.