> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.4/product-specifications/core-functions/5.-issue-certificate.md). # 6. Issue certificate As a legal document, it is important that we track that the vital event certificate has ben issued to the informant so that there is a log of this action having occurred. OpenCRVS allows certificates to be printed off in advance of collection to support Registration Office practices where there is a certificate collection on a specific day of the week for informants. Certificates printed off in advance show in the Ready to issue workqueue so that on collections the Registrar or Registration Agent can log that the certificate has been issued. ### **Configuration options:** * Enable/disable printing off in advance of issuance ### **Pre-condition** A record is in the Ready for Issue workqueue with the status ‘Certified’ ### **Triggers** Informant has come to the Registration Office to collect their certificate which has been printed off in advance ### **Standard flow** 1. Registrar or Registration Agent navigates to the Ready to Issue workqueue 2. User assigns themselves to a record 3. Record is downloaded and is now available to be issued offline 4. User clicks “Review” 5. User selects who is collecting the certificate 1. For a birth record this could be the Mother, Father or Informant 2. If Someone else is collecting the certificate. Then the user captures their details. 6. User checks the collectors ID against the details captured in the record 7. User confirms the collectors proof of ID match 1. If they don’t the user is warned that by proceed, they will be responsible for issuing a certificate without the necessary proof of ID from the collector 8. User is prompted to collect payment if fess are required (based on system configuration) 9. User clicks “Issue” 10. User is navigated back to Ready to issue workqueue 11. Record is sent to the Outbox for processing 12. Once processed the record status is updated to ‘Issued’ ### **Post conditions** * Record is removed from all workqueues but can be search for using tracking id, reg no. etc. * Record audit is updated to show that the record has been ‘Issued’ {% embed url="" %} --- # 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://documentation.opencrvs.org/v1.4/product-specifications/core-functions/5.-issue-certificate.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.