Procedure Before Rent Controller

Substantive rights under the Himachal Pradesh Urban Rent Control Act, 1987 are worthless without the machinery that enforces them, and that machinery is the Controller. Section 14(1) shuts the door of the ordinary civil court: a tenant in possession cannot be evicted "except in accordance with the provisions of this Act," which means a landlord must apply to the Controller and prove a statutory ground. This note maps the full procedural journey — who the Controller is, how an application is instituted, the summary leave-to-defend route for bona fide-need cases, the Controller's evidentiary powers, and the channels of appeal and revision. For judiciary and CLAT-PG aspirants the topic is a perennial favourite because it blends a tight statutory scheme with rich Supreme Court learning on summary procedure and the limited scope of revision.

The Controller as the exclusive forum

The architecture of the Act diverts every landlord-tenant dispute over a building or rented land away from the civil court and into the hands of the Rent Controller. Section 14(1) is the hinge: "a tenant in possession of a building or rented land shall not be evicted therefrom... except in accordance with the provisions of this Act." The corollary is that the landlord cannot file a suit for ejectment; he must present an application to the Controller and bring his case within the closed list of grounds in Section 14. The Controller is appointed by the State Government for a defined area, and he alone fixes fair rent, decides applications for permissible increase in rent, and passes orders of eviction. Because the Controller decides lis between parties on evidence and is bound by judicial norms, he is not a persona designata acting in a private capacity but an authority discharging quasi-judicial functions — the distinction the Supreme Court drew in Central Talkies Ltd. v. Dwarka Prasad, AIR 1961 SC 606, where it held that an officer named in a rent statute who functions with the powers and trappings of a court is not a persona designata. This characterisation matters for everything that follows: appeal, revision and the application of general procedural law.

Instituting an application before the Controller

Proceedings begin with a written application by the landlord (for eviction or increase of rent) or by the tenant or landlord (for fixation of fair rent or for deposit of rent). The application must set out the ground relied upon — for an eviction petition, the precise clause of Section 14(2) or 14(3) under which possession is claimed — because the Controller's jurisdiction is ground-specific and the landlord is confined to what he pleads. On receipt of the application the Controller issues summons to the respondent, who is entitled to notice and an opportunity to file a reply and lead evidence. The pleadings frame the dispute; the parties then go to issues, evidence and arguments much as in a civil trial, save where the special summary procedure displaces this ordinary course. Rent due during the pendency of an eviction petition is regulated separately: a tenant resisting a default petition will ordinarily deposit the admitted rent, and the statutory scheme for deposit of rent with the Controller protects a tenant whose landlord refuses to accept payment. The substantive grounds the landlord must establish are catalogued in the companion note on grounds for eviction, while the present note concentrates on the procedural route those grounds must travel.

The ordinary trial: pleadings, issues and evidence

For the bulk of eviction petitions — non-payment of rent, sub-letting, change of user, material impairment of the premises, nuisance and ceasing to occupy under Section 14(2) — the Controller follows a full adversarial procedure. The landlord pleads and proves the ground; the tenant contests on the merits; both sides lead oral and documentary evidence; and the Controller records findings of fact before passing a reasoned order. A defaulting tenant retains the statutory cushions built into Section 14(2)(i): the first proviso lets him purge default on the first hearing by tendering arrears with interest and assessed costs, and the third proviso lets him escape an eviction order by paying the amount due within thirty days. The Supreme Court clarified the post-order safety net in Kailash Chand v. Dharam Dass, (2005) 5 SCC 375, holding that the "amount due" payable within thirty days under the third proviso means only the arrears of rent, not interest or the cost of the petition — a reading that keeps the procedural escape route genuinely available to tenants. The ordinary procedure thus secures a contested hearing on the merits in every default and conduct-based case, in keeping with the Act's protective object explained in the note on the object and coverage of the Act.

The special summary procedure under Section 16

For certain urgent eviction claims the Act borrows the summary model of Section 25B of the Delhi Rent Control Act. Section 16 prescribes a "special procedure for the disposal of applications for eviction" on the ground of bona fide requirement under Section 14(3)(a)(iii) and under Section 15 (immediate possession for specified categories such as Armed Forces personnel and certain officials). On such an application the Controller issues summons to the tenant in the form set out in Schedule II to the Act. The defining feature is the inversion of the right to contest: the tenant served with the Schedule II summons "shall not contest the prayer for eviction" unless, within fifteen days of service, he files an affidavit stating the grounds on which he seeks to contest and obtains leave from the Controller to defend. This is a deliberate departure from the ordinary procedure, designed to give a deserving landlord swift possession without the delay of a full trial. The mechanism is examined in detail in the note on bona fide need, but its procedural skeleton — summons in Schedule II, affidavit, leave to defend — is central to the procedure before the Controller.

The leave-to-defend threshold: Inderjeet Kaur v. Nirpal Singh

Because the summary route can end a tenancy without a trial, the standard for granting leave to defend is the procedural fulcrum of Section 16. The statute directs the Controller to grant leave if the tenant's affidavit "discloses such facts as would disentitle the landlord... from obtaining an order for the recovery of possession." Interpreting the cognate Delhi provision, the Supreme Court in Inderjeet Kaur v. Nirpal Singh, (2001) 1 SCC 706, held that the burden on a tenant at the leave stage is light: it is enough that the affidavit prima facie discloses facts which, if proved, would disentitle the landlord, and where a triable issue is raised the statute itself casts a duty on the Controller to grant leave. Only a wholly frivolous or sham defence justifies refusal. The Court stressed that at this stage the parties proceed on affidavits, and the real test is whether the facts disclosed prima facie show the landlord would be disentitled — not whether the defence will ultimately succeed. The companion safeguard is the consequence of default: if the tenant neither appears nor obtains leave, the statements in the landlord's application are deemed admitted and an order of eviction follows. Inderjeet Kaur therefore prevents the summary procedure from collapsing into a rubber stamp while preserving its speed.

