The actual order defines the restriction
Companies Act section 222 allows the Tribunal, on the stated investigation or complaint facts and its necessary opinion, to impose restrictions on relevant securities issued or to be issued by a company. The specified period cannot exceed three years. The company must read the securities, activities, conditions and period in the operative order; the statutory maximum does not automatically make every order last three years or freeze every security.
Read the applicable text: NCLT-hosted Companies Act section 222.
Identify the jurisdictional basis without inventing an order
The provision refers to an investigation under section 216 or a complaint by a person in this behalf, with the Tribunal considering restrictions necessary to discover relevant facts. A complaint alone is not the same as an operative order. Record the case reference, authority and actual directions before changing the company’s transaction-control status.
Map securities precisely
Translate class, certificate, folio, distinctive-number or depository descriptions into the register population, using the identifiers applicable to the holding. Include securities to be issued if covered by the order. Do not assume an order concerning one class automatically covers another, or that an unissued security cannot be restricted merely because it lacks a certificate yet.
Map actions separately from holdings
For each proposed issue, transfer or other action, check what the order actually restricts. Section 222(2) addresses securities issued, transferred or acted upon in contravention; compliance cannot be reduced to a transfer-only checkbox. Conversely, an order should not be expanded into prohibitions it does not contain. Resolve ambiguous directions through an appropriate legal process rather than treating software settings as interpretation.
Maintain versions and dates
Retain the signed order and later variations, clarifications or relief. Record the actual period, commencement and expiry wording. Calendar-year periods should not be converted casually to a fixed number of days that ignores leap years. A shorter period does not automatically extend to the statutory maximum; an internal diary entry is not evidence of a judicial extension.
Use a controlled review record
Preserve the request, matching restricted holdings, proposed action, decision and source order. Reconcile system coverage to the legal scope, with no duplicate holdings in the count. Examples below are fictional control calculations; being outside the population of one assumed order does not establish freedom from every other law, order or contractual restriction. No penalty amount or case outcome is inferred from these counts.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Covered shares versus total capital
A company has 1,000,000 issued shares; an assumed order specifically covers 600,000. The other 400,000 are outside that order’s stated security population, not automatically approved for all transactions. System coverage should match 600,000 rather than all capital by default.
Illustrative example 2: Request overlap
A proposed transfer covers 50,000 shares, of which 30,000 match the order’s restricted identifiers. Review that 30,000 against the operative restriction and separately review the 20,000 outside this match. A partial match must not be hidden in a single all-clear status.
Illustrative example 3: Unissued securities
An assumed order covers a proposed issue of 200,000 identified securities. A draft upload includes 150,000, leaving 50,000 missing from that future-issue control population. The securities being unissued does not itself remove the order’s assumed coverage.
Illustrative example 4: Duplicate register match
Two linked reports each show the same 80,000 restricted shares. Their naive sum is 160,000; the unique restricted population remains 80,000. Reconcile depository and company references before concluding the number covered.
Illustrative example 5: Shorter actual period
Assume the operative order expressly imposes an 18-calendar-month period. The statutory three-year maximum corresponds to 36 calendar months, but does not add the remaining 18 months automatically. Determine actual calendar dates from the order rather than treating this comparison as an extension.
Illustrative example 6: Order variation
An assumed later operative order expressly releases 25,000 of an original 100,000 restricted shares and leaves the remainder covered. Updated population is 75,000. Preserve the original order, relief and effective wording; an unapproved company request for release would not produce this result.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the proceeding | Case and statutory basis. |
| 2 | Obtain the operative order | Signed directions and authentic copy. |
| 3 | Identify securities covered | Class and holding identifiers. |
| 4 | Include future issues where directed | Proposed-security mapping. |
| 5 | Identify restricted actions | Issue, transfer and other directions in the order. |
| 6 | Determine actual period | Start/end wording and calendar-date review. |
| 7 | Reconcile system coverage | Unique holdings and excluded duplicates. |
| 8 | Review each proposed action | Request-to-order matching evidence. |
| 9 | Apply later orders accurately | Variations and effective dates. |
| 10 | Preserve decisions and unresolved issues | Review trail and appropriate clarification. |
Sixteen practitioner FAQs
1. Does a complaint alone create a section 222 restriction?
No. Distinguish the complaint from the Tribunal’s operative order.
2. What investigation does subsection (1) mention?
An investigation under section 216, alongside the stated complaint route.
3. Can securities to be issued be covered?
Yes. The text includes issued securities and securities to be issued.
4. Is the maximum period three years?
Yes, the order’s specified period must not exceed that statutory limit.
5. Does every order last three years?
No. Read its actual period.
6. Can the company extend a shorter order internally?
An internal setting does not constitute an operative extension.
7. Does one security class automatically mean all classes?
No. Map the actual directions.
8. Why match distinctive or depository identifiers?
They establish which holdings actually fall within the order’s description.
9. Are only transfers relevant?
No. Subsection (2) also refers to issue and securities acted upon in contravention.
10. Can software determine the legal scope?
No. Its controls should implement the interpreted operative order.
11. What if a request partly overlaps covered securities?
Separate matched and unmatched populations and review both on their actual legal bases.
12. Are unmatched securities free from every restriction?
No. The absence of this match does not resolve other laws or orders.
13. Should depository and register counts be added blindly?
No. They may describe the same holdings.
14. Can a release request reduce coverage by itself?
No. Obtain and apply the actual operative relief.
15. Should all three-year periods be counted as 1,095 days?
No. Read the calendar period and dates; leap years can affect day counts.
16. What evidence supports a transaction decision?
The request, identifiers, current order version, applicable period and documented review.