Competition law merger-control diligence in India is not a threshold calculator completed after the commercial deal is settled. It is an evidence exercise that connects the proposed transaction, the parties and their groups, the relevant financial records, market overlaps, contractual steps, and the planned timetable. A sound process helps counsel decide what must be investigated, what remains uncertain, and which workstream owns the next action.
The governing materials can change, so the file should point to the version actually reviewed. Start with the Competition Act, 2002 on India Code and the Competition Commission of India's current legal framework and regulations. CCI publications and orders can add procedural context, but transaction-specific conclusions belong to qualified counsel.
What should the merger-control diligence team establish first?
Begin with a short transaction map rather than a yes-or-no filing question. Record every acquisition, merger, amalgamation, subscription, asset transfer, option, step, and connected agreement that may form part of the arrangement. Identify the direct parties, ultimate controllers, relevant group relationships, signing sequence, closing conditions, interim rights, and jurisdictions involved.
The initial map should separate confirmed evidence from management description. A slide saying “minority investment” does not establish the rights attached to shares, board representation, reserved matters, information access, commercial arrangements, or later acquisition steps. Review the executed or latest proposed instruments and the connected definitions.
| Workstream question | Evidence to collect | Owner | Escalation signal |
|---|---|---|---|
| What is being acquired? | Term sheet, structure chart, draft transaction documents | Deal counsel | Inconsistent steps or missing side agreement |
| Who are the relevant persons and groups? | Ownership records, control rights, organisation charts | Corporate and competition counsel | Unclear beneficial ownership or joint control |
| Which financial measures may matter? | Audited accounts, turnover and asset workings, geographic allocation | Finance with counsel | Different periods, currencies, or group perimeters |
| Where do activities overlap? | Product lists, customer data, internal strategy papers | Business and economics teams | Narrow segment or pipeline overlap omitted |
| What timetable is assumed? | Signing plan, long-stop date, conditions precedent | Transaction lead | Closing dependency not reflected in documents |
A controlled workspace helps keep this material linked. Gotham's practice tools can support matter-centred document and workflow organisation, while the bulk contract review guide explains how to establish a traceable document population.
How should parties test whether a combination assessment is required?
Counsel should build a dated assessment memo that shows its inputs and sources. Do not hard-code statutory figures into a reusable checklist. Thresholds, exemptions, notification routes, forms, and procedural rules can change, and transitional questions may depend on signing or closing dates. Instead, link the matter file to the current CCI notification, regulations, and statutory text reviewed on the assessment date.
Use a sequence that can be audited:
- Characterise each transaction step and the rights or assets involved.
- Identify all persons and group entities relevant to the applicable test.
- determine the correct financial periods, accounting records, currencies, and geographic allocations.
- Test any exemption or exclusion separately, with its evidence and conditions.
- Assess whether connected or interdependent steps need to be considered together.
- Record the conclusion, assumptions, unresolved facts, reviewer, and review date.
- Reopen the assessment if the structure, rights, accounts, law, or timetable changes.
For financial data, preserve both the source account and the calculation sheet. A bare total is difficult to validate. Each line should identify the entity, period, measure, source page, adjustment, exchange-rate source where relevant, and reviewer note. If the company perimeter differs between ownership charts and consolidated accounts, treat that as an issue rather than choosing the convenient version.
What market information belongs in competition diligence?
Threshold analysis and substantive overlap analysis are related but distinct workstreams. Even when an initial view appears straightforward, counsel may need enough commercial evidence to understand horizontal overlaps, vertical links, complementary activities, portfolio relationships, data advantages, distribution dependencies, or pipeline competition.
Ask business teams for facts in their ordinary language before forcing products into legal market labels. Collect product and service descriptions, use cases, customer groups, geographies, routes to market, major inputs, sales channels, internal competitor tracking, recent bids, planned launches, and capacity constraints. Date each dataset and define its scope.
| Evidence set | Useful question | Common diligence weakness |
|---|---|---|
| Revenue by product and geography | Where do both parties earn revenue from similar activity? | Categories differ between parties |
| Customer and bid records | Do customers treat the parties as alternatives? | Only successful bids are supplied |
| Internal strategy documents | How does management describe competitors and expansion? | Search limited to polished board decks |
| Supplier and distribution contracts | Could the deal affect access to an input or route to market? | Amendments and regional schedules missing |
| Product roadmap | Are future offerings likely to meet? | Aspirational plans reported as committed facts |
| Industry material | What external evidence tests internal claims? | Undated or promotional sources treated as proof |
Avoid writing a final market definition into an intake form. Record plausible frames and the evidence that supports or cuts against each one. Counsel can then decide what analysis is needed without losing the underlying business facts.
Which transaction documents deserve clause-level review?
Merger-control diligence is not confined to the notification form. The share purchase, subscription, shareholders', business transfer, merger, financing, transitional-services, supply, distribution, and side agreements may contain rights or steps relevant to the assessment and timetable.
Reviewers should extract the precise clause and connected definition for:
- conditions precedent tied to CCI approval or expiry of a waiting period;
- efforts standards, cooperation duties, information rights, and filing control;
- long-stop dates, extension mechanics, termination rights, and break consequences;
- interim operating covenants and buyer consent rights;
- risk allocation for remedies, divestment, behavioural commitments, or litigation;
- warranties concerning filing information and competition compliance;
- confidentiality rules governing competitively sensitive information; and
- post-signing integration, clean-team, or information-sharing arrangements.
Labels can mislead. An “ordinary course” covenant may contain detailed consent rights, and a cooperation clause may allocate control over submissions or commitments. The contract review playbook offers a method for turning questions into review rules. For sensitive deal material, review Gotham's security overview before introducing a platform into the workflow.
How can a team manage gun-jumping and information-sharing risk?
Signing does not make the parties one business. The diligence plan should address how personnel exchange information and how the target operates before closing. Qualified counsel should decide what information can be shared, who can see it, and whether aggregation, redaction, a clean team, or another safeguard is appropriate.
Build an information-request register with four fields: purpose, requested data, permitted recipients, and approved handling method. Commercially sensitive material such as current customer-level pricing, future bids, granular costs, or strategic plans warrants careful review. A broad request made for “diligence” should not bypass the agreed protocol.
Run an interim-covenant check before consent workflows go live:
- Is the request connected to value preservation or another documented purpose?
- Does the proposed right allow influence over ordinary competitive decisions?
- Can the question be answered with older, aggregated, or redacted data?
- Are clean-team recipients named and access logged?
- Is advice or approval recorded before information is released?
- Are integration planning and operational implementation kept distinct?
- Can the team suspend access promptly if scope changes?
The process must work in practice, not only in a protocol document. Train deal participants, name an escalation contact, keep access logs, and sample-test folders and communications.
What should the CCI filing evidence file contain?
A filing workroom should let another authorised reviewer understand where each material statement came from. Maintain a source table that links form questions to source documents, business owners, legal review, open points, and submission versions. Preserve calculations and approvals rather than overwriting them.
A useful evidence file contains:
- the dated statutory and regulatory materials relied upon;
- the final transaction map and entity perimeter;
- audited accounts and traceable threshold workings;
- product, geography, customer, competitor, and market datasets with definitions;
- transaction documents and an indexed clause extraction;
- minutes or notes of factual interviews with named owners;
- draft-to-final changes, factual verification, and sign-offs;
- correspondence, information requests, and response owners; and
- a log of assumptions that changed during the process.
Use the CCI's official website to locate current forms, notices, orders, and contact material. A search-engine snippet or secondary summary is not a controlled source. Store the accessed date and a copy or stable citation permitted by the team's records policy.
How should red flags be reported to decision-makers?
A long legal memo is not a substitute for a live risk register. Each red flag should state the verified fact, source, why it matters, decision required, owner, due date, and status. Separate a missing fact from an adverse fact. “Turnover allocation not yet reconciled” and “filing required” are not the same conclusion.
| Status | Meaning | Required action |
|---|---|---|
| Confirmed | Evidence has been checked and legal reviewer has classified the issue | Reflect it in timetable and documents |
| Provisional | Preliminary evidence supports a view but validation remains | Assign source and review deadline |
| Open | A necessary fact or document is missing | Issue focused request and track response |
| Changed | Deal or evidence changed after prior review | Reassess affected conclusions |
| Closed | The issue was resolved with evidence | Retain resolution and approval trail |
Report dependencies plainly. A filing assessment may affect signing language, closing conditions, financing assumptions, information exchange, and long-stop dates. It should therefore appear in the central deal plan, not sit in a separate competition folder that transaction leaders rarely open.
If your team needs a structured intake, document review, and issues workflow, contact Gotham. The objective is not to automate legal judgment. It is to keep facts, sources, responsibilities, and decisions connected while counsel applies the current law to the actual transaction.
