Save and reopen a project file

What the file keeps

A project JSON file preserves the structured time card: the reporting period, dated shifts and breaks, paid/unpaid labels, drafts, project text and settings. The schema version tells the importer how to validate the structure. The current project format is version 1.

Download a backup

1. Review the open card and use Download project JSON.
2. Save the file somewhere you can find again.
3. Keep the current tab open until the file is saved.
4. If the backup is important, reopen it as a separate project and compare key values.

Reopen without overwriting another card

Choose Import project JSON from Saved cards or the relevant file action. The importer validates the version and dated record structure before making a new project available. Existing cards remain unchanged. A duplicate or renamed project is a separate local record; use a clear name so you can tell the versions apart.

If validation fails

Keep the original file. Read the reported version or field error rather than deleting fields until the import appears to work. An unsupported version, invalid date or broken record should produce an actionable error, not a partially restored project that quietly omits data.

Files and local saves are different copies

A local save remains in the current browser’s storage. A downloaded JSON file exists wherever your browser saved it. Clearing site data or deleting a local card does not delete that file, and updating the open card does not automatically update a previously downloaded backup. Export a new backup after changes you want to keep.

JSON, CSV and PDF have different purposes

JSON restores the complete editable project and settings. CSV is spreadsheet record data and may require column mapping. PDF is a readable submission or printing copy. Do not treat the latter two as complete substitutes for the project file.