Counsel should manage bidder questions through one controlled register that preserves each request, assigns a factual owner, and separates drafting from approval and release. Maintain a verified common fact set, then assess each bidder's permitted access rather than copying answers indiscriminately. Require seller verification of business facts and counsel review of legal interpretation, confidentiality, and recipient restrictions before approving the exact response. AI may suggest routing and assemble cited drafts from authorized records, but it must not approve or send them. Preserve the released version, recipients, approvals, source references, and later corrections. This is a process framework, not transaction-specific legal advice; applicable rules and agreements require qualified counsel's assessment.
Define who can approve facts, legal wording, and disclosure
Before opening the question queue, identify the represented client and the people authorized to speak for the seller. Agree who verifies business facts, who reviews legal analysis, who authorizes disclosure, and who releases the response. A process coordinator can manage deadlines without becoming the decision-maker. For this workflow, seller and counsel approval are separate gates, even when one person coordinates both.
Under ABA Model Rule 1.6, disclosure of representation information requires informed consent, implied authorization, or a permitted exception, and lawyers must make reasonable efforts to prevent unauthorized disclosure or access. These are US model provisions, not a blanket rule for every jurisdiction. Counsel should check adopted local rules, client instructions, confidentiality agreements, and relevant privacy law before defining permissions. A bidder's signed nondisclosure agreement does not by itself settle every disclosure question. [1] [2]
Preserve each question and give every issue an owner
Use one internal intake register rather than separate, unconnected email drafts. Record the question identifier, bidder, original wording, date received, requested response date, subject, factual owner, legal reviewer, and current status. Keep the original request intact when clarifying it. Link duplicate questions to a common issue, but retain their separate recipient records and approval paths.
Split compound requests into linked issues when different people must verify them. An illustrative request about a customer agreement might ask about termination rights, outstanding disputes, and consent to the proposed transaction. The commercial owner can verify relationship facts, while counsel reviews the relevant clauses and transaction structure. Assign one coordinator to assemble the answer without allowing that coordinator to resolve legal uncertainty. Useful statuses include awaiting evidence, awaiting seller verification, legal review, approved for named recipients, released, and superseded. A deadline is not authority to skip a status.
Build a verified fact set from records, not prior answers
Treat executed agreements, amendments, relevant notices, and confirmed seller records as source material. For each proposed assertion, record the document version and clause or page, or identify the seller confirmation and its date. Distinguish what a document says from what management reports has happened. A contract permitting termination is not evidence that a termination notice has been received.
Before approving a negative answer, define the scope of the check. Missing evidence in a folder is not proof that no dispute, consent requirement, or amendment exists. Ask the accountable seller owner to verify completeness and unresolved exceptions. If the records conflict, keep the issue open and describe the uncertainty accurately rather than converting it into a confident answer.
Counsel should review qualifications that affect meaning. ABA Rule 4.1 commentary warns that affirming a known false statement, or making a partially true but misleading statement equivalent to a false statement, can be a misrepresentation. This is model-rule guidance; applicable professional rules and law control the actual matter. Seller confirmation does not remove counsel's responsibility to assess the wording. [5]
Separate consistent facts from bidder-specific access
A common fact set is an internal reference, not a universal response packet. Before reusing an approved answer, compare the new request's scope, transaction assumptions, and recipient permissions. Record whether the proposed disclosure is permitted for that bidder and its advisers, limited to counsel or a clean team, requires further authorization, or should be deferred. Any exception needs an owner and a reason.
For example, one bidder may propose an asset acquisition while another proposes a share acquisition. Counsel may need different analyses of a consent clause while preserving the same verified contract facts. Do not describe a bidder-specific interpretation as a fact already established for everyone. Conversely, redaction should not make a permitted response materially misleading. Counsel decides what can lawfully be disclosed or withheld under the relevant facts and agreements. [5]
Keep one bidder's questions, negotiated requests, and transaction-specific analysis out of another bidder's response materials unless disclosure has been specifically assessed and authorized. Similar wording is not evidence of identical access rights. Review attachments and linked documents as well as the response itself.
Escalate competitively sensitive requests before drafting
Bidders competing to acquire a business are not necessarily competitors of the seller. Where a bidder is a competitor or potential competitor, involve qualified antitrust counsel before preparing answers about sensitive commercial information. FTC Bureau of Competition guidance from March 2018 identifies current and future pricing, strategic plans, and costs as examples requiring care during pre-merger information exchange. [3]
That guidance recommends narrowly tailored information sharing and, where appropriate, aggregation, masking, independent advisers, or clean teams. Clean teams are restricted groups operating under a defined information protocol; the FTC guidance recommends excluding personnel responsible for competitive planning, pricing, or strategy. These safeguards are fact-dependent, not a safe harbor or a guarantee. [3]
Document the allowed recipient group and counsel's conditions in the issue record. Review whether an answer combined with other available records could reveal information intended to be masked. A summary generated from restricted material belongs under review too, not in an unrestricted response merely because it omits the source attachment. [3]
Limit AI to authorized routing and cited draft preparation
Give AI a narrow task: suggest an issue category and owner, retrieve relevant passages from a permitted source set, and prepare a draft with source locations and unanswered questions. The coordinator checks routing; the seller verifies facts; counsel reviews interpretation and disclosure. Do not let the tool resolve ambiguity, certify completeness, or change a release status. ABA Formal Opinion 512 emphasizes task-dependent independent verification and that lawyers remain responsible for professional judgment. [4]
Before entering representation information, counsel should assess the actual tool's terms, privacy policies, access arrangements, and handling of inputs and outputs. Opinion 512 discusses these checks and circumstances requiring informed consent, particularly risks associated with self-learning tools. Its July 2024 analysis is based on ABA Model Rules; current local requirements and the selected tool's actual configuration still need review. [4]
Use a matter-specific, recipient-restricted source set and exclude privileged legal analysis from routine bidder drafting unless counsel has expressly assessed its use. Require every draft assertion to link to a permitted document passage or seller confirmation. Tell the tool to flag missing evidence rather than infer an answer. A citation is a checking aid, not proof that the cited passage supports the conclusion.
Test the preparation workflow and define when it stops
Start with synthetic or genuinely nonconfidential records suitable for the trial. Counsel should establish the expected answers and classification decisions before comparing AI output. Include a changed contract clause, an incomplete record set, duplicate questions with different recipient permissions, and a request that should be escalated rather than answered. Opinion 512 describes manually reviewed subset testing as one approach to evaluating an AI tool's accuracy, while making review task-dependent. [4]
A limited live trial should proceed only after counsel approves the source set and confidentiality arrangements. Check source accuracy, omitted amendments, unsupported conclusions, routing mistakes, and attempted cross-bidder retrieval. Pause AI use for the affected workflow if it invents a source, retrieves unauthorized material, bypasses an approval gate, or operates under unclear data-handling terms. Investigate and retest before resuming. Reassess after material changes to the tool, permissions, or source collection. A successful trial does not eliminate human review of released answers.
Approve the exact response and release it through a human
Create a review package containing the proposed external answer, permitted attachments, source references, open exceptions, and recipient list. The seller approver confirms factual accuracy and scope. Counsel checks legal interpretation, required qualifications, confidentiality, possible privilege issues, and bidder-specific restrictions. Approval should identify the exact version and authorized recipients. Any substantive edit or changed attachment returns the package to the relevant reviewers.
Keep internal legal reasoning separate from the external answer. ABA Rule 1.6 commentary distinguishes ethical confidentiality from attorney-client privilege and work product protection. Their application depends on the relevant law and circumstances; neither a confidentiality label nor software establishes protection. Counsel should decide what belongs in the external record. [2]
Only an authorized human should perform release after checking the approved version, attachments, and recipients. AI and software must not send or approve client responses autonomously. Record who approved and released the package, when release occurred, and which channel was used. Confirm intended recipients can access the permitted materials without expanding access to the underlying restricted collection.
Preserve corrections and a reviewable response history
Keep a recipient-specific history of released wording, attachments, evidence versions, approvals, and follow-up questions. If new information changes an answer, flag the earlier response as potentially superseded rather than silently overwriting it. Counsel should assess correction needs under applicable rules, agreements, and law, identify affected recipients, and approve any correction through the same seller and legal review process. Preserve the relationship between the original and corrected responses.
At bidder withdrawal or process completion, review access removal and contractual return or destruction requirements with counsel. FTC guidance recommends clear destruction instructions and follow-up for competitively sensitive diligence information. Reconcile those requirements with applicable preservation duties before deleting records. [3] Set retention and access rules for the internal review history too, rather than retaining every AI prompt indefinitely.
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 software is user-operated and has no success fee. This recommended Q&A framework does not assert particular Acquivo AI or audit features. Counsel and the seller remain accountable for verification, approval, and disclosure; Acquivo does not represent clients or provide legal advice.
Key Points
- Preserve original bidder requests and assign separate factual, legal, approval, and release responsibilities.
- Use verified records as the common fact set, but assess permissions and transaction assumptions for each recipient.
- Limit AI to routing suggestions and cited drafts; check tool terms, source support, and restricted access before use.
- Stop AI preparation when sources are invented, restricted material appears, or required approval gates are bypassed.
- Require seller and counsel approval of the exact response, then retain the human release and correction history.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
- [1] ABA Model Rule 1.6: Confidentiality of Information · Accessed
- [2] ABA Rule 1.6 Confidentiality of Information: Comment · Accessed
- [3] FTC: Avoiding antitrust pitfalls during pre-merger negotiations and due diligence · Accessed
- [4] ABA Formal Opinion 512: Generative Artificial Intelligence Tools, July 29, 2024 · Accessed
- [5] ABA Rule 4.1 Truthfulness in Statements to Others: Comment · 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.