Saving and opening Carbon Verify projects

Continue your current project in the same browser. Save a project file when you need a backup, want to change devices or work on another organisation.

What is saved, and where?

Save a portable copy

1. Check the organisation name and reporting period in the project bar.
2. Select Save project file. The app prepares a standard browser download.
3. Find the file in your downloads or the location you selected. The browser may ask where to put it.
4. Keep it in an appropriate organisation folder. Save a fresh copy after significant changes and before switching projects or devices.

A name such as Acme-Engineering_2025-10-01_2026-09-30_saved-2026-10-08_1430.carbonverify helps identify the organisation, period and save time. The app also records the organisation and period inside the file, so renaming it does not change the project.

The file retains your inputs, selected reporting mode, evidence references, assumptions, targets, review information and project-specific document appearance. It does not carry your licence activation or copies of documents referred to in the evidence log.

New projects start in Standard CRP · PPN 006. Turn on Extended footprint when you need wider supported coverage. Returning to Standard keeps wider entries saved but excludes only information outside its active scope. Checked other fuels, gases, purchased heat or steam, shipments and supplied figures within Standard's Scope 1, Scope 2 and five required Scope 3 categories can still contribute. The app asks you to review affected sections, baseline comparability and approval again; it does not silently rewrite a real baseline or target. See the current source routes.

Open a saved project

1. Select Open project and choose the saved file.
2. Check the organisation and reporting period shown in the preview, and read any compatibility message.
3. If your current workspace matters, save its project file before continuing.
4. Confirm the switch only when you are ready. Opening a project replaces the active workspace; it does not merge two organisations.
5. Check the restored organisation, figures, evidence references and review status before editing or producing documents.

Cancel if you selected the wrong file. A rejected or corrupt file should not replace your current work. Keep the original file untouched if an import cannot be completed, and contact support with the error message. Do not send a client file unless a suitable sharing arrangement has been agreed.

Start another organisation safely

Use New project, not an existing organisation with its name changed. Save the current project when prompted, continue without exporting only if you are sure, or cancel to stay where you are.

A new project starts empty. Add that organisation’s own reporting period, records, assumptions, targets and approvals. Choose its document branding separately. Your licence activation remains with the app; it is not part of the organisation’s file.

For several organisations, give each its own folder and dated project files. Open only one active workspace in the same browser profile at a time: separate tabs are not a safe way to isolate clients or collaborate simultaneously.

Move to another device

Save the latest project file and transfer it using a secure method appropriate for its contents. On the other device, open the CRP tool, arrange access within your purchased activation allowance, and use Open project. A file does not activate paid features or transfer a licence.

There is no cloud synchronisation between devices. Agree which copy is current, especially when handing a project to someone else. Keep the previous version until you have checked the new one.

Older backups and factor editions

Carbon Verify continues to accept supported, valid legacy .json backups. Choose the original backup through Open project; changing an unrelated file’s extension will not make it compatible. Preserve the original until you have checked the imported project and saved a new copy.

This release contains the embedded 2026 factor edition. Legacy files with an unsupported edition or a reporting period ending outside the supported year are blocked rather than silently switched to another year’s factors. Some older backups did not store the exact factor values: where one can be opened, the app explains that limitation and asks you to compare previously issued figures before relying on regenerated documents.

Supported projects keep their activity data when opened in this version. Older projects with additional inputs reopen in Extended footprint rather than silently dropping those inputs from the calculation. Read the compatibility message and check the restored reporting mode before issuing fresh documents.

Some older projects require a calculation-method migration. Carbon Verify's totals consistently use grid-based electricity, with an evidenced tariff result disclosed separately in Extended. Where a migration changes the calculation basis, the app withdraws affected reviews and approval: check the figures, baseline comparability and source coverage. Keep previously issued reports unchanged as the record of that earlier work.

A project must be read with a supported application format and factor edition. If Carbon Verify cannot safely restore it, follow the warning rather than assuming the newest factors produce the same historical result. Do not replace recorded factors just to get an older file to open.

Keep approved reports and their Evidence Pack alongside the dated project file. These provide a record of what was actually issued even if a future app version cannot reopen a particular historical edition.

Save work before and after document production

Stage 6, Reduction plan, holds targets, measures and approval. All document controls are in stage 7, Check & download, with the CRP and Evidence Pack prominent and draft/optional Statement controls in closed explainers. You do not need to create the separate Carbon Footprint Statement to save a project or produce a CRP. The declaration within the CRP remains part of that plan where required.

Save a working project before sending a draft for review, then save a fresh dated copy after changes and genuine approval. A draft is not a final plan. Evidence references are saved in the browser and project file; original records are not attachments. Nothing in a downloaded report changes when you later edit the project.

Before you finish a reporting session

• Check the active organisation and period.
• Save a new project file if you have made changes worth keeping.
• Confirm the downloaded copy is where you expect it to be.
• Retain original evidence separately, with references that you can follow later.
• Keep a secure backup of the organisation folder. Project files can contain sensitive business information and are not encrypted by the app.

Next: prepare branded, editable documents or follow the client-work workflow.