English English 
By Joash Boyton, founder, owner and CEO of Acquiry
Sponsored educational article by Acquiry.
An acquisition origination report should help the buyer decide what to pursue, what to clarify and what to change. It should show why each live candidate matters, the evidence supporting its current status, what the owner has actually agreed to discuss and which action is blocking the next decision. A long activity log can support that report, but it cannot replace the explanation.
The most useful reporting question is not whether the team has been busy. It is what the buyer now understands that it did not understand before, and what that learning requires it to do. Sometimes the answer is to advance a conversation. Sometimes it is to narrow the search, revise an assumption or stop pursuing a candidate whose apparent fit has not survived investigation.
This guide proposes a reporting framework for buyers managing an origination engagement. It is a set of commissioning and review questions, not a statement that every adviser supplies the same deliverables. Scope, cadence, responsibilities, fees and information handling should be agreed explicitly. The framework can also help an internal corporate development team make its own search reporting more useful.
A report intended for an operating sponsor should answer different questions from one prepared for an investment committee. The sponsor may need to allocate product or management time. The committee may need to understand whether the acquisition thesis still has support. A search manager may need to resolve contact ownership or approve a revised approach.
List those decisions before designing the template. Otherwise, the report tends to follow whichever data is easiest to export. Sent messages, company counts and meeting dates are convenient to record, while unresolved strategic questions require judgment. Convenience should not determine the content of the buyer's decision process.
For each audience, identify the decisions it is authorised to make and the information it needs. An investment committee may not need personal details from an owner conversation. A technical reviewer may need a narrowly scoped dependency description rather than the entire pipeline. Different views can draw from the same controlled record without distributing identical information to everyone.
Choose a report owner who can distinguish an activity update from a recommendation. The report should make that distinction visible. Observations belong to the evidence; recommendations explain what the team proposes in response; decisions identify what the buyer has actually approved.
A practical report can have three layers. The first is a concise decision summary: material changes, decisions requested and immediate constraints. The second is the live candidate view, containing the facts needed to understand each current conversation. The third is supporting evidence, accessed by authorised reviewers when a decision requires more depth.
The decision summary should be readable without opening every attachment. It should identify where the thesis has gained or lost support and what the buyer needs to do next. Avoid opening with a collection of totals that requires the reader to infer the commercial meaning.
The candidate view should be structured enough to compare records while allowing important differences to remain visible. A narrowly targeted product acquisition and a potential platform business may require different fit questions. A common schema should organise the evidence, not force every candidate into a misleadingly identical profile.
The evidence layer should preserve traceability without making the main report unwieldy. Link internally to appropriate records rather than copying sensitive documents repeatedly. Confirm that recipients can access only the information authorised for their role. The existence of supporting evidence should not be confused with permission to circulate it.
Each live candidate should have a short rationale connecting it to the acquisition objective. Describe the capability, customer access, operating characteristic or strategic gap the candidate might address. A sector label alone does not explain why the buyer should spend time on it.
The rationale should distinguish established fit from a thesis requiring evidence. For example, a business may publicly offer a relevant product, while the buyer's assumption about transferable technology remains unverified. The report should not compress those statements into a confident claim that the target delivers the required capability.
Include the principal reason the candidate could fail. This creates a balanced view without requiring a lengthy risk register for every researched name. The reason might be an operating dependency, incompatible owner objectives or a mismatch with the buyer's integration capacity. It should connect to a decision, not function as a generic warning.
Review the rationale when new evidence arrives. If the candidate is now attractive for a different reason, state the revised thesis and obtain the relevant buyer decision. Quietly changing the rationale makes it difficult to understand whether the search is executing the original strategy or drifting into a new one.
A report should identify which material statements are confirmed, provisional, contradicted or awaiting review. Use these labels consistently and explain the underlying evidence. An owner statement, a public source and a specialist conclusion serve different roles; they should not all appear as verified facts merely because they have been entered into a system.
Record the date of the evidence as well as the date the report was prepared. A newly generated report can contain old information. The buyer needs to know whether an owner's position was confirmed recently and whether financial or operating material relates to the period under discussion.
Where a conclusion depends on several facts, identify the weakest unresolved link. A target may fit the product category and customer segment but depend on a critical arrangement outside the proposed perimeter. The report should highlight that dependency rather than allowing several positive fields to obscure it.
Keep unknown separate from unfavourable. Missing information may justify a question, a specialist review or a pause. It does not automatically establish a defect. Equally, an unknown should not be treated as neutral support for the investment case when it concerns an essential requirement.
Activity describes what the team did: research, contact attempts, discussions, information requests and follow-up. Progress describes what those actions established. Both can be useful, but they answer different management questions.
A completed call may establish a clear strategic fit, reveal a mismatch or leave the principal questions unanswered. Reporting only the meeting hides the outcome. A failed contact attempt may still reveal an incorrect ownership assumption, but that learning should be described directly rather than counted as owner engagement.
Use the agreed opportunity-stage definitions without reproducing a new ladder in every report. The report should show the current stage, the evidence that supports it and what changed since the previous review. A researched name, a reached owner and a qualified dialogue should remain distinct.
Activity data can help diagnose workload or process issues. It should not become a substitute for qualification quality or a promise of transaction outcomes. If the buyer wants activity measures, agree why they matter and how they will be interpreted alongside the evidence.
Owner feedback is often the most commercially useful part of a search report. It can explain timing, preferred involvement, transaction possibilities and concerns about the buyer. It can also contain sensitive personal or business information that should not be distributed more widely than necessary.
Summarise the decision implication accurately. If an owner is willing to explore a minority investment but not a full sale, the buyer needs that distinction. It may not need every private reason behind the preference. Keep the summary faithful to what was actually said and within the authorised sharing scope.
Separate a direct statement from the adviser's interpretation. The owner requested more buyer information is an observation. The owner may be testing strategic credibility is an interpretation. Either may be useful, but the latter should not be presented as confirmed intent.
Avoid labels such as highly motivated or ready to transact unless the report explains their evidence and limits. An enthusiastic conversation can coexist with unresolved shareholder alignment, timing constraints or a different view of transaction structure. Precise language helps the buyer choose the right next step.
A blocker should identify the dependency preventing a defined next action. Waiting for information is too vague. State which information is needed, who can provide it, what decision it supports and what happens if it remains unavailable.
Distinguish external dependencies from buyer decisions. The owner may be preparing an approved summary, while the buyer may need to decide whether a proposed founder role is acceptable. Presenting both as awaiting response conceals who is responsible and which issue the buyer can resolve immediately.
Some blockers require specialist input. A question about contractual continuity, regulatory permissions or ownership of technology should be assigned to appropriate advisers rather than resolved by a confident note in the pipeline. The report should state the commercial consequence and the review required, without presenting a legal or technical conclusion beyond the evidence.
Include the next review event. This might be receipt of a document, an internal meeting or a specific response agreed with the owner. A date is useful when grounded in an actual commitment. Do not manufacture deadlines merely to make the report look controlled.
A separate decision register prevents requests for buyer input from disappearing among company descriptions. Each entry should state the decision, the options, the evidence, the recommendation if any, the responsible decision-maker and the consequence of delay.
Keep the request narrow enough to answer. Approve further work is less useful than decide whether to investigate a target that requires a longer founder transition than the original brief allowed. The latter reveals the strategic trade-off and the person whose judgment is needed.
Record the decision once it is made and link it to affected candidates. If the buyer changes a criterion, the search team should know which records need to be reconsidered. If a candidate is declined, the disposition should explain the reason so it is not repeatedly reintroduced without new evidence.
The register also shows whether the buyer's own process is constraining progress. It should do so factually, not as a device for assigning blame. A delayed decision may reflect a genuine need for more information. The report should identify that need and the route to resolving it.
The following schema is a starting point for agreement, not a promised service specification. Use fields that support the engagement's decisions, and remove fields that generate work without improving them. Blank or unverified should remain legitimate entries where the evidence is incomplete.
A supporting evidence index can sit behind these fields. It should make the record auditable by authorised participants without encouraging indiscriminate circulation. The report is a decision interface to the underlying work, not a replacement for the source records.
If the report includes counts, define the unit being counted. A company, corporate group, product line, shareholder and contact person are different units. Several contacts at one business should not inflate the target count. Several subsidiaries should not automatically be treated as separate acquisition opportunities.
Distinguish the current stock of records from activity during the period. A report can show how many candidates are currently in a stage and how many entered or left it during the reporting window. Adding the same live candidate to a cumulative total every period creates a misleading impression of new progress.
Explain additions, removals and reclassifications. A fall in active candidates may reflect useful disqualification rather than reduced effort. A rise may reflect a broader mandate rather than better access. Without that explanation, the buyer may reward the wrong behaviour.
Avoid comparing ratios across searches with different definitions or populations. A narrowly researched specialist search and a broad exploratory map may have different purposes. The report should make the basis clear before drawing conclusions from conversion, response or qualification measures.
A report should allow the search to become less attractive when the evidence warrants it. If repeated owner conversations reveal a mismatch with the buyer's proposed structure, that finding belongs near the top of the review. Hiding it in individual notes prevents the buyer from reconsidering the approach.
Group negative findings by their decision relevance. A shortage of businesses meeting a genuine operating requirement differs from owners declining the proposed timing. The first may challenge the target universe; the second may challenge the process or structure. The remedy should follow the evidence rather than defaulting to more outreach.
Describe alternative explanations before recommending a major change. Low engagement might reflect the target profile, message relevance, contact accuracy or a small sample. The report should state what is known and what would discriminate between those explanations. Avoid presenting an unsupported diagnosis as a market fact.
When a search assumption fails, propose a decision: retain it and accept a narrower universe, revise it with a clear rationale or investigate a different route to the strategic objective. This is where reporting becomes part of strategy rather than a retrospective account of tasks.
Reporting frequency should reflect the pace and consequences of the decisions. A search with several live owner conversations may need short, frequent operational updates. An early market-mapping phase may benefit from a less frequent but more substantive review. There is no universal cadence established by this framework.
Separate scheduled reporting from material-event escalation. A significant change in owner intentions, an unexpected confidentiality issue or a decision that blocks an agreed next step may need attention before the next regular report. Agree what qualifies as a material event and who should be contacted.
Make the preparation burden proportionate. A detailed report that consumes the time needed for substantive research may not serve the buyer. Reuse structured records where possible, but retain human judgment about what has changed and why it matters. Automated exports can organise facts without deciding which facts are commercially important.
Write the agreed cadence, format and responsibilities into the engagement arrangements. If the buyer's needs change, discuss the scope and resource implications rather than assuming the adviser will provide unlimited additional reporting within the original terms.
Ask which reporting activities are included and which require separate agreement. Does the engagement cover an initial market map, ongoing candidate updates, owner-call summaries or support for an internal committee paper? These are different tasks, and a general reference to origination does not define every deliverable.
Clarify who maintains the authoritative record and who can amend it. The buyer may use its own system, the adviser may maintain a separate workspace, or the parties may agree a shared process. Whichever route is chosen, resolve how corrections, handovers and access changes will be handled.
Ask how existing relationships and overlapping advisers will be reflected. A candidate already known to the buyer should not be presented as newly discovered without qualification. A conversation led by another adviser should have a clear coordination arrangement. Reporting should make these relationships understandable rather than turning attribution into a contest.
Fees and performance expectations should be addressed in the actual written engagement. This article does not recommend a universal fee model or a numerical service target. The useful principle is that the buyer should understand what work is being commissioned, how progress will be evidenced and what remains outside scope.
Consider a wholly hypothetical buyer seeking a specialist capability that can be integrated without a long founder transition. Its origination partner brings two fictional candidate records to a review. No real client, target or performance result is represented, and the example supplies no conversion benchmark.
The first record initially appeared to fit the capability requirement. The latest owner conversation shows that critical delivery work remains concentrated with the founder, who wants to reduce involvement quickly. A weak report might say positive meeting completed and leave the record in an attractive category. A useful report explains that the capability fit remains plausible but the transition assumption is now unsupported.
The decision request is specific: should the buyer fund a limited operating review to test whether the dependency can be reduced, or decline because its current integration resources cannot support that work? The report identifies the internal operating sponsor who can decide and the information needed to compare the options.
The second record fits the operating model more closely, but the owner will not share further information until the buyer explains its intended post-acquisition role for management. The blocker belongs to the buyer. The next action is an approved statement of intentions, not another generic request for financial material.
The report also notes that the original brief did not distinguish between retaining a management team and retaining a founder personally. The buyer clarifies that requirement and asks the search team to reassess relevant records. The review has produced a better search criterion and two concrete decisions, even though no transaction has been agreed.
The lesson is about report design, not the outcome of either fictional opportunity. The useful content is the changed evidence, the implication for the thesis and the decision required. A table of meetings alone would not have exposed those distinctions.
Distribute the report with enough context for the authorised audience to prepare. During the meeting, focus on material changes, unresolved assumptions and decisions requiring discussion. Avoid reading every field aloud when the written record is clear.
For each decision, establish whether the evidence is sufficient. If it is, record the direction and the responsible person. If it is not, specify the missing evidence and the next review event. Deferring a decision can be reasonable, but the deferral should have a reason beyond needing more comfort.
Separate questions that change the search from questions that affect only one candidate. A problem with one target should not automatically alter the whole mandate. Conversely, a repeated pattern should not remain buried in separate records when it challenges a central assumption.
End with a short action confirmation. The buyer and adviser should leave with the same understanding of approvals, open questions, communication responsibilities and any changed disclosure permissions. Update the record promptly so the written report and the conversation do not diverge.
Use a pass-or-revise review for the report itself. Can an authorised reader understand why each live candidate matters? Are important claims linked to evidence? Are owner intentions described accurately? Are blockers and buyer decisions specific? Are counts and dates interpretable?
Sample a few records and trace them to the underlying evidence. If the report says a criterion is confirmed, check what supports that conclusion. If a meeting is described as qualified, check the agreed gate. The purpose is to test reliability, not to punish honest uncertainty.
Ask whether the report would support a decision to stop. If every paragraph implies continued pursuit, it may be presenting advocacy rather than an assessment. Balanced reporting should allow the buyer to recognise a weak thesis, a poor fit or a process that needs redesign.
Review the template periodically. Remove fields no one uses, add questions repeatedly asked in meetings and clarify ambiguous labels. A stable schema supports comparison, but it should not become an obstacle to learning when the engagement changes.
A revised mandate can make the current report look better or worse without any change in execution. If the buyer expands geography, changes the desired ownership stake or relaxes a capability requirement, record the effective date and the reason. Preserve the previous brief so historical results remain interpretable.
Identify which candidate records are newly in scope, newly excluded or unchanged. A business that becomes relevant after a mandate change was not necessarily missed by the original search. A candidate removed under a new constraint was not necessarily poorly screened. The report should explain the relationship between the evidence and the applicable brief.
Use a change note rather than rewriting history. State the old assumption, the new decision, the supporting evidence and the resulting work. If the change requires additional research or outreach, identify the resource and commercial implications for agreement. This allows the buyer to understand what it is asking the origination partner to do differently.
Apply the same discipline to corrections. If a duplicate record is removed or an owner statement was previously misunderstood, correct the current view and explain any material effect on earlier conclusions. Quietly editing a number can leave committee papers and other downstream documents inconsistent. A concise correction is usually more useful than pretending the earlier version never existed.
Before the first reporting cycle, complete the following worksheet together. The entries should be concrete enough that both sides can recognise whether the report serves its purpose. Where the answer remains open, identify who will settle it and when, rather than assuming a default service level.
Test the proposed format with a fictional record before using it on a sensitive opportunity. Ask the buyer to identify the rationale, strongest evidence, key uncertainty and next decision. If those cannot be found quickly, improve the structure before adding more detail. A report should reduce interpretation effort, not transfer the entire burden of understanding the search to the reader.
When the buyer moves a candidate into a more detailed transaction process, the origination record should travel with it. Provide the current rationale, evidence limits, owner objectives, permissions and unresolved questions to the authorised receiving team. A company profile alone loses the history that explains why the discussion developed.
Clarify which reporting responsibilities continue and which transfer. The origination partner may retain owner communication responsibilities, support a handover or conclude a defined phase, depending on the agreement. The buyer should not assume that entry into diligence automatically expands the engagement to cover every transaction task.
Archive the relevant snapshot while keeping corrections visible. The transaction team should be able to distinguish facts established before handover from matters it later verifies. That distinction helps prevent an early screening assumption from becoming an apparently settled diligence conclusion merely through repetition in successive reports.
Only if that serves the agreed purpose and information permissions. A strategic review may need a market map, while an operational review may need only changed records and decisions. Keep researched candidates distinct from qualified conversations so a broad list is not mistaken for available opportunities.
A dashboard can show status and change efficiently, but it needs definitions, evidence links and a way to explain exceptions. If a buyer cannot tell why a candidate moved or what action is required, the dashboard is incomplete as a decision tool.
Use the authorised level of detail and explain the commercial implication accurately. Limit access to appropriate recipients. If the report would identify an opportunity or reveal sensitive intentions beyond the approved scope, obtain the required permission before including it.
Ask what the activity has established and where the evidence stops. Review the target criteria, contact route, relevance of the approach and buyer-side decisions. Do not assume either poor performance or an impossible market without investigating the specific bottleneck.
Ask for the known process dependencies and conditional timing assumptions rather than treating a search report as a completion forecast. Owner decisions, financing, diligence and terms can remain unresolved. Any timing view should make its basis and uncertainty explicit.
Yes, by agreement. Explain the decision need, the additional work and any access implications. Confirm revised scope, responsibilities and commercial terms where necessary. A useful reporting relationship can adapt without implying that every new request was included from the start.
Acquiry's public acquisition process covers target criteria, company research, owner approaches and qualification. Its company information states that engagement scope and fees are agreed individually in writing. Those are appropriate foundations for a buyer discussion about what evidence and reporting will be useful in a specific search.
The reporting schema in this article is a recommended commissioning framework, not a claim about a fixed Acquiry package or reporting service level. Buyers should agree the actual deliverables and responsibilities. A team that already has strong origination coverage may need better internal records or specialist diligence rather than an additional external search partner.
A useful report makes the buyer's next decision clearer. It shows what has changed, what remains uncertain and who can resolve the important question. When reporting meets that standard, it supports the acquisition strategy instead of merely demonstrating that a pipeline exists.
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.