How Do I Write a CCTV Policy for My Building Staff?

A useful CCTV policy is more than a notice saying that cameras are operating. It tells staff why each camera is there, who may view or export footage, how long recordings are kept, and what to do when someone asks for a copy. Without clear rules, cameras can drift from a specific security purpose into casual monitoring, and recordings can be shared or retained longer than necessary.

This guide is for building owners, managers, facilities teams and staff in residential, commercial and mixed-use properties in the UK. It offers a practical structure for a written CCTV policy. It is not legal advice: check the current requirements that apply to your organisation, including data protection law and guidance from the Information Commissioner’s Office (ICO), and take advice where needed.

Start with the purpose, not the equipment

Before writing the policy, ask: What security question does this camera answer? If the answer is vague—“it might be useful” or “everyone else has cameras”—pause before installing or keeping it. Identify a specific, legitimate need, such as investigating unauthorised entry, protecting a particular access point, or reviewing a reported incident in a garage.

Then consider whether CCTV is necessary and proportionate. Could improved lighting, a controlled entry system, staff procedures or a mirror address the problem with less intrusion? Record the decision and the reason. For higher-risk or extensive monitoring, assess whether a data protection impact assessment is needed.

Data minimisation should guide every choice: collect only the footage needed for the stated purpose, limit the area captured, restrict access, and delete recordings when they are no longer required. A camera is not a general-purpose observation tool.

Set out who owns and governs CCTV decisions

The policy should name the organisation responsible for the system and the people authorised to make decisions about it. Depending on the building, responsibility may sit with a property company, landlord, management company, employer or another organisation. Do not assume that the installer, concierge or security contractor is automatically the decision-maker.

For shared buildings, clarify how decisions are approved. A board or management committee may set the overall approach, while a designated manager administers the system. The policy should explain who can approve new cameras, changes to their view, new uses of footage, routine access and disclosures. Involve relevant stakeholders where appropriate, but avoid giving every stakeholder unrestricted access to recordings.

Role Typical responsibility Responsible organisation Sets the purpose, ensures lawful and proportionate use, and oversees compliance. System administrator Manages accounts, permissions, maintenance and secure deletion. Authorised viewer Views footage only for an approved purpose and records the access. Contractor or security provider Provides only the services and access authorised by contract and policy.

Assign a named role—not just an individual—so the process still works when someone is on leave or leaves the organisation. Review access when staff change roles, and remove accounts promptly when access is no longer needed.

Write camera access rules staff can follow

Camera access rules should be specific enough to prevent casual browsing. State who may view live feeds, who may review recorded footage, and who may export or disclose it. Keep permissions to the minimum needed for each job. A concierge who watches a live entrance feed may not need permission to download recordings from every camera.

Make clear that staff must not view footage out of curiosity, to keep tabs on colleagues or residents, or to settle personal disagreements. Access should be tied to a recorded reason—for example, a reported incident, an authorised maintenance check, or a documented request handled under the organisation’s process. If an urgent safety issue requires immediate review, staff should record the reason as soon as practicable afterwards.

Use individual accounts rather than shared logins. Protect the system with strong authentication, keep access logs, and review those logs periodically. Do not point screens towards public areas or leave a live feed visible to people who are not authorised. Staff should not use personal phones to photograph monitors or make their own copies.

Include a clear export rule

Exporting footage creates a copy that can be harder to control than the recording in the CCTV system. The policy should identify who may authorise an export, who may carry it out, and what safeguards apply. Use a secure, approved method; encrypt or password-protect files where appropriate; and share access details separately. Do not email raw clips around or place them in a broadly accessible shared folder.

Ask two practical questions every time a clip is exported: Where does the exported clip end up, and who can open it? Record the destination, recipient, purpose, export date, authoriser and any deletion or return date. Make sure the recipient understands that the clip must not be copied, forwarded or used for another purpose without permission.

Control camera placement and field of view

List each camera, its location and its approved purpose. A camera should capture only what is reasonably needed for that purpose. Adjust its angle, zoom, privacy mask and resolution to exclude areas that do not need to be monitored. This is especially important around homes, changing areas, staff break spaces, neighbouring property and places where people may expect greater privacy.

For a building with a lobby, lift, mailroom and garage, do not assume that one broad view is appropriate everywhere. A camera covering a lobby entrance may not need to capture residents’ conversations or the interior of a reception workspace. A mailroom camera may be justified for a specific parcel-security problem, but it should not be aimed at screens legal hold security footage or documents. In a garage, consider whether the view can focus on vehicle access and circulation routes without unnecessarily recording neighbouring spaces or private areas.

Document any privacy masks or restricted zones and check them after maintenance, repositioning or software changes. Keep a simple camera register that includes the camera ID, location, purpose, field of view, authorised users, retention setting, and last review date. Reassess a camera if the risk changes or the original purpose no longer applies.

