Reserved Matters in Shareholder Agreements: Reverse Vetoes vs Affirmative Votes
Reserved matters are the structural protection of minority shareholders in Indian joint ventures and investee companies. The choice between a reverse-veto architecture and an affirmative-vote architecture — which appears at first glance to be a drafting nicety — has direct consequences for enforceability, governance friction, and exit dynamics.
The two architectures
The reserved-matters list in a shareholders' agreement (SHA) typically protects the minority shareholder by requiring its consent for specified board and shareholder decisions. The protection can be drafted in two ways.
The affirmative-vote architecture requires that the specified decision be approved by an affirmative vote that includes the minority shareholder's consent. The decision cannot be passed unless the minority shareholder votes in favour. The minority's consent is constitutive of the resolution.
The reverse-veto architecture permits the majority to pass the specified decision in the ordinary course, but requires the company (or the majority) not to act on the decision without the minority's prior written consent. The minority does not vote on the resolution; the minority's consent is a condition precedent to implementation.
The two architectures appear functionally similar — in both, the minority can block the decision. But the legal consequences are quite different.
The Companies Act constraint
The starting point is Section 6 of the Companies Act, 2013: any provision of an SHA or other contract that is contrary to the Articles of Association of the company is, to that extent, void. The Articles are the constitutional document; the SHA is a contractual document; and where they conflict, the Articles prevail in matters of corporate governance.
The Supreme Court's decision in V.B. Rangaraj v. V.B. Gopalakrishnan, and the long line of authority that has followed, confirms that restrictions on transferability of shares (and, more broadly, restrictions on the exercise of corporate-law powers) must be in the Articles to be enforceable against the company.
The Vodafone International Holdings line of authority refined this position: while restrictions in the SHA may be enforceable as between the parties to the SHA (as contractual obligations), they are not enforceable against the company unless mirrored in the Articles.
The affirmative-vote architecture
The affirmative-vote architecture, properly mirrored in the Articles, gives the minority a constitutional voting right. The minority's vote is an integral part of the corporate-law process; without that vote, the resolution does not pass.
The architecture has two consequences. First, where the Articles are properly drafted, the resolution passed without the minority's vote is void — not merely unenforceable. The company cannot act on it; the consequences flow as a matter of corporate law.
Second, the architecture creates direct enforceability through the corporate-law process. The minority can challenge a resolution passed without its consent before the NCLT under Section 241/242 (oppression and mismanagement) or, where applicable, under the relevant SEBI framework for listed companies.
The drawback is governance friction. The minority's consent is required for every reserved-matter decision; even routine decisions that fall within the reserved-matters list (which is typically broad) require the minority's affirmative vote. The board cannot act in the minority's absence; the shareholders meeting cannot conclude without the minority's participation.
The reverse-veto architecture
The reverse-veto architecture preserves the company's freedom to pass resolutions in the ordinary course, while preserving the minority's contractual protection. The board passes the resolution; the company does not implement it without the minority's consent.
The architecture has the practical advantage of governance flexibility. Routine reserved-matter decisions can be passed without bringing the minority's voting machinery into play. The minority's protection is exercised at the implementation stage, where it matters most.
The drawback is the enforceability question. The reverse-veto is a contractual obligation between the parties to the SHA; it is not, of itself, a constraint on the company's corporate-law actions. Where the company implements the decision without the minority's consent, the minority's remedy is in damages or specific performance against the breaching party — not a finding that the corporate action is void.
The affirmative-vote architecture is constitutional protection at the cost of governance friction. The reverse-veto architecture is contractual protection at the cost of corporate-law enforceability. The choice depends on the parties' relative concerns.
The hybrid approach
In practice, sophisticated SHAs deploy a hybrid approach. Highly consequential decisions — where corporate-law voidness is the desired remedy — are structured as affirmative-vote items, with mirroring in the Articles. Routine but minority-significant decisions — where contractual enforceability is sufficient — are structured as reverse-veto items in the SHA only.
The hybrid drafting requires careful classification of the reserved matters. Decisions affecting corporate fundamentals (alteration of Articles, capital structure, fundamental transactions, exit triggers) are typically structured as affirmative-vote items mirrored in the Articles. Decisions affecting operational matters (budget approval, capital expenditure thresholds, key-management appointments below board level) are often structured as reverse-veto items in the SHA only.
The Articles question
The drafting of the Articles to mirror the SHA's affirmative-vote architecture requires careful attention. Three drafting protocols are critical.
First, the Articles must use language consistent with the Companies Act framework. The Articles should refer to the relevant resolution-type (board resolution, special resolution, ordinary resolution) and require, in addition to the statutory threshold, the affirmative vote of the specified shareholder.
Second, the Articles should preserve the company's flexibility to act where the affirmative vote is unreasonably withheld. A typical drafting includes a "good faith" obligation on the protected shareholder to consider the matter on its merits, with the consent not to be "unreasonably withheld" — though the enforceability of such qualifiers is contested in Indian law.
Third, the Articles should include a mechanism for resolving deadlocks. Where the affirmative-vote requirement results in deadlock — the majority wishing to act, the minority withholding consent — the contract should provide a deadlock-resolution mechanism (typically buyout, swing-vote, expert determination, or, as a last resort, exit-trigger).
Working observations
Three observations from current practice. First: the choice of architecture must be made at the term-sheet stage, not as a drafting afterthought at definitive-documentation stage. The choice has consequences for the Articles drafting, the regulatory clearances (where applicable), and the eventual exit dynamics.
Second: where the affirmative-vote architecture is adopted, the Articles must be drafted in alignment with the SHA from day one. Discrepancies between the two documents — the SHA recording the protection, the Articles silent on it — create the dual-document enforceability gap that has been the subject of significant Indian litigation.
Third: the reserved-matters list must be calibrated to the specific concerns of the parties. A list that is too broad creates governance friction; a list that is too narrow leaves substantive concerns unprotected. The list-drafting is the working judgment of the SHA process. For an analysis of related drafting concerns, see our corporate practice page on shareholder agreements.