An M&A red-flag due diligence report should help a decision-maker act before the opportunity to act disappears. It is not a catalogue of every document reviewed, and it is not a compressed full legal opinion. Its job is to identify material verified facts, expose important uncertainty, explain transaction relevance, and connect each issue to a decision, owner, and deadline.
For Indian transactions, primary sources may include the Companies Act, 2013 on India Code, the Competition Commission of India, and SEBI legal materials. Counsel should verify the current provisions, rules, orders, and applicability. The report should state which official materials were reviewed and when, rather than presenting changing requirements from memory.
What should a red-flag report answer for the deal team?
Start with the decisions the report must support. These may concern whether to proceed, change structure or price, seek an approval or consent, require remediation, alter a condition precedent, revise a warranty or indemnity, extend the timetable, or assign an integration action. The precise list depends on the transaction.
Write a scope statement with entities, workstreams, jurisdictions, review period, materiality rules, source cut-off, excluded matters, access limitations, and reliance assumptions. A short report without a clear scope can create more false confidence than a long one.
| Reader question | Report response | Evidence standard |
|---|---|---|
| What happened or may happen? | Verified fact and stated uncertainty | Citation to source or named factual owner |
| Why does it matter? | Deal, operating, timing, or value consequence | Counsel's reasoned assessment |
| How serious is it? | Agreed priority and rationale | Materiality rule applied consistently |
| What decision is needed? | Specific choice or escalation | Named decision-maker and date |
| What happens next? | Action, owner, dependency, and status | Tracked through closure |
Keep background proportionate. If context does not change a decision or help a reader understand the evidence, it may belong in an appendix or full report.
How do you separate a fact, an assessment, and a recommendation?
These layers should be visible. A contract may state that counterparty consent is required for a defined event. Whether the proposed structure meets the definition is a legal assessment. Whether the buyer should seek consent before signing, make it a closing condition, or change structure is a transaction recommendation.
Use a standard issue block:
- Finding: the verified fact, with document and section citation.
- Gap: missing evidence, ambiguity, or factual assumption.
- Assessment: why the matter may affect the transaction.
- Response: decision or work product required.
- Owner: accountable role, reviewer, and due date.
- Status: open, provisional, agreed, mitigated, accepted, or closed.
Avoid statements such as “no issues identified” unless the report defines the tested population and limitations. “No responsive clause found in the validated sample” is narrower and more honest when that is what the evidence shows.
How should red flags be prioritised without oversimplifying them?
Agree priority definitions at the start. Consider likelihood, consequence, timing, reversibility, evidence quality, and ability to mitigate. Do not let financial value become the only measure. A modest contract may hold a permission or infrastructure dependency that is difficult to replace.
| Priority | Practical meaning | Expected response |
|---|---|---|
| Critical | May prevent the proposed deal or lawful operation, subject to counsel's assessment | Immediate leadership and specialist review |
| High | Could materially affect structure, value, timetable, or continuity | Decision and owner before the relevant milestone |
| Medium | Requires drafting, remediation, or integration planning | Track with a dated action |
| Information | Useful context that does not presently require a deal response | Preserve for handoff or full report |
| Open | Evidence is insufficient to classify responsibly | Focused request and provisional consequence |
The contract risk scoring framework provides a documented scoring approach. Use scoring to support judgment, not replace it. Always show the rationale and cited evidence beside the label.
Which findings usually deserve red-flag treatment?
The answer depends on the deal thesis. Common workstreams include title and ownership, authority, encumbrances, key contracts, licences, disputes, employment, intellectual property, technology, data, compliance, competition, property, insurance, and related-party arrangements.
Examples that may warrant escalation include an unexplained cap-table difference, missing authority, a material encumbrance, an essential licence with uncertain continuity, a contract termination or consent right, an unresolved proceeding, incomplete intellectual-property chain of title, a significant security incident, or a transaction step requiring specialist regulatory analysis. These are prompts, not predetermined conclusions.
For each workstream, ask:
- What fact would change price, structure, timetable, or willingness to proceed?
- What could interrupt the target's ability to operate after closing?
- Which consent, filing, or approval has a long lead time?
- Which assertion rests only on management representation?
- Where do sources disagree or coverage remain incomplete?
- Which issue needs protection in transaction documents?
- Which issue can be handled only through operational remediation?
The bulk contract review workflow explains how to link material contract findings to their operative evidence.
How should missing information appear in the report?
Treat significant gaps as findings. State the request, scope affected, response received, why the absence matters, provisional consequence, next step, and owner. A missing amendment may prevent a contract conclusion; an incomplete register may prevent an ownership conclusion. These are not administrative footnotes.
Maintain a cut-off log for late uploads. When new evidence arrives, identify which findings and drafts it may affect, route it to the reviewer, and preserve the change history. Do not simply replace the report text without recording why the conclusion changed.
| Gap state | Meaning | Reporting approach |
|---|---|---|
| Requested | Evidence has not been supplied | Show request and potential relevance |
| Partial | Some entities, periods, or attachments are absent | Define the precise missing scope |
| Conflicting | Sources do not agree | Cite both and identify resolution owner |
| Unreadable | File cannot be reliably reviewed | Request replacement and avoid inference |
| Unverified | Management response lacks supporting material | Attribute response and keep it provisional |
This treatment helps leaders distinguish “not found” from “does not exist.”
How do you preserve traceability without overwhelming the reader?
Use concise issue summaries with stable source references, then provide a controlled appendix or issues register for detail. Each citation should identify the document or official source, date or version, and page, section, filing, or record location where possible.
The evidence trail should include the original source, extracted text, reviewer analysis, validation state, and later changes. Automation can assist classification and candidate extraction, but a material conclusion needs accountable human review. Keep uncertainty visible and route low-confidence outputs to a reviewer.
Gotham's practice tools are designed to keep matter documents, research, and workflows close together. Before placing sensitive deal material into any platform, assess access, retention, deployment, and audit controls. Gotham's security overview provides a starting point for that evaluation.
What quality controls should apply before circulation?
Use independent senior review for every critical and high-priority issue. Sample-test lower-priority findings and negative conclusions based on risk. Reconcile report issues against the live request list, contract register, regulatory workstreams, and transaction-document drafting log.
Run a pre-circulation checklist:
- scope, entities, dates, and transaction version are current;
- every material fact has a citation or named source;
- fact, assessment, and recommendation are distinguishable;
- priority follows the agreed definitions;
- unresolved gaps and assumptions are conspicuous;
- deal-document responses match the reported issue;
- owners and milestones are named;
- privileged or restricted material is handled appropriately; and
- an authorised reviewer approved circulation.
Read the executive summary against the detailed register. It should neither introduce unsupported claims nor omit an issue that could change a near-term decision.
How should the report influence signing and closing documents?
Create a response matrix that links each accepted finding to the responsible transaction-document provision or operational action. Possible responses may include conditions precedent, covenants, disclosures, warranties, indemnities, holdbacks, price mechanisms, consents, waivers, remediation, or acceptance of a known risk. Qualified counsel decides which response is appropriate.
Track drafting status and evidence. “Addressed in SPA” is incomplete unless the register identifies the provision, draft version, reviewer, and any remaining negotiation. If the commercial team accepts a risk, record the decision and authority rather than silently closing the issue.
Competition and securities issues may affect process, disclosure, information sharing, and timetable. Keep specialist counsel's current assessment linked to the main report so a structure or date change can trigger re-review.
What should be handed to the integration team?
Convert surviving issues into operational records. Include obligation, trigger, owner, due-date logic, source, dependency, evidence of completion, and escalation path. Relevant items may include contract notices, licence renewals, dispute dates, policy remediation, employee actions, data commitments, security improvements, and intellectual-property assignments.
Mark what remains provisional. Integration owners should not inherit a legal summary without the documents and assumptions needed to act. Confirm acceptance of each high-priority handoff, schedule follow-up, and preserve the final report with its source cut-off and evidence index.
If your team needs an evidence-linked diligence and exceptions workflow, contact Gotham. A useful red-flag report is brief enough to guide action, detailed enough to verify, and candid enough to show where the answer is not yet known.
