Continuous recording and motion recording provide a different timeline. In an incident, you sometimes also want to be able to see what happened before a report is made. Therefore, make the choice based on the event you want to reconstruct later, not only based on the available disk space.
Think of a delivery where you want to see both the arrival and the departure. A continuous recording period provides a different overview than separate segments around detections. Write a concrete example and determine how many minutes you need for it. This will make it clear what you expect from the timeline.
When recording based on movement, it matters what the system recognizes as an event. Let someone walk through the relevant area and see if the desired fragment occurs. Also assess slow movement or partial shielding if that occurs in the real situation. A successful report does not constitute complete control over all possible events.
In a busy passage, activity can be almost constant. The difference between continuous recording can manifest differently in a quiet storage environment. Let the actual recording usage be seen before you promise a storage time. Resolution, compression, and recording settings are part of that assessment.
If the recorder supports multiple recording modes, discuss which combination fits the different spaces. Also check how events are marked when reviewing. An event marker above a continuous recording is not the same as saving only a short event fragment.
Allow the future user to find a chosen time without the help of the installer. This makes it clear whether the timeline and filters are understandable. Document the made choice and any limitations, so that a changed opening hours or printer usage can be a reason to re-evaluate.
No. This depends in part on how much activity is recorded and on the recording settings.
That depends on the features of the recorder and camera. Recording and notifications must be set up separately and tested.
