Security & surveillance

The day you need the footage: extracting, showing, handing over

Recording is easy; producing a usable sequence is not. The order of operations, who may watch, and what gets handed to whom.

Published on 31 May 2026 — Algeria Agency

The companion article chooses and mounts the cameras: field before resolution, night, the recorder, the retention period. It stops at the moment the installation works.

This page starts exactly there. An installation that records properly is worth nothing if, on the day of the incident, nobody knows how to produce a sequence, who to give it to, or what may be shown.

The three failures we actually see are not camera failures. A recording overwritten while somebody was searching, a file nobody could open, and an image obtained in conditions that make it arguable.

The order matters more than the equipment and it fits in one sentence: protect first, search second, watch last. Most people do exactly the reverse, and it is the first act that costs the most.

What you need has already begun to erase itself

A recorder is a loop. It does not archive, it writes over the oldest material continuously, with nobody having to do anything for that to happen. Every hour that passes erases an hour.

That is obvious until it is set against the second obvious thing: the moment a problem is discovered is almost never the moment it happened. A night theft is seen next morning; a stock discrepancy is seen at inventory, which is weeks later.

The companion article settled the retention period and we are not reopening it. The question that remains is a different one and nobody asks it: how long passes, in your business, between the event and the moment somebody finally touches the recorder.

That delay is not technical. It is made of who notices, who tells whom, who remembers there are cameras, and who holds the password. We have watched three weeks of retention consumed entirely by one week of internal delay and two weeks of leave.

The practical consequence is easy to hold and it reorders everything that follows: your real window is not the duration set on the disk, it is that duration minus your own slowness. Shortening the second costs less than lengthening the first.

The first act: protect before watching

Everybody’s reflex is to sit down in front of the screen and search. It is the right act in the wrong order, and it is the one that loses sequences.

While you are searching, the loop keeps writing. A two-hour search on an installation set short, on a Friday evening before a weekend, is enough to erase precisely what you were looking for.

So the first act is to put the period beyond reach without having watched it. Depending on the recorder this is called protecting, locking or exporting — what matters is that the period stops being overwritable.

Bound it wide, far wider than you think you need: two hours before, two hours after, and the whole day if you are unsure of the time. An external disk costs the price of a meal; the sequence will not happen again.

Only then do you watch, and you watch the copy rather than the recorder. From that moment you can take as long as you need without time working against you — which is the exact opposite of most people’s situation when they call us.

Finding the sequence when you do not know the hour

You rarely know the minute. You know a box went missing between Monday and Thursday, or that the till was out "last week", and that is all.

Three anchors cost nothing and frame a search better than any function on the recorder. The time printed on the till receipt. The access-control log, if you have one, which dates every door opening. And the alarm history, which dates every arming.

Motion detection is the tool of last resort rather than the first, because in a shop it hands you back the entire day. It becomes useful only at night, or in a stockroom where nothing moves without a reason.

The method that works is halves: look at one frame every thirty minutes to bracket the event between two bounds, then narrow. Four or five glances reduce a day to a quarter of an hour, which no continuous viewing will do.

And check the recorder’s clock against your phone before trusting any anchor. A twenty-minute drift is ordinary on a device not set from the network, and it makes the till receipt misleading instead of useful — you will search at the right moment in the wrong file.

Exporting: the file nobody can open

This is the commonest failure in the whole chapter, and it is always discovered at the worst moment: the sequence exists, it is good, and the recipient cannot read it.

The cause is nearly always the same. Recorders export in a format of their own, bundled with a small viewer program. That file is refused by an insurer’s mail system, unreadable on a lawyer’s machine, and blocked by a recent Windows that will not run an unknown program.

So the rule is to export twice. Once in the native format, which preserves the recorder’s own information and is the version to keep. Once in a standard format any computer opens with nothing installed, which is the version to hand over.

Add a three-line note to the export: the camera, the date, the start and end times, and the recorder’s clock against the real time if they differ. That note is worth more than image quality to somebody who was not there.

And try the file on a machine other than the one that produced it, before you need it. That is exactly the test the installation article asks for at handover, and it is the one that fails most often — because everybody runs it on the machine where the manufacturer’s program is already installed.

Who may watch

A recorder is a device that allows watching everybody, all the time, without anybody knowing. What gets restricted is not the camera, it is access to that device.

Three people at most, named, each with their own account. The number matters less than the fact of having been decided: an access nobody decided ends up belonging to the installer, a former manager, and the nephew who set up the phone app.

