Verification is a duty, not a vibe
Tenant police verification sits in an odd triangle: the landlord carries the legal duty in most cities, the police hold the process, and the society ends up as the checkpoint that notices whether it happened. This guide walks the process and draws the society's actual boundaries.
Operator guide, written August 2026. Security practice varies with premises and state rules; treat this as method, and your society's bye-laws and local police guidance as the authority.
Whose duty it is, and where it comes from
In most Indian cities, intimation of tenancy to police is the landlord's obligation, typically created by orders under Section 144 CrPC or its successor provisions, renewed by police commissionerates, and in some states by rent-act rules. The tenant cooperates; the landlord files. Non-compliance exposes the landlord, penalties vary by city and order. The society is not the duty-holder, but bye-laws commonly require members to intimate lettings and complete society formalities, which is how the society legitimately asks whether verification was done.
How the process actually runs
The shape is consistent city to city even as portals differ: the landlord submits tenant details, photographs and identity documents, commonly through the city police's online citizen portal, sometimes through the local station, and receives an acknowledgement. The police may verify antecedents against records; the acknowledgement, not a certificate of good character, is what the landlord holds. Timing matters: before or immediately at occupancy, not months later. Documents typically involved: the tenancy agreement, tenant photo and government identity, prior address, and the landlord's own details. Keep the acknowledgement with the agreement; both surface together at renewals, disputes and society records.
The society as record-keeper, done right
The society's real power is the register: who occupies which unit on what basis, since when, with which formalities complete. Kept well, it answers the police enquiry in minutes, gives the gate its resident list, and protects the committee when an incident makes occupancy a question. Kept in scattered chats, it fails exactly when needed. The register earns its keep only if move-ins feed it as they happen — which is why the move-in checklist, the verification acknowledgement and the unit record belong in one workflow, not three drawers.
The move-in day itself, choreographed
Verification is one item in a move-in that touches half the society's systems, and the day goes smoothly when it is a checklist rather than a negotiation at the gate. Before the truck arrives: intimation received, agreement copy and verification acknowledgement filed, any deposit per bye-laws receipted, lift protection and timing agreed, gate told the date. On the day: the unit's electricity and water readings noted, common-area condition walked where the society does that, tenant contacts and vehicles entered so the gate app recognises the household by evening. After: the register updated, billing pointed at the right payer for the heads that follow occupancy, and the welcome note with the society's rules — quiet hours, wet waste, visitor process — sent through the official channel. Ten minutes of choreography per move-in saves the committee the recurring genre of dispute that begins with 'nobody told us'.
Boundaries that keep committees out of trouble
Committees get into avoidable trouble in two directions: demanding beyond the bye-laws, community-specific tenant bans, arbitrary interviews, discriminatory refusals, which courts and registrars strike down; and ignoring the register entirely, which turns the society into the building where nobody knows who lives in B-704. The lawful middle is boring and effective: bye-law-based intimation, a complete register, non-occupancy charges exactly as capped, and escalation through the member when formalities stall. Write the move-in requirements once, publish them, and apply them to every unit identically.
How EstateDeck applies this
EstateDeck runs the move-in as one workflow: the intimation and checklist, the verification acknowledgement filed against the unit, tenant and vehicle details flowing to the gate, and a register that answers occupancy questions on demand.
Go deeper: Move-in/out · Unit register
Written by Databus Technology Solutions, the makers of EstateDeck. These guides describe how housing societies and property operations run in practice; they are not legal advice. Cooperative and apartment law varies by state and changes on its own schedule, so verify specifics against your state's act and your society's bye-laws before acting.
Frequently asked questions
Can the society refuse move-in until verification is shown?
The society can enforce its registered bye-laws: intimation of letting, NOC formalities where prescribed, records for the register. Physically barring a lawful tenant is where committees overstep into liability; the working lever is the member — the flat owner — whose obligations the bye-laws actually bind, including any non-occupancy charges.
What if the landlord simply refuses to do the verification?
The society cannot file it for them, and should not — the duty and the declaration are the landlord's. What the society can do is what its bye-laws support: record the tenancy intimation as incomplete, notify the member in writing that the formality is pending, apply the charges the bye-laws attach to letting, and keep the correspondence. If something later goes wrong with that tenancy, the society's file shows it asked, in writing, at the right time — which is exactly the position a committee wants to be in, and pressure enough that most landlords complete a process that takes an evening online.
Is police verification the same as background screening?
No. Police intimation notifies the state and checks records; it is not a character certificate or an employment-style screen. Landlords wanting more run reference checks and agreements with proper clauses; societies should not represent the acknowledgement as more than it is.
What should the society's own move-in record contain?
The unit, owner, tenant names and contacts, agreement dates, the verification acknowledgement reference, vehicle details for the gate, and the move-in checklist. That record serves gates, parking, dues and emergencies — and it is personal data, so keep it in the society's system with restricted access, not in a committee member's phone.
Do these rules apply to family members and long-term guests?
Occupancy by the member's own family is not a tenancy and needs no verification; a long-term guest or an informal arrangement without rent sits in a grey zone that societies handle through the intimation register rather than the police process. The practical line: if the occupant is not the member's household and the arrangement walks and talks like a tenancy, treat it as one — ask the member for the intimation, record the occupants, and let the landlord and police process apply. The register protects everyone precisely because it does not depend on what the arrangement is called.
Does verification repeat on renewal?
Fresh intimation on new tenancy is the safe rule; on same-tenant renewals, practice varies by city order. The landlord should check the current order's language; the society's record simply notes the renewal and the fresh acknowledgement where filed.
What about paying-guest arrangements and short stays?
PG operators fall under the same or stricter intimation regimes in most cities, sometimes with separate registration. Societies facing PG-heavy buildings should anchor rules in bye-laws and general-body resolutions rather than gate-level improvisation, which never survives the first argument.
Move-ins with a paper trail.
Applied on every payslip, files generated for upload — per employee, per month.
Start free