Is It OK to Install Cameras “Just in Case” Something Happens Later?

It is a familiar suggestion at a residents’ meeting: “Let’s put up a camera now, just in case something happens later.” It sounds prudent, particularly after a theft, a garage door is damaged or residents report feeling unsafe. But a camera is not a neutral precaution. It records people going about their daily lives, and once footage exists, someone has to control access, storage, disclosure and deletion.

For a UK block of flats or mixed-use building, the better starting point is not “Where could we put a camera?” It is: What security question does this camera answer? If there is no clear, specific answer, the installation may amount to overbroad surveillance rather than a proportionate security measure.

This guide explains how to decide whether CCTV is justified, who should make that decision, how to limit what a camera captures and how to manage footage responsibly. It also covers costs: if you are comparing proposals or reading a scraped article that lists no prices, there are practical ways to assess value without relying on a made-up headline figure.

Why “just in case” is not a purpose

Good security planning starts with a defined problem. For example, there may be repeated parcel thefts at a particular entrance, vandalism in a specific garage bay, or a recurring safety incident near a controlled access point. Each concern can be investigated and, if CCTV is appropriate, linked to a limited recording area.

“Something might happen” is different. It does not explain what risk the system is meant to address, whether a camera is likely to help, or what amount of recording is necessary. Without those answers, it is difficult to justify the intrusion on residents, workers and visitors—or to show that the installation is being managed responsibly.

The data minimization principle means collecting only the personal information needed for a stated purpose. Applied to CCTV, that means limiting the number of cameras, their view, the detail they record and the time footage is kept. It also means considering less intrusive measures first, such as repairing a faulty lock, improving lighting, reviewing access control or changing parcel procedures.

Set a clear purpose before choosing equipment

Write down the specific security concern and the outcome you expect CCTV to support. A camera may help identify what happened in a defined area, but it will not necessarily prevent an incident or identify a person clearly. Test the proposal against the real conditions: lighting, camera angle, image quality, obstructions and how quickly footage could be reviewed.

A short assessment can help the building’s decision-makers compare CCTV with other options. Record the concern, the evidence for it, possible alternatives, the proposed location, who would have access to footage and when the arrangement will be reviewed. If the risk is uncertain, a trial or time-limited installation may be more appropriate than a permanent system.

Question What a useful answer looks like What problem are we addressing? A defined, evidenced concern in a particular place—not general curiosity or hypothetical future events. Why is CCTV needed? Other reasonable measures have been considered and CCTV is likely to help with the stated purpose. What will the camera capture? The smallest practical field of view that covers the relevant area. When will the footage be deleted? A documented retention period with routine deletion and a controlled exception for specific incidents.

Purpose based camera placement and field of view

Purpose based camera placement means deciding on the purpose first and positioning equipment to serve it—not installing cameras at every entrance or covering as much space as possible because the technology allows it. The camera should record the area relevant to the identified concern and avoid capturing unrelated spaces wherever reasonably possible.

In practice, this may mean directing a camera towards a parcel shelf rather than across a whole lobby, or covering a garage entry point without recording every parking space. Check whether the lens also captures residents’ doors, neighbouring windows, a public pavement, a staff break area or a space where people might reasonably expect greater privacy. The right adjustment could be a narrower lens, a changed angle, privacy masking or a different location.

Checklist: reduce unnecessary capture

Map the proposed field of view before installation and check it on site.
Exclude private windows, residential door interiors and unrelated neighbouring areas where possible.
Limit audio recording; do not enable it by default.
Consider whether high-resolution, zoom or continuous recording is actually needed.
Use privacy masking where unavoidable areas should not be visible.
Review the image at different times of day, including in low light.
Recheck the field of view after maintenance, replacement or a change to the surrounding layout.

These are not just technical details. They are part of preventing overbroad surveillance. A camera that is well positioned but left with unrestricted access, indefinite storage or no deletion process is still a governance problem.

Who owns the decision?

In a shared building, CCTV decisions should not be left to an individual resident, concierge or contractor acting on their own. The appropriate decision-maker depends on the building’s arrangements and the purpose of the system. It may be the management company, landlord, residents’ management company or another organisation responsible for deciding why and how footage is used. That organisation will generally need to understand its data protection responsibilities and establish who is authorised to act for it.