Set retention periods and routine deletion

There is no single retention period that is right for every building. Set a period based on the purpose, the time normally needed to discover and report an incident, and the organisation’s documented assessment. Keep routine footage only for as long as it is genuinely needed. Do not retain it indefinitely “just in case”.

Explain how automatic overwriting or deletion works, who checks that it is operating, and how exceptions are handled. Routine footage should be deleted on schedule. If a particular clip is needed for an incident, complaint or legal process, isolate only the relevant material, restrict access, record the reason for keeping it and set a review or deletion date. Do not preserve an entire system’s recordings when a short segment is enough.

Build a routine deletion check into the operating schedule. Confirm that the retention setting has not been changed, that exports are not being kept in untracked locations, and that expired incident copies are deleted securely. A retention table makes the rule easy to apply:

Footage type Retention approach Review or deletion action Routine recordings Keep for the approved, documented period only. Automatically overwrite or securely delete; periodically verify the setting. Incident clip Keep only the relevant section for the documented case. Restrict access and review the need to retain it at set intervals. Exported copy Store in an approved secure location, not personal devices or open folders. Record a deletion or return date and confirm completion.

Explain the footage disclosure process

A footage disclosure process prevents staff from making informal promises or releasing recordings without checking the request. The policy should tell staff where to send requests, who assesses them, what information to capture, and how the response is recorded. Requests may come from a person seeking their own personal information, a police officer, an insurer, a resident, an employee or a third party. These requests may require different checks and responses.

Staff should not decide on the spot to send a clip. Direct the request to the designated privacy or management contact. Record the requester’s details, the date and time, the location and approximate time of the footage, the purpose stated, and the action taken. Verify identity and authority where appropriate. Assess what can lawfully be provided, whether other people appear in the footage, and whether redaction or another response is appropriate. Follow the relevant legal deadlines and procedures.

Keep a disclosure log, including requests that are refused or cannot be fulfilled. Record what was disclosed, to whom, when, by whom, the approval basis, the delivery method and any conditions on use. Do not disclose footage merely because someone is a resident, board member, employee or police officer; check the applicable process and authority first.

Check more than faces and number plates

When preparing footage for disclosure, review the full clip and the surrounding frames. Redaction may need to cover more than faces and vehicle registration plates. Check for:

• Children, visitors, delivery workers and other identifiable people in the background.
• Access codes, keypads, pass cards, computer screens or paperwork visible in the scene.
• Unit numbers, name labels, post, parcel details or other identifying information.
• Audio, if the system records it, including conversations unrelated to the request.
• Reflections, monitor previews, timestamps or camera views that reveal sensitive information.

Use a suitable redaction method and verify that the original image cannot simply be recovered from the exported file. Keep an untouched original securely where required, and record which version was disclosed.

Train staff and keep the policy usable

A policy works only if staff know what to do. Give relevant staff a short induction and refresher training covering approved on-premise video redaction purposes, access rules, incident handling, disclosure requests, exports and deletion. Include a simple instruction: when in doubt, do not share or promise footage; refer the matter to the named contact.

Keep an incident and access record, and review the policy at least annually and after a significant incident, system change, camera relocation or change in the organisation’s responsibilities. Check that the camera register matches the live system and that former staff accounts have been removed.

Do not leave prices out of procurement information

A CCTV policy is not a price list, and staff should not make up costs that are missing from a scraped article, supplier page or old proposal. However, if your guidance recommends buying cameras, software, storage, installation or redaction services, state the relevant price, currency, date and what the figure includes—or clearly say that a quote is required. Note whether recurring charges, maintenance, tax or storage are excluded. Prices change, so link to a current supplier source and verify it before publication.

Keep commercial information separate from the policy’s operational rules. The policy should explain who approves spending and procurement, while a current, dated cost schedule can support budget decisions. This avoids misleading readers with missing or stale prices without turning a staff policy into an advertisement.

Use this checklist before issuing the policy

1. Have we stated a specific purpose for every camera and considered less intrusive alternatives?
2. Is the responsible organisation named, with clear approval and oversight roles?
3. Are camera access rules based on job need, individual accounts and logged access?
4. Are camera positions and fields of view limited to the approved purpose?
5. Is there a documented retention period, routine deletion and a controlled exception process?
6. Does the footage disclosure process cover requests, approvals, redaction, secure delivery and logging?
7. Do we know where exported clips are stored, who can open them and when they will be deleted?
8. Have staff been trained, and is there a review date for the policy and camera register?

A strong written CCTV policy makes surveillance more accountable and less ad hoc. It connects each camera to a defined need, limits the footage collected, gives staff clear access and disclosure rules, and ensures recordings do not linger without a reason. Keep it practical, review it regularly and make sure every staff member knows whom to contact before viewing, exporting or sharing footage.

Share on Facebook  |  Share on X (Twitter)