> 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/v2.0/implementation/your-opencrvs-project.md).

# Your OpenCRVS Project

### 1. Introduction

This section is your guide to implementing OpenCRVS in your country — from the first planning conversations through to running and improving the system in production.

It is organised as a sequence of stages. If you are at the start of your journey, work through them in order; if you are already underway, jump to the stage you are in. Each stage page explains what it involves, what you need to begin, and what it produces for the next stage.

{% hint style="info" %} **Where to start:** if you are beginning a new implementation, start with [Project planning](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/project-planning) and [Establish project & team](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/establish-project-and-team). Everything else builds on those foundations. {% endhint %}

***

### 2. The implementation journey

A typical OpenCRVS implementation moves through five broad phases: **plan and prepare**, **understand and design**, **build**, **launch**, and **run and improve**.

**Plan and prepare**

* [Project planning](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/project-planning) — agree the scope, timeline, budget and approach for the implementation.
* [Establish project & team](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/establish-project-and-team) — identify the roles and skills needed to set up, configure, run and sustain OpenCRVS.

**Understand and design**

* [Gathering requirements](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/gathering-requirements) — collect and prepare the inputs for an optimal configuration, through desk research, field research, co-design and design & specification.
* [Solution architecture](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/solution-architecture) — decide how OpenCRVS fits into your country's wider, interoperable digital ecosystem.

**Build**

* [Configuration](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/configuration) — turn the signed-off configuration inputs into a working system.

**Launch**

* [Deployment](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/deployment) — set up the servers and environments and deploy OpenCRVS.
* [Migrate legacy data](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/migrate-legacy-data) — bring existing civil registration records into OpenCRVS.
* [Quality assurance](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/quality-assurance) — test the configured system against the requirements before go-live.
* [Go-live](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/go-live) — launch OpenCRVS into production use.

**Run and improve**

* [Operational support](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/operational-support) — keep the system running and support users day to day.
* [Monitoring](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/monitoring) — track performance, usage and registration outcomes.
* [Upgrading](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/upgrading) — keep OpenCRVS up to date with new releases.

***

### 3. Who you need

Implementing OpenCRVS is led by a small, multidisciplinary team that grows with the scope of your work — a proof of concept may need only a couple of core roles, while a national programme draws in technical, design, change-management, training and monitoring roles. See [Establish project & team](https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs/establish-project-and-team) for the full set of roles and how to size your team.

{% hint style="info" %} **Embed your own people.** Wherever an implementing partner supports the work, include government staff throughout. Their knowledge keeps the implementation grounded, and their involvement is what makes the system sustainable after handover. {% endhint %}


---

# 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:

```
GET https://documentation.opencrvs.org/v2.0/implementation/your-opencrvs-project.md?ask=<question>
```

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.