Geye / Industry playbookCounter demand
Renewal deadlines bring several service types into one hall.
Geye / Industry playbook
Government
Plan auditable visual workflows for public facilities, queues, and controlled areas.
Planning guidance, not a claim of installed capabilities or customer results. Validate scope and feasibility before deployment.
Industry overview
Public-service facilities need transparent, accessible operations at counters and shared entrances. Aggregate queue and occupancy review can inform service design without linking visits to benefit eligibility or citizen identities.
Inclusive access
A queue can spill into the route used by visitors with mobility aids.
Staff entrances
Public opening hours and staff access schedules may differ.
Use cases
01
Counter demand
- Context
- Renewal deadlines bring several service types into one hall.
- Human action
- Review service-counter queues by time window.
- Intended outcome
- An aggregate service-window comparison without citizen records.
02
Inclusive access
- Context
- A queue can spill into the route used by visitors with mobility aids.
- Human action
- Observe obstructions along accessible public routes.
- Intended outcome
- An accessibility inspection before queue guidance changes.
03
Staff entrances
- Context
- Public opening hours and staff access schedules may differ.
- Human action
- Review activity at approved staff-only entrances.
- Intended outcome
- A purpose-limited access review under the facility policy.
AI vision capabilities
Read the scene, retain the context
Evaluate queue counts, zone occupancy, and time-bounded entry events. Mixed service queues and visitors using mobility aids require inclusive validation; observations must not classify citizen status.
Evidence contract
Keep zone, source timestamp, and view availability together. A stale frame must not become a current event.
A person owns the decision
An aggregate service-window comparison without citizen records.
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: a document-service queue extends across an accessible corridor. A service supervisor validates the obstruction and adjusts queue guidance while preserving accessible access and service order.
- 01
Context
Renewal deadlines bring several service types into one hall.
- 02
Review trigger
A candidate observation in the selected zone requires confirmation against current conditions.
- 03
Human response
Review service-counter queues by time window.
- 04
Intended result
An aggregate service-window comparison without citizen records.
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
Set acceptance thresholds for accuracy, retention, accessibility, and incident review.
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
Choose one public service hall, document the public purpose and accountable owner, and involve accessibility and records officers. Test busy renewal periods and a network-outage exercise before expanding.
- 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
Inventory camera ownership, procurement constraints, record retention systems, and segmented network access. Check that service forms and identity documents are not readable within the proposed view.
| 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: publish approved aggregate queue intervals to an internal service-performance report. Agree records classifications and export approval; no connection to citizen case files is assumed.
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
Separate facility observations from citizen records, immigration status, and benefit decisions. Require purpose-limited access, auditable exports, and a documented process for access requests and deletion obligations.
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: compare service-hall counts with manual samples during a renewal deadline. Have accessibility and records reviewers examine both errors and data handling before approving any additional hall.
A proposed evaluation exercise, not a deployed case study. There are no named clients, claimed results, or implied endorsements.
Frequently asked questions
Can it affect benefit eligibility?
No. Facility signals must remain separate from eligibility and citizen case decisions.
Is a compliance certification included?
No certification is claimed. The institution must assess applicable requirements and approve the design.
Can summaries be published publicly?
Only after authorized review of aggregation, re-identification risk, and records obligations.
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.