Never a shared account, and this is the rule that goes first. A log that says "admin" says nothing, and on the day the question becomes "who viewed this sequence", you have no answer to give — including no answer that clears you.

Plan for the manager being away, because it always happens at the wrong moment. A named second holder, or the password in a sealed envelope in the safe, with a written rule: an opened envelope is recorded and the password is changed afterwards.

Finally, for anything concerning a person, watch in pairs. That protects not only the person filmed but the person watching: a solo viewing, where nobody can say what it contained or how long it lasted, turns against whoever did it.

What has to be posted and said beforehand

An image obtained without anybody having been informed is an image that will be argued about instead of what it shows being argued about. This is the only part of this article played entirely before the incident.

A sign at every entrance, visible before entering the field rather than after. It costs a few hundred dinars and it is the first thing a third party looks for when the conversation turns serious.

Employees informed in writing, on hiring and again whenever a camera is added or moved. "Everybody knew" is not information, it is a collective memory, and it has never held up in front of anybody.

What the notice has to contain is four points: that the place is filmed, who is responsible for the system, how long images are kept, and who to ask a question of. You already have all four answers; the job is writing them down once.

The arithmetic is asymmetric and that is what makes this section decisive. Doing it beforehand costs an afternoon and a few signs. Not having done it cannot be repaired afterwards: the recording exists, it is accurate, and it is unusable for the one thing you had it for.

What gets handed over, to whom, in what form

The order is the same everywhere and is rarely followed: file the complaint first, then hand over what is asked for in that context. A sequence distributed before any formal step loses the one context that gave it weight.

You hand over a copy, never the only copy, and never the disk or the recorder. A recorder that leaves with its evidence also takes the surveillance of the following weeks, which is precisely when it is most useful.

Write down what you handed over, to whom, when, and what period the sequence covered. Two lines in the register described further down. Those two lines are what will let you answer, six months later, a question nobody remembers the answer to.

Do not circulate the images beyond that. Not in a neighbourhood traders’ group, not in a company conversation, not to a friend who "knows somebody". Every copy outside your control is a copy you answer for.

And never publish an image to get somebody identified. It is the commonest and costliest act on this page: it moves you from the person something happened to into the person who has to explain themselves, and it always happens within two hours of the discovery, when nobody is in a state to decide well.

Insurance: what it asks for, and the deadline

The declaration deadline is short and it runs from discovery, not from the event. It is the only deadline in this article that cannot be recovered, and it falls during the days when there is least time.

The images are not the file, they support it. What constitutes the file is the declaration, the complaint, and an inventory of what is missing, costed. An excellent sequence without those three pieces does not advance a settlement by a single day.

What is asked for is a readable file and a description: which camera, which angle, which hours, and what is visible. This is the moment the three-line note from section 4 saves you a week, because nobody has to call you back to reconstruct it.

Keep your own copy after handing theirs over, and keep it somewhere other than the recorder. A file can be reopened months later, at a point when the loop has turned five or six times over the period concerned.

The usual unpleasant surprise is not refusal, it is the gap: the contract assumes a system you do not exactly have, or premises part of which was not covered. That gets checked once, calmly, by rereading the terms — and it belongs to the security and surveillance article rather than to this one.

The hardest case: an employee

This is the moment an installation put in against theft becomes something else, and where many installations change their nature without anybody having decided it.

What a sequence honestly establishes is narrow and worth staying inside: somebody, at that time, in that place, making that movement. It is often enough. It is not the same thing as intent, and the companion article gives its last section to that difference.

What it does not establish is vast: everything outside the field, everything that happened with a back turned, and everything whose result the camera shows without showing its cause. An incident is rarely reconstructed from images alone, and a case resting only on them is a fragile case.

The distinction that matters is not legal, it is one of proportion. Reviewing a bounded period around a specific fact is one thing. Watching a person for a week to see what turns up is another, and the second is not a more thorough version of the first.

The working rule we apply fits in a sentence: if the answer needs more than one review of a bounded period, the question is not a camera question. It is a question of organisation, till control or stocktaking, and it is handled with the corresponding tools — which also give an answer nobody disputes.

The person filmed who asks to see

It happens, more often than people expect, and usually from somebody who knows they were filmed and believes the sequence supports them.

A reflex refusal is the wrong choice, because it turns an ordinary request into a suspicion and because it is the one act on this page that costs nothing to avoid. The right answer is a timeframe and a method, not a no.

