The most common question from someone starting a PG is "what licence do I need?" The uncomfortable answer is that "paying guest accommodation" isn't a single national legal category, so the question has no single answer — and that ambiguity is exactly what gets owners into trouble.
Quick answer (for the impatient)
PG regulation is local — municipal and state, sometimes with police involvement, and it genuinely differs city to city.
Several obligations apply regardless of whether your city has a specific PG rule: building use, food, fire, tax and tenant records.
"Nobody around here registers" is not a compliance position. It's a description of enforcement, which changes.
Why the category is murky
A PG sits between a residential tenancy and a commercial lodging business, and different authorities view it differently. To the municipality it may be a change of building use. To the police it may be lodging with guest-record obligations. To the tax authorities it's a business. To your neighbours it's a residential flat with fourteen people in it.
Several Indian cities have introduced or attempted specific PG regulations covering registration, minimum space per occupant, safety requirements and record-keeping. Others have not. Bengaluru, Pune, Hyderabad, Delhi and others have each moved differently and at different times — which is why advice from a PG owner in another city is genuinely not transferable.
What applies almost everywhere
Building use and occupancy. Running a commercial PG from a property zoned or approved as residential is the most common underlying exposure, and the one that surfaces when a neighbour complains.
Trade licence from the municipal body, where your city requires one for this activity.
Food licence if you run a mess — see FSSAI for a PG mess. Providing meals is a food business, no matter how informal.
Fire safety requirements, which scale with building height and occupancy — see fire safety for hostels.
Tenant records and verification, where local police require them — see tenant verification.
Tax registration — GST position, and your income being business income. See GST on PG.
Shops and Establishments registration if you employ staff — a cook and a warden count.
The building-use question is the serious one
Most PG enforcement action starts with a complaint, and most complaints are about the building rather than the business — parking, noise, water usage, or simply the number of people. Once an inspection is triggered on that basis, everything else gets looked at.
This is why the "everyone here does it" position is fragile. It holds until one neighbour is annoyed enough, and at that point the informality that was convenient becomes the whole problem.
A practical operating workflow for this PG
The useful way to apply Is a PG Even a Legal Category? What You Actually Need to Register is to turn the idea into a repeatable operating rhythm. Start with the current process, not the software screen. Write down who begins the task, what information they need, where the record is kept, who checks an exception, and what the resident is told. That prevents a common PG mistake: digitising an unclear process and discovering that the same argument now happens faster.
Step 1 — establish the starting record. PG regulation is local — municipal and state, sometimes with police involvement, and it genuinely differs city to city. The owner or warden should decide which field, document or confirmation is the source of truth. Existing residents, rooms, balances or requests should be checked before a new workflow is switched on. If the starting record is incomplete, note the gap openly instead of filling it with an assumption.
Step 2 — define responsibility. Several obligations apply regardless of whether your city has a specific PG rule: building use, food, fire, tax and tenant records. Name the person who enters the record, the person who can approve a change, and the person who follows up when something is overdue. In a small PG those roles may belong to one person, but writing them down still matters. It stops a cook, caretaker, accountant and owner from each believing that somebody else handled the same exception.
Step 3 — test one real case end to end. "Nobody around here registers" is not a compliance position. It's a description of enforcement, which changes. Use one room, one resident or one billing cycle first. Follow the record from the first action to the final acknowledgement. Check the owner view, staff view and resident-facing result separately. A backend record or internal screen is not enough if the person expected to act cannot reach it.
Step 4 — keep an exception path. Decide what happens when information is late, a resident disputes the record, a staff member lacks permission, or the usual approver is absent. Record the reason for any manual correction. Do not quietly overwrite history simply to make a dashboard look tidy.
What the weekly review should cover
Fifteen focused minutes is enough when the team brings the same evidence each week. Review what was completed, what remains open, which cases needed manual intervention, and whether residents received the message or document they were meant to receive. The objective is not a perfect-looking count. It is to find repeated friction while it is still small enough to fix.
Review question Evidence to check Action if it fails
Did the process start with a complete record? The original entry, document or resident confirmation Correct the source and note who verified it
Did the right person act? User, timestamp and permission trail where available Clarify responsibility or access before the next cycle
Did the resident receive a clear outcome? Receipt, message, portal view or signed acknowledgement Send the missing confirmation and repair the template
Did an exception repeat? Open cases and manual corrections from the week Change the process; do not keep relying on memory
For Why the category is murky, ask whether staff explain the process consistently. For What applies almost everywhere, compare the operating record with what the resident experienced. For The building-use question is the serious one, look for cases handled outside the agreed path. These checks do not assume an automated report, alert or capability that the article has not established.
A safe rollout checklist
Confirm the property, room and resident scope before changing any record.
Check that only the intended role can create, approve, reverse or view the relevant information.
Run a real test with the people who perform the work, not only an administrator.
Keep the previous record available until the new result has been checked.
Tell residents what changes, what does not, and where they can raise a dispute.
Review the first week and document every manual workaround.
This checklist protects both sides. Residents get a process they can understand and question. Owners get a record that can be checked later instead of an argument reconstructed from memory. It also respects the boundary between guidance and capability: use only screens, permissions and resident surfaces actually reachable in your Hotel/Hospitality tenant.
One more question operators ask
Should we move every existing case into the new process at once?
No. Start with a controlled group or the next clean cycle, reconcile the result, and then expand. A staged rollout is slower for a few days and far safer than correcting every resident record after a rushed migration.
Where we're honest about the limits of this post
This deliberately names no specific city's current requirements, quotes no fees, and states no thresholds. PG regulation has changed repeatedly in several Indian cities, sometimes been challenged in court, and sometimes been announced and then not enforced. Any specific claim here would be unreliable and potentially harmful.
What to do instead: consult a local lawyer or consultant who has registered a PG in your municipality, in the last year. That specificity is the whole value — they'll know what's currently required, what's currently enforced, and which department is currently slow.
FAQ
I'm running two rooms in my own house — does any of this apply?
Possibly less, and possibly not none. Scale often affects which rules apply, but "small" is rarely a complete exemption. Confirm locally.
My landlord doesn't know I'm running a PG here.
That's a serious exposure independent of licensing — most residential leases prohibit it, and you risk both eviction and having no legal standing with your own tenants.
What if my city has no PG-specific rule?
The general obligations above still apply. The absence of a specific PG regulation is not the absence of regulation.
The bottom line
Should I rely on another PG owner's licence list?
No. Use it to frame questions, then confirm the current requirements for your own premises, use, capacity and local authority in writing.
PG owners get caught out not by breaking a clear rule but by assuming an unclear category means no obligations. Get local, current advice once — it's cheaper than the version where you find out through an inspection.
See how to start a PG, rent agreements, or pricing.
Keep every record straight from day one. Start free →
Comments