> 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/training.md).

# Training

Training helps members prepare for real work, guild participation, safety requirements, and broader responsibility. Course completion is evidence of learning; it is not an automatic token mint, rank promotion, job placement, or fixed payment promise.

## Learning paths

Training may include:

* platform and wallet onboarding;
* project, construction, and workplace safety;
* trade and technical foundations;
* project delivery, documentation, and review;
* leadership, mentorship, and conflict resolution; and
* governance and operating-policy orientation.

Each course should identify its owner, intended audience, prerequisites, evidence, assessment method, expiration or renewal rule, and whether an external credentialing body is involved.

## Completion evidence

A completion record can contain the course version, learner, assessor or issuing provider, date, evidence reference, score/result where appropriate, and expiration. The dashboard should distinguish:

* enrolled;
* in progress;
* submitted for review;
* completed;
* externally verified;
* expired; and
* revoked or corrected.

Private assessment material and personal records remain access-controlled off-chain.

## Relationship to membership and guild merit

Training may support a later rank or guild-merit case, but the decisions are separate. Rank changes require the membership review and authorized DAOMembershipNFT action. Guild merit requires the applicable guild and MERIT\_ISSUER action. Neither follows automatically from clicking complete.

## Relationship to Contribution EQTBLT

Task-based training earns Contribution EQTBLT when it is explicitly approved as qualifying contribution under the current class and rate policy, supported by evidence, settled through an authorized funded ProjectFlow release, and confirmed on-chain. Eligible first-month learning steps and event check-ins instead follow their own source records and reward policies; a standalone course is not automatically one of those steps. See [Earning EQTBLT](/guides/earning-eqtblt.md). There is no universal course reward table or guaranteed number of EQTBLT.

If a course is purely educational, required for eligibility, externally paid, or already compensated under another agreement, it may produce no EQTBLT at all.

## Dashboard requirements

Training pages should:

* show the current course version and owner;
* state whether the course itself is unpaid, separately compensated, or potentially eligible for evidence-backed contribution;
* avoid displaying a guaranteed token amount;
* record review evidence and corrections;
* show pending versus confirmed credential or issuance actions; and
* keep resource authorization separate from contract authority.

## Safety and professional credentials

Built By DAO training does not replace a license, union requirement, apprenticeship registration, OSHA requirement, regulated certification, or employer-specific instruction. The project owner must verify the credential actually required for the task and jurisdiction.

## Continue

* [Contributing](/contributors/contribute.md)
* [Tasks](/operations/tasks.md)
* [Membership Progression](/membership/progression.md)
* [Guilds](/membership/guilds.md)
* [Earning EQTBLT](/guides/earning-eqtblt.md)


---

# 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/training.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.