A PG runs on two or three people: someone who cooks, someone who cleans, and often a warden or caretaker who lives on site. All three are usually engaged informally, paid in cash, and have no documentation at all. That works until it doesn't.
Quick answer (for the impatient)
Informal arrangements are still employment if that's what they are in substance.
The live-in warden is the highest-risk arrangement — on call at all hours, with no defined working time.
Records are what decide disputes, and the party without them loses regardless of who was right.
The live-in warden problem
This is the arrangement most PGs have and least examine. Someone lives on the premises, often rent-free or at reduced rent, and is effectively available whenever something happens — a tenant locked out at 1am, a water problem at 6am, a dispute at midnight.
The questions this raises, none of which most PG owners have answered: What are their actual working hours? Is on-call time working time? Is the accommodation part of their remuneration, and if so at what value? Is there any weekly rest?
None of that is a reason not to have a live-in warden — it's an extremely practical arrangement for a PG. It's a reason to define it, in writing, rather than leaving it as an open-ended availability that neither side has ever articulated.
Contractor or employee?
The distinction turns on substance, not on the label or on how they're paid. A cook who works fixed hours, in your kitchen, with your equipment, under your direction, exclusively for you, is likely an employee whatever the arrangement is called.
Where you genuinely use a contractor — an agency supplying cleaning staff, say — verify that they're actually meeting their own statutory obligations, because exposure can flow back to you as principal employer. Asking for evidence periodically, rather than at onboarding only, is the practical version of that diligence.
What to have on record for every person
An appointment letter stating role, wage, hours and any accommodation provided. Even one page changes your position substantially.
Identity and address verification — for staff as much as tenants. Staff have access to residents' rooms and belongings.
Attendance records, including who actually worked rather than who was scheduled.
Wage payment records. Cash payments with no acknowledgement are the single most common gap, and the hardest to defend.
Medical fitness for kitchen staff, which is an FSSAI requirement as well as a labour one.
Leave taken and owed.
The wage records point is worth stressing. In a dispute about unpaid wages, an owner who paid faithfully in cash for three years and has no acknowledgements is in a materially worse position than one with signed receipts — and the cost of collecting those receipts was nothing.
The safety dimension
Staff verification isn't only a labour matter. In a PG — particularly a girls' PG where safety is the core promise — the people with keys and access are a safety consideration that parents will reasonably ask about. Being able to say that staff are verified and documented is part of the same conversation as visitor logs and guardian details.
A practical operating workflow for this PG
The useful way to apply Your Cook, Your Warden, Your Cleaner: The Employment Question PGs Avoid 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. Informal arrangements are still employment if that's what they are in substance. 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. The live-in warden is the highest-risk arrangement — on call at all hours, with no defined working time. 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. Records are what decide disputes , and the party without them loses regardless of who was right. 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 The live-in warden problem, ask whether staff explain the process consistently. For Contractor or employee?, compare the operating record with what the resident experienced. For What to have on record for every person, 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
Labour law in India combines central and state legislation, with the labour codes' implementation status varying and Shops and Establishments rules differing substantially by state. Whether registrations apply to you depends on headcount, state and structure. No thresholds, rates or requirements are stated here. Engage a labour consultant familiar with your state.
FAQ
I have two staff — surely nothing applies at that size?
Some obligations attach at low headcount and some at higher. Basic documentation is worth having at any size purely as dispute protection.
Can I pay in cash?
Payment mode is a separate question from documentation. If you pay cash, get acknowledgements — that's the gap, not the cash itself.
Does free accommodation count as part of wages?
It may, with implications for how wages are computed. Raise it specifically rather than assuming it's outside the calculation.
The bottom line
PG staffing is informal because it's small, and small is exactly when a single dispute is most damaging. An appointment letter and a wage acknowledgement per person costs an afternoon and changes your position entirely.
See hiring for a PG, safety and compliance, or pricing.
Document the people who run it. Start free →
Comments