A camera shift handover that the next crew can use
The next crew should not have to guess whether “quiet shift” means no observed activity, no alerts or no working feed. A good handover separates those statements and leaves someone responsible for unfinished work.
The following is a proposed house worksheet. It is not a statutory record format or a claim about what a particular video product exports.
Begin with the watch you promised
Write the shift start/end, timezone, intended cameras and schedules, then list known observation gaps with their evidence and uncertainty. Under the house method, coverage is monitored time divided by scheduled time M02. The method uses its own operating definitions rather than ActEV's time-based false-alarm normalization.
Take a hypothetical two-camera eight-hour watch: the schedule totals sixteen camera-hours, and if one camera loses two hours while both otherwise stay monitored, coverage is fourteen of sixteen, or 87.5%. Write down the affected camera and interval as well as the total. The estate-level fraction alone won't tell the next crew which gate had the gap.
Use a compact handover table
| Item | What the outgoing crew records | What the incoming crew checks |
|---|---|---|
| Watch | Cameras, schedule, timezone | Same intended coverage now? |
| Gaps | Known interval, uncertainty, support reference | Recovery demonstrated? |
| Open events | Identifier, permitted evidence, action already taken | Named response owner? |
| Rule changes | Old/new version, reason, time | Correct version active? |
| Delivery faults | Expected endpoint, failed step | Approved retest complete? |
| Next actions | Owner and due time | Accepted by incoming crew? |
Keep private addresses and access credentials in the approved operational system, not on a widely circulated summary.
Do not let the incident total stand alone
An incident may group continuing activity or repeated observations depending on the product, so define the unit before treating the total as a count of visits. Our proposed field evaluation matches system events to annotated reference events using a declared rule M03.
For routine handover, simple language works: “Three alerts reviewed; two matched permitted deliveries; one unresolved.” That hypothetical statement tells the next crew more than a bare number with no review status. Keep the supporting details in the approved incident record.
Finish with a small recovery check
If a feed failed, confirm the current timestamp and an approved visible movement after recovery. If delivery failed, test the recipient route separately. Record who checked and when, and never overwrite the earlier failure with the later successful result.
Any unresolved issue needs an owner and an agreed next step. “IT aware” is incomplete unless the incoming crew can find the support reference and knows the temporary operating arrangement.
A useful closing sentence
Try this structure: “During monitored periods, the crew reviewed the listed events. Camera West had an unresolved gap from the recorded last-good time to recovery. The incoming supervisor owns the remaining support action.” Fill it in with the actual evidence and uncertainty; don't copy a clean version onto an incomplete watch.
Use the offline-camera guide for observation gaps and the delivery checklist for missing notifications. They belong to different branches of the handover.
FAQ
Should we say nothing happened?
Prefer an evidence-bounded statement about observed activity during known monitored time. Keep gaps and unresolved events visible.
Can a percentage replace the gap list?
No. The fraction summarizes the schedule; the interval and camera tell the next crew what needs attention.
Fact traceability
Source-register IDs used on this page: M02, M03. Direct primary links sit beside the relevant claims. Calculations and selection judgments are editorial examples, not measured product results.