A legal due diligence checklist for an Indian transaction is useful only when it is tied to the deal thesis, the target's actual structure, and verifiable source material. A generic request list may collect thousands of files while missing the one approval, encumbrance, contract right, or dispute that affects value or closing.

Build the process around questions and evidence. The Companies Act, 2013 on India Code, the Ministry of Corporate Affairs portal, and the Competition Commission of India are primary starting points for company and competition context. Counsel should confirm the current law, rules, forms, exemptions, and transaction-specific consequences.

What should be fixed before the first request list is sent?

Write a scope note that names the transaction, entities, review period, materiality logic, jurisdictions, workstreams, exclusions, reporting format, and decision owners. Tie each request to a question the deal team needs answered. “All material documents” is not a testable request unless the team defines materiality and completeness.

Scope itemDecision it supportsEvidence ownerCompletion test
Corporate authorityCan the entity enter and complete the deal?Company secretarial teamRecords reconciled and exceptions logged
Ownership and securitiesWhat is being acquired and from whom?Corporate counselCap table traced to supporting instruments
Material contractsWhat rights or dependencies can affect continuity?Commercial counselPopulation reconciled and clauses validated
Disputes and investigationsWhat exposure or restriction may persist?Litigation counselInternal and external sources compared
Regulatory permissionsCan the business operate and can approval transfer?Specialist counselPermission, holder, scope, and status verified
Competition assessmentDoes the transaction require analysis or process?Competition counselDated memo with sources and assumptions

Create an issues taxonomy before review. Agree what is critical, high, medium, informational, and out of scope. The label should reflect transaction consequence, not how surprising a reviewer finds the document.

Which corporate and ownership records should be reconciled?

Collect constitutional documents, statutory registers, board and shareholder minutes, annual filings, share certificates, allotment and transfer records, shareholder agreements, option and incentive records, convertible instruments, beneficial-ownership material, charges, and group charts. Retrieve authorised MCA material where appropriate and record the retrieval date.

Reconcile the legal register, management cap table, financial statements, transaction documents, and filings. Differences belong in the issues log. Do not silently correct one source to match another.

  • Trace issued securities to approvals, consideration, and supporting instruments.
  • Identify transfer restrictions, pre-emption, tag, drag, veto, and exit rights.
  • Map options, warrants, convertibles, pledges, liens, and other encumbrances.
  • Check whether board and shareholder actions were taken by the required body.
  • Link changes in directors, registered office, capital, and charges to filings.
  • Record missing registers, incomplete minutes, and unexplained cap-table movements.

Corporate records should be reviewed as a timeline. An approval dated after an allotment, or minutes that do not match a filing, may call for further factual and legal review even when every individual file looks complete.

How should material contracts be reviewed?

Build a contract population from more than the data room. Reconcile authorised finance, procurement, sales, property, technology, licensing, and operations records. Then group the governing agreement with amendments, orders, schedules, guarantees, waivers, renewals, and notices.

The bulk contract review workflow explains this reconciliation in detail. For each material relationship, extract the operative term, termination, renewal, assignment, change-of-control, exclusivity, pricing, liability, indemnity, audit, data, intellectual-property, compliance, and dispute provisions relevant to the deal.

Review questionRequired outputEscalate when
Can the relationship continue?Trigger, consequence, consent or notice pathAmendment or definition is missing
Can either party exit?Right, notice, timing, and costTermination provisions conflict
Are economics dependable?Pricing mechanism and adjustment rightsSide letter changes the schedule
Are key assets or rights usable?Licence scope, ownership, restrictionsChain of title is incomplete
What survives closing?Obligation, owner, trigger, durationHandoff owner is not identified

Keep citations with findings. A summary without document identity, section, source text, and validation status forces later reviewers to repeat the work.

Which regulatory and competition questions belong in the checklist?

Prepare a licence and approval register showing the holder, issuing authority, activity, territory, validity, conditions, renewal status, transfer or control implications, correspondence, and evidence source. Ask which permissions are actually needed to operate, rather than relying only on what appears in a folder labelled “licences.”

Map the target's products, locations, regulated activities, data practices, imports, exports, environmental interfaces, employment footprint, and government relationships. Route specialist questions to qualified counsel. Record what was checked and what was not.

Competition diligence needs its own dated transaction and entity map. Counsel may need current financial evidence, group relationships, transaction steps, market overlaps, filing materials, and interim-conduct controls. Do not embed changing statutory thresholds in a permanent checklist. Link to the current official material used and preserve the assessment date.

How should litigation, compliance, and investigations be tested?

Request pleadings, orders, notices, legal opinions, settlement documents, investigation correspondence, internal case lists, contingent-liability records, insurance notifications, and relevant board materials. Reconcile these against authorised court, tribunal, regulator, finance, and auditor sources where appropriate. Name searches alone can miss older names, subsidiaries, and matters filed in another capacity.

For each matter, record forum, parties, number, subject, stage, relief, financial exposure, operational consequence, next date, counsel, insurance position, and source date. Separate management estimates from verified orders or filings.

Compliance review should test the target's actual controls and incidents, not only policy titles. Select risk-based samples for approvals, gifts, third parties, complaints, training, investigations, remediation, and monitoring. If policy and practice differ, report the evidence and potential consequence without inventing a legal conclusion.

Gotham's legal research workflow guide offers a verification-first method for source research. Its security overview can help teams assess handling controls before sensitive investigation or personnel material enters a review system.

How should intellectual property, technology, and data be examined?

Create an asset and dependency map. For intellectual property, connect registered and unregistered assets to creators, assignments, licences, employment or contractor terms, renewal evidence, disputes, and products that use them. A registration list alone does not prove ownership or freedom to operate.

For technology, identify critical software, hosting, source-code access, open-source components, outsourced development, service dependencies, resilience obligations, security incidents, and termination assistance. Review what the contract promises against how the system is operated.

For data, identify categories, purposes, sources, sharing, processors, locations, retention, security commitments, incidents, and deletion or migration needs. Counsel should assess current applicable requirements and contractual restrictions. Record uncertainties instead of converting a questionnaire response into a verified fact.

What makes a red-flag report decision-ready?

A decision-ready report separates fact, legal assessment, deal consequence, and recommended next step. It begins with scope, dates, sources, assumptions, limitations, and missing information. Each issue links back to the evidence and names an owner.

FieldPractical entry
Verified factShort statement with document or source citation
UncertaintyMissing fact, inconsistent evidence, or unresolved interpretation
Deal relevancePrice, structure, condition, covenant, indemnity, timetable, or integration
ActionFocused request, specialist review, drafting response, or operational task
Owner and statusNamed role, due date, open or closed state

Do not bury document gaps at the end. Missing evidence may be the central finding. Maintain a live request-and-issues register so late uploads and deal changes can update affected conclusions.

How does diligence move into signing, closing, and integration?

Convert findings into drafting and operations. Link each condition precedent, consent, approval, disclosure, remediation item, and closing deliverable to the relevant issue and evidence. After closing, hand continuing obligations, licence renewals, litigation dates, security commitments, contract notices, and remediation work to accountable owners.

Use final gates:

  1. scope changes and transaction versions have been reflected;
  2. high-priority findings received senior review;
  3. open requests show their consequence and owner;
  4. report statements have traceable citations;
  5. required consents and approvals have evidence of status;
  6. signing and closing documents address agreed findings; and
  7. integration owners have accepted continuing tasks.

If your team needs a structured evidence, review, and exception process, contact Gotham or explore its practice tools. A strong checklist does not promise that every risk has been found. It shows what was asked, what was tested, what the evidence supports, and what still needs a decision.