> For the complete documentation index, see [llms.txt](https://help.canoa.supply/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.canoa.supply/docs/support/faqs/how-does-the-carbon-estimator-work.md).

# How does the carbon estimator work?

Our Carbon Estimator shows the sum of embodied carbon in metric tons of CO2 emitted.

{% embed url="<https://www.youtube.com/watch?v=RGAjyFKQN2E>" %}
Watch me :)&#x20;
{% endembed %}

Our Carbon Estimator shows the sum of embodied carbon in metric tons of CO2 emitted. Canoa does not over-ride anything that has a specific embodied carbon included from the owner of the product. Our carbon estimate is an estimate only, based on manufacturers available data, and in some cases, our own calculations of categorical averages.&#x20;

When designing with second-life furniture and adding a [<mark style="color:purple;">**Dashboard**</mark>](/docs/design/how-to-use-dashboards.md) to your Canvas, you will be able to see the carbon estimator and track the percentage of second life items included in your project. Pre-owned furniture are all considered net zero. So designing with second-life items in your projects has a great impact on reducing your carbon estimates.


---

# 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://help.canoa.supply/docs/support/faqs/how-does-the-carbon-estimator-work.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.
