Too many screens
Supervisors cover several zones and shifts with no time to watch every feed.
Every alert.
Every review.
On record.
PPE and site-safety review from the CCTV you already have. CompliSight flags configured events, a supervisor checks the context and decides, and detection, review, action and closure stay connected.
- No new cameras
- A supervisor closes every alert
- No emotion inference
Illustration. Camera feeds, configured rules and retention are confirmed during scoping.
Approved feeds onlyIt analyses the CCTV feeds you have approved, already in place.
Narrow, configured rulesPPE and site-safety rules agreed for each zone, nothing broader.
Evidence that stays connectedDetection, review, corrective action and closure in one record.
The site supervisor’s reality
Cameras record everything. Safety teams still need proof.
PPE exceptions and hazards happen across shifts and zones, and supervisors cannot watch every screen.
When an auditor or investigator asks what was seen, who looked at it and what was done, the answer is often spread across footage, radios and spreadsheets.
Missed exceptions
A missing hard hat or a person in a restricted zone is noticed late, or not at all.
Weak follow-up
Corrective actions are agreed verbally and closure is hard to show later.
Audit gaps
The record of detection, review and closure lives in separate places.
From an approved camera to a reviewed safety action.
CompliSight is generally available. It works from approved CCTV feeds already in place; camera and video-management compatibility is confirmed during scoping.
CompliSight
Analyses approved CCTV feeds for configured PPE and site-safety rules and keeps the evidence of each alert.
Supervisor review
A person checks the visual context and decides. Safety responsibility stays with your team.
TrustOps + Evidence Fabric
The configured boundary before an alert and the retained record afterwards.
Start with the risk that matters on your site.
Rules are narrow and agreed for each zone. Choose one to begin; the others follow the same review and evidence pattern.
PPE compliance
Flag configured PPE conditions, such as a hard hat or high-visibility vest required in a marked area, for supervisor review.
- Hard hat
- Hi-vis vest
- Marked area
- Supervisor review
Restricted zones
Surface entries into agreed zones, such as loading bays or machine areas, so a supervisor can check whether the entry was authorised.
- Zone boundary
- Camera context
- Shift
- Authorisation check
Site hazards
Configure site-safety conditions agreed for the site and route them to the responsible team with the visual context attached.
- Agreed conditions
- Visual context
- Responsible team
- Severity label
Follow-up and closure
Record the response, the corrective action and the closure, so reporting draws on what was actually reviewed and decided.
- Corrective action
- Owner
- Closure
- Evidence record
From camera event to closed action.
Five steps. AI supports the decision; people keep safety responsibility.
- 01 · CAMERA
Use approved feeds
Existing CCTV with agreed camera context and zones.
- 02 · DETECT
Flag a configured event
Narrow PPE and site-safety rules flag a possible exception.
TrustOps: configured rules only.
- 03 · REVIEW
A supervisor checks
The visual context is checked against the agreed site procedure.
TrustOps: a person decides.
- 04 · ACT
Record the response
The responsible person records the corrective action and follow-up.
- 05 · RETAIN
Keep the evidence
Detection, review, action and closure stay connected for inspection.
Evidence Fabric: the retained record.
One alert. One check. A closure you can show.
A synthetic safety event. CompliSight flags the configured condition; the supervisor decides what happens next.
CompliSight · Safety eventSynthetic example
- Camera and zone
- Camera 04 · Loading bay B
- Configured rule
- Hard hat in marked area
- Event time
- Shift 2 · 14:32
- Status
- Awaiting supervisor review
Possible PPE exceptionReview
Illustrative values. Severity labels are operational and do not indicate EU AI Act classification.
TrustOps · Policy and reviewPolicy example
- OBSERVECompliSight flags the event
Camera, zone, rule and visual context stay attached to the alert.
- ESCALATESAFE-02: route to the zone supervisor
The supervisor on shift reviews the context and decides the response.
- DENYSAFE-05: no inference beyond the rule
No emotion or intent inference, and no automatic action against a person.
- RECORDReviewable evidence record
Detection, reviewer, decision, corrective action and closure.
The people who review, close and audit.
Site supervisors
Review configured alerts in context, decide the response and close them with a record.
Safety and operations leads
See open events, corrective actions and closure across zones and shifts.
Auditors and investigators
Inspect what was seen, who looked at it and what was decided, after the fact.
Privacy and TrustOps boundaries
ALLOW · SAFE-01
ESCALATE · SAFE-02
DENY · SAFE-05
Cameras detect. Supervisors decide.
Being clear about the boundary matters more in safety than anywhere else. These are example policies for a site deployment, not a deployed rulebook.
Approved feeds and zones
Only the CCTV feeds and zones approved for the deployment are analysed against the configured rules.
Route to a supervisor
A flagged event goes to the responsible supervisor with the visual context attached.
Nothing beyond the rule
No emotion or intent inference, and an alert is never closed without a person.
- Camera and zone
- Configured rule
- Visual context
- Reviewer and decision
- Corrective action
- Closure
Identification handling, masking or blurring, where video is processed, access and retention are confirmed per deployment. Customers remain responsible for legal, privacy and worker-representation assessments. EU AI Act guidance · Security review
One site. One rule set. A review you can judge.
Start with agreed camera feeds and a narrow rule set in one area. Feeds, rules, retention and success criteria are confirmed during scoping; pricing is discussed privately.
Agree the scope
Choose the site area, approved feeds, configured rules and the supervisors who will review.
Assess the deployment
Confirm privacy, masking, access, retention and worker-representation requirements for the site.
Review together
Evaluate alert usefulness, the review flow and the evidence with your safety team.
Decide the next step
Check the agreed criteria and whether more zones or sites fit.
Clear rules. Clear responsibility.
Which part of the site should we start with?
Start with one area where a missed PPE or zone exception matters most, such as a loading bay or machine area. Approved feeds and a narrow rule set for that area are agreed during scoping.
Who reviews the alerts?
The supervisor responsible for that zone and shift, agreed during scoping. Every alert is reviewed and closed by a person, and that review is part of the record.
How long are video and records kept?
Retention is configured per deployment. Your organisation decides how long visual context and records are kept, based on its own legal and privacy assessment.
What should we assess before deployment?
Privacy, identification handling, masking or blurring, where video is processed, access and worker-representation requirements for the site. See the EU AI Act guidance and the security review.
Is CompliSight available today?
Yes. CompliSight is generally available. Feeds, configured rules and evidence retention are confirmed during scoping.
CompliSight product overview · Industrial and manufacturing · Security review · Workflow examples
Bring one site area. Let’s make every alert reviewable.
Tell us the site area, the cameras already approved and who supervises each shift. We will scope a narrow rule set and the record you need after every alert.