# Product roadmap

## The OpenCRVS Use Case Inventory

We often get the question "What does OpenCRVS do?". Beyond the descriptions found in the [functional-architecture](https://documentation.opencrvs.org/v1.7/product-specifications/functional-architecture "mention") section, we maintain a full inventory of use cases, which will allow you to quickly map existing and future use cases supported by OpenCRVS with your own country requirements. 

{% file src="<https://2662731974-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvgBjh6h3DfeeMhA5gwiP%2Fuploads%2FNmcm6qiqFVC5QMjs4BmO%2FOpenCRVS%20Use%20Cases%20Inventory%20v1.7.0.xlsx?alt=media&token=19b17132-b662-4e59-b3c8-bc4095312526>" %}

In addition to the functional and integration use cases, a separate tab includes non-functional requirements (NFRs) that we believe are important for national scale civil registration systems, the majority of which OpenCRVS is already compliant with. &#x20;

## Future release dates

The following table provides an overview of projected delivery dates for future releases, as defined in the Use Case Inventory above.&#x20;

* The beta release is typically made available after initial QA testing, but before full regression testing has been commenced. It is not intended for live use in a production environment, however it allows accredited implementation partners to test out sample configurations and to contribute to the release testing effort.
* All dates provided are indicative and are subject to change, however OpenCRVS Product Management makes every effort to provide accurate estimates to support implementation planning.&#x20;

<table><thead><tr><th width="148">Release</th><th>Beta release date</th><th>Full release date</th></tr></thead><tbody><tr><td>v1.8.0</td><td>28 April 2025</td><td>21 July 2025</td></tr><tr><td>v1.9.0</td><td>05 September 2025</td><td>17 October 2025</td></tr><tr><td>v1.10.0</td><td>TBC</td><td>TBC</td></tr></tbody></table>

## Future product scope

The scope for future releases of OpenCRVS is primarily determined based on confirmed system requirements coming from current and future OpenCRVS implementations.&#x20;

Get in touch via [OpenCRVS Github Discussion ](https://github.com/opencrvs/opencrvs-core/discussions/categories/feature-requests)to share your priority feature requests.