data.day
diligence / q&a / audit-trail / deal-velocity

The Spreadsheet Q&A That Became a Discovery Trap

Answering diligence questions in a loose Excel sheet is a trap. Without evidence, your answers are just opinions that breed more questions. Anchor every response to a document.

Elena Dossier Elena Dossier

Opinions Are Not Evidence

You believe that answering a diligence question is a conversation. You think if you explain the context nicely in a spreadsheet cell, the auditor will understand.

You are wrong. An auditor does not want your explanation; they want your proof. When you provide text without a citation, you are inviting them to debate your interpretation.

The Amateur Move: The Infinite Loop

Consider the “Case of the Floating IP.” A buyer asked a simple question in a shared spreadsheet:

  • Question: “Do all developers sign IP assignment agreements?”
  • Founder Answer: “Yes, everyone signs as part of onboarding.”

This looks like a closed issue. It is not. Two weeks later, the buyer’s counsel finds a commit from a contractor named “Dev_04” in 2022. They check the folder. No contract for Dev_04.

Now, the buyer does not just lack a contract; they lack trust in your previous answer. They reopen the question:

  • Re-inquiry: “Please reconcile the ‘Yes’ above with the missing contract for Dev_04.”

The founder scrambles. “Oh, that was a temporary agency, the agency signed the IP.”

  • Buyer: “Show me the agency agreement.”

This is the Discovery Trap. One sloppy “Yes” created three new lines of inquiry. The spreadsheet grew from 50 rows to 200 rows. The deal fatigue set in.

The Defense: The Anchored Response

We do not offer prose. We offer pointers. Every answer in the Q&A log must point to a specific file in the Data Room Index. If you cannot point to a file, you cannot answer the question.

The Rule of Citation Structure your responses like a legal brief, not a text message.

  • Question: “Is the IP assigned?”
  • Bad Answer: “Yes, we handle this in onboarding.”
  • Elena’s Protocol: “Yes. Refer to 1.04_IP_Assignments, specifically 1.04.01_Employee_Template.pdf (Clause 6) and 1.04.02_Executed_Agreements folder. For the contractor exception, refer to 1.04.05_Agency_Agreements_2022.pdf.”

The Staging Protocol Never answer questions one by one. This creates a “ping pong” dynamic that drains morale.

  1. Batch Ingest: Receive the buyer’s questions on Monday.
  2. Internal Triage: Assign questions to your finance, legal, and ops leads.
  3. Draft & verify: Write the answers and test the links. Does the file actually prove the point?
  4. Batch Release: Publish answers on Thursday.

This rhythm signals control. It shows you are not reacting to their anxiety; you are processing their requests.

[TO EDITOR: Guidance for illustration. A flowchart. Path A (Bad): Question -> Text Answer -> Follow-up Question -> Confusion. Path B (Good): Question -> Answer + File Reference -> Verified -> Closed.]

The “No” Is Just as Important

Sometimes the answer is “We do not have that.” Do not spin a paragraph of excuses.

  • Answer: “Not applicable. Company does not track this metric. See 0.00_Disclosure_Schedule for details.”

A precise gap is better than a fuzzy bridge. The former is a risk to be priced; the latter is a lie to be prosecuted.

FAQs

Why not just answer quickly in email/slack to keep things moving?

Because email is where the 'truth' gets fragmented. A Data Room Q&A tool centralizes the liability and the resolution.

What if the document doesn't exist yet?

Then you state: 'Document to be created.' Do not describe what it *will* say. Admit the gap and close it.

Should we allow the buyer to upload their own Q&A tracker?

No. You control the format. Ingest their questions into your system. Do not play on their home field.