3.0 The departments3.6 Sets
Sets
How the locations of an episode become sets with references, versions and a sign-off before the finals.
Sets decides what every location looks like. Each location in the breakdown becomes a set: an element with an @handle, versions and reference pictures. Every shot in that location uses them, so the kitchen in shot 3 is the kitchen in shot 9.

What this step produces #
A signed-off look per set: a current version with reference pictures (wide, details and others). Cast & sets → Locations shows a card per set ("3 sets in this production") with its version and who works on it.
Who works on it #
On a film crew, a production designer does the work and the director signs it off. Those are crew jobs, not Filmsquare roles: what a person may do comes from their workspace role. A producer can assign the whole step, or one set to one person: "Joe works on sets · Sam on Backlot street".
How AI prepares it #
- The breakdown brings in a set per location. To add one yourself, choose New set and describe it, or pick one from Elements.
- Open the set and render a sheet under Sheets, then choose Sign off as reference on the one you want. Or add a photo of a real place with Add reference.
- Sets can be shared by every production in the workspace: a set made once is called with its @handle anywhere.

See Elements, versions and @handles.
Signing it off #
Signing off Sets says: these are the locations. Sets locks the finals by default.
What makes it go stale #
A new version (v2 and up) of a set makes Sets Changed after sign-off in every episode that uses it, as a scene's location or in a shot ("A new set version came in after the sign-off"). The change flows on to the Animatic, the Draft and the Final.
The free lineage check also flags a shot that uses another set than the rest of its scene. See Continuity.
What it costs #
A set still on Seedream 5.0 Pro costs 1.66 credits · €0.08. Routing picks the model with the lowest cost per accepted take unless you choose one. See Credits and what things cost.
With your own Claude #
The tools are under With Claude on this page. Rendering a sheet, accepting it and forking a version go through
find_actions and run_action.
With Claude
MCPYour own Claude does this over MCP, in your name and with your role:
work_on_stepPromptA working method: prepares one department step of an episode for sign-off, with the cost first.
Ask: Use the Filmsquare work_on_step prompt for Sets on episode 2.
view_mediaLooks at a still, keyframe or take; video comes back as its poster plus a download link.
Ask: Show me the picked still of shot 3 and tell me if it matches its references.
upload_fileAdds a file you have as a new take on a shot or scene, or as a production asset (10 MB at most).
Ask: Upload this reference photo to the assets of the production.
get_continuityLays an episode's picked shots side by side, with the element versions each one uses.
Ask: Lay out the picks of scene S2 for a continuity check.
report_continuityRecords the continuity check you did; each mismatch becomes a note on the shot's pick.
Ask: Check continuity in scene S2 and report the mismatches you find.
request_signoffAsks the signers of a department step to sign off; they get a notification.
Ask: Ask the signers of Sets on episode 2 to sign off, with a note on what changed.
sign_offRecords your decision on a step: signed off or changes requested. Only when you ask it to decide.
Ask: Sign off Sets on episode 2 for me.
find_actionsSearches everything the API can do and returns the matching actions with their inputs.
Ask: Find the action that changes a step's sign-off rule.
run_actionRuns one action found with find_actions, as you, with your role and rights.
Ask: Pick the second take of shot 5 on episode 2.
Connect Claude 5.1