> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/pbms/functionality/program-management/program-life-cycle.md).

# Program Life Cycle

A program is a scheme created to assist an individual/group to avail benefits given by the government of their country. An Individual/group must undergo sequence of verification process to avail the benefits.

* **Create a program:** A program manager or an administrator creates a program.
* **Configure managers:** A program manager configures the relevant manager to a program, such as eligibility managers, deduplication manager, notification managers, program manager, cycle manager, entitlement manager and payment manager.
* **Allocate fund:** A program manager allocates funds to a program
* **Activate a program:** In this phase, after the eligibility manager completes the verification process, an individual/group becomes eligible to enroll in a program and is referred to as a beneficiary. Once the program is activated for an individual/group, he/she can receive the allocated entitlements.
* **Close a program:** A program lifecycle ends for an individual/group after they receive the entitlements mentioned in their enrolled program are delivered to them. The benefits can be delivered in single cycle or multiple cycles depends on the program disbursement cycle.
* **Re-activate a program:** A program (scheme) ends after the entitlement reaches the individual/group. It can also be re-activated once the program managers invoke the program.


---

# 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://docs.openg2p.org/1.3/pbms/functionality/program-management/program-life-cycle.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.