How to Write a Request Form for CCTV Footage for Residents and Insurers

A clear CCTV footage request form helps residents and insurers report incidents without turning a building’s cameras into an informal viewing service. It should collect enough information to locate relevant footage, verify who is asking and decide what can lawfully be disclosed—without encouraging broad or speculative searches.

The form is only one part of the process. Before using it, the building’s management team, landlord, managing agent or owners’ association should agree who controls the system, who reviews requests, how decisions are recorded and where any exported clip is stored. A simple reality check helps keep that process focused: What security question does this camera answer?

This guide explains what to include, what to avoid and how to make the process useful for both residents and insurers. It also addresses a frequent gap in online guidance: no prices listed. If the building charges for any service connected with a request, the form or accompanying guidance should state the applicable fees—or clearly say that no fee is charged.

Start with purpose, not a promise to provide footage

A request form should explain that submitting it does not guarantee access to a recording. Footage may contain images of other residents, staff, visitors or children. It may also be unavailable because the relevant camera did not cover the location, the recording has already been overwritten, or the requester does not have a right to receive a copy.

Ask for the purpose of the request in plain language. A resident might be reporting damage to a bicycle in a cycle store; an insurer might be investigating a claim involving a vehicle in the garage. The stated purpose helps the authorised reviewer decide whether the request is relevant and proportionate. It is not a reason to collect extra information that the reviewer does not need.

Distinguish between a request to preserve or review footage and a request for a copy. For example, a resident may want the building to check whether an incident was captured, while an insurer may ask for a copy to assess a claim. The form should let the requester choose the outcome they are seeking and should not imply that every review leads to disclosure.

Agree who owns the decision

Buildings can have several parties involved in CCTV operations: an owners’ association or freeholder, a managing agent, an onsite team and an external security provider. The form should name the organisation responsible for receiving requests and explain who makes the disclosure decision. A camera contractor may maintain equipment, but that does not automatically make it the right party to decide who sees footage.

Before the form goes live, document the decision-making arrangements. Clarify who may receive requests, who can view recordings, who approves exports, and who records the decision. Limit access to people with a defined operational need. Casual viewing—because someone is curious or knows a person in the footage—is not a valid reason to open a recording.

Form or process item What to make clear Responsible organisation Name the body or organisation that handles requests and explain how to contact it. Decision-maker Identify the role or team authorised to approve a review, preservation or disclosure. Access controls State that access is restricted to authorised personnel and logged. Fees List any applicable prices, explain when they may apply, or state that no fee is charged. Response expectations Give a realistic acknowledgement and update timeframe, without guaranteeing footage exists.

Governance also means being able to explain why cameras are installed and what each one is intended to do. A camera should not be added “just in case”. Its purpose, position and field of view should be considered before installation, and checked again if the building layout or use changes.

Collect the details needed to find the recording

The most useful request forms make it easy to search for a specific event. A vague description such as “last weekend in the car park” may cover many hours and several camera views. Ask for a narrow date, time and location, while allowing the requester to explain when the time is approximate.

Essential incident details

Incident date: Ask for the date, or a short date range if it is genuinely uncertain.
Incident time: Request the approximate start time and, where possible, an end time. Ask the requester to note whether the time comes from a phone, vehicle clock or another source that may be inaccurate.
Incident location: Use building-specific options such as entrance, lift, lobby, mailroom, cycle store, garage level or loading area. Include a field for a more precise description.
What happened: Request a brief factual description. Avoid asking for a full account of unrelated personal circumstances.
People or property involved: Ask for details that can help identify the relevant event, but only where needed.
Purpose of request: For example, incident review, insurance claim or another specified purpose.

Make it possible to give “unknown” or “not sure” as an answer. A form that forces someone to guess an exact time can create misleading information. If the request covers a long period or a large area, ask the requester to narrow it down or explain why a wider search is necessary.

Verify identity and authority proportionately

Contact and identity verification helps the responsible organisation confirm who is asking and respond securely. It should not become an excuse to collect excessive personal information. Ask for the requester’s name, preferred contact details and relationship to the incident—for example, resident, vehicle owner, insurer or authorised representative.

For a resident, explain what reasonable verification is needed and how it will be handled. For an insurer or other representative, request relevant authority to act for the person concerned, such as an appropriate signed authorisation or claim reference where suitable. Do not ask for complete identity documents by default if a less intrusive check will do.

Include a secure way to submit supporting documents. Avoid inviting people to send sensitive identity material to a general inbox without explaining how it will be protected. The form should say which details are required, who will see them and how long they will be retained.

Build data minimisation into the form

Data minimisation means asking for only what is needed to assess and process the request. A request form is not an incident diary, a general complaints form or a route to browse building recordings. Keep CCTV request fields separate from unrelated matters, and do not use a single open text box that encourages people to include unnecessary personal details.

Explain that the reviewer will search only the relevant cameras and time window, where possible. This reflects a broader system design principle: camera placement and field of view should be controlled so cameras capture the intended area, not neighbouring homes, private spaces or more of the street than is necessary. If the field of view is wider than the stated purpose requires, adjust the camera or use suitable privacy masking rather than relying on request forms to solve the problem.

