Every PG owner has done this. A tenant who's been there three years gets ₹500 off. Someone's brother joins and skips the meal plan. A student gets a lower rate for the exam months. None of it is written down, all of it is remembered — until the person who remembers isn't there.
Quick answer (for the impatient)
Tenancy terms are recorded on the tenancy, not held in the owner's head or a diary.
Standing discounts apply automatically to that tenant's billing rather than being remembered each month.
Meal terms sit in the same place, so a tenant's food arrangement is part of their agreement.
The cost of an undocumented arrangement
It looks free. It isn't, and the bill arrives in three ways.
The monthly leak. Whoever generates bills has to remember every exception. Miss one and a tenant is overcharged, complains, and now trusts the billing less. Miss it the other way and you've quietly given away money.
The dispute. Six months later the tenant says the agreed rent was ₹8,000 and you remember ₹8,500. Neither of you is lying. Without a record there's no way to resolve it except by who argues harder.
The handover. The day a manager takes over, or the owner is away, every undocumented arrangement becomes an unpleasant surprise for a tenant who assumed it was settled.
What gets recorded
The arrangement lives on the tenancy itself, available from both the add-tenant and edit-tenant forms — so it's captured when the deal is made rather than reconstructed later. That covers the rent side (a standing discount that applies to their billing without anyone re-applying it monthly) and the meal side (what their food arrangement actually is, feeding into meal plan billing).
The design point worth noting: capturing this at the point of agreement is what makes it reliable. A field that has to be filled in later, separately, is a field that mostly stays empty.
Why this matters more in a PG than a hotel
A hotel guest stays three nights at a rate and leaves. A PG tenant stays fourteen months, on terms agreed once, that get billed fourteen times. An error in a hotel rate is a one-time annoyance. An error in a PG tenancy repeats monthly until someone notices, and by then it's a cumulative amount neither side wants to discuss.
The long relationship is also why the goodwill matters. A PG tenant who feels the billing is arbitrary starts looking at other PGs, and replacing them costs a vacancy plus acquisition.
A practical operating workflow for this PG
The useful way to apply The Deal You Made With That One Tenant Shouldn't Live in Your Memory 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. Tenancy terms are recorded on the tenancy , not held in the owner's head or a diary. 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. Standing discounts apply automatically to that tenant's billing rather than being remembered each month. 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. Meal terms sit in the same place , so a tenant's food arrangement is part of their agreement. 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 cost of an undocumented arrangement, ask whether staff explain the process consistently. For What gets recorded, compare the operating record with what the resident experienced. For Why this matters more in a PG than a hotel, 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 AXOIX is honest about its limits
Recording terms is not a rent agreement. This is operational record-keeping, not a legal document. Your actual rent agreement is separate and still necessary.
Nothing validates that a discount is sensible. If you record a term that loses money, it will be applied faithfully.
Terms apply going forward. Recording an arrangement today doesn't retroactively correct bills already raised — those need adjusting.
FAQ
Can I set a discount that expires?
Confirm the scope of date-bounded terms in your account before promising a tenant that a concession ends automatically.
Does the tenant see their agreed terms?
What's visible to the tenant depends on your portal setup. Transparency here reduces disputes rather than creating them.
What about a tenant who negotiates every few months?
Record each change with its effective date. The history is what protects both sides.
The bottom line
PG owners make individual deals because that's how the business works — it's a relationship business, not a rate card business. The mistake isn't making the deals. It's keeping them somewhere only one person can read.
See how rent and deposits are billed, how meal plans attach, or pricing.
Write the deal down once. Start free →
Comments