Roadmap
1. Introduction
The OpenCRVS roadmap provides visibility into planned features and release timelines. This helps implementation partners, governments, and the OpenCRVS community plan their implementations and understand when specific capabilities will become available.
The roadmap is primarily determined based on confirmed system requirements coming from current and future OpenCRVS implementations, ensuring that development priorities align with real-world needs.
2. Release Schedule
The following table provides an overview of projected delivery dates for future releases.
Release
Beta release date
Full release date
v2.0
30 April 2026
25 June 2026
v2.1
Late August 2026
Late September 2026
Release types
Beta release — 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.
Full release — Production-ready release that has passed full regression testing and is ready for live use.
📆 Dates are indicative
All dates provided are subject to change, however OpenCRVS Product Management makes every effort to provide accurate estimates to support implementation planning.
3. Future product scope
Future releases are expected to evolve based on implementation feedback, country priorities, and emerging technical or regulatory requirements. The items outlined in this section represent potential areas of enhancement and should be treated as indicative rather than committed scope.
Workflow Configuration
Enable configurable form fields on core actions and and provide greater control over record flag management during notification workflows
Notification Management
Add notification-based filtering to scopes, enabling records to be filtered by where notifications were issued and by the user who issued them
Platform Modernisation
Modernise the platform by removing deprecated components and improving long-term maintainability
Versioning of Administrative Structure and Locations
Allow administrative boundaries and locations to change over time without affecting the accuracy of existing civil registration records
Protected Records
Allow sensitive records to be marked as protected, making them hidden from standard searches and accessible only to authorised users.
4. How Roadmap Priorities Are Determined
Roadmap priorities are informed by:
Requirements from active country implementations
Feedback from implementation partners
Community feature requests
Strategic product objectives
Technical platform improvements
5. Influence the Roadmap
Get in touch via OpenCRVS GitHub Discussions to share your priority feature requests.
Your input helps us:
Prioritise features that solve real-world problems
Understand use cases that drive design decisions
Align releases with implementation timelines
Build capabilities that work across different country contexts
6. Stay informed
To stay up to date with OpenCRVS releases and roadmap changes:
GitHub Discussions — Follow feature request discussions and provide feedback
Release notes — Review detailed release notes for each version
Last updated