> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/getting-started/implementation/earned-value.md).

# Earned Value

The concept of Earned Value is measuring value that a project has earned towards its major goals measured against planned progress and budget consumption.

Typically, value is attained based on major tasks within phases. These tasks are given a numerical "weight" as is the phase as a whole.

For example, the first build phase could have a total weight for the phase of 10 made up of weights of:

* Configuration (4)
* 3D modeling (4)
* UI/UX, eComm, Outputs (2)

The total of all phases weights will equal 100.

As each task is fully completed, you will recognize the value for that tasks.

There is a correlation between the value earned to date and the budget expended to date. Typically, budget consumed to date should track closely to earned value but there will be times within phases where EV will lag behind budget consumption until the value is recognized once the main tasks are completed. Once value is recognized, EV and Budget should be tracking closely once again.

[Earned Value Template](https://docs.google.com/spreadsheets/d/1RUBbcSUa46YNHwpbFZ1pxj1Ry3_KNfjpS-JN9uGJdls/edit?usp=sharing)


---

# 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://community.threekit.com/getting-started/implementation/earned-value.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.
