> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/operate/dynamic-exit-zoning.md). # Dynamic exit zoning Dynamic Exit Zoning lets an operator assign a single cardholder, typically **a bus carrying passengers**, to a door, so the door's **Exit Access Zone** automatically updates to match that cardholder's (the bus's) current location. It is compatible with **Tag Boards** and **Evacuation Reporting** for staff safety, and is built for mine sites bussing workers to work areas. ## How it works The door's Exit Access Zone follows the assigned cardholder (the bus). This removes the need for cardholders to badge at a fixed reader at their work location after exiting the bus. It is ideal when workers enter a large geographic work area through a gateway (for example Nedap tag-reading technology) with no guarantee of a hardwired reader at the exact bus-stop location. ## Use case Mine sites transporting workers to and from work areas by bus (30-minute-plus trips). Buses are equipped with Gallagher hardware (a controller plus Entry and Exit Readers) and network capability (a 3G/4G router). The cardholder badges entering and exiting the bus; the bus itself registers zone changes via its **Nedap tag** at primary entry-control points. **Versions supported:** v8.10 to v8.80. *** 🔗 **Related** * [Nedap](/knowledge-hub/products/integrations/third-party-readers/nedap.md). The Nedap tag technology used at entry-control points. * [Dual Authorisation Enhancement](/knowledge-hub/products/cc-software/operate/dual-authorisation-enhancement.md). Another Access Management Solutions feature. --- # 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://help.security.gallagher.com/knowledge-hub/products/cc-software/operate/dynamic-exit-zoning.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.