> 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/product-specifications/core-functions/6.-search-for-a-record.md). # 6. Search for a record Civil registration systems must be able to store, file, archive and retrieve records. OpenCRVS enables users to search by a number of different criteria, reducing the search scope for a better user experience. ### **Pre-condition** A record exist in the system with the status 'Notified', ‘Declared, ‘Validated’, ‘Archived’, ‘Registered’ ### **Triggers** * A user `scope:search[event=event]` can search for all event records * A user `scope:search[event=event my-jurisdiction]` can search for event records only in their jurisdiction ### **Standard flow** 1. User enters in search query eg. Tracking ID, Registration No. National ID, Phone number 2. If user has a connection then the system will process the search query 3. Any results are displayed ### **Post conditions** * User can then choose to assign themselves to the record and complete the required action * User can choose to view the record audit for the record * User can choose to view the record (read only) ### **Variations/Exceptions** If the user does not have a unique identifier such as a tracking ID or registration no. then they can use **Advanced search**. Advance search lets you search for a record by: * Record status eg. Registered or Issued * Place of registration * Date of registration * Using different event parameters configured to be searchable. eg. Child, Mother or Fathers details {% 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 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://documentation.opencrvs.org/product-specifications/core-functions/6.-search-for-a-record.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.