# Co-Design & Validation ## Purpose This phase emphasises **collaboration with CRVS stakeholders to validate findings, align on priorities, and co-create future service models**, all through co-creation sessions and workshops. The aim is a unified, evidence-backed vision for CRVS service delivery. Key tasks include **translating challenges into a validated scope**, **drafting prioritised features**, and **establishing technical groundwork**. This ensures innovative, viable models **aligned with stakeholder needs**, **reducing risks and ensuring smooth system implementation**. ## **Objectives** 1. **Vision for future CRVS Service Delivery Models (SDMs):** workshops refine the CRVS system by tackling inefficiencies. They clarify roles (e.g., registrars, statistics offices), citizen interaction methods (e.g., in-person, online), and procedures for life events (births, deaths, marriages), ensuring stakeholder alignment in CRVS operations. 2. **Detailed scope and feature epics:** the collaborative process identifies problems and defines actionable development tasks, resulting in a clear scope and prioritized feature epics. This guides the design team to focus on solving critical issues and delivering high-value features for the CRVS system. 3. **Finalised user roles, office hierarchy, and integration requirements:** establishes administrative/technical groundwork, defining office hierarchy & user roles (who, what, where, when) for system setup. Specifies integration use cases/requirements for data exchange between the CRVS system and other systems like National ID and Health, ensuring technical viability and interoperability. ## **Key Outputs** **CRVS Business Objectives**: enhance civil registration by aligning stakeholders with a unified vision. It links system upgrades like digitisation to improved services, inclusion, and reliable statistics. This is done via workshops to review, co-create, and prioritise objectives, culminating in documented goals for leadership endorsement to ensure commitment and informed decision-making. **Validated as-is business processes (bottlenecks & barriers)**: create a shared, evidence-based understanding of current registration processes, identifying challenges like inefficiencies, inequities, and access barriers. Map full registration journeys with diverse stakeholders to inform high-impact reform priorities. **Key insights & priority problems to solve:** transform discovery findings into priorities, aligning decision-makers on citizen barriers. It bridges research and action, setting a design mandate by: synthesising evidence into themes, using validation techniques, sharing stories, and collaboratively establishing concise problem statements for solution design. **OpenCRVS scope & features prioritised:** balance citizen and government value with feasibility to optimize resources. Use collaborative methods like MoSCoW and value/effort matrices to prioritise features by social, legal, and statistical value, ensuring an aligned roadmap with clear milestones. **Future Service Delivery Models (SDMs):** SDMs promote innovative, citizen-focused civil registration, beyond mere improvements. They envision adaptable systems for demographic and technological changes, centred on life events. This involves scenario planning (e.g., mobile-first), service design (e.g., journey maps), rapid prototyping, and blending global best practices with local needs for shared accountability. **Admin Structure & Office Hierarchy maps:** clarify roles and align digital solutions with staff needs. Clarify and define responsibilities for decisions, data, and reporting through cataloging offices, user roles, and reporting lines, validated with stakeholders. **New Service Concept Epics:** enhanced versions of Service Design Maps (SDMs) providing stakeholders with a concise, high-level view of new services geared towards fulfilling citizen needs and addressing service gaps. They outline the vision by defining the problem, illustrating use cases, outlining current challenges, presenting a summary in an epic statement, and setting forth initial design and development principles. **Integration use-cases:** crucial for new digital CRVS solutions to exchange data seamlessly with external systems (health, ID). This avoids data silos, reduces redundancy, and ensures compliance. The process involves system mapping, identifying connection points, defining exchange scenarios, and validating them with officials and IT teams for practical needs and security. --- # Agent Instructions: 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: ``` GET https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/gathering-requirements/co-design-and-validation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.