Assignments

An Assignment is one piece of work your Production Studio is making. “This week’s newsletter.” “The launch video.” “The explainer for the new feature.” Each Assignment carries everything related to that work — the brief, the drafts, the rendered audio, the artwork, the assembled video, your review notes — and tracks where it is in its lifecycle.

If Production Studio is the studio, Assignments are what get made there. Open Production Studio and the first thing you see is “what are you working on?” — answered by your list of Assignments.

What’s in an Assignment

A single Assignment holds:

• The brief. A short description of what you’re making, the audience, the format, any specific constraints (tone, length, voice choice, brand elements).
• The draft work. Output from each studio that contributed — Forge’s script, Voice Studio’s audio takes, Vector Studio’s artwork, Video Studio’s assembled cuts.
• Your reviews. Notes, approvals, revision requests. Each review is timestamped and attached to the specific version it applies to.
• The published version. Once approved, the finished deliverable is marked published and made available wherever it goes (download, publish to a channel, hand off to a connector).
• The history. Earlier versions don’t disappear when superseded — you can always go back to a prior take.

You don’t curate any of this manually. As studios produce work for the Assignment, the Assignment automatically becomes the canonical place where it all lives.

Lifecycle

An Assignment moves through a few states:

State	What it means
Planning	The brief exists but no studio has produced anything yet.
In progress	At least one studio has produced a draft. Others may still be working.
Review	Drafts are complete and awaiting your approval.
Published	You’ve approved the work; the finished version is available.
Archived	The Assignment is closed out and removed from your active list (but not deleted).

You don’t typically move Assignments through these states manually. As work progresses and you approve or reject pieces, the state updates itself. You can override — manually mark something as archived, for instance — but the default is automatic.

How it ties studios together

The reason Assignments matter as an entity is coordination. A 90-second explainer video isn’t four separate outputs; it’s one deliverable that depends on:

• The script (Forge).
• The voice take (Voice Studio, reading the script).
• The artwork (Vector Studio).
• The final assembly (Video Studio, combining audio + visuals).

If you change the script after the voice is recorded, Production Studio knows the voice take is now stale. The Assignment carries that knowledge — without it, the four studios would just produce four outputs and you’d have to track the dependencies in your head.

When you do change something upstream, the Assignment shows you what downstream pieces are now out-of-date and offers to re-run them. Nothing silently drifts; nothing gets shipped because you forgot a re-render.

When NOT to create an Assignment

If you’re doing a single-output task — write me one email, draft this one document, give me a quick voice memo — don’t bother creating an Assignment. Use the relevant studio directly. The friction of “is this an Assignment?” overhead isn’t worth it for one-shot work.

Assignments earn their keep when the work has multiple stages, multiple studios, or a clear lifecycle (planning → review → publish). For everything else, the standalone studios are fine.

Recurring Assignments

For work that repeats on a schedule — a weekly newsletter, a daily voice-memo to your team, a monthly explainer video — you don’t have to create the Assignment by hand each time. A goal can create the Assignment for you, populate it with the brief, and kick the studios off.

This is the most common Production Studio setup for ongoing content. Define the recurring brief once; the Assignments arrive on schedule.

Finding Assignments

Assignments are first-class in your sidebar — they’re how you navigate Production Studio. You can also reach them from:

• A chat reference (“how’s the May launch video coming?”) — your AI knows which Assignment matches.
• A search across the instance.
• Links from the artifacts each Assignment produces (every artifact knows which Assignment it belongs to).

Related

• Production Studio — the coordination layer Assignments live in.
• Artifacts — the individual files produced inside an Assignment.
• Projects, programs, and tasks — how Assignments relate to broader work. Often a project (e.g., “spring launch”) contains several Assignments (each video, each email, each post).