> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/notices/end-of-life-migration/access-control-system-migration-and-planned-service-impact.md). # Access Control System Migration and Planned Service Impact Frequently Asked Questions (FAQ) **Q. What are the project dates?** The biometric reader replacement project is scheduled for the week commencing 24 August 2026. Should these dates change, Colt will provide further communication to customers, employees and contractors. **Q. Will I receive a new access badge?** Yes. All customers, employees and contractors will be issued with a new Colt access badge and adhesive badge overlay. **Q. Do I need to complete any paperwork?** No. **Q. Will I need a new photograph?** If you currently hold an access badge, no new photograph is required. New badge applicants will need to submit a photograph through the Customer Portal as part of the application process. **Q. Will I need to re-enrol my biometric data?** Yes. All badge holders using facilities equipped with biometric readers will need to enrol their fingerprint on the new biometric system to continue accessing those facilities after the upgrade. **Q. When can I enrol my biometric information?** Appointments will be available from week commencing 24 August 2026 during normal business hours, Monday to Friday. To arrange an appointment, please contact the Colt Access Team: Email: \ Phone: +44 330 060 8457 **Q. How long does enrolment take?** Biometric enrolment typically takes no longer than 10 minutes. **Q. Do I need to keep my existing Lumen badge?** No. Your existing badge must be surrendered when your new Colt badge is issued. **Q. What if my access permissions appear incorrect?** Please contact the Colt Access Team, who will investigate and confirm the appropriate access level for your account. **Q. Who should I contact if I experience a badge or access issue?** Please contact the Colt Access Team: Email: \ Phone: +44 330 060 8457 **Q. Do I need to display my badge while on-site?** Yes. Permanent and temporary badges must be worn visibly at or above waist level at all times while within the facility. All badges remain the property of Colt and must be returned upon request. Badges must not be altered or modified in any way that affects their visibility, readability or function. **Q. Can I share my badge with another person?** No. Badge sharing is strictly prohibited. Tailgating, where an individual gains entry by following another authorised person through a secured access point, is also prohibited. **Q. What should I do if my badge is lost or stolen?** Report the loss immediately to the Colt Access Team during UK business hours so the badge can be disabled without delay. **Q. How do the biometric readers work?** Colt uses fingerprint readers as part of a dual-authentication process to enhance facility security. The system stores an encrypted biometric template on the access card itself. No fingerprint images are stored within the access control database. When access is requested, the biometric reader compares the encrypted template stored on the badge to the fingerprint presented at the reader. Access is granted only when a valid match is confirmed. **Q. How does Colt protect personal information?** Colt maintains physical, electronic and procedural safeguards that align with industry standards to protect personal information held within its access control systems from unauthorised access, use or disclosure. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.colt.net/notices/end-of-life-migration/access-control-system-migration-and-planned-service-impact.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.