> ## Documentation Index
> Fetch the complete documentation index at: https://docs.realtimelca.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Reports
> Generate a formatted LCA report from the project's current state.
Reports turn the project into something you can hand over. The **LCA Report** is a PDF — cover, methodology, project parameters, results, the charts behind them, and the EPDs the calculation used — and depending on where the project is, there are **Excel reports** alongside it.
Open **Reports** in the project rail.
**Open** starts the report builder. Anything you have generated before is listed underneath, so a report you have already issued stays reachable.
## What you can generate
Which reports appear here depends on the project's **country**. Every project gets the **LCA Report** PDF. On top of that, projects get the **Excel reports** their country's scheme or authority expects — so a project in one country offers a different set from a project in another.
The country is set when the project is created and [fixed for its life](/user-guide/project/create-new-project), so the reports available to a project never change.
The PDF is the readable deliverable; the Excel reports are the machine-readable ones, in the layouts a scheme or authority asks for. Where a submission expects a specific spreadsheet, use the Excel report rather than transcribing figures out of the PDF.
## The builder
**Pages** on the left walks through the document; the preview shows exactly what will print. Along the bottom sit the three things that apply to the whole report:
| Control | What it does |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **Mapping incomplete** | A warning, not a block. It means some of the inventory has no data behind it, so the figures in the report are partial. |
| **Has editable content** | Marks the pages that take your input — a logo, a description, a photo, notes. |
| **Language** | The language the report is written in. |
**Download PDF** produces the file.
A report generated while mapping is incomplete reports the project as it stands, not as it will be. Check the [mapping overview](/user-guide/project/project-dashboard#mapping-overview) before issuing one to a client.
## What is in it
The **Cover** carries the project name and the headline LCA result, and takes your **client logo**. The **LCA** page is the contents list plus a plain-language explanation of what a life-cycle assessment covers — useful when the report goes to someone who does not read LCAs for a living.
**Overview** is the one to spend time on. The **project description** is yours to write, there is a slot for a **building render or photo**, and the QA/QC fields record who checked the calculation and when. **Included LCA modules** shows at a glance which stages the result covers.
**Results** states the calculation method and every project parameter behind the number — consideration period, areas, energy supply, standard values — then the total against the limit value and the same splits you see on the dashboard.
**Additional Results** carries the ranked impacts and the cumulative curve, each with a **note box** beside it. Those notes are where a report earns its keep: the chart shows what happened, your note says why it matters and what you recommend.
**Background Data** documents what the numbers rest on: the standard values in use, and every EPD referenced by the project's materials with its declaration number. This is the page an auditor turns to first.
## Reports and revisions
A report is pinned to the [revision](/user-guide/project/revisions) it was taken from — it names that revision and version, and is listed while the project is on, or previewing, that revision.
Save a revision before generating a report you intend to send. The revision is what lets you come back months later and reproduce exactly the figures the report contains.