A construction camera plan must follow the site's changing gates, assets, power and people. Start with the current phase, assign a job to each view, and plan retesting after every move. The practical system includes recording, connectivity, response and handover as well as cameras.
Define the evidence and the response
For each location, write what a reviewer must see: a delivery handover, removal of material, entry to a tool container, or movement around parked equipment. Specify target distance, earliest approach point, nighttime conditions and whether a complete timeline is required. A high overview camera useful for progress pictures may not provide the detail needed to identify a person at a gate.
List closed periods, incident-discovery delay, required retention, remote viewers and the alert responder. Cameras do not guarantee prevention. Decide who receives an after-hours alert, how they verify it and how they contact the agreed site response. Test delivery to the actual recipient; an app setting is not evidence that someone will respond.
Mark current camera positions, viewing directions, target routes, planned obstructions, power points, network paths and storage location on a dated site drawing. Distinguish overview and detail views, then walk routes to find blind transitions. Axis's Site Designer description illustrates map-based coverage and bandwidth/storage planning for supported systems. A drawing remains a planning aid: verify the installed image and saved footage at the actual distances.
Review coverage as the project changes
| Phase | Likely change | Required review |
|---|---|---|
| Mobilisation and excavation | Temporary gate, office/container placement, moving machinery | Entry route, stable approved mounts, out-of-hours power and equipment travel |
| Structure and scaffolding | New walls, lifting areas, metalwork and shade | Blocked views, wireless/cellular performance, solar exposure and safe service access |
| Fit-out and material peaks | More stored goods, smaller entrances, subcontractor turnover | Container doors, handling routes, user access, retention and alert volume |
| Demobilisation | Power removed, assets moved, equipment reused | Evidence export, owner sign-off, decommissioning and new-site acceptance |
Assign a person to review the drawing before a cabin, stockpile, gate or hoarding moves. Also retest after a mount is struck, a cable route changes, night lighting is removed or a new subcontractor takes over. A formerly clear view may remain online while becoming useless behind a container.
Worked example: a temporary yard with four views
Illustrative planning scenario, not a customer installation: a 60 m × 40 m fenced yard has one south delivery gate, an office at the south-west corner, a tool container on the west side and an equipment area to the north. Assume approved mounts near the office and container, safe cable routes to those positions, and a remote north area where a cable route has not been approved. These assumptions must be checked on site; four cameras are not a coverage guarantee.
| View | Task and candidate arrangement | Acceptance scene |
|---|---|---|
| A: gate approach | Overview of queue, entry and handover; wired recording near the office | Follow a vehicle approaching, stopping and leaving without a parked truck hiding the route |
| B: gate interaction | Tighter detail at the agreed handover point; separate from the overview | Read the required person/object detail from recorded daytime and nighttime activity; do not presume plate recognition |
| C: tool container | Door and removal route; protected wired connection if feasible | Capture door opening and a carried object through the full relevant route |
| D: north equipment | Candidate cellular/solar unit if its recording and energy fit the risk | Record a fast approach, a long event and a repeat event; verify remote alert and local playback |
Choose lens, mounting height and lighting from these tasks. Avoid aiming only at the middle of a wide yard where people are too small to assess. If view D needs a continuous timeline but the proposed event camera cannot supply it, revise the power/network design or add an appropriate view. Recheck equipment-area coverage when stacks move and panel shade changes.
Keep the whole system powered through closed hours
Find out when temporary supplies are switched off, whether generators stop overnight, and who controls the distribution. A UPS sized for a short interruption cannot cover an unpowered weekend. Have authorised site personnel approve mounts, temporary electrical work and protected cable routes; avoid lifting paths, vehicle crossings and structures scheduled for removal. Specify environmental protection for the camera, connectors and cabinet, including dust and rain exposure.
Illustrative backup calculation: assume three wired cameras at an average 6 W each, recorder/disk at 15 W and switch/router at 12 W, giving 45 W total. For eight hours, equipment needs 45 × 8 = 360 Wh delivered. At an assumed 80% battery-to-load efficiency, nominal starting energy is 450 Wh before reserve and ageing. A 60-hour shutdown would instead need 2,700 Wh delivered, or 3,375 Wh under the same assumption. Replace these invented loads with measured operating loads and use the backup manufacturer's runtime curves.
Check maximum PoE requirements as well as average energy: a port or switch may fail at night even when the backup arithmetic looks sufficient. Back up the cameras and recorder together, plus the router if remote alerts are required. Test an upstream interruption with all required equipment operating; note the last clip, outage interval, restart and first new clip. For off-grid views, use the seasonal energy and recovery calculation.
Choose network and storage independently
| Path | Benefit | Failure to plan for |
|---|---|---|
| Ethernet cameras to local recorder | Local traffic and footage do not need mobile upload | Cable damage, recorder theft, loss of supply; remote access still needs an uplink |
| Wireless bridge to local network | Can avoid an unsuitable cable crossing | Power at both ends, obstructions, alignment and capacity; site structures may change |
| Cellular camera or LTE router | Remote access before fixed broadband | SIM renewal, upload limitations, service outages, power and exact integration |
Local recording plus selected remote event copies can control data use where equipment supports it. It also creates two retention policies to verify. Local media may be lost with stolen equipment; remote copies may omit context if uploads contain only short clips. Continuous cellular upload needs a separate data budget: one assumed 1 Mbps stream uses about 324 GB over 30 days before overhead. Verify the SIM, access path and outage behaviour before relying on it.
Choose retention from the delay until review, not simply the site working week. If an incident near the start of a 10-day closure is reviewed three days after reopening, footage must remain available at least 13 days after capture; add operational margin for delayed discovery. Check permissions, privacy masks, audio settings and authorised use before commissioning, with applicable local requirements handled by the site owner.
Illustrative storage calculation: four continuously recorded streams averaging 2 Mbps each for 14 days require 4 × 2 × 86,400 × 14 ÷ 8,000 = 1,209.6 decimal GB of video payload. This excludes audio not in that bitrate, recorder overhead and unusable/reserved disk space. Specify a suitable usable recording capacity with margin and inspect actual oldest footage. Variable bitrate, night noise and scene activity can change demand; an event-recording estimate depends on observed event duration rather than an assumed universal saving.
Commission, move and hand over with evidence
- View test: walk and drive agreed routes in day and night conditions, including backlighting and normal site lighting. Review saved detail, overlap and blocked paths. Adjust mount/lens/lighting and repeat the affected scene.
- Timeline test: create fast, long and closely repeated events. Retrieve beginnings, endings and the required pre-event context. Verify timestamps and camera/site labels.
- Resilience test: interrupt the test uplink with power maintained, then test upstream power separately under the approved procedure. Verify local recording, alert limitations, restart and any supported delayed upload.
- Evidence test: export an agreed clip using the intended reviewer account and play it on the recipient's system. Check the oldest recording once the retention window has elapsed. Until then, retention is a design estimate rather than demonstrated performance.
- Response test: route a test alert to the responsible person, record acknowledgement and rehearse the agreed escalation. Tune wind-blown tarps, shadows or headlights using supported settings while preserving required detection.
Before relocation, save necessary footage and configuration, label camera IDs and record the old viewing direction, mount, supply and network settings. Establish how the temporary coverage gap will be handled. Move under the site's approved procedure, update the drawing and repeat the affected view, power, connectivity and export tests. Reusing or formatting storage can erase evidence; export and obtain the site owner's retention decision before reuse.
Handover should include the dated map, camera tasks, reference clips, recording schedules, retention target, power/backup assumptions, SIM renewal, fault contacts and relocation inventory. Assign checks for recent recordings, storage, charging, clean lenses and unblocked views before weekends or closures. Provide named user accounts where supported, strong passwords and a firmware-update owner; remove departed contractors' access. Schedule the next phase review; the system is ready for that phase only when its new scene and recording path have been retested.