What not to ask for by default

Full identity documents where a lighter verification step is sufficient.
Information about unrelated people or events.
Open-ended permission to search all cameras or all dates.
Details that have no bearing on the request or decision.
Copies of sensitive claim records when a limited confirmation would be enough.

Explain retention and routine deletion

Recording systems usually retain footage for a set period and then overwrite or delete it. The form should tell requesters the building’s standard retention period, how quickly they should submit a request and what happens when footage is no longer available. Do not publish a retention period the building does not actually follow.

Where a request arrives before routine deletion, an authorised person may need to consider whether a specific clip should be preserved while the request is assessed. Preservation should be limited to relevant footage, authorised, documented and subject to a defined review date. A request should not silently place an entire camera system or broad time range on indefinite hold.

Routine deletion is part of good governance, not an administrative afterthought. Set a schedule, assign responsibility for checking it and record exceptions. When a preserved clip is no longer needed, delete it securely and record that action in line with the building’s policy.

Set out the review, disclosure and export process

Tell requesters what may happen after submission: acknowledgement, verification, review by an authorised person, a decision and a secure response. Give a realistic timeframe for an initial update and explain that a complete response may take longer if the request needs clarification or footage must be reviewed for other people’s privacy.

Where disclosure is approved, consider whether the requester needs the full recording, a limited extract, a still image or another form of response. Protect third parties where appropriate. Redaction is not just about faces and number plates. A reviewer’s checklist should also consider:

Reflections in glass, mirrors or polished surfaces.
Names, access codes, badges or information visible on screens and paperwork.
Children and people in sensitive or vulnerable situations.
Audio, if the system records it, and whether it is necessary to include.
Other homes, private areas, entrances or locations that could reveal someone’s routine.
Metadata or file details that may expose more information than the clip itself.

Keep an audit record of the request, identity checks, search terms, cameras and time window reviewed, decision, any redactions, recipient and deletion or retention action. Record enough to explain the decision without duplicating the footage or adding unnecessary personal information to the log.

Ask the export question before approving a copy

When footage is exported, ask: Where will the clip end up, and who can open it? A secure export process should identify the intended recipient, use an appropriate protected delivery method and avoid raw clips being emailed casually or placed in a shared folder with no access limits or cctv signage requirements deletion date.

Tell the recipient how the clip should be handled, who may access it and when it should be deleted, subject to any applicable obligations to preserve it. Keep a record of the export and do not give access credentials to people who have no need to view the clip.

Be transparent about prices

A common flaw in scraped or republished CCTV guidance is no prices listed. If a building charges for handling a request, producing a copy, providing secure media or another service, state the price and explain what it covers before the requester submits the form. If charges depend on the scope or format, explain how the amount will be calculated and when the requester will be told.

If no fee is charged, say so explicitly. Do not invent a standard price or imply that a fee applies when it does not. Any fee policy should be checked against the organisation’s legal obligations and approved by the responsible decision-maker. A clear statement prevents surprises and helps residents and insurers decide whether they are asking for a review, a copy or both.

Suggested request form structure

Requester details: Name, contact details, relationship to the incident and preferred secure response method.
Authority: Any relevant confirmation that the requester is entitled to act for the person concerned.
Purpose of request: A concise explanation of why footage is being requested.
Incident details: Date, approximate time, location and short factual description.
Requested outcome: Request a review, preservation consideration, copy or other specified response.
Supporting information: Optional details that help locate the event, with instructions not to include unrelated sensitive data.
Fees and timing: Applicable prices, or a clear no-fee statement, plus realistic response expectations.
Privacy notice: Who handles the request, how information is used, who may access it and how long records are kept.
Declaration: A confirmation that the details are accurate and the requester understands that footage may not be available or disclosable.

Share the form where residents can find it

Publish the form alongside a short explanation of the building’s CCTV request process, retention period, fees and contact route. Make it available in an accessible format and provide a way to ask for help completing it. Do not ask residents to post incident details or footage publicly.

If sharing this guidance on social media, use the relevant platform’s sharing tools:

Facebook share
X (Twitter) share

Replace YOUR-ARTICLE-URL with the published article address before adding these links to a live page.

Final checklist

Does the form ask for a clear purpose, incident date, time and location?
Are contact and identity checks proportionate to the request?
Is it clear who governs the CCTV system and who decides on disclosure?
Are camera placement and field of view limited to the intended security purpose?
Does the form explain retention, routine deletion and possible preservation?
Are fees listed—or is it clear that no fee is charged?
Are exports logged, securely delivered and protected from casual access?
Does the redaction checklist cover more than faces and number plates?

A well-written form makes CCTV requests narrower, more consistent and easier to review. It protects the privacy of people captured by building cameras while giving residents and insurers a clear route to raise a genuine incident. Most importantly, it keeps the process tied to a defined purpose rather than allowing footage to become something people can browse out of curiosity.