Build a Public Film Project Page Without Uploading the Private Deck

A public project page is a selection, not a redaction. The private deck and the public page are built from overlapping material, but they answer different questions for different readers, and the second reader will never see the deck at all.

That distinction does most of the work here. If you start from the deck and remove what shouldn't be public, you get a document shaped by absence — sections that gesture at a budget table, a synopsis that stops mid-turn, a bio that assumes you already know who is asking. If you start from the visitor's reason to be on the page and select material that serves it, you get something shorter and considerably more useful.

Everything below runs on one invented package. Marrow Creek is a feature-length fiction project in development. The production company has a private deck and no public page yet. The package contains:

• a full synopsis, including the reveal the second half turns on, written for financing conversations;
• a wish list of five actors, none of whom has been approached;
• a mood photograph licensed to the production for private review only;
• a one-sentence premise the owner has approved for public use;
• a stage statement the owner has confirmed;
• a budget top sheet marked private and internal;
• no release date, no mailing list, and no signup of any kind.

The company's general enquiries address is already published on the company's own website. Nobody has decided whether it belongs on a project page.

Hold those facts. They constrain every decision that follows.

Decide what the public page is for before you decide what goes on it

A private recipient is evaluating something: whether to finance, represent, crew, or collaborate. The deck is built to survive that evaluation, which is why it contains figures, comparisons, and a plot summary that gives away the ending.

A public visitor is doing one of three things: understanding what the project is, following its development, or considering a clearly defined involvement. Those are different jobs, and each one pulls different material onto the page.

The fixture above can serve only the first. Following a project requires an update route, and there isn't one. Considering an involvement requires a defined step, and there isn't one. So the page's job is to explain, and it should be written as though that is the whole job — because for now, it is.

This is where a lot of development pages go wrong. They promise a relationship the production can't currently maintain. "Follow our journey" over an empty space, "More details coming soon" under a paragraph that has no more details coming — both are commitments, and the fact that they're vague doesn't make them free. If no update route exists, don't write copy that assumes one.

Sort the package by intended use, not by quality

The strongest slide in a deck is not automatically public material. Permission travels with context: a synopsis cleared for a private review portal is not thereby cleared for a website, and an image cleared for a festival catalogue is not thereby cleared for a project page. Approval has a scope — what, where, for how long — and when nobody can state that scope, the honest answer is unknown rather than probably fine.

Small print does not create permission. A caption reading "for reference only" under an image whose licence covers private review does not make the image publishable; it just makes the page look careful while doing the same thing.

Here is the fixture sorted. The public job column is the one that decides everything else.

Two rows in that table are the ones people get wrong. The actor list is not a confidentiality problem so much as an accuracy one: publishing names nobody has approached invites the reader to conclude those people are involved. That conclusion is false, and no amount of careful verb tense prevents it. The mood image is the opposite — it's tempting precisely because it's beautiful, and a page built around an unlicensed photograph has traded a real asset for an imaginary one.

Write a description that stands without the deck

The approved premise was written to sit alongside other material. On its own, it needs a sentence of context and a verb tense it can live with.

Marrow Creek is a feature-length fiction project in development.

A young county surveyor returns to the town that raised her to redraw a property line, and finds the map she has been handed has her own family's name written out of it.

The screenplay is in revision. No cast is attached, and no production dates are set.

Look at what didn't survive. The synopsis's reveal is gone; the premise stops before it. Nothing refers to an attached budget or a slide number, because there is no attached anything on a public page. There are no gaps to notice, because the paragraph was written to be complete rather than to be the remains of something longer.

That last point is the one that separates a rewritten page from a stripped deck. Deck language leaves sediment: "as discussed," "see schedule," a bullet list where every line is a fragment, a biography that assumes the reader knows the project's history. If you find yourself writing around a hole — "further details to follow," "cast to be announced at a later date" — you are describing an absence instead of writing a sentence, and the reader can feel it even if they can't name it.

Two smaller decisions in that copy are worth making deliberately.

First, "No cast is attached" is true in this package, and it's the owner's call whether to say it. The alternative is to say nothing about casting at all. Both are honest; the plain sentence forecloses a guess, and the silence declines to raise the subject. What you should not do is leave a "Cast:" line waiting to be filled, which reads as an announcement in progress.

Second, the stage statement records where the project stands — script in revision, no cast attached, no dates set — and stops there. It does not say the project is seeking financing, and it does not need to. Describing the stage is not the same act as soliciting, and a public page that slides from one into the other has changed what the page is for.

State the stage, and add a next step only where one exists

Development is not a smaller version of release. A film in development is a script, some people, and an intention; a completed film is an object other people can watch. Copy written for the second will misdescribe the first, and the misdescription is not a small inaccuracy — it changes what the visitor thinks they can do.

The fixture has no release date to publish and no signup to offer. So the page has no date and no signup, and the correct next step is a deliberate absence rather than a placeholder. That is a finished editorial decision, not an unfinished page.

If the owner later approves the company's existing enquiries address for use here, one line goes in: a real address that already exists, already reaches a person, and is controlled by the people who own the page. That is a proposed change, not something the fixture supports today. What the page still must not have is a contact form built for a mailing list that doesn't exist, a "stay tuned" line with no schedule behind it, or an invitation to submit materials for a project with no process for receiving them.

Assign an owner and name the changes that force a revision

A public page needs someone responsible for it, and it needs a short list of facts that would make it wrong. For this project:

• the stage statement changes, because the screenplay is no longer in revision or the project moves toward production;
• a name becomes genuinely attached, which changes the description and possibly the stage line;
• an approved asset's permission is withdrawn, which removes it;
• the next step changes, whether because a route is approved or because one is retired.

Internal work should not move the page. A new draft of the screenplay, a revised budget, a sixth name on the wish list — none of these change anything a visitor reads. Keeping the public page in step with every internal change is how pages end up carrying language no one has re-read.

Before the copy goes anywhere, assemble it as one document — description, stage line, asset list including the empty slot, next step or its absence — and check it against the approved selection. Not against the deck. Against the list of what was approved for this purpose, in this place, at this stage.

The brief this produces

For Marrow Creek, the assembled public account is short: three sentences of description and stage, no assets yet, no date, no signup, no contact route, with a note recording that an existing address may be added later if the owner approves it and that the mood image stays out until something cleared replaces it.

That is a complete page brief. It is also, for now, most of a page.

Two things sit outside this method. It decides editorial selection, not clearance: whether a particular image licence covers a website is a question for whoever holds the rights, and the editor's job is to record the answer rather than assume it. And nothing here verifies a real project — the package above is invented, and the method is a proposal to test against an actual page and an actual permission record.

The test of the result isn't whether it hides what shouldn't be public. It's whether a stranger who has never seen the deck can read the page without noticing that anything is missing.

Frequently asked questions

Why start a public project page from the visitor's reason to be there rather than by stripping the private deck?

The private deck is built for someone evaluating whether to finance, represent, crew or collaborate, so it contains figures, comparisons and a plot summary that gives away the ending. A public visitor may be trying to understand the project, follow its development or consider a clearly defined involvement. If you start by removing material from the deck, you get a document shaped by absence; selecting material for the visitor gives a shorter and more useful page.

How do you decide whether a deck item can go on the public page?

Sort by intended use, not by quality. Permission travels with context and scope, so a synopsis cleared for a private review portal is not thereby cleared for a website, and an image cleared for a festival catalogue is not thereby cleared for a project page. Small print does not create permission. In the Marrow Creek fixture, the full synopsis, actor wish list, privately licensed mood photograph and budget top sheet are omitted; the approved premise and stage statement are kept.

Why should a wish list of actors be omitted, and what should not be said about casting?

The actor list is an accuracy problem, not just a confidentiality one. Publishing names nobody has approached invites the reader to conclude those people are involved, and no careful verb tense prevents that conclusion. Omit 'attached,' 'starring' and 'with' as well. Saying 'no cast is attached' is true in the fixture and is the owner's call; saying nothing is also honest, but a waiting 'Cast:' line reads as an announcement in progress.

What should a public description do, and what should it avoid?

The description should stand without the deck. The approved premise may need a sentence of context and a verb tense it can live with, and the stage statement should say where the project actually is. Avoid deck-language sediment such as 'as discussed,' 'see schedule,' fragment bullets, and writing around holes with 'further details to follow' or 'cast to be announced at a later date.'

How should the page handle next steps, updates and revision triggers?

If no release date and no signup exist, the page has neither, and the correct next step is a deliberate absence rather than a placeholder. If the owner later approves the company's existing enquiries address for use there, one line can go in; do not build a contact form for a mailing list that does not exist or invite submissions with no process. Assign an owner and name the changes that force a revision: stage changes, a name genuinely attached, an approved asset's permission withdrawn, or the next step changing. Internal work should not move the page.

Further reading

• Who Is Actually Attached to Your Film? Write a Useful Package-Status Page — Go here to write stage and package-status material precisely: keep wish-list names off the page and pair each open item with its source and the decision it blocks.