“Who is responsible for our CCTV?” sounds like one question. In practice it is at least three, and conflating them is where societies get into trouble - not because the answer is complicated, but because nobody separated the parts before asking.
Three different questions hiding inside one
There is the operational question: who decides where cameras go, who approves the budget, who signs off on the vendor. There is the custodial question: who actually holds the footage, controls the recorder login, and handles an access request. And there is the legal question: what does your specific state's co-operative societies act, and your society's own registered bylaws, actually say about liability if something goes wrong. The first two are governance questions we can help you structure. The third is a legal question specific to your society's registration and bylaws, and it needs your society's advocate, not a security installer, to answer definitively.
Who typically holds this in a co-operative structure
In most registered co-operative housing societies, the managing committee - collectively, not one individual - holds operational responsibility for common-area systems, CCTV included, in the same way it holds responsibility for the lift, the water pump, or the boundary wall. Day-to-day custodial responsibility is usually delegated to a named office-bearer, commonly the secretary, sometimes with a second committee member as backup. This is a structural default we see across the societies we work with, not a legal citation - your society's own bylaws are the actual authority on how your committee has structured this.
What the committee is actually accountable for day to day
- Deciding and documenting camera positions, ideally with resident input where placement is contested.
- Controlling who can view footage, and keeping a written record of any export or disclosure.
- Maintaining the system, whether directly or through an AMC, so footage is actually there when it is needed.
- Responding to resident concerns about a specific camera's placement or an access request, rather than treating either as an inconvenience.
None of this requires legal training. It requires the committee treating the system as an asset it manages, with the same seriousness as the society's accounts.
Where this stops being governance and becomes law
Questions like “can we be held liable if footage is misused,” “what happens if we are asked to hand footage to police,” or “can a resident sue the committee over a camera’s placement” are genuine legal questions with answers that depend on your state's co-operative societies act, your society's specific bylaws, and the facts of the situation. We are not qualified to answer these, and any installer who claims to be should be treated with caution. This is exactly the kind of question worth a short, focused consultation with your society's advocate - often cheaper and faster than the uncertainty of not asking.
Making responsibility explicit in writing
Whatever your committee decides operationally, write it down: who holds the recorder credentials, who approves footage access, who is the named point of contact if something goes wrong. This single document - reviewed at each committee handover - is what turns “the committee is responsible” from a vague assumption into something the next committee can actually pick up and continue.
Common questions
Should our society have a written CCTV policy?
It is a sensible governance practice, yes - a short document covering who can view footage, how camera positions are decided, and who is the named point of contact. We can help you structure the operational content of a policy like this. Whether your specific bylaws require one, or what it must legally contain, is a question for your society’s advocate.
Can the committee delegate footage access to the security guard?
Operationally, some societies do give the guard on-duty live-view access while restricting export and playback to a committee member. Whether this is advisable depends on how much you trust the arrangement and how it is documented - we can help structure the access levels on the system itself, but the policy decision is the committee’s to make.
What happens if a committee member who held the login leaves?
This is exactly the gap a written handover document closes - the account should be reset and reassigned to the incoming office-bearer immediately, not left active under a former committee member’s name. See our guide on handover checklists for the full process.