> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/contributors/tasks.md).

# Tasks & Rewards

Tasks are scoped units of work in the dashboard. A task should identify its owner, project, expected outcome, evidence type, reviewer, due state, and whether an approved contribution-credit settlement path applies.

## Lifecycle

1. A scoped project lead creates and publishes the task.
2. An eligible member claims or is assigned the work.
3. The member submits the required evidence, such as a link, file, or attestation.
4. The reviewer approves, requests changes, or rejects with a reason.
5. If the task qualifies for contribution credits, the authorized funded ProjectFlow lane prepares settlement.
6. EQTBLT appears only after the contract transaction confirms and the event is reconciled.

Task completion never guarantees a fixed number of credits. The work class, policy rate band, evidence, standing, role, available project custody, and confirmed execution all apply. Some tasks are unpaid orientation, volunteer activity, separately compensated work, or ineligible for EQTBLT.

## Dashboard controls

Task creation, assignment, review, and settlement are resource-scoped. A project lead cannot mutate another project, a reviewer cannot approve their own unsupported work, and a shared super-admin fixture is not a substitute for the intended persona. Notifications and audit history preserve every state change.

See [Earning EQTBLT](/guides/earning-eqtblt.md), [Training](/contributors/training.md), and [ProjectFlow](/developers/contracts.md#flowtreasurer).


---

# 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.builtbydao.com/contributors/tasks.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.