Sentinel ID deployment planning
Agree the infrastructure and pilot scope before committing to production capacity, specialist hardware or integration delivery.
Deployment requirements
- Agency-controlled hosting and protected database/storage.
- Approved biometric, camera and field inputs.
- Defined agency, unit and role policies.
- Representative capacity, accuracy and recovery validation.
- Agreed training and support responsibilities.
Pilot and implementation
Discovery: confirm the users, scope, source systems and success criteria.
Configuration: provision access, register inputs and prepare the intended workflows.
Pilot: test representative cases, failures and the acceptance criteria.
Handover: train the responsible staff and agree support, recovery and maintenance.
Acceptance criteria
- Protected records reject unauthorised roles.
- Device and agency boundaries remain enforced.
- Matches and false matches receive review.
- Evidence retains source context.
- Field and alert workflows pass representative tests.
- Recovery and audit checks succeed.
Training and support
- Administrator setup and account/access management for Sentinel ID.
- Operator training using the product’s own workflow and representative data.
- Integration, backup and recovery handover for the responsible technical staff.
- An agreed support scope, escalation route and change-control process.
Commercial scope
Request a separate Sentinel ID quote. The agreed scope should list software rights, deployment, users, data sources, hardware interfaces, training and support. Third-party services, hardware, taxes, travel, ongoing infrastructure and optional integration work must be explicitly included or excluded. No price, deployment date or capacity guarantee is implied by this overview.
Frequently asked questions
Does a candidate prove identity?
No. Review the candidate with the underlying evidence.
Are government databases connected automatically?
No. External sources require an authorised configured integration.
Are the other products included?
Sentinel Assure, Sentinel SiteGuard and Sentinel SkyWatch are separate products.
Where is the full technical detail?
The existing feature, field app, security, deployment and documentation pages remain dedicated to Sentinel ID.
Does a planner guarantee capacity?
No. Planning assumptions require representative benchmarks.
How are commercial terms agreed?
Use a Sentinel ID-specific scope covering the intended deployment and integrations.
A demonstration for your workflow
Discuss Sentinel ID with your team and agree the relevant scope, input sources, deployment, training and support.