A managing committee in Mumbai that sets out to review its security arrangement usually discovers that there is no single written standard against which to measure it. Societies differ in the number of buildings, entrances, resident households and delivery volume, and agencies tend to quote a headcount and a monthly figure without describing the duties behind them. This document sets out the standard a Mumbai housing society can reasonably expect from a security provider: how posts are derived from the layout of the society, which duties each post performs, what is recorded and reported, and how a committee can benchmark its current provider against that standard.
The scope is residential: cooperative housing societies, apartment owners’ associations and gated communities. The same principles are developed for specific building types on the page for housing society security in Mumbai and in the practice description for gated communities and residential enclaves.
Why a written standard matters for a society
A housing society is a controlled-access environment in which the people who need to enter are numerous and mostly legitimate: residents, domestic staff, delivery personnel, contractors, tenants’ guests and service technicians. A security arrangement is therefore judged less by the number of people it turns away than by how reliably it identifies, records and routes those who are admitted. Three characteristics of residential premises shape the standard.
- Volume at the entrance. Daily movement is dominated by recurring visitors such as domestic workers, drivers and delivery riders. A procedure that takes several minutes per entry produces queues; a procedure that takes none produces gaps.
- Mixed accountability. The managing committee engages the provider, but the people who experience the service are individual residents. The standard has to be explicit enough that a committee can enforce it without depending on individual complaints.
- Personal data. Visitor registers, entry photographs and camera footage record the movements of identifiable people. Since the Digital Personal Data Protection Act, 2023 this is a governance matter as well as an operational one.
Deriving posts from the layout of the society
The number of guards is an output of the layout and the operating pattern, not an input. The correct sequence is to list every point at which a person or vehicle can enter or leave, every area that requires periodic inspection, and every time period in which each is active, and then to convert the result into posts and shifts. A post that must be occupied around the clock requires several individuals across a week once weekly offs and absences are covered; this is why a quotation that lists only guards on duty at a given moment understates the engagement.
Indicative post structure by society profile
The table below describes the posts that each common society profile is expected to carry. It does not prescribe headcount, which follows from the site survey, but it fixes the roles, so that a committee can see whether a quotation omits one.
| Society profile | Posts expected | Duties that must be assigned | Supervision and reporting |
|---|---|---|---|
| Single building, one entrance | Entrance post; a night patrol function that may be combined with the entrance post where the building is small | Visitor registration, delivery handling, vehicle entry, key and register handover at each shift change | Periodic supervisor visit; monthly summary to the committee |
| Multi-building society, single main gate | Main gate post; internal patrol post; basement or parking post where parking is below ground | All of the above, plus a separate record of contractor entry and a patrol route covering each building lobby and the parking level | Named site supervisor; weekly review of registers; monthly report with incident log |
| Multi-building society, separate vehicle and pedestrian gates, or a service entrance | One post per gate; roving patrol; a fixed post at the service entrance where domestic and contractor movement is separated | Segregated handling of resident vehicles, visitor vehicles, service staff and goods; a controlled exit route for materials leaving the premises | Supervisor present on a defined schedule; escalation contact for the committee; monthly report |
| Township or large enclave with amenities | Gate posts; patrol teams by zone; amenity posts at clubhouse and play areas; a control point for camera monitoring where cameras are installed | Zone patrol with checkpoints, amenity access control, event and move-in coordination, emergency contact procedure | Security officer or senior supervisor on site; structured weekly and monthly reporting; committee review meeting |
The duty list a post is expected to perform
Each duty below is a standing instruction that should appear in the written post orders. A provider that cannot show post orders covering these items has not specified the work.
Gate and visitor management
Every visitor is recorded at the gate with name, the flat visited, the purpose, the time in and the time out. The resident is contacted by intercom or an approved application before entry is permitted, and a visitor whom the resident does not confirm is not admitted. Recurring visitors, such as domestic workers, are enrolled once and carry an identity credential agreed with the committee. Exit times are recorded as carefully as entry times, because an entry without an exit is the quickest indicator of a procedural gap.
Delivery and parcel handling
Deliveries are the largest single category of entries in most societies. The standard position is that delivery personnel are held at the gate, the resident is informed, and either the resident collects or an agreed drop point is used. Where a society allows delivery personnel to proceed to the flat, the entry is registered and the exit is recorded. The post orders should state which of these applies and whether the society maintains a parcel room, in which case the guard’s role is to log receipt and hand-over, not to accept responsibility for contents.
Vehicle control and parking
Resident vehicles are identified by a sticker or equivalent agreed with the committee; visitor vehicles are recorded by registration number and directed to visitor parking. Unrecognised vehicles in resident parking, vehicles blocking fire access routes and vehicles left in basement parking beyond an agreed period are reported to the committee through the incident log. Guards direct and report; enforcement of parking rules through penalties remains a decision of the committee under its bye-laws.
Patrolling
Patrols follow a defined route with checkpoints, at set intervals, and are recorded. The route includes lobbies, staircases, terraces, the parking level, the generator and pump areas, meter rooms and the boundary. A patrol that is not recorded cannot be audited; a recording method that can be filled in afterwards, such as an unsigned notebook, offers little more assurance than no recording at all. Checkpoint tags, a patrol application or time-stamped entries countersigned by the supervisor provide a verifiable record.
Fire and emergency readiness
Guards are expected to know the location of fire extinguishers, hydrant points, assembly areas and the electrical isolation points, to be able to raise an alarm and call the appropriate emergency service, and to keep access routes clear. They are also expected to keep the emergency contact sheet current at each post. The committee remains responsible for the fire equipment and its maintenance; the guard’s duty is observation, reporting and initial response.
Role boundaries
A security guard at a housing society observes, records, controls access at the gate within the society’s rules and reports. Guards do not search residents, do not detain or arrest any person, and do not use force. Where a situation exceeds the guard’s role, the correct response is to alert the supervisor and the committee contact and to call the relevant emergency service. Post orders that state these boundaries protect both the residents and the society.
Personnel standards the committee can verify
A committee is entitled to ask for, and to retain on file, evidence of the following for the provider and for the individuals posted at the society.
- The provider’s licence under the Private Security Agencies (Regulation) Act, 2005, with its validity and the area it covers. The provider’s position is described on the compliance and licences page.
- Background verification of each guard before deployment, with the date of verification recorded.
- Records of induction and training, including fire safety and visitor-handling instruction.
- Statutory compliance for the guards: provident fund and insurance contributions and wages paid in line with the applicable minimum wage notification.
- A named supervisor and a documented escalation contact for the committee.
Minimum wages for security personnel in Mumbai are revised by the Maharashtra Security Guards Board in January and July each year, and the order in force for the relevant period governs the cost basis of a compliant contract. The security cost calculator allows the arithmetic to be run against current inputs, and this document deliberately does not quote a figure that would date.
Records, reporting and review
A standard that is not reported against cannot be enforced. The reporting set below is proportionate for a society of any size; larger societies add frequency and detail rather than new categories.
| Record or report | Content | Frequency | Recipient |
|---|---|---|---|
| Visitor and delivery register | Name, flat, purpose, time in, time out, vehicle number where applicable | Continuous; reviewed by the supervisor | Supervisor; available to the committee on request |
| Patrol record | Checkpoint, time, observations, signature or tag record | Each patrol; reviewed daily | Supervisor |
| Incident log | Date, time, location, description, action taken, persons informed | As events occur; summarised weekly | Committee contact |
| Attendance and shift handover record | Guard on each post, relief arrangements, handover of keys and registers | Daily | Supervisor; summarised monthly |
| Monthly service report | Posts staffed against posts contracted, incidents by category, open actions, recommendations | Monthly | Managing committee |
| Camera and data handling note | Who may view footage, how long it is retained, how access is logged | Agreed once; reviewed annually | Managing committee |
Personal data in a residential setting
The visitor register, entry photographs, intercom logs and camera footage together form a record of who entered the society and when. Under the Digital Personal Data Protection Act, 2023, a society that decides why and how this data is collected carries responsibility for it, even where the guard force is supplied by a contractor. The committee should therefore settle four points in writing with the provider.
- The purpose for which visitor and footage data is collected, and that it is not used for any other purpose.
- Who within the society and the provider may view footage and registers, and how each access is logged.
- How long registers and recordings are retained and how they are disposed of afterwards.
- Notice to residents and visitors, through signage at the gate and in the common areas, that cameras and registers are in use.
Camera placement is also a society matter. Reporting in the Mumbai press on cooperative housing disputes has noted that cameras directed at the entrance and common areas are regarded as ordinary security measures, whereas cameras pointed at a private residence require the consent of the society and the affected household. The committee, not the provider, should decide placement.
Benchmarking a current provider
The checklist below can be completed by a committee member over a week without special tools. Each item is answerable from the register, the post orders or a walk through the society. A provider that meets most items has a documented system; a provider that meets few relies on the individual conduct of whoever is on duty.
Benchmark checklist
- Written post orders exist for every post and are kept at the post.
- The number of guards actually present on a sampled day matches the number contracted for that post and shift.
- The visitor register shows an exit time for the large majority of entries made at least a few hours earlier.
- Recurring visitors are enrolled and carry an agreed credential.
- Deliveries are handled by a stated procedure that residents can describe.
- Patrol records show recorded checkpoints at the intervals set in the post orders, including night hours.
- An incident log exists and shows entries that were actioned, not only entries that were noted.
- The supervisor can be named, visits on a stated schedule, and signs the registers he or she reviews.
- A monthly report reaches the committee without being requested.
- The provider’s licence, guard verification records and statutory contribution records are on file with the society.
- Retention and access rules for registers and footage have been agreed in writing.
- The guards know the fire equipment locations and the emergency contacts at their post, which can be tested by asking.
Contract terms that support the standard
The standard holds only if the engagement documents carry it. A renewal or quotation should include the following.
- A schedule of posts, shifts and hours, with the duty list above attached as post orders and capable of revision by written agreement.
- The reporting set, with the monthly report named as a deliverable.
- The statutory compliance undertakings and the right of the society to inspect the supporting records.
- Replacement terms: the time within which an absent guard is replaced, and the right to request the removal of a guard with reasons recorded.
- Data handling terms consistent with the points listed in the previous section.
Reference points for societies in Mumbai
Cooperative housing societies in Maharashtra operate under the Maharashtra Co-operative Societies Act, 1960 and the model bye-laws, and the State government has circulated draft model bye-laws for 2026 that address, among other matters, digital communication, parking and structural safety. Committees should read the bye-laws in force for their society when specifying security rules, such as visitor policy and parking, because the provider implements the society’s rules and does not set them. Where a society wishes to compare its arrangement with arrangements in other parts of the city, the buyer’s guide to security services in Mumbai sets out the wider market, and the guide to security and housekeeping for housing societies covers how the two services are combined and supervised.
Next step
Bryte Guard Force is a PSARA-licensed, ex-servicemen-led security provider operating since 1996 and serving Mumbai, Navi Mumbai and Thane among its core cities. A committee that wishes to compare its present arrangement with the standard above can request a free site risk assessment through the quotation form; a written proposal follows within 48 hours, and the response time to enquiries is four business hours.
Frequently asked questions
How many guards does a Mumbai housing society need?
The number follows from the layout and operating pattern rather than from the number of flats. The count of entrances, the separation of vehicle, pedestrian and service movement, the presence of basement parking, and the hours in which each point is active determine the posts. Each post that must be covered around the clock requires several individuals across a week once weekly offs and absence cover are included, so a site survey should precede any headcount.
What should a society ask for when it reviews a security provider?
The provider’s licence under the Private Security Agencies (Regulation) Act, 2005, evidence of background verification for each guard, training and induction records, statutory contribution records, written post orders, and a named supervisor. These can be requested from the provider and retained on the society’s file, and they allow the committee to assess the arrangement without relying on individual impressions.
Are visitor registers and CCTV footage covered by data protection law?
Yes. Names, photographs, vehicle numbers and entry times are personal data, and the Digital Personal Data Protection Act, 2023 applies to their collection and handling. The society should record the purpose, restrict who may view the data, set a retention period, and display notice at the gate and in the common areas, and should settle these terms with the provider in writing.
Can a security guard stop or detain a person at the society gate?
A guard controls access at the gate according to the society’s rules, which includes declining to admit a visitor whom the resident has not confirmed. A guard does not arrest or detain anyone and does not use force. Where a situation exceeds the role, the guard informs the supervisor and the committee contact and calls the relevant emergency service.
How often should the managing committee receive a report from the security provider?
A monthly written report is the working minimum, covering posts staffed against posts contracted, incidents by category, open actions and recommendations. The committee should be able to see the visitor register and incident log on request, and larger societies commonly add a weekly summary.
Does the committee or the provider decide where cameras are placed?
The committee decides. Cameras at the entrance and in common areas are ordinary security measures, but placement that captures the interior of a private residence requires the consent of the society and the affected household. The provider can advise on coverage and operate the equipment within the rules the committee sets.