> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/setup/cookbook/closure.md). # Closure ## Pilot Closure and Hand-Off Closure is not just turning the lights off. It is the moment the country team formally takes ownership of MOSIP and decides what to keep, what to redo and what to scale. The closure activities below are a structured way to make sure no lesson learned in the pilot is lost in the transition. ### Formal closure * Inform the country authorities, in writing, that the pilot has been completed. * Generate the formal pilot reports from the reporting console --- registration, authentication, exceptions, dashboards. ### Capturing field experience * Interview every registration field operator and supervisor; record their experience in their own words. * Interview the country technical leads and program managers. * Hold a closure meeting with the MOSIP team to discuss outcomes, surprises and recommendations. * Send a formal pilot closure report to the MOSIP team. ### Closure deliverables * Registration metrics: total registered, breakdown by demographic group, on-line vs off-line split, biometric exception rates, average registration time per kit. * Authentication metrics: OTP and biometric success rates, helpdesk incident counts. * Lessons-learned register, captured weekly across the pilot. * Configuration baselines: ID schema, master data, customisation diff, infrastructure footprint as actually deployed. * Recommendations for scale: sizing, integrations, capacity, governance. * Final sign-off from the Pilot Governance Committee. {% hint style="info" %} **Cost note** The pilot platform is provided at no cost (open source). The country invests in infrastructure, country-side hardware, gateways, personnel and travel. Production costing for a national rollout is a separate exercise and is not represented by the pilot footprint. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mosip.io/1.2.0/setup/cookbook/closure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.