By Joash Boyton, founder, owner and CEO of Acquiry
Sponsored educational article by Acquiry.
A confidential acquisition search needs a disclosure sequence: what information is required for the next decision, who should receive it and whose permission is needed before it moves. An anonymous introduction, identification of the parties and detailed diligence serve different purposes. Treating them as separate steps helps a buyer pursue a relevant conversation without distributing sensitive information prematurely.
The operational rule is to authorise a defined disclosure, not simply to label a relationship confidential. A recipient can be appropriate for one summary and inappropriate for the underlying customer data. A buyer can know a business exists without being authorised to tell additional colleagues that it is considering a transaction. Information that was sufficient for an initial screen may be inadequate for a later proposal, requiring a fresh decision about scope.
This guide sets out a practical framework for those decisions. It does not provide legal advice, confidentiality terms or a universal rule about what information may lawfully be shared. Counsel should determine the applicable legal requirements and documentation. The commercial team's responsibility is to understand the purpose, keep permissions specific and ensure actual handling follows the agreed process.
Before preparing a disclosure, write one sentence explaining the recipient's next decision. For example, the recipient may need to decide whether a target profile fits the acquisition brief, whether to accept an introductory call or whether to authorise technical diligence. These decisions require different levels of information.
Then list the facts essential to that decision. A preliminary strategic screen might require a broad business model, customer segment and operating geography. It may not need the business name, exact financial results or customer identities. Conversely, a buyer assessing a specific integration question may need detailed technical information that an anonymous summary cannot supply. The answer is a controlled next stage, not pretending the summary answers everything.
Identify the information owner or person entitled to approve its disclosure. An adviser may possess documents without having unrestricted authority to circulate them. A buyer's employee may know the acquisition strategy without being authorised to disclose the buyer's identity externally. Possession, relevance and permission should be checked separately.
Finally, ask what happens if the recipient cannot make the decision with the proposed information. They may need a narrower question, a different reviewer or additional permission. That is better than quietly adding detail until the document becomes identifying or commercially sensitive.
A single presentation can contain information with very different disclosure implications. It might combine a public product description, an owner intention, an unpublished financial figure and an identifiable customer example. Calling the entire file a teaser does not make each component suitable for broad circulation.
Use an information inventory that distinguishes public descriptions, confidential commercial facts, party identities, personal information and material requiring specialist handling. The categories are practical prompts, not legal classifications. Counsel and relevant specialists should advise where legal or professional obligations apply.
Record whether a fact is public in the same context. A business name may be public, while the fact that its owner is discussing a transaction is not. A management biography may be published, while an individual's proposed departure is private. Combining public facts with a confidential context can reveal more than the facts alone.
Consider information about the buyer as carefully as information about the target. An acquisition brief can reveal strategic priorities, product gaps or geographic ambitions. A financing description can reveal assumptions that the buyer has not approved for external use. A useful disclosure sequence protects both sides' legitimate concerns rather than treating confidentiality as exclusively the seller's issue.
An initial anonymous approach should explain the relevance of the conversation without identifying an opportunity that has not been cleared for disclosure. Describe broad characteristics and the reason a discussion may be worthwhile. Avoid turning anonymity into a vague message that gives the recipient no basis for deciding whether to engage.
At the same time, test combinations of details. A small niche, exact location, distinctive customer, precise revenue figure and founder history can identify a business even when the name is absent. The relevant question is whether the intended recipient could reasonably recognise the opportunity from the combination, particularly if they know the sector well.
Reduce precision where it is unnecessary for the decision. Broad categories or ranges may be sufficient, but they should remain truthful and should not manufacture a misleading impression. If generalising a detail would distort the investment rationale, consider withholding it until an appropriate identified discussion rather than presenting a false substitute.
Do not describe an opportunity as available merely because an anonymous overview has been prepared. The summary should distinguish a researched fit from a business whose owner has authorised an approach. This protects the recipient from misunderstanding the status and protects the owner from being represented as seeking a sale without evidence.
Some buyers want their identity disclosed immediately because their operating capabilities provide the strongest reason for an owner to engage. Others have a legitimate reason to begin anonymously. Either approach requires an agreed explanation of representation and a plan for when the principal will become known.
If the buyer remains unnamed initially, provide an accurate description within the approved boundaries. Distinguish the adviser making the approach from the principal considering an acquisition. Do not use anonymity to imply a stronger buyer, a more advanced mandate or more certain funding than the evidence supports.
Ask what the owner needs to know to decide whether a further conversation is worthwhile. They may reasonably want to identify competitive sensitivities, strategic fit or potential conflicts before sharing information. If those questions cannot be answered anonymously, the buyer must decide whether to approve identification, use an alternative review arrangement with advice or stop the discussion.
Record the buyer's permission for identity disclosure and any limitations. Permission to identify the buyer to one owner does not automatically authorise publishing the acquisition strategy or circulating the name to a broader set of targets. The recipient and purpose remain part of the approval.
Before an acquisition opportunity's business name or identifying details enter an external message or external draft, obtain explicit approval to disclose them. The approval should cover the intended recipient and the information being revealed. A request to discuss an asset by name internally does not itself authorise revealing that identity to someone else.
This boundary applies to drafts as well as sends. A draft in an external shared workspace can already expose information to collaborators. Preparing a useful anonymous overview is the appropriate default when permission is absent. Do not place the identifying details in the draft and assume a later review will provide consent.
Where a message includes several businesses, check each opportunity separately. Approval for one does not extend to the others. Where a recipient list changes, reassess whether the existing permission covers the added people. Where an adviser forwards information to a different team, confirm the purpose and authorised scope instead of treating the organisation as a single unrestricted audience.
Keep the approval record close enough to the workflow that the person preparing the disclosure can verify it. A vague recollection that the owner was comfortable is inadequate. If the approval is ambiguous, ask a specific question about the particular recipient and identifying information before proceeding.
Use the following matrix as a sequence of decisions rather than an automatic conveyor belt. Each stage identifies a purpose, possible information, recipient and release condition. The appropriate legal documentation and any special handling requirements should be settled with counsel.
For every stage, add an accountable approver, record location and next review event. If a release condition is unmet, hold the dependent disclosure while continuing work that does not require it. This makes the boundary operational rather than a general statement of good intentions.
A disclosure register can be simple. Record the information item or version, the purpose, the sender, the recipient, the approver, the approval date and any conditions. Link to the permission evidence and the version actually shared. Avoid storing unnecessary sensitive detail in the register itself.
Use people or clearly defined groups rather than an unrestricted company label where the sensitivity warrants it. A finance reviewer and a commercial competitor team within the same group may have different roles. Ask counsel about suitable arrangements for sensitive competitive information rather than improvising a clean-team process from a generic template.
Track onward-sharing permissions. If a recipient asks to involve a colleague, establish who they are, why they need the information and whether the existing approval and documentation cover them. Requiring this check need not slow every routine communication; it means the workflow anticipates changes instead of discovering them after a file has circulated.
Record refusals and limitations as clearly as approvals. An owner may authorise a business description but not the customer list. A buyer may approve its name but not its investment range. These limits should survive handovers between team members and advisers.
Ask whether the recipient needs a conclusion, a summary, a sample or the complete underlying record. The least sensitive form capable of supporting the decision is often the best starting point. This is a practical test of relevance, not a substitute for legal requirements.
For example, a buyer assessing concentration may initially need the proportion of revenue represented by the largest customers, not their names. A technical reviewer may first need an architecture description rather than access to source code. A discussion about management depth may begin with roles and responsibilities rather than individual employment files.
The summary must preserve important limitations. Aggregation can hide dependencies, and redaction can remove context needed for interpretation. Explain what has been withheld and why it matters to the recipient's conclusion. If the question cannot be answered responsibly without more detail, identify the permission and review needed for the next stage.
Do not use reduced disclosure to create false reassurance. A summary that omits an essential qualification is not improved by being confidential. The objective is proportionate, accurate information, not selective presentation that makes the opportunity appear stronger.
A permission may relate to a particular version of a document. Later edits can add identifying details, new figures or a changed transaction status. Treat a material revision as a fresh disclosure check rather than assuming the original approval covers everything with the same filename.
Use clear version labels and a single approved copy for a defined purpose. Retire superseded versions from active circulation where the process allows. If a recipient already has an outdated copy, explain the relevant correction rather than relying on them to discover the new version.
Choose communication and storage arrangements suited to the information and the parties' requirements. A short anonymous summary and a detailed diligence folder may need different controls. Confirm access before uploading sensitive material, and do not assume a folder is private because it was created by someone on the team.
Keep the channel decision separate from the content decision. A secure system does not authorise an unapproved disclosure, and a permitted recipient does not make every transfer method appropriate. Both questions should be addressed before the information moves.
Requests often become more detailed during a productive conversation. A buyer may ask for a customer name to understand a use case, or an owner may ask which competitors the buyer has approached. The person on the call should know which questions they can answer and which require a pause.
A useful response explains the next step without inventing permission: that detail requires approval; the team can provide an anonymous description now; or the relevant specialist can review it under an agreed process. The goal is to keep the conversation constructive while respecting the boundary.
When the purpose changes, revisit the disclosure plan. Information provided to assess an acquisition should not silently become material for sales prospecting, recruitment or another commercial activity. Ask what the recipient now intends to do and obtain the appropriate advice and authorisation before accommodating the new purpose.
Do the same when the transaction perimeter changes. A discussion about a minority investment may become a proposed asset acquisition, or a single buyer may introduce a consortium. Those changes can alter who needs information and which facts matter. Update the register and permissions rather than stretching the original approval to fit.
The commercial team can define the decision, assemble information, identify recipients and keep records. Counsel should advise on the appropriate legal terms, applicable restrictions, disclosure obligations and consequences of the proposed arrangements. Other specialists may be needed for financial, technical or data-handling questions.
Do not assume a signed confidentiality agreement solves every issue. Ask whether it covers the parties, intended purpose, proposed recipients and type of information involved. Ask how onward sharing, access by advisers and the end of discussions should be handled. The answers should come from the actual documents and relevant advice.
Equally, do not ask counsel to compensate for an undefined operational process. An agreement cannot tell the team which version was sent if no one records it. Clear documentation and careful execution support each other. The team should understand the practical steps necessary to follow the arrangements its advisers establish.
Where advice identifies a restriction, translate it into an actionable workflow. Specify who can review the material, which information should be withheld, what approval is needed and what alternative can support the commercial decision. A warning with no operational owner is easily lost during a busy process.
Consider a wholly hypothetical buyer seeking a specialist workflow capability. Its adviser identifies a potentially relevant business. The owner has not authorised the business to be named in external materials, and the buyer has not approved disclosure of its identity to the owner. No real opportunity or client is represented in this example.
The first step is internal. The adviser records the apparent fit using public information and identifies the unknowns. A proposed anonymous approach explains the broad capability sought and the adviser's representation within the buyer's approved boundaries. It avoids the buyer's distinctive product roadmap and does not claim the owner is considering a sale.
The owner responds with interest in understanding the rationale but asks to know the principal before sharing information. The adviser does not send a financial questionnaire immediately. It returns to the buyer for a decision about identity disclosure to that owner. The buyer approves its name and a limited strategic explanation for that recipient.
After the introduction, the owner agrees to an initial fit discussion but does not approve circulation of the business to additional parties. The parties obtain advice on the appropriate confidentiality arrangements. The owner provides an approved, aggregated operating summary to the specified participants. The adviser records the version and the scope of permission.
A technical question then emerges about a dependency. Rather than sending a complete code repository to the commercial team, the parties agree a scoped specialist review. The owner approves the relevant information and recipients under the advised arrangements. The specialist's conclusion is shared in an appropriate summary that makes its limitations clear.
The buyer later proposes involving an operating subsidiary. That is a new recipient question. The adviser checks whether existing permissions and arrangements cover it and obtains any additional approval before sharing. At each step, the next commercial decision determines the disclosure; progress does not create unlimited permission.
If information is sent to an unintended recipient, stop further distribution and establish what happened. Record the actual material, version, recipient and access status. Follow the relevant internal process and obtain legal or specialist advice about containment, notification and other required actions. Do not assume a request to delete the message fully resolves the issue.
Communicate accurately with the people responsible for the matter. Avoid minimising the event before the facts are known, but do not speculate about consequences. The immediate objective is to contain the disclosure, preserve necessary evidence and follow the appropriate response.
Review why the error occurred. Perhaps an old recipient list was reused, a permission was stored in an inaccessible message or a supposedly anonymous document included a distinctive detail. Improve the specific control rather than merely reminding everyone to be careful.
Changed circumstances also deserve attention without being treated as incidents. A recipient may leave an organisation, an adviser may change roles or the transaction may pause. Update access and responsibility records so the disclosure plan reflects the current participants.
A search may involve several targets, and an owner may speak with several potential buyers. Keep the permission record specific to each relationship. Information approved for one conversation should not be copied into another because the recipients seem similar.
Use separate versions where audiences differ. A strategic buyer may require different information from a financial investor, and a direct competitor may raise additional questions for counsel. Consistency of facts remains important, but consistency does not mean every party receives identical material at the same time.
Be careful when summarising market feedback. An anonymous observation can still reveal who said it if the surrounding details are distinctive. Aggregate feedback only where doing so remains accurate and authorised, and avoid presenting another party's confidential intentions as general market intelligence.
When advisers collaborate, agree who maintains the master disclosure record and how changes are communicated. Multiple private spreadsheets with conflicting permissions can defeat an otherwise careful process. The arrangement should make the latest approved scope easy for authorised participants to verify.
Before an external draft or information transfer, complete a short release note. For routine low-sensitivity material, the note can be concise. For identifying or sensitive material, make the evidence of approval explicit.
If an essential answer is missing, do not fill it with an assumption. Seek the required approval or clarification. Meanwhile, continue authorised research, prepare a non-identifying version or refine the question the recipient needs answered.
A disclosure process is only as clear as the next person can understand it. Before a search becomes busy, test a fictional handover between a researcher, an outreach lead and a buyer representative. Give each person the record they would normally receive and ask what they believe they are authorised to share.
The researcher should be able to distinguish public research from owner-provided information. The outreach lead should know the approved buyer description and the limits on identifying a target. The buyer representative should know why a document was shared, which colleagues can receive it and which questions must return to the owner or adviser.
If their answers differ, repair the record or responsibility assignment before using the process on sensitive material. A handover note should include the current purpose, disclosure status, approval evidence, recipient scope and unresolved questions. It should not rely on the previous person's memory or informal assurances that everyone understands.
Test ordinary administrative artefacts too. A calendar invitation can reveal the names of parties and the purpose of a meeting. A file title can identify the target even when the document body is anonymous. A shared task description can expose a confidential transaction to a broader group than the diligence folder. Review these surfaces as part of the same disclosure decision.
For remote or cross-organisational meetings, confirm participants before substantive discussion. If an unexpected attendee joins, establish their role and whether the current permissions cover them. The appropriate response may be to keep the conversation general, pause a sensitive topic or obtain approval for a later exchange.
At the start of a disclosure stage, identify the event that will trigger an access review. It might be completion of a particular assessment, a decision not to proceed, a change in the recipient's role or a revised transaction perimeter. This prevents access from continuing indefinitely simply because no one was assigned to revisit it.
Ask counsel and relevant information-management specialists how the actual terms and obligations should be implemented. Retention, return and deletion questions can involve records that must be handled differently. The commercial team should not promise a universal deletion result it cannot verify or implement.
Operationally, maintain a list of the systems and locations used for the authorised exchange. When the review event occurs, the responsible person can check access, close unused workspaces where appropriate and confirm the next steps under the agreed arrangements. Keep an accurate record of what was done and what remains unresolved.
A paused conversation also needs a defined status. The owner may permit a later approach while withholding permission for further information circulation. The buyer may retain an internal research record but stop active diligence. Record those distinctions so a future team member does not mistake a historical discussion for current authority.
The public existence of a business does not establish permission to disclose its involvement in an acquisition discussion. Check the context and the specific approval. For this framework, an opportunity's name or identifying details require explicit approval before entering an external draft or outreach.
Not necessarily. Other details may identify the business when combined. Consider the recipient's knowledge and the whole description. If useful accuracy and anonymity cannot coexist, obtain permission for an identified discussion rather than relying on superficial redaction.
There is no universal commercial sequence. The parties' concerns and the purpose of the next decision matter. Agree the sequence, obtain the necessary permissions and use appropriate advice. Do not exchange one party's identity as though it automatically purchases permission to reveal the other's.
No. Discussing an asset internally, including by name, does not itself approve revealing it to an outside recipient. The external purpose, audience and identifying content must be considered separately, and the approval should be specific enough to verify.
State the limitation clearly. The parties can decide whether to authorise a controlled next stage, obtain a specialist assessment, pursue a different route or stop. A confidentiality constraint can be a legitimate reason not to progress; it should not be disguised by an unsupported conclusion.
Yes. Operationally, record the condition as part of the approval rather than as a separate reminder. It might require a particular recipient, an approved version or completion of an agreed review before release. Check that the condition has actually been met. A future intention to satisfy it is not the same as permission to disclose now.
Only within the authorised scope and in a form appropriate to its audience. A buyer may need to understand the decision implication without receiving every personal detail behind it. Summarise accurately, preserve material uncertainty and avoid identifying a business through a distinctive combination of facts. Where the permitted level of detail is unclear, ask before including it.
Acquiry describes confidential owner approaches and structured advisory processes that include preparation and diligence. Its role can be relevant where a buyer needs research, coordinated conversations and qualification against a defined brief. Actual scope and responsibilities should be agreed for the engagement rather than inferred from this proposed framework.
A buyer with established relationships may handle the initial conversation internally while using counsel and specialists for the relevant disclosure questions. Sensitive competitive, technical or legal issues may require arrangements beyond an origination adviser's role. Choosing that support is part of designing the process, not an admission that the search has failed.
The test of a good disclosure sequence is whether the parties can learn what they need for the next decision while understanding what was shared, with whom and under whose authority. That clarity is more useful than a general promise of confidentiality detached from the actual information flow.
About the author: Joash Boyton is the founder, owner and CEO of Acquiry, an international M&A advisory firm based in Melbourne with a core focus on buy-side acquisition origination. acquiry.com.
