Guides
CCTV Requirements: Describe the Scene and Review Task Before Choosing Cameras
Prepare a CCTV scene brief with authorised observation boundaries, operating conditions and task checks, without assuming coverage or image performance.
DETIAN ICT · Tanzania & East Africa
Discuss your ICT project with DETIAN.
DETIAN ICT supports audiovisual, security, network and smart-building projects in Tanzania and East Africa, with design, equipment supply, installation and maintenance services.
Share your site location, required systems and available drawings or equipment list. Start a discussion about the work scope and the information still needed.
Describe what the authorised operator needs to see
Before asking for a CCTV proposal, describe the scene, the observation task and the conditions under which that task needs to be reviewed. “A camera at the entrance” identifies a possible location, but it does not explain what the owner expects an authorised operator to see. Keep that requirement separate from a proposed camera model or an untested picture-quality claim.
For a business site in Tanzania or elsewhere in East Africa, a scene brief can connect the site plan with specific operational questions. DETIAN’s public solutions page includes video surveillance and explains that site plans should identify observation areas and operating procedures. The worksheet below prepares that discussion; it does not select cameras, certify coverage or grant permission to monitor an area.
Give the scene a clear boundary
Identify the relevant business area on the current plan and describe the activity the owner needs to review there. Use a stable area reference, a dated plan and an agreed description. An entrance, reception area and delivery point may be related, but they are not interchangeable simply because they appear in the same photograph.
Ask the responsible owner to confirm the authorised observation scope and any areas or activities that must remain outside it. Record unresolved boundaries for the project review. Do not reposition equipment, broaden an existing view or change recording settings merely to complete this enquiry. Permissions and operational requirements belong to the established site process.
State the question in ordinary task language. For example, a business may want to review whether an authorised test parcel was placed at a designated handover point. That is narrower than recognising every person, reading every label or seeing every movement across the whole site. Different expectations need their own assessment rather than an assumed upgrade in wording.
Record conditions that can change the view
Describe the operating periods relevant to the task and the lighting conditions known to the owner. Daytime and after-hours use should not be collapsed into a single unqualified requirement. Mark observations as observations and proposed future conditions as assumptions. A photograph taken at one time does not demonstrate the scene under every other condition.
Identify ordinary operational changes that may matter, such as an open or closed door, a movable trolley or the usual position of goods within the agreed area. Use factual site information and approved images. This is not an instruction to disclose sensitive layouts publicly or to test ways around a security system.
Keep unknown dimensions, mounting constraints and infrastructure questions visible for the technical team. Do not estimate a usable recognition distance, camera count or resolution from an ordinary photograph. Equipment selection and installation assessment require the actual scene and the agreed task, with the proposed method explained by the responsible designer.
Prepare one row per scene and task
A useful row contains the scene ID, plan revision, intended task, permitted observation boundary, relevant operating conditions, known infrastructure and unanswered questions. Add who owns the requirement and who will agree the later check. The row should point to the relevant plan location without replacing the technical design.
Separate live viewing from reviewing a recorded event if both are requested. The ability to see a current image does not, by itself, demonstrate the ability to locate and review an earlier agreed event. Ask which functions are included in the proposal and how each would be checked. Do not infer a recording duration or retrieval capability from the presence of a camera.
The existing office location-schedule guide provides a way to keep area references consistent. The CCTV scene row adds the observation task and conditions for that location. A network connection shown on the plan does not establish that a suitable view or recording workflow has been achieved.
Work through a fictional delivery-point example
Imagine a site owner preparing a proposal request for an authorised goods handover area, labelled DEMO-A1. The owner wants an authorised operator to review a staged placement and removal of a test parcel on the designated surface. The area name, parcel and exercise are invented, not a DETIAN customer installation or a statement of delivered performance.
The brief specifies the task and asks the project team to agree representative daytime and after-hours conditions. It also records that the owner has not yet confirmed the after-hours lighting arrangement. The request is therefore ready for clarification, not for a statement that the task can already be performed under both conditions.
Suppose a later authorised demonstration shows the agreed parcel activity during daytime, but the after-hours check has not occurred. The record can say which daytime task was observed and retain the after-hours item as untested. It should not say “the whole CCTV system passed,” nor extend a parcel-activity check to face identification, small-label reading or another area.
If the owner subsequently changes the handover position, update the scene requirement and ask the technical team which parts need reassessment. A successful observation at the original position is not automatically evidence for the new one. Preserve the earlier check with its actual conditions instead of rewriting it to match the revised requirement.
Agree the evidence before calling a check complete
Before acceptance, agree the task, conditions, authorised test material, responsible participants and record to retain. A check should name what was performed and the result observed. Where live viewing and recorded review are both in scope, record those outcomes separately and leave an unperformed step open.
Keep a screenshot, where authorised and appropriate, tied to its scene and check rather than treating one image as proof of every operating condition. Record any difference between the proposed requirement and the demonstrated result for the responsible team to review. The worksheet does not replace a technical acceptance procedure or determine whether a design is adequate.
Organise the resulting scene records, agreed settings documentation and open questions in the handover index. If the work changes a live installation, use a separately agreed changeover process. A proposal or a scene worksheet is not approval to interrupt an operating service.
Send a bounded scene brief to DETIAN
Prepare the project country and town, facility type, relevant plan, scene rows, known existing equipment and the questions requiring site-specific assessment. Include the intended schedule and any constraints already approved by the owner. Share necessary project material through the official contact route rather than posting sensitive site information in public.
DETIAN’s service page describes design, equipment supply, installation and maintenance arranged around project conditions. Ask the team to clarify the proposed assessment, equipment scope, task checks and handover arrangements. This article does not promise particular image quality, identification results, monitoring coverage, delivery dates or a response arrangement for an unassessed site.
