> ## 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.
# History
> Every change to a project, as a version you can restore.
Real-Time LCA records every change made to a project — base information, materials, and mappings — as a **version**. Nothing is lost: you can see who changed what, and turn any point back into a working project.
Team changes are logged here too, but for reference only — they are not versions and cannot be restored. Exported [reports](/user-guide/project/reports) are listed the same way: each names the revision and version it was taken from, and appears while the project is on, or previewing, that [revision](/user-guide/project/revisions).
## Finding a change
The chips narrow the log to **Base info**, **Materials & models**, **Mappings**, **Team**, **Reports**, or **Revisions**. Search matches the change description, the date filter limits the range, and **Export** downloads the log.
Each entry carries its version number, what changed, who changed it, when, and where it came from — *In-app*, *Service*, or an integration. The version the project is currently on is badged **Current**.
## Restore a version
**Restore** on any entry does not overwrite your project. It creates a *new* project holding the materials and project information as they were at that version, along with transport and waste mappings, custom emission factors, and the history up to that point.
Name the copy, then choose what happens to the 3D model connection:
| Option | Result |
| ------------------------ | ----------------------------------------------------------------------------------- |
| **Use the same project** | The copy stays connected to the same Speckle project, so the same models feed both. |
| **Create new project** | The copy gets its own Speckle project. |
The original project is left exactly as it was.
Restoring is for recovering work or branching from a past decision. To copy the project *as it is now*, use [Clone](/user-guide/project/clone-project) instead — it also brings the team across.
## Marking a version worth keeping
Any version in the log can become a named **revision** — a save point the project can be moved between. Open the **⋮** menu on the entry and choose **Save as revision**.
The **Revisions** chip at the top of this page switches the view to the revision list, where you save, preview, and move between them. See [Revisions](/user-guide/project/revisions).