> 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/functional/markdown/events.md).

# Events

## Overview

As part of the **Functional Architecture**, the **Events** section describes the events module in OpenCRVS — how different civil event types are modelled and configured.

It is organised into the following modules:

* **Types** — describes how event types (for example, birth, death, marriage) are defined and linked to forms, statuses, actions, and outputs.
* **Business Rules** — shows how legislation and policy are translated into configurable rules that control which actions are available, when declarations become late, when approvals are required, and related behaviour.
* **Forms** — explains how event forms are configured to capture Notify/Declare, Correct, and other action data, including pages, fields, validations, and evidence uploads.
* **UINs** — describes how unique identifiers (for example, Tracking ID, Registration number, National ID integration) are generated or captured for events and how they are used across workflows and search.

Together, these modules show how to configure each event type so that it reflects national law and policy while using a consistent model across OpenCRVS.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.opencrvs.org/v2.0/functional/markdown/events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.