Evidentiary powers of the Controller: Section 25

To decide disputed questions of fact the Controller is armed with the procedural tools of a civil court. Section 25 confers on the Controller (and the appellate authority) the same powers as are vested in a civil court under the Code of Civil Procedure, 1908 in respect of summoning and enforcing the attendance of witnesses, compelling the production of documents, and examining witnesses on oath. These powers make the Controller's proceedings genuinely adjudicatory rather than administrative: parties can be compelled to produce rent records, lease deeds and account books, and witnesses can be examined and cross-examined. Coupled with the duty to record reasons and findings, this is precisely the constellation of features that stamps the Controller as a tribunal with the "trappings of a court." The practical upshot for an examinee is that a Controller's order is not a mere licensing decision but a judicial determination on evidence, reviewable on appeal and revision in the manner the Act prescribes. The same evidentiary discipline governs the fixation of fair rent, where the Controller must assess comparable rents and the condition of the premises on material led by the parties.

Appeal to the appellate authority: Section 24

An order of the Controller is not the last word. Section 24 provides for an appeal to the appellate authority, a forum the State Government constitutes by vesting the powers of the appellate authority in officers — in practice District and Sessions Judges or Additional District and Sessions Judges. The appeal is presented as a memorandum signed by the appellant or his recognised agent, within the period of limitation prescribed by the Act and Rules. The appellate authority hears the matter as a court of first appeal: it can re-appraise the evidence, reverse findings of fact, and substitute its own conclusion for that of the Controller, subject to giving the parties a hearing. Crucially, the appellate authority under a rent statute is itself a court. In Mukri Gopalan v. Cheppilat Puthanpurayil Aboobacker, AIR 1995 SC 2272, (1995) 5 SCC 5, the Supreme Court held that the appellate authority constituted under a State Rent Act has all the trappings of a court, that the Limitation Act, 1963 applies to appeals before it by virtue of Section 29(2) of that Act, and that it can therefore condone delay under Section 5 of the Limitation Act. The principle directly governs the HP appellate authority, so a delayed appeal under Section 24 is not automatically barred — the appellant may seek condonation on sufficient cause.

Revision to the High Court: Section 24(5)

The decision of the appellate authority is final "except" for the supervisory power of the High Court. Section 24(5) empowers the High Court, on the application of an aggrieved party or of its own motion, to call for and examine the record of any proceeding to satisfy itself as to the legality or propriety of an order or proceeding, and to pass such order as it thinks fit. This is a revisional, not an appellate, jurisdiction, and its scope is correspondingly narrow. The Himachal Pradesh High Court reaffirmed its limits in Usha Chaudhary v. Raj Prakash, 2025:HHC:33885, holding that while exercising revisional jurisdiction the High Court "will not sit as a Court of appeal," that concurrent findings of fact recorded by the Controller and the appellate authority cannot normally be interfered with, and that interference is warranted only where there is perversity or absolute illegality; a reappraisal of evidence in revision is impermissible. The revisional court therefore polices legality and propriety, not the correctness of every factual finding — a distinction examinees frequently confuse with the wider re-hearing available before the appellate authority under Section 24.

Execution of orders and restoration of possession

An order of eviction is meaningless unless it can be enforced. Section 26 provides for the execution of the Controller's orders, so that an order for recovery of possession is given effect through the machinery available for executing the decree of a civil court, and the tenant who fails to comply can be dispossessed in due course of law. The Act also builds in anti-abuse and restoration safeguards that have a procedural dimension. Under Section 14(5), a tenant evicted on a bona fide-need ground may apply to the Controller to be restored to possession if the landlord fails to occupy the premises within the prescribed period or re-lets or misuses them — a fresh proceeding before the Controller that polices the genuineness of the original claim. Section 14(7) lets the Controller award compensation up to five hundred rupees against a landlord whose eviction application is found frivolous or vexatious, deterring abuse of the very procedure described in this note. Together, execution under Section 26 and restoration under Section 14(5) close the procedural loop, ensuring that the Controller's order is both enforceable and, where the landlord acts in bad faith, reversible.

Tenancies for a limited period and decisions that have become final

Two further provisions shape the procedure in specific situations. Section 17 deals with tenancies for a limited period: where, on the landlord's application, the Controller has earlier granted permission to create a tenancy for a fixed term, the landlord can on expiry of that term recover possession through a relatively expedited order, the Controller's role being to verify that the conditions of the permission are satisfied rather than to retry the question of need. This is a procedural device that lets landlords let out premises temporarily without forfeiting the right to recover them. Section 18 then protects the finality of adjudication: decisions which have become final are not to be reopened, barring a party from relitigating the same questions before the Controller in fresh proceedings. The provision imports a statutory analogue of res judicata into rent control practice, preventing harassment by successive applications on identical grounds. For an examinee, the pairing illustrates the Act's balance — Section 17 gives the landlord a fast track in genuine fixed-term lettings, while Section 18 protects the tenant (and the system) from endless re-agitation of settled disputes. Both feed back into the definitions of the parties and premises explored in the note on tenant, landlord and building.