Camera Field-of-View Schedule for India (2026): Proving Each Camera Sees What It Should

A camera list tells you where cameras are. A camera field-of-view schedule tells you what each one is actually meant to see - and to what quality. It is the document that pins down coverage intent: for every camera, the scene it must cover, how much of the frame the target should fill, and therefore whether the design will hold up when something happens. Without it, "we have thirty cameras" is a count, not a coverage guarantee.

This is a companion to the plain camera list in the camera schedule and the area-by-area picture in the CCTV coverage schedule. Where those record hardware and zones, the field-of-view schedule records purpose and proof - and it is written at design, then verified line by line at commissioning. It sits inside the wider professional security resources toolkit.

Scope and how to read this. This is a ready-to-adapt professional template, not authoritative, contractual or legal wording. The exact lens, sensor, mounting height and pixel density for any purpose level come from your project, the site survey, the equipment you specify and the manufacturer data - engineer each camera to its purpose. Get professional review for the contract documents. Where a real figure belongs, this page says "specify" or "engineer to purpose" rather than inventing a number.

What the schedule is, and where it sits

The field-of-view schedule is produced by the security consultant, designer or PMC during design, alongside the camera layout. It is issued for procurement so the installer prices the right lenses and mounts, and it becomes the acceptance yardstick at commissioning: each camera is walked, its live view compared to the intent, and only then is the row marked verified. It is handed over as part of the as-built pack.

Think of it as the bridge between a marketing promise ("full coverage") and an engineering fact ("this camera, at this scene, achieves this purpose"). It makes coverage auditable.

The concept: purpose drives the view

Every camera in the schedule is defined by five linked decisions. Get the first right and the rest follow.

• Scene / target. What must this camera cover - a gate line, a lobby, a cash counter, a car park aisle? Name it plainly.
• Purpose level. What must the footage let you do? The widely used ladder runs monitor, detect, recognise, identify. Monitor: is anyone in the area at all. Detect: a person is present and where they are moving. Recognise: this is someone I already know. Identify: establish who a stranger is to an evidential standard. The key idea, in words: the higher the purpose, the more of the frame the target must fill - more pixels on target - which means a tighter, closer view.
• Intended view. Wide, mid or tight, following directly from the purpose. Identify needs the closest, tightest view of the lot; monitor tolerates the widest.
• Coverage width and distance intent. How wide a scene at roughly what range - a doorway a few metres away, or an approach path further out. State the intent; the exact distance for a purpose is engineered, not guessed.
• Lens / angle and blind spots. The angle of view needed to hold the scene, plus any overlap with a neighbour (deliberate, for handover between cameras) and any blind spot (recorded and accepted, or closed with another camera).

Do not chase one camera doing everything. A single wide camera cannot both survey a whole yard and identify a face at the gate - those are different purpose levels needing different views. Split the job: a wide "detect" camera for the scene, a tight "identify" camera on the choke point. The schedule makes that split explicit.

Worked example: a filled field-of-view schedule

Example only - adapt to your project. Values are generic and illustrative. Lenses, angles, distances and pixel densities are shown as "specify" or "engineer to purpose" - never copy them as facts.

Blank, copy-ready template

Copy this into your sheet or drawing register. One row per camera; carry the same camera refs used in your camera list and coverage schedule so the documents cross-check.

Field guide: how to fill each column well

