You discover damage on Monday and open the camera timeline to check the previous week. The date is there, but the useful recording is not. A retention setting and a usable recording history are not always the same thing.
Choose a retention period for a documented business purpose and applicable obligations, then verify the system can actually deliver it at the required quality. We would not start by choosing the largest drive or repeating a standard number of days. Neither explains why your business needs the footage.
Decide why the footage is being kept
Describe the security problem the cameras address and how quickly the business normally learns about relevant incidents. A site checked only after a closure may have a different discovery pattern from an entrance reviewed during every shift. Treat that as an input to the decision, not an automatic legal entitlement to retain more.
Canadian privacy guidance for overt surveillance in publicly accessible private sector areas says recordings should be kept only as long as necessary for the purpose and securely destroyed when no longer needed. The guidance does not set one period for every business and explicitly does not cover employee surveillance.
Ask the responsible adviser about obligations affecting your setting, including a valid preservation requirement or sector specific rules. Record the approved rationale and who can change it. More storage should not silently extend the policy just because it becomes available.
Separate policy from storage capacity
The retention policy says how long footage should be kept and why. The recorder's available capacity determines how much it can hold under the configured recording conditions. A setting alone cannot create capacity that does not exist.
Camera count, image quality, frame rate, compression and recording mode affect storage use. Continuous recording and recording only selected events do not produce the same history. Event based recording may use less space, but it also depends on what the system triggers and saves.
Ask for an estimate using the actual proposed configuration, with its assumptions written down. Then verify observed history after enough normal operation. A drive's advertised capacity is not necessarily all available for recordings once the system's storage arrangement and other requirements are considered.
Do not lower recording quality merely to reach a calendar target without checking the resulting footage. A longer history that no longer shows the detail needed for the stated purpose may not solve the business problem.
Check whether older recordings change quality
Some platforms can keep recent footage at higher quality and reduce older footage to save space. Others use different retention controls. Ask what the installed version does and whether those features are enabled.
Manufacturer guidance for one storage system warns that footage already reduced in quality cannot be restored to high quality by changing the setting later. The practical lesson is to inspect the age and quality of the footage you expect to use, not only whether a date appears on the timeline.
Review representative recordings at the stages covered by the policy. Check a scene relevant to your purpose, such as an authorized entry test, rather than an empty room. Avoid retaining unnecessary test footage after it has served the agreed verification purpose.
The useful question is how far back you can play the required detail, not how many days a setting displays.Verify the oldest usable recording per camera
After the system has operated long enough for the planned retention window, check each relevant camera. Record the earliest playable time, the recording mode, the quality at that age and any gaps. A systemwide estimate may conceal a camera with different settings or a recording fault.
Repeat the check after adding cameras, increasing quality, changing storage or enabling new recording features. Those changes can alter the available history. Assign a person to review the result instead of assuming the original estimate remains accurate indefinitely.
If observed history falls short, investigate capacity, configuration, recording interruptions and storage health before promising a fix. Increasing capacity may be appropriate; so may correcting a setting. Keep any revised policy and technical changes separately approved.
Preserve incidents without keeping everything forever
An incident can justify preserving a specific segment outside the routine deletion cycle. Use an authorized process that identifies the cameras, time range, reason and responsible person. Include enough context to understand the event without collecting unrelated days of activity by default.
Track exported clips, archives and copies sent outside the organization. Changing the recorder's retention does not necessarily delete a file already downloaded to a laptop or shared storage. Each retained copy needs appropriate access, security and a review or disposal process.
If a legal hold or investigation applies, get direction before deleting relevant material. Conversely, preserving one incident is not a reason to disable routine deletion for every camera. Keep the distinction visible in the policy so staff know when to escalate rather than improvising.
Plan the next step with NeuroDesk
NeuroDesk's business camera planning can connect your agreed recording purpose with storage, access and a practical verification process. Bring the existing retention policy and the incident discovery pattern you need to account for. Legal retention decisions remain with the business and its qualified advisers.
See our business camera planning for the relevant scope.
Sources and technical scope
The technical references below describe particular equipment and software. Features and limits must be checked against the installed model and configuration; they are not promises for every system.