Geye / Industry playbookGate duty
Rain and umbrellas change visibility during pupil pickup.
Geye / Industry playbook
School
Observe site activity and occupancy patterns using purpose-limited zones and clear retention rules.
Planning guidance, not a claim of installed capabilities or customer results. Validate scope and feasibility before deployment.
Industry overview
School operations must balance arrival flow, safeguarding, and children’s privacy. Limit visual analysis to approved shared spaces and treat every signal as a prompt for authorized staff review.
Transition periods
Brief corridor surges coincide with scheduled lesson changes.
After-hours access
Authorized clubs and maintenance may use the same entrance.
Use cases
01
Gate duty
- Context
- Rain and umbrellas change visibility during pupil pickup.
- Human action
- Review arrival congestion at the main gate.
- Intended outcome
- A duty-teacher observation supporting the existing pickup plan.
02
Transition periods
- Context
- Brief corridor surges coincide with scheduled lesson changes.
- Human action
- Observe shared-corridor occupancy during transitions.
- Intended outcome
- A shared-space review without individual behavior scores.
03
After-hours access
- Context
- Authorized clubs and maintenance may use the same entrance.
- Human action
- Review activity at approved after-hours entrances.
- Intended outcome
- An entrance event checked against approved activities.
AI vision capabilities
Read the scene, retain the context
Test anonymous counts, gate crossings, and time-windowed zone activity. Different student heights, group movement, and school bags affect detection; no emotion, behavior score, or attendance identity inference is proposed.
Evidence contract
Keep zone, source timestamp, and view availability together. A stale frame must not become a current event.
A person owns the decision
A duty-teacher observation supporting the existing pickup plan.
Define acceptanceProposed capabilities must be tested against representative inputs. Unsupported or low-confidence results belong in a review queue, not an automatic decision.
Real-world scenario
Hypothetical, not a client story
Hypothetical: pickup traffic causes a crowded pedestrian gate. A duty teacher checks the scene and coordinates the existing pickup plan without identifying or scoring individual pupils.
- 01
Context
Rain and umbrellas change visibility during pupil pickup.
- 02
Review trigger
A candidate observation in the selected zone requires confirmation against current conditions.
- 03
Human response
Review arrival congestion at the main gate.
- 04
Intended result
A duty-teacher observation supporting the existing pickup plan.
How it works
CCTV
Read an authorized stream from the selected zone. Track source health and timestamps; a missing view is not an empty scene.
AI analysis
Apply validated models and zone rules on assessed compute. Group candidate events and expose uncertainty instead of implying certainty.
Reviewed insight
An assigned person checks evidence, records the outcome, and follows the existing operational procedure. Rejected signals feed back into evaluation.
Business and operational value
Review privacy impact, false-alert rate, and staff acceptance before expanding coverage.
Evidence quality
Accepted observations / reviewed observations. Count missed cases separately against the manual reference.
Target: agree before pilotReview effort
Record minutes per reviewed item, including rework and escalations. Compare the same task with the manual baseline.
Target: agree before pilotSafe failure
Record whether stale inputs, denied access, and unavailable sources stop or visibly degrade the workflow.
Target: agree before pilotEstablish a manual baseline, agree acceptance thresholds with the operational owner, and compare review effort as well as accuracy. Any benefit must be measured in the pilot; no savings or ROI are promised here.
Deployment plan
Obtain safeguarding and privacy review before selecting a gate-only pilot. Inform the school community appropriately, validate arrival and dismissal samples, and appoint a trained duty reviewer.
- Scope: name the owner, permitted inputs, reviewers, and acceptance criteria.
- Prepare: assess edge, on-premises, or approved hybrid compute, storage, power, and network capacity with representative streams.
- Validate: compare with human-labelled samples, exercise denied access and outages, and document rejected results.
- Decide: approve a limited rollout only after review; keep a rollback owner and re-evaluate when inputs change.
Existing CCTV and infrastructure
Inspect gate visibility, seasonal sunlight, student-height coverage, and separation from learning systems. Mask nearby homes and exclude toilets, changing rooms, and private counselling spaces.
| Check | Required evidence |
|---|---|
| Source access | Authorized stream, codec, resolution, frame rate, recorder connection limit. |
| Scene quality | Day, night, occlusion, and missing-frame samples from the selected zone. |
| Compute & recovery | Concurrent decoding benchmark, storage budget, clock sync, outage fallback. |
Existing CCTV may be reusable after compatibility assessment, not by default. Inventory codecs, resolution, frame rate, authorized stream protocols, recorder limits, time synchronization, and sample quality. Benchmark concurrent decoding and models before sizing hardware.
Integration planning
01
Approved source
02
Scoped processing
03
Human approval
04
Controlled export
Example: provide aggregate gate observations to the facilities duty log. Do not connect observations to pupil records, grades, or disciplinary systems.
These are example integration plans, not live connectors. Confirm schemas, least-privilege credentials, delivery acknowledgements, retry limits, and duplicate handling in a sandbox before enabling data exchange.
Security and privacy
Use the minimum data necessary for a specific safeguarding purpose. Restrict access to trained staff, set short justified retention, and prohibit automatic discipline or child profiling.
Least privilege
Approve reviewer roles and test a denied-access case before launch.
Data lifecycle
Set retention, deletion ownership, and encryption for stored and transmitted evidence.
Accountable operations
Log access and decisions; rehearse incident escalation and rollback.
Before launch, approve purpose and lawful access, role-based permissions, encryption configuration, retention and deletion rules, audit logging, and incident ownership. Verify these controls in the chosen environment; this page does not claim compliance certification.
Hypothetical pilot example
HYPOTHETICAL PILOT
One bounded question. Evidence before expansion.
Hypothetical pilot: duty staff tally gate congestion on ordinary and rainy dismissal days. Review umbrella-related misses and parent feedback before deciding whether the limited view should remain in use.
A proposed evaluation exercise, not a deployed case study. There are no named clients, claimed results, or implied endorsements.
Frequently asked questions
Is this an attendance system?
No. Anonymous gate counts cannot establish which pupil attended school.
Can classrooms be added by default?
No. A new purpose and safeguarding assessment are required; this pilot is limited to approved shared spaces.
Who can see clips?
Only explicitly authorized trained staff under a documented access and retention policy.
Plan your next step
Bring an authorized camera inventory, representative scenes, and one operational question. Prepare a planning brief, then validate sizing assumptions with a scoped pilot.