Markdown edition

# Build a checked film production office in Claude Cowork

> Use Claude Cowork to draft a source-checked film office, then deliver approved TXT and CSV copies through private project knowledge and verify every recipient file.

By BIGCHANGE.AI Editorial

Published: 2026-10-24T21:07:04.355Z
Updated: 2026-10-24T21:07:04.355Z
Canonical: https://bigchange.ai/blog/claude-cowork-checked-film-production-office-guide

![Conceptual charcoal illustration of an open film clapperboard beside a blank production checklist held by an orange clip.](https://bigchange.ai/api/media/file/cowork-film-planning-clapperboard-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE; no actual production, Cowork document, team decision or completed shoot is depicted.

Claude Cowork can draft the paperwork around a film shoot from files you permit it to read. The useful result is a production office whose shot briefs, call sheet, schedule and budget trace back to your actual approved records. A polished draft is still a draft until the producer checks it. This guide uses [Anthropic's Cowork documentation](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork); BIG CHANGE has not connected a production folder, run a media model, shared a Claude project or measured the cost of this workflow.

## The big change

- **What changed:** Cowork can work across a permitted local folder and draft several connected production documents. The team still has to supply the real shoot facts and approve each consequential file.
- **Why it matters:** A coordinator can keep shot IDs, creative briefs and production records in one checked index instead of reconciling unrelated drafts by memory. The producer remains responsible for rights, contacts, time and money.
- **What to watch:** [Cowork project files remain on the producer's computer](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) until approved copies are explicitly added to account project knowledge. Sharing a project title or session does not establish that a colleague received the office.

## Before you connect the folder

You need Claude Desktop on macOS or Windows, a paid Claude plan, an active connection and permission to use Cowork with the selected local folder. [Anthropic says](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork) the app must stay open and connected for local file work; Cowork tasks run on Anthropic's servers. Confirm your organization's data rules before making any material available to that service. Check your plan and Settings > Usage in the actual account.

Bring a current, producer-approved brief with its revision and owner; an approved script or shot source; rights records for references and likenesses; actual shoot dates, places and crew details where known; rate and cost records; and a restorable backup. Record which material the account may process and which people may receive each output. Keep restricted contacts, contracts, secrets and unreleased footage outside the connected folder unless the owner approves that specific route. Leave any missing field blank or mark it `unknown`. Cowork cannot supply a real shoot date, consent, crew availability or price from an absent record.

For the final handoff, you also need a Team or Enterprise account with project sharing enabled, a private **account project**, an approved recipient and permission to upload redacted copies. A project created from a local folder may remain local, depending on the account's Chat and Cowork setup. Check the actual project state before planning a share. Project instructions guide Claude's work; they do not grant or restrict file access by themselves.

## 1. Approve the office layout before writes

Make a backup that you can open. Record the source paths and their hashes or modification dates. Select only the approved drafting folder in Claude Desktop, inspect its actual path and permissions, and choose Manual approval mode while reviewing file changes and connectors. Read back the project's current instructions. Ask Cowork to propose paths before it creates anything:

```prompt
Read only [approved brief path] and [approved rights record path]. Propose a folder and filename plan for [real project name] covering a document index, shot list, image and video briefs, an observed platform log, call sheet, schedule, budget and producer decisions. List facts absent from those sources. Do not create, rename or delete files yet.
```

One workable naming convention is `00-source/` for approved originals, `01-office/` for the index, `02-shots/` for the shot list and briefs, `03-platform-log/` for observations, `04-production/` for call sheet, schedule and budget drafts, and `05-approvals/` for signed decisions. These names are an editorial suggestion. Compare Cowork's plan with existing paths and your team's naming rules. Approve only the needed creations, then open every new file on disk and confirm the originals and backup still open. A folder name is not a privacy control.

Keep an office index with artifact path, approved source revision, owner, document version, status (`draft`, `approved` or `blocked`), decision date and next check. The producer sets the status after review. Tell Cowork to show proposed edits and to leave messages, purchases, publishing, scheduled tasks, media submissions, deletions and permission changes for separate human decisions. Check its actions; an instruction alone cannot enforce those boundaries.

## 2. Link every creative brief to a real shot

Have the producer approve the shot list from the actual script and production brief. Give each shot a stable ID. Record its script reference and purpose, subject or location only where documented, the responsible reviewer, reference IDs and rights status. Put missing duration, aspect ratio or other controls in an `unknown` field.

For each approved shot, ask Cowork to draft an image brief and a video motion brief using only that shot and the permitted references. Each brief should include its shot ID and revision, source-supported subject and action, composition, intended platform and model if the team has chosen them, approved reference IDs, known format controls and a producer check. Mark a platform setting that has not been verified `verify in current platform`. Do not submit the briefs to an image or video tool as part of this office task. Open each saved brief and compare it with the script and rights record. When a shot changes, revise its linked briefs and index together.

Start the safety-filter log empty. Give it columns for the actual attempt time, platform and model version, account route, shot ID, approved prompt and reference versions, action attempted, observed response or error, displayed credits or charges, and producer decision. Add a row only after a separately authorized platform run. An untried platform stays `not tested`; neither Cowork nor this guide can predict its filters. For a rejection, read the real response and current policy, then revise only within those rules and seek fresh approval before another paid attempt. Do not use the log to search for ways around a filter.

## 3. Draft and check the production records

Give Cowork only approved records for the shot list, call sheet, schedule and budget. Ask it to mark each material field with a source pointer or `unknown / owner confirmation needed`. The call sheet needs the actual date, place, required roles and a permitted contact route. The schedule needs owner-supplied availability, setup, travel and dependencies. Budget lines need the approved quantity, unit, unit price, currency, tax or fees and source. Keep restricted contacts in a separate file when the intended audience cannot see them.

Check the files in sequence. Resolve every shot ID to the approved shot and its briefs. Compare call-sheet names, times, addresses and contact routes with the owner's records. Have the producer check schedule dependencies, duration and availability. Recalculate budget line totals and subtotals from source quantities and prices; check currency, tax and fees before accepting the grand total. Leave unsupported values visibly blank. Ask the producer to date an `approved` or `held` decision for each file. Correct a specific draft and read it back rather than accepting a plausible looking replacement. [Cowork can create documents and spreadsheets](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork); its documentation does not validate this production's calculations.

## 4. Prepare copies that the team may actually receive

The drafting folder and Cowork session do not upload local files to colleagues. [Anthropic's project guide](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) says local folder files stay on the computer during project migration, and its [cross-device guide](https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile) requires content to be added deliberately. Check whether your drafting project is shareable in the actual Team or Enterprise account. If it is local-only, use a separate private account project for the delivery.

Create a delivery manifest from the approved office index. For every proposed copy, record its approved local source path and version, owner decision, permitted audience, exact recipient, redactions, delivery filename and the copy's own version and hash. Exclude raw references, unapproved drafts, contracts, secrets and private contacts unless that exact recipient is allowed to receive them. Open any redacted call sheet and confirm the restricted fields are gone. Preserve approved originals in the local office.

Convert approved narrative files to plain TXT and tables to CSV when their column meanings and values survive export. Compare the shot IDs, key rows, dates and budget totals in each copy with its approved local source. If the local budget relies on spreadsheet formulas, check the calculated values and assumptions before exporting. [Anthropic lists TXT and CSV as supported file types](https://support.claude.com/en/articles/8241126-upload-files-to-claude), with a 30 MB limit for each project file and further extracted-content/context limits. Do not assume Markdown or TSV is a supported project upload. An XLSX upload requires the account's code execution and file creation capability; verify that route before using it, or hold that item.

The following blank record can be copied into a local TXT file. Add one line per *actual* delivery file and per *actual* recipient readback; never prefill a success state:

```text
PROJECT / ACCOUNT: [private Team or Enterprise account project and owner]
LOCAL SOURCE FOLDER / BACKUP: [paths and source revision]
PROJECT VISIBILITY / MEMORY SETTING: [actual readback]
SHARED INSTRUCTIONS VERSION / READBACK: [actual version and display check]

DELIVERY FILE: [filename.txt or filename.csv]
APPROVED LOCAL SOURCE: [path, version, producer and decision date]
COPY VERSION / SHA-256: [version and hash after redaction/export]
ALLOWED AUDIENCE / NAMED RECIPIENT: [owner-approved identities]
REDACTIONS / COPY CHECK: [removed fields; checked shot ID, row or total]
PROJECT KNOWLEDGE UPLOAD: [actual time and Files/knowledge display]
RECIPIENT ROLE / OPENED AT: [Can view or approved Can edit; actual time]
RECIPIENT READBACK: [displayed filename/version and chosen non-sensitive row]
PRODUCER MATCH / STATUS: [approved, held, or pending; reason]
```

Open the **account project's main page**. Keep it private to named members. Use the `+` control in [project knowledge](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects) to upload *each* approved delivery copy. Read back the Files/knowledge list and open each item where the interface allows; compare its displayed version and selected rows with the manifest. Set the reviewed shared instructions separately through **Set project instructions**, then reread them. A chat attachment, downloadable session artifact or local project instruction does not replace these uploads. Hold any truncated or uncertain item, inspect its current Files entry and content, and retry only after you know what was saved.

## 5. Verify the recipient's complete handoff

Use the [Team or Enterprise project controls](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects) to invite only the approved organization colleague. Give `Can view` to a reader; use `Can edit` only when that person is authorized to change knowledge or instructions. Check the project's memory setting and visibility first, because account memory can surface context beyond this project.

Ask the recipient, using their own authorized account, to find the project under **Shared with you** and open its instructions and every intended knowledge file. For each file, have them report the displayed filename and version plus a producer-selected, non-sensitive shot ID and checked row or total. Compare each response with the manifest and record their identity, role and readback time. A visible title or invitation is not evidence that the full office is readable. If you cannot obtain a recipient readback, leave the handoff `pending` with the exact missing item.

Project roles govern account access. A person who previously downloaded or copied a file may still hold that copy after a role change; use the team's retention process for those copies. When a file changes, approve and upload a new delivery version, update the manifest and repeat the recipient check. Preserve the old decision and version history.

## Check the result and recover narrowly

The office is ready when the approved source and backup open; all shot IDs resolve; briefs, observed log and production documents match the actual brief, rights and owner records; producer decisions are dated; every permitted delivery copy matches its source; the account project's files and instructions display correctly; and the named recipient reads back **every** intended version. A missing permission, fact, supported upload route or recipient check is a specific hold, not a successful handoff.

If Cowork cannot read a file, inspect its real path and permission. For an unexpected edit, compare disk with the backup and repair only the affected draft. After an uncertain write, inspect disk before retrying. For a wrong budget total, correct the source or formula and recalculate. After an uncertain upload, inspect project knowledge before sending another copy. If the recipient cannot see a file, check the account plan, local versus account project, sharing role, format, size and Files listing, then record the unresolved item.

Cowork usage depends on the paid plan and task length. Image and video services, music, storage, labor and retries can carry separate charges; set a production spending limit from current account prices before later media work. Rights to process a brief, likeness or reference and rights to distribute the output require the actual owner's review. This guide documents a way to assemble and check the office. No account session, upload, film generation, recipient readback or cost measurement was performed for this article.

## Sources & further reading

- [Get started with Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork): paid access, desktop local-file requirements, cloud task processing, action review and document creation. Checked 24 October 2026. It provides no film-office template or accuracy guarantee.
- [Organize tasks with projects in Claude Cowork](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork): local folders, project instructions, memory and Team/Enterprise sharing. Checked 24 October 2026. Local files staying on disk does not mean Cowork processing is local-only.
- [Create and manage projects](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects): project knowledge upload, private sharing and view/edit roles. Checked 24 October 2026. Invitation alone does not prove a recipient opened the approved files.
- [Upload files to Claude](https://support.claude.com/en/articles/8241126-upload-files-to-claude): supported document types, 30 MB project-file limit and extracted-content limits. Page dated 23 July 2026; checked 24 October 2026. Actual account capability and successful extraction still need readback.
- [Use Cowork on web, desktop and mobile](https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile): local-folder project boundaries and explicit addition of project content. Checked 24 October 2026.

## Sources

- [Get started with Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork) — Checked 24 October 2026. Paid plans, connected Desktop local-file work, cloud processing, manual action review and document/spreadsheet creation. It does not validate a film office or any reader's results.
- [Organize your tasks with projects in Claude Cowork](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) — Checked 24 October 2026. Local folder, instructions, memory and Team/Enterprise sharing boundaries. Local folder files remain on the computer through migration; processing itself may use Anthropic servers.
- [How can I create and manage projects?](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects) — Checked 24 October 2026. Account project knowledge upload, shared instructions, private invitation and Can view/Can edit roles. Recipient access to exact files needs separate verification.
- [Upload files to Claude](https://support.claude.com/en/articles/8241126-upload-files-to-claude) — Page dated 23 July 2026; checked 24 October 2026. Lists TXT and CSV, a 30 MB project-file limit and extracted-content/context constraints. XLSX requires account code execution and file creation.
- [Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile) — Checked 24 October 2026. Local-folder projects support desktop Cowork and project content must be added explicitly; local session artifacts do not establish a shared knowledge handoff.