Security appears on the agenda of most managing committee meetings, and it usually appears as a complaint rather than as a plan. A parcel has gone missing, a stranger was seen on the eleventh floor, a guard was asleep at four in the morning, or a resident has objected to being telephoned about their own guest.
Treated individually, each of these is an incident to be settled. Treated together, they form a short and fairly consistent list of structural problems that nearly every residential project encounters. The list below is that set, ordered roughly by how often it reaches a committee, with the control that addresses each.
The purpose of setting them out this way is practical. A society that responds to complaints one at a time will keep responding to them. A society that identifies which of these twelve conditions applies to it can resolve several complaints with a single decision.
The twelve recurring problems
| # | The problem as it is reported | What is actually causing it | The control that resolves it |
|---|---|---|---|
| 1 | “Anyone can walk in” | No defined entry categories, so classification is left to the guard | A written entry standard, published to residents |
| 2 | Deliveries entering unchecked | No stated policy on door delivery, and no handover point | A committee decision on door delivery, plus a parcel handover area |
| 3 | Domestic staff unverified | Verification treated as the employing flat’s private matter | Society-issued cards held against a verification record |
| 4 | Parking disputes reaching the committee | The guard has no written authority, so refusal becomes personal | An allocation policy with a named escalation point |
| 5 | Loss during shifting | Move-in and move-out handled by a phone call | A permit, a materials list and a scheduled window |
| 6 | Renovation workers roaming | Contractor access granted without a worker list | A work permit naming workers, hours and areas |
| 7 | “The register was no use” | Entries recorded in bulk after the fact, exits never recorded | Entry-time recording and exit reconciliation |
| 8 | Guards inattentive at night | Unlit patrol routes and no check-call interval | Lighting audit, irregular rounds, logged check calls |
| 9 | A new guard every few weeks | Agency attrition, usually driven by pay and posting conditions | Continuity written into the contract and monitored |
| 10 | Theft of parcels, cycles, footwear | Common areas outside any patrol route | Patrol route covering lobbies, parking and stilt areas |
| 11 | Cameras “not working” when needed | No one owns verification or retention | A named person, a weekly check, a set retention period |
| 12 | Guards running personal errands | No stated boundary on what guard duty includes | A duty list that states what is excluded, agreed by the committee |
The remainder of this article takes the five that cause the most difficulty and sets out what the control looks like in practice.
Entry: the problem is definition, not vigilance
“Anyone can walk in” is rarely a complaint about a guard’s attentiveness. It is almost always a complaint about an undefined standard. If a society has not decided, in writing, which categories of person may enter, on whose authority, and with what record, then each guard applies their own judgement and each resident forms their own expectation. The gap between those is what residents experience as laxity.
The decision a committee has to make is narrow: list the categories of entrant, and for each, state the identification required, who authorises, and what is recorded. Once that exists, guard performance becomes measurable against something. Until it exists, it cannot be.
The single provision that changes the most is requiring resident authorisation before an unexpected visitor is admitted. It is also the provision residents most frequently object to, because it means a telephone call every time. A committee that introduces it without publishing it to residents places the guard in an argument they cannot win, and the provision quietly lapses within weeks.
Deliveries: the highest-volume security task in a modern society
E-commerce and food delivery have made this the most frequent interaction at any residential gate, and in most societies it is the least defined. The committee has three workable options, and the problem is usually that it has not chosen between them.
Gate handover. All deliveries are received at the gate and collected by the resident. Strongest control, least convenience, and it requires a staffed handover point and shelf space.
Door delivery with recorded entry. The delivery person is admitted after identification is sighted and the resident contacted, and the exit is recorded. Convenient, workable, and it depends entirely on the exit record being kept — without it the society does not know who is still inside.
Parcel room. Deliveries are deposited in a secured room and residents collect against a log. Best for high-volume projects and the only option that scales, but it requires space and an accountable custodian.
Whichever is chosen, two things must follow: it is published to residents, and the gate is equipped for it. A gate-handover policy without a shelf and a shaded waiting area will be abandoned by the guards within a fortnight, not from indiscipline but from impracticality.
Domestic staff: verification is a society function
Committees often treat the verification of domestic staff as a matter between the helper and the employing flat. This is understandable and it is a mistake, because the person is admitted to the common areas of the whole building on the strength of that arrangement.
A workable regime has three parts. The society holds a record for every person granted standing entry, consisting of photo identification, current address, the employing flat and a contact. A society-issued card is produced, carrying a number rather than personal details. Entry and exit timings are recorded daily against the card.
Two cautions. The society is now holding personal data about people who are not its members, so it should keep only what it needs, hold it securely, and define how long it keeps it after the person stops working there. And background verification should be arranged through a proper process — it is a service a licensed agency can organise — rather than by the committee collecting documents informally.
Guard turnover: the cost a society pays without seeing it
Attrition is usually read as the agency’s problem. It is in fact the society’s, because every replacement arrives knowing nothing about the site. They do not know which face belongs on the fourth floor, which vehicle is a resident’s, which corner of the parking is poorly lit, or which resident will escalate. That knowledge is the substance of site security, and it is rebuilt from zero with each new posting.
A committee can address this on three fronts. Make continuity an explicit term of the contract, with notice before any planned change. Ask for the monthly deployment list and compare it month to month, since this is the only way to see turnover rather than hear about it. And look at the conditions of the post itself — shelter, water, lighting and a reasonable duty pattern materially affect whether people stay.
It is also worth asking what the guards are being paid, and whether that is consistent with the rate the society is charged. A deployment priced below the statutory floor will produce turnover, and the society will experience it as a security problem rather than a pricing one. Our guide to security guard costs in Maharashtra sets out how to read a quotation on that basis.
Night cover: an engineering problem before it is a discipline one
A guard found inattentive at night is usually dealt with as a conduct matter. That is sometimes correct, and it is rarely the whole explanation. Night alertness is substantially determined by the conditions of the post, and three of those are within the society’s control rather than the agency’s.
Lighting. The first question for any society reporting weak night cover is what a patrol can actually see. Stilt parking, rear perimeters, service corridors and refuse areas are the places where unauthorised activity occurs and the places most commonly unlit. Where a route is dark, a round through it produces no information, and the guard reasonably concludes there is little point walking it. Correcting the lighting on those sections generally does more for night security than adding a guard.
Round design. A patrol at the top of every hour is a published timetable to anyone who observes the building for a week. Rounds should vary in order and timing while still being evidenced, which is what checkpoint scanning is for. The society should be able to see that the rounds happened, without the rounds being predictable.
Check calls. Between midnight and dawn there is no supervisor on site. A scheduled call at a defined interval, logged at both ends, is what establishes that the guard is present, alert and safe. Societies that report finding a guard asleep almost never have a check-call protocol; the absence of one means nobody knows the state of the site for seven hours at a stretch.
Cameras: the system nobody owns until it is needed
Few complaints are as common, or as avoidable, as discovering that footage is unavailable for the one incident it was wanted for. The recorder was full, the camera had been out for weeks, the retention was shorter than anyone assumed, or no one present knew how to export a clip.
This is an ownership problem. Cameras are installed as a project and then belong to nobody. Three provisions fix it, and none is expensive.
- A named person is accountable — a committee member or the manager — for the system working, not the vendor.
- A weekly check confirming every camera is recording and the retention period is being met, recorded in a short log. A fault found in a weekly check is an inconvenience; the same fault found during an incident is a loss.
- A written retention period and access rule. Footage is personal data, so the society should decide how long it is kept, who may view it, and record each request to do so. This is also what protects the committee if a resident later disputes how footage was used.
It is worth stating plainly that cameras do not replace presence. They record what happened; they do not intervene while it is happening. A society choosing between an additional camera and an additional patrol round should be clear about which of those two problems it is trying to solve.
Guard duty: stating what is excluded
The twelfth item on the list is the one committees are most reluctant to raise, and it undermines more of the others than any single factor. Guards are asked to water plants, carry shopping, hold keys for private deliveries, supervise a resident’s workmen, and fetch items from the market. Each request is small and refusing it is socially awkward.
The cumulative effect is that the post is unattended, the gate is unmanned at unpredictable moments, and the guard’s position in relation to residents becomes that of personal help rather than someone with authority to stop and ask questions. The twelve-point list above cannot be delivered from that position.
The remedy is a duty list that states explicitly what guard duty does not include, agreed by the committee and published to residents, so that a guard declining a request is applying a society rule rather than refusing a neighbour. This is a governance decision, not a security one, and it has to be made by the committee rather than left to the agency.
Where to begin
A committee working through this list should take the decisions in this order, because each makes the next easier.
- Define entry categories and the authorisation rule, and publish both to residents.
- Decide the delivery policy and provide what it requires at the gate.
- Establish the domestic staff record and issue cards.
- Agree the duty list, including what is excluded.
- Set the patrol route to cover the common areas where loss actually occurs.
- Name one person accountable for cameras, retention and the monthly register check.
None of these requires additional guards. They require decisions that only the committee can take, after which the security team has something definite to deliver against.
Bryte secures residential projects across Mumbai, Navi Mumbai, Thane and Pune, and provides the entry standard, duty list and patrol design as part of mobilisation rather than as an extra. Our gated communities and residential enclaves practice and residential security service describe the full scope, and the managing committee guide covers security and housekeeping together. Societies in the city can begin at housing society security in Mumbai, or request a site assessment for a written review of the current arrangement.
Frequently asked questions
What are the most common security problems in housing societies?
Undefined entry rules, unmanaged delivery volume, unverified domestic staff, parking disputes the guard has no authority to settle, loss during shifting, uncontrolled renovation access, registers that record entries but not exits, inattentive night cover, high guard turnover, theft from common areas, cameras that are not verified until footage is needed, and guards being used for personal errands.
Should a housing society verify domestic staff itself?
Yes. The person is admitted to common areas used by every resident, so the society should hold a record for anyone granted standing entry and issue a card against it. Verification should be arranged through a proper process, which a licensed agency can organise, rather than by the committee collecting documents informally. The society should also decide how long it keeps those records after the person stops working there.
How should a society handle online deliveries?
Choose one of three models and publish it: handover at the gate, door delivery with identification sighted and both entry and exit recorded, or a parcel room with a collection log. The choice matters less than making it and equipping the gate for it. A policy the gate cannot physically support will be abandoned within weeks.
Why do societies keep getting new security guards?
Agency attrition, which is usually driven by pay and by the conditions of the post. It matters because each replacement arrives without site knowledge, which is the substance of security. A committee can make continuity a contract term, ask for the monthly deployment list to see turnover rather than hear about it, and check that the rate being charged is consistent with lawful wages.
Can security guards be asked to do non-security work in a society?
They should not be. Errands and personal tasks leave the post unattended at unpredictable times and change the guard’s standing with residents, which makes it harder for them to stop and question anyone. The committee should agree a duty list that states what is excluded and publish it, so a guard declining is applying a society rule rather than refusing a neighbour.
How many security guards does a housing society need?
It follows from gates, towers, parking levels, entry volume at peak hours and whether night patrolling is required, rather than from the number of flats alone. The calculation should start from observed peak volumes at each gate. A site assessment produces a posting plan on that basis, which is also what allows a society to tell whether a quotation is over or under-manned.