• Camera ref. Reuse the reference from the camera schedule exactly. One camera, one ref, across every document.
• Scene / target. Name the thing that must be captured, not just the room. "People entering at the gate" is stronger than "gate area" because it forces a purpose decision.
• Purpose level. Pick the highest level the scene genuinely needs, and no higher - identify everywhere is expensive and rarely justified. Choke points where a face must be established get identify; open areas get detect. The coverage planning guide helps decide.
• Intended view. Wide, mid or tight, matched to the purpose. Remember the rule: identify needs the closest view. If the scene is wide and the purpose is identify, that is a signal you need two cameras, not one.
• Distance intent. State the range you are designing for. The exact pixel density that achieves a purpose at that range is engineered from the equipment - specify it with the manufacturer data, do not assume.
• Lens / angle note. Record the intent ("narrow angle to fill frame with a face"); the final focal length and sensor are selected during procurement to meet it.
• Lighting / IR need. A purpose is only met if the scene is lit. Identify at a gate at night needs face-quality light or IR; note the need here and design it with the lighting for facial identification guidance. Backlight from a bright sky or headlights defeats an identify camera even in daylight.
• Blind-spot / overlap note. Mark overlaps as deliberate handover zones, and record blind spots honestly. A logged, accepted blind spot is a design decision; an unnoticed one is a failure waiting to be found after an incident. Perimeter runs especially need this discipline - see perimeter CCTV.
• Verified at commissioning. Left as N at design. It only becomes Y when someone stands on site, opens the live view and confirms the scene matches the stated purpose.

Verifying on site: turning intent into proof

Commissioning is where the schedule earns its keep. For each camera, open the live view and check:

• Does the scene match? The framed area is what the schedule says it should be, with the deliberate overlaps present.
• Is the purpose met? Have a person stand at the target and judge whether the footage supports the stated purpose - can you monitor, detect, recognise or identify as intended? Where identify is claimed, the face must be usable, not a distant blur.
• Day and night. Check again under night or IR conditions. A camera that identifies at noon and fails at midnight has not met an identify purpose.
• Blind spots as drawn. Confirm the accepted gaps are the ones on the plan and no new ones have appeared from a shifted mount.

Only then mark the row verified, date it and note who checked. A camera is not accepted until its live view proves it sees what the schedule promised.

Privacy and DPDP. Footage that identifies people is personal data under the Digital Personal Data Protection Act, 2023. A field-of-view schedule is also a privacy control: it defines exactly what each camera is meant to see, which means anything outside that intent - a neighbour window, a private balcony, a residential interior - should be masked or the camera re-aimed. Record required privacy masks against the relevant rows and confirm they are applied at commissioning. Do not over-capture beyond the stated purpose.

How it connects to the neighbouring documents

The field-of-view schedule does not stand alone:

• The camera schedule lists the hardware and refs; this schedule adds the purpose and view for each of those refs.
• The CCTV coverage schedule rolls the cameras up into area-by-area coverage; the field-of-view rows are the evidence beneath it.
• The coverage planning guide is where the purpose decisions are reasoned before they land in these rows.
• Commissioning uses the "Verified" column as its acceptance checklist, and the completed schedule is handed over as part of the as-built record.

Keep the camera refs identical across all of them, issue the field-of-view schedule with the layout at design, and close it out at commissioning. That is how coverage stops being a claim and becomes something you can prove.

Completion checklist

• Every camera ref from the camera schedule has a row here.
• Each row states a scene, a single purpose level, and an intended view that matches that purpose.
• Distance, lens/angle and lighting are recorded as intent ("specify" / "engineer to purpose"), not invented numbers.
• Overlaps are marked deliberate; blind spots are recorded and accepted or closed.
• Required privacy masks are noted against the relevant rows (DPDP).
• The "Verified at commissioning" column is filled on site, dated and signed off.

References

• Digital Personal Data Protection Act, 2023 - CCTV footage identifying people is personal data; capture only what the stated purpose needs, mask areas outside intent, and keep access and retention controlled.
• Manufacturer camera and lens data - the authoritative source for the angle of view, sensor and pixel density that achieve a given purpose at a given distance; engineer each camera to its purpose from this data.
• Recognised CCTV operational-requirement practice (monitor / detect / recognise / identify purpose levels) - use as a qualitative framework; confirm the specific pixel-on-target criteria with your equipment and project standard.
• Bureau of Indian Standards catalogue - verify the current edition of any standard referenced in your specification at https://www.services.bis.gov.in/

This is an educational, ready-to-adapt template, not authoritative, contractual or legal advice. Lens selection, mounting and any electrical work are qualified professional tasks - engage licensed professionals, and consult a professional for legal or data-protection questions.