Use scheduled CCTV snapshots to draft hazard records.
Picture a loading-dock camera saving one still every hour. The image lands in a folder your team controls, where a proposed Soter workflow checks the question set for that view. It returns a draft for a person to compare with the snapshot, then keep, edit, or dismiss.
- INPUT
- Scheduled still snapshots
- SOURCE
- A folder your team controls
- ENGINE
- Configured SoterAI workflow
- REVIEW
- Always human
SYSTEM MAP
One snapshot, from camera to review
This concept starts with a still from an existing camera, not a live feed. The proposed workflow returns a draft record for a reviewer to check.
- 0101
Scheduled snapshot
Your camera saves a still on a schedule you choose.
- 0202
A folder your team controls
The image lands in storage you control.
- 0303
Proposed storage access
Scoping decides which folder is selected, who grants access, and what that access allows.
- 0404
SoterAI reads the scene
Soter describes the image and answers the question set for that camera view.
- 0505
A person reviews the draftALWAYS HUMAN
A draft hazard record waits for someone to check it and decide what happens next.
ASSUMPTIONS: your CCTV system can export scheduled snapshots to a folder your team controls; SoterAI can access the selected storage; and the workflow can create the proposed draft record. All three points require confirmation for your setup before anything is built.
MATERIAL
What goes in, what comes back
IN
The snapshot
Pick a camera already aimed at the problem area. Save a still on a schedule that makes sense for that view, perhaps once an hour at a loading dock. The image lands in a folder you control. Access and data handling are confirmed during scoping.
ANALYSIS
The question for this camera
Soter describes the scene, then checks the question written for that view. Is the exit clear? Is the spill kit in place? The question stays narrow enough for a reviewer to check against the image.
- Is the emergency exit route clear?
- Is the spill kit where it should be?
- Is PPE being worn in this zone?
Examples only. The real question is written with the Soter team for each camera.
OUT
A draft, not a verdict
Proposed fields include a plain-language observation, the camera reference, and the snapshot time. The exact record shape still needs approval; whatever it contains, a person compares it with the image before keeping it.
HUMAN REVIEW
A person still makes the call.
A blocked exit can look obvious in a still. The camera cannot tell you whether the area is closed or the view is misleading. Every finding therefore waits for someone to compare the draft with the snapshot and decide what happens.
- CONFIRMthe words match the image, so the draft can become a hazard record
- EDITadd the context the camera cannot know
- DISMISSthere is nothing useful here; drop the draft and tighten the question if it keeps happening
BOUNDARIES
Good for things that stay put
A blocked exit can remain visible in the next scheduled image. A near-miss can be over before any still is saved, which is why this concept is not live monitoring.
What it is
- Cameras and storage you already control
- Snapshot checks on a schedule you choose
- One clear question for each camera view
- Draft hazard records for your review queue
- A person checks every finding
What it is not
- It does not watch live video; anything between snapshots can be missed
- It does not decide whether you are compliant
- It can get a finding wrong, which is why a person checks the draft
- It needs to be scoped for your setup before anything is built
WALKTHROUGH
See the workflow on screen
Matt’s walkthrough will sit here once the video is supplied. For now, the system map above shows the full path from snapshot to review.
VIDEO · TO BE ADDED
SCOPING
Start with one camera
Bring one camera view and the recurring problem it should help you check. We can work out the export, folder access, and review step from there.
- STEP 01
Show us one camera view
Pick a camera already pointed at the problem, perhaps a fire exit that keeps getting blocked. Bring the question you wish someone checked more often.
- STEP 02
Check the route in
Can the system save a still on schedule? Where does it land? Who can grant access to that folder? We answer those questions before building.
- STEP 03
Read the first batch together
Reviewers log false positives, missed conditions, and missing context. The team then decides whether to revise the question, stop, or test another camera.
QUESTIONS
Questions we would ask too
Bring us one camera and one recurring problem
We will check the export, the folder, and what your reviewer needs to decide before anything is built.
A build concept, scoped per customer. Not a shipped integration.