The board or management body should approve the purpose, scope, funding and operating rules. The managing agent may coordinate the work, but should not assume that an informal instruction amounts to a complete governance process. Contractors should be given limited, documented access for their work and should not use recordings for unrelated purposes.

Agree in writing who is responsible for:

approving camera locations and changes to the system;
maintaining signs and providing privacy information;
authorising live viewing and recorded-footage searches;
responding to requests for footage or personal data;
managing disclosures to police, insurers or other third parties;
checking that retention and deletion rules are followed; and
reviewing whether each camera is still necessary.

UK data protection requirements can apply to CCTV that identifies, or could identify, people. Building operators should check current guidance from the Information Commissioner’s Office (ICO) and obtain appropriate advice for their circumstances. A written assessment of the need and impact of the system is a sensible step; a data protection impact assessment may be required where processing is likely to result in a high risk to people’s rights and freedoms.

Access, exports and disclosure: know where clips go

Restricting access is essential. Live views should not become background entertainment for staff or a way for residents to watch other people’s movements. Access should be given only to people with a defined operational role, and viewing or exporting footage should have a legitimate reason. Keep an access log that records who viewed or exported a clip, when, why and under whose authority.

Before any export, ask two questions: Where will the exported clip end up, and who can open it? Avoid emailing raw clips around or dropping them into a general shared folder. Use a controlled, secure transfer method, limit access to named recipients and set an expiry or deletion date. Record what was disclosed and why. If a request involves footage of several people, consider whether other individuals should be obscured before sharing, subject to the applicable rules and advice.

Redaction checklist

Faces and vehicle registration plates are not the only details to check. Depending on the scene, review whether a clip reveals:

door-entry keypads, access codes or security procedures;
resident names, flat numbers, delivery labels or post;
children, vulnerable people or bystanders unrelated to the request;
computer screens, documents or confidential staff activity;
precise movements that could expose someone to a safety risk; and
audio or other information that was not needed for the disclosure.

Do not promise a clip to a resident simply because they ask for it. Requests need to be handled through the building’s established process, with relevant identity checks, privacy considerations and applicable legal obligations taken into account.

Retention periods and routine deletion

There is no single retention period that is right for every building. The period should be set according to the stated purpose and the time reasonably needed to identify and review an incident. Keeping footage “in case it is useful one day” undermines data minimization. It also increases the amount of personal information at risk if an account or system is compromised.

Set a routine deletion schedule, configure the system to follow it where possible and check that deletion actually happens. Document the normal retention period and explain it in the building’s CCTV information. If an incident is reported, relevant footage may need to be preserved for a specific investigation or claim. That should be a targeted hold, not a reason to keep all recordings indefinitely; note who authorised the hold, its purpose and when it will be reviewed.

Choose and document a normal retention period that fits the security purpose.
Automate routine deletion and assign someone to verify the settings.
Preserve only relevant footage when a specific incident requires it.
Review each preserved clip and delete it when the reason for retaining it ends.

What about the cost?

If you have found a scraped article with no prices listed, treat that as a gap in the information—not a reason to assume cameras are either cheap or prohibitively expensive. Costs vary with the number and type of cameras, cabling, lighting, installation conditions, storage, maintenance, monitoring and any ongoing support. A single equipment price may not include the work needed to operate the system responsibly.

Ask suppliers to itemise the initial and recurring costs, explain what is included, and identify any charges for secure storage, software licences, repairs or exporting footage. Compare proposals against the same brief and the https://dlf-ne.org/cctv-clip-shows-a-badge-and-a-screen-what-needs-to-be-redacted/ same field-of-view requirements. Do not buy more cameras or storage capacity than the documented purpose requires. A cheaper installation that captures too much, cannot delete footage reliably or has weak access controls may create greater operational and privacy costs later.

Make the decision reviewable

A camera can be justified in a shared building, but “just in case” is not a sound basis for installing one. Tie each device to an evidenced concern, use purpose based camera role based cctv access placement, keep the field of view as narrow as practical, and make ownership of the decision and footage explicit. Set a retention period, delete routinely and control every export.

Finally, review the system after an agreed period and whenever the risk, building layout or technology changes. Ask whether the camera still answers the original security question—and whether a less intrusive measure could now do the job. If it no longer serves a clear purpose, switch it off or remove it.

Share this article: Facebook share | X (Twitter) share