A reliable NVR or DVR workflow separates daily monitoring, incident handling, evidence export, and planned maintenance. Operators should know the fastest supported path for each task, while administrators should verify storage, accounts, firmware, time, and recovery on a fixed schedule.
Features such as event thumbnails, human/vehicle filters, AcuSearch, two-way audio, remote recovery, or browser viewing depend on the recorder, connected cameras, firmware, and client. Use this runbook as a process map, then confirm the functions listed for your exact system.
Daily: establish a clean live view
- Check that priority cameras are online and showing the correct time.
- Use a layout matched to the operator's task instead of filling every tile by default.
- Choose main streams for detail and sub-streams for dense multi-camera views when supported.
- Review event snapshots or alerts before opening individual channels.
- Confirm that audio, talk, alarm, or arming controls are authorized before use.
During an incident: search from evidence, not guesswork
Begin with the narrowest reliable facts: camera, date, time window, target type, and event. Widen the search only if the first result is incomplete.
| Search tool | Best use | Dependency to verify |
|---|---|---|
| Timeline playback | Known camera and approximate time | Recording schedule, storage, and accurate device time |
| Event filter | Known alarm or analytics event | Event rule and linkage configured before the incident |
| Human/vehicle filter | Reducing irrelevant motion results | Compatible analytics and supported recorder workflow |
| AcuSearch or similar target search | Finding visually similar people or vehicles | Applicable recorder/camera model and supported metadata |
| Thumbnail or segmented playback | Scanning a long period quickly | Feature availability and sufficient recorded footage |
For evidence: export the smallest complete package
- Confirm the original camera and recorder time against the incident record.
- Select a window that includes context before and after the event.
- Export the native clip and the supported player or verification component when required.
- Keep the original file unchanged; create a separate working copy for viewing or redaction.
- Record who exported the file, when, from which channel, and where it was stored.
- Open the exported media on another authorized computer before closing the case.
Monthly: complete the maintenance loop
- Storage: inspect disk health, overwrite behavior, recording gaps, and retention against policy.
- Time: confirm time zone, daylight-saving settings, and synchronization across cameras and recorder.
- Accounts: remove dormant access, review administrator ownership, and test the approved recovery method.
- Firmware: compare installed releases with the official support channel, review notes, back up configuration, and schedule tested updates.
- Network: review offline events, bandwidth constraints, remote-access paths, and certificates where applicable.
- Browser/client: test live view, playback, and export in the supported environment. Do not assume every model is plugin-free in every browser.
- Recovery: confirm the configuration backup is readable and the responsible team knows how to restore it.
Handover checklist
Before a site moves into normal operation, document the supported clients, operator roles, camera map, recording policy, export procedure, recovery owner, maintenance window, and escalation path. A feature is operational only when the responsible person can use and verify it.
Compare supported network video recorders and consult the official NVR/DVR operation tips alongside the current model manual. Interface labels and feature coverage can change with hardware and firmware.