What can be shown is the sequence concerning that person. What cannot is what concerns the other people present in the same image, and that limit is not negotiable through goodwill: you cannot give one person what belongs to another.

The practical solution, in a business of this size, is to watch together on screen rather than hand over a file. The request is met, nothing leaves, and the exchange takes ten minutes instead of becoming a case.

Record the request and the answer in the same place as everything else. A request refused with no trace gets retold however anybody likes afterwards; a request logged, dated and dealt with in ten minutes does not get retold at all.

The register: five lines per extraction

This is not paperwork and it is the piece that makes everything else checkable. Without it, each of the eight preceding sections rests on somebody’s memory.

Five columns are enough: the date of the extraction, the period the sequence covers, the reason, the person who did it, and the person it was given to. Nothing else. A line takes forty seconds to write.

A sheet in a drawer beats a shared file nobody will maintain. The quality wanted here is that it gets filled in every time, and the only register that does is the one sitting next to the screen.

What it gives you is not compliance, it is a demonstration: it shows the system is used to handle events rather than to observe people. That is exactly the question an employee, an inspector or a lawyer will ask, and it is the only one answered with a document rather than with an assertion.

It also answers the question you will ask yourself in a year, and that nobody ever settles from memory: had we already looked at this period, and what did we see.

What we do, and what we refuse to do

What we refuse first: setting up an ongoing review aimed at a named person. That is not surveillance of premises, it is something else, and it does not become acceptable because the request comes from the employer paying for the installation.

We also refuse to certify that a file has not been modified. We have neither the means nor the standing. What we do instead is plain: we hand over the native export as the recorder produced it, with the note saying where it came from, and we say that it is that and nothing more.

And we do not extract a sequence at the request of somebody who is not the person responsible for the system, whatever urgency is claimed. The rule looks rigid until the day it protects you.

What we do gladly, and it takes a morning: the rehearsal. A dry-run extraction on an invented incident, with your own people, until the file opens on a machine that is not the recorder’s. Nobody runs that rehearsal and it is the thing that decides all the rest.

And one thing to do today without us, in thirty seconds: compare the recorder’s clock with your phone’s. Drift is ordinary, it is invisible until looked for, and it is the commonest reason a search anchor leads nowhere.

Frequently asked questions

What should we do in the first minutes after discovering something?

Protect the period before watching it. Depending on the recorder this is called locking, protecting or exporting, and the point is that the loop stops being able to write over it. Bound it wide — two hours before, two hours after, the whole day if in doubt. Only then do you search, and you search the copy.

Why can nobody open the file we sent?

Because recorders export in a proprietary format bundled with a viewer program, and that program is refused by a mail system, blocked by a recent Windows, or unusable on another operating system. Export twice: the native format to keep, a standard format to hand over. And try the file on another machine before you need it.

Should we hand over the hard disk or the recorder?

No. You hand over a copy of the sequence concerned, never the medium or the device. A recorder that leaves takes the surveillance of the following weeks with it, which is exactly the period when it is most useful. Write down what you handed over, to whom, and for what period.

Can a sequence be used in a dispute with an employee?

That assumes two things done beforehand: employees informed in writing and a sign at the entrance. And it assumes a limit during: reviewing a bounded period around a specific fact is not the same as following a person for a week. Our working rule is that if the answer needs more than one review of a bounded period, the question is not a camera question.

An employee asks to see footage concerning them. What do we say?

A timeframe and a method, never a flat refusal. What can be shown is what concerns them; what concerns other people present in the image cannot be handed over. The simplest approach at this size of business is to watch together on screen rather than hand over a file — and to log the request and the answer.

How long do we keep an extracted sequence?

A sequence extracted for a specific reason is kept as long as the reason lasts: an insurance file or a complaint can be reopened months later, when the loop has turned five or six times. Keep it somewhere other than the recorder, and delete it when the reason is closed — recording the deletion in the same register.

Where we come in

A recorder whose clock has drifted makes every sequence arguable on the day it matters, and the drift shows in thirty seconds.

We rehearse a dry run on a made-up incident until the file comes out.
We write down who at your company may request a sequence.
We show you how to hand over a copy without losing the original.

No integrity statement will come from us: we do not have the standing, and an accommodating one would be turned against you.

See the IP Cameras page Write to us

Let us talk about your project

A free audit, no commitment: we look at your online presence and tell you what is holding it back.

Request the free audit Write to us