Who Is Actually Attached to Your Film? Write a Useful Package-Status Page
Who Is Actually Attached to Your Film? Write a Useful Package-Status Page
A package-status page has one job: show an outsider what the project can rely on today, and what it still needs.
Most pages miss that in the same way. Not by lying. By using one verb for different things. A phone call and a signed agreement get the same grammar. A wish-list name sits in the same column as the director, same size, same color. Nobody typed the word "attached," and the page said it anyway.
The repair isn't modesty. It's precision about kinds of information, and then a page that carries those kinds honestly. Put what's in place in an in-place section. Put what's open in an open section. Keep the wish list off the page. Connect each open item to the decision it's blocking. End on the one gap a reader could actually fill. Then date it.
That's the answer. What follows is how to get there, worked through an invented project so the details stay concrete.
Inventory the package before you choose impressive names
Before you write a page, write down what exists. Not in deck language — in plain sentences with sources and dates.
Here's an invented project. Call it Harrow Sound, a feature. Nothing about it is real; the shape is ordinary.
- Script. Second draft complete, 3 March. Written by Priya Raman. Source: the file.
- Director. Daniel Okonkwo has agreed to direct. Agreement signed 18 April. Source: the signed agreement.
- Lead role. The script went to Mara Feld on 5 May. Daniel spoke with her on 21 May. She said she liked it and asked when we'd shoot. Daniel had no dates to give. No offer, no terms. Source: Daniel's call notes, 21 May.
- Producing. No producer attached. Nothing to source, because nothing happened.
- Wish list. Ana Villalobos, for the same lead role. No approach, no contact. Source: Daniel's own list.
Five lines. Two of them are about people who are not on the project, and one is about a person nobody has called.
The inventory isn't the page. It's the material the page gets built from, and the reason to write it first is that those five lines are not five of the same thing. One is a fact about an object. One is a fact about an agreement. One is a memory of a phone call. One is a preference. A row of names in a deck flattens all four into the same shape.
A test sorts them faster than any ranking of attachment words: what can the project do now that it couldn't do before? The finished script means there's something to send. The director's agreement means you can say who's directing, and that his notes are going into the next draft. The phone call with Mara Feld means nothing has changed except that one more conversation is possible. You can't book a date, build a budget, or announce anything.
That test isn't about how impressive a line is. It's about what a reader could act on.
Two columns belong in the record and usually don't get one. First, source and date on every line. Status rots. By July you won't remember whether Mara asked about the shooting window or whether you volunteered it, and that difference changes what you're allowed to write next. Second, what the team is authorized to communicate. You may know that a financier passed, that an actor's calendar is full, or that a fee came down twice. Knowing it isn't permission to publish it. Keep that column in the working record. It should never reach the page.
Write the status you can actually support
Here's the page most projects would build from that inventory.
HARROW SOUND A feature film by Priya Raman Directed by Daniel Okonkwo With Mara Feld and Ana Villalobos
Two problems. The word "with" performs an attachment for two people: one who has had a single phone call, and one who has never heard of the project. And the page has no open items at all, which is the loudest accidental claim a page can make. A reader scanning for what's missing finds nothing missing.
Here's the same package, bounded.
HARROW SOUND — package status, 12 June
In place
- Second-draft screenplay, complete 3 March. Writer: Priya Raman. The director's notes are going into the next draft.
- Director: Daniel Okonkwo. Agreement signed 18 April.
Open
- Lead producer: none. The finance plan runs through a regional production incentive. The budget that application needs hasn't been commissioned, and nobody has confirmed the project qualifies. Next decision: bring on a producer who has closed an incentive on a feature at this scale. Until that person is in, the plan can't be tested — by us or by you.
- Lead role: unfilled. Mara Feld has read the script and we've spoken once. No offer, no terms, no dates. The lead has to be cast before we can name a shooting window.
Not on this page Wish-list names, and conversations with nothing agreed in them.
Notice what the verbs are doing. "Has read," "has agreed to direct," "signed," "none." Each one describes something the reader could check. None of them is "attached," which is the word this page can most easily do without, because it doesn't say what anyone has agreed to do.
There is a folk ladder — interested, circling, attached, locked — and it means something different in every office. Nobody has agreed on it, so it can't carry your meaning for you. The better question is narrower: what can this person's answer support? If the answer is "one more conversation," write that.
Applications have to make the same distinction. A June 2025 proposal checklist for the Nonfiction Core Application asks for Key Creative Personnel and Funding Detail as separate items, and its prompts treat confirmed participation or support differently from states that aren't confirmed yet. That's one documentary funder's framework, and how recipients use it varies. It isn't a definition of attachment, and it won't tell you whether your actor is "in discussion" or "circling." What transfers is the habit: confirmed and unconfirmed are answers to different questions, and the person reading your page is asking both.
When you can't tell what a description means, the fix is not a stronger word. It's asking. If the sentence is about a person, the language has to be language they or their representative would recognize. If it's about a role or a piece of the production, the producer responsible for that area is the one who can approve the wording. Rewriting a status because the first draft sounded weak is the moment to stop and make a call, not to reach for a bigger verb.
Keep the wish list off the package page
Now put Ana Villalobos back on the page and look at what happens. Her name carries the same weight as the director's, in the same type, in the same list. A reader who doesn't know the project reads four people at the same level. You can add an asterisk. You can add a legend. You can set her name smaller.
None of it works, because small type can't unsay large type. If a stranger covers the legend and looks at the page, the page says four people are in. The qualifier is doing work the layout has already undone.
The useful edit is usually deletion, not annotation. Ana Villalobos comes off the page, and the reason isn't that she's unimportant — it's that a status page reports states, and there is no state to report. Nothing has happened.
You don't have to lose the information. "We're casting the lead and working from a list of actors at this level" tells a reader about the project's ambition without making a claim about a person. The difference between that sentence and a name is the difference between describing your list and recruiting someone onto it without asking.
Show what the missing piece prevents
Look at the open section again. The producer gap isn't interesting because a role is empty. It's interesting because of what the emptiness blocks.
The finance plan depends on a regional incentive. The application needs a budget in the format the incentive office uses. There's no producer to build that budget, so the plan can't be tested by anyone — not by a financier, not by the incentive office, not by a reader who might know exactly the person the project needs. One missing role, standing between the project and its next real answer.
Every open item on a page should have that shape: a gap, and the decision it's holding up. "Seeking a lead actor" is a status. "Seeking a lead actor; the role must be cast, and the budget built, before we can name a shooting window" is a dependency a reader can use.
One caution. Dependencies invite invented deadlines. Most gaps have a next decision and almost none has a date you can defend, so write the decision, not a deadline you're guessing at. If a date is real — a funder's cycle, a market, an actor's availability — say it and say where it comes from. If it isn't, leave it out.
The other caution is volume. A page that explains what's blocking the project is useful. A page that attaches the script, the budget, the call notes, and three letters of interest is a document dump, and it makes a reader do your editing. The supporting records stay with the team. The page states the dependency and moves on.
When one line changes, check what else it moves
Suppose it's July and Mara Feld has agreed to play the lead. One conversation changed status, and several things on the page are now wrong.
The line moves from open to in place, with a verb that matches what she actually agreed to and wording her team has cleared. If the agreement is signed, say signed. This isn't the place to interpret what her contract means elsewhere — the page reports the fact, not its legal reach.
The lead role is no longer a gap, but it doesn't simply disappear from the open section either. The shooting window is now a named open item, and it can't be set until there's a budget, and the budget can't be built without a producer. So the open list still has two entries: the producer, and the dates. The second is downstream of the first, and the page should say so, because that's the part a reader can help with.
The record gains the agreement's date, who signed, and where the document lives. It also gains what has to be reconfirmed before the next circulation: whether the public wording about her role is still approved, and whether the dates are fixed yet.
And the ask doesn't change. A producer who has closed an incentive is still the thing the project needs — arguably more so, now that there's a reason to build the budget.
The same discipline runs in reverse, and that direction is harder. If Mara had passed, the page would get smaller. Her name comes off, because a status page isn't the place to publish someone's decision not to join. The record keeps the name, the date, and the reason, because the team needs to remember what was said. The next action changes from "call her agent" to "rebuild the list." Nothing on the page gets more impressive, and the page gets more accurate. That's a working page, not a failing one.
Close on the gap the reader can fill
The page should end the way it began: with what's real, and with the one thing a reader could do about it.
Next step. We need a lead producer who has closed a regional incentive on a feature at this scale. Until that role is filled, Daniel Okonkwo is handling the search and can answer questions about it: [contact].
Status current as of 12 June.
One gap, and a person who can answer. Not three needs with no owner, which leaves a reader deciding whether to help with casting, financing, or nothing. Pick the gap that's actually blocking the next decision, name who holds it, and let the rest of the page do the explaining.
The date goes on the page, because a reader needs to know how old this is before they rely on it or repeat it. The list of what to reconfirm before the next circulation goes in the record, because that's about your process, not the reader's decision.
Then leave it alone until something changes. The page that says less and means all of it is the one someone answers.
Frequently asked questions
What is the one job of a package-status page?
It should show an outsider what the project can rely on today and what it still needs. That means separating what is in place from what is open, not flattening a signed agreement, a phone call, and a wish-list name into the same kind of claim.
Why can the word 'attached' be misleading?
It does not say what anyone has agreed to do. A phone call and a signed agreement can receive the same grammar, and the folk ladder of interested, circling, attached, locked means different things in different offices. A narrower verb—has read, has agreed, signed, none—describes something a reader could check.
What belongs in an open section?
Each open item should name a gap and the decision it is blocking. In the Harrow Sound example, no lead producer means the budget for a regional incentive application has not been commissioned, so the finance plan cannot be tested. An unfilled lead role blocks naming a shooting window.
Why keep wish-list names off the page?
A wish-list name in the same type as the director implies a claim the page cannot support. Asterisks, legends, or smaller type cannot undo the layout, because the page already reads as if the person is in. A useful alternative is to describe the ambition—working from a list of actors at this level—without recruiting someone onto the project without asking.
What is the difference between the page and the working record?
The page carries in-place status, open dependencies, one next step a reader could fill, and a date. The record keeps source and date for each line, what the team is authorized to communicate, passed names and reasons, supporting documents, and what must be reconfirmed before the next circulation.