Manage locations and scouting

Keep screenplay-derived locations consistent, organize them visually, and enrich them for production.

Locations start in the screenplay

Location identities are derived from scene headings. Consistent headings help recurring places resolve to the same project entity. Correct spelling and naming at the screenplay source before adding extensive scouting or visual data.

Use the available views

The location canvas supports visual organization. Network and grouping views help understand related spaces. The scouting table supports structured production review. All views describe the same project-level locations shared by every episode.

Separate story place from production place

A story location may later map to a real shooting location, set, or virtual environment. Keep the dramatic identity stable while enriching it with scouting details. If one dramatic location requires several production spaces, name and group them clearly instead of overloading one ambiguous record.

Give AI filmable constraints

When asking for a location or scene, specify observable constraints: scale, access, time, weather, light, sound, geography, and what the characters can or cannot do there. Ask the assistant to read existing locations first so a new scene does not introduce an accidental duplicate.

Review after imports and renames

FDX import parses common interior/exterior prefixes, dashes, and time labels, but screenplay conventions vary. Review unusual headings after import. A location rename can affect many episodes, so use version history and coordinate the change with collaborators.