How projects are structured

Backscene is built around what happens on a shoot — not around a spreadsheet line. This page is the map. Each primitive has its own deep guide linked below.

The pieces

• Projects — a production or job with tabs for spend, locations, items, and settings
• Project Locations — org library places linked into this project (with optional alias and location budget)
• Scenes — moments belonging to one project, optionally tied to a location
• Project Vendors — suppliers that already have spend on this project
• Purchases — receipts and expenses on the project
• Items — what was bought or tracked, on a purchase or standalone

Org-level vs project-level

Locations and vendors are shared org records. You manage the catalogs in Locations Library and Vendors Library. On a project you link locations and see vendors that have purchases here.

Scenes, purchases, and most items are project-scoped (items can also stand alone with project links).

A typical flow

1. Create a project (brief, script, or manual)
2. Link locations from the library
3. Add scenes, optionally on those locations
4. Log purchases against the project (and later link scenes)
5. Track items and budgets

Day-to-day navigation: Working in a Project.