> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/project-manual/project-coordinators.md).

# Project coordination

This section explains how CorrelAid projects are coordinated and describes the relevant processes. The content is relevant for project coordinators and project leads.

Those pages contain information for project coordinators and project team leads.

**Project coordinators** are most important at the first stages of a project, from the first contact of the organization with CorrelAid up until a team has been formed and it has started working. During the project work phase, the project coordinator gets updates from the project team to ensure that the project is running smoothly. After the project has been successfully implemented, the project coordinator is responsible for the follow-up with the organization and the project team.

The **project lead / team lead** ideally gets involved from the team selection process onwards. They are part of the project team but also have some additonal responsibilities related to team coordination, communication with the NPO and other organizational tasks.

{% hint style="info" %}
Want to become a project coordinator? Write <projects@correlaid.org> an email.&#x20;
{% 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 by asking a question.

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

```
GET https://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/project-manual/project-coordinators.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.