Filmmaker EPK Website Updates: Public Assets And Private Screeners
For filmmakers and producers updating an existing press page while keeping private screening access under separate owner control.
Start filmmaker EPK website updates by checking the existing public page against approved project materials. Confirm the current logline, synopsis, credits, stills, trailer, and contact route, then note stale items, broken links, and permission gaps. Keep private screener details in a separate, owner-controlled handoff. Publish only approved materials, and test the public page and authorized private procedure before sharing the update.
- Compare the live EPK with approved project materials before making edits.
- Record public assets and private screener decisions in separate worksheets.
- Hold assets with unclear versions or permissions until an owner confirms them.
- Test public links and contact delivery before sharing the revised page.
Open the current EPK as a press recipient would. Compare its live logline, synopsis, credits, stills, trailer, and contact route with the versions the project owner approved. Write down errors before editing, then review screener access separately. The public page helps visitors understand the project and find its press route; it should not expose credentials or confidential recipient details.
For filmmaker EPK website updates, a simple asset swap may be manageable by the owner. A page with several outdated items, unclear approvals, or ongoing changes may call for managed website help. In either case, the project owner approves public content and the authorized screener owner controls private access.
What Should You Check On The Existing EPK First?
Open the actual public page on desktop and mobile, then compare what visitors see with the project’s approved materials. Start with the title and logline, followed by the synopsis, credits, trailer, stills, and contact route. Record the live URL or file, the exact issue, and the person who can approve a correction.
Fix accuracy and access problems before adding sections. An old trailer or outdated contact destination can make a polished EPK misleading. Keep uncertain items in a pending list rather than relying on memory or assuming that a file in a project folder is cleared for public use.
This audit is about the project’s website and handoff. It cannot establish whether a festival received or viewed a submission, or predict a festival’s decision.
Which Public Assets Belong In The Register?
Use this worksheet with actual project records. Enter the current page location or version, not a guess. If the rights holder, content approver, or intended use is unclear, mark the item pending and hold it out of the public update until the project owner confirms it.
| Asset or page element | Live version or URL | Public or private status | Approver or rights owner | Replacement trigger | Last owner check |
|---|---|---|---|---|---|
| Logline | Record live text or page location | Public only if approved | Project copy approver | Owner approves revised wording | Enter date or pending |
| Synopsis | Record live text or page location | Public only if approved | Project copy approver | Approved synopsis revision | Enter date or pending |
| Press still | Record image file or page location | Public only with permission | Rights holder or authorized approver | Replacement image approved or permission changes | Enter date or pending |
| Trailer | Record current public URL or embed | Public only if approved | Project owner or designated approver | Replacement cut approved for public use | Enter date or pending |
| Credits | Record live credit text or page location | Public only if approved | Project owner or designated credit approver | Owner approves corrected or updated credit wording | Enter date of credit review or pending |
Treat Missing Permission As A Hold
A still’s presence in a shared folder does not establish permission to publish it. Ask the rights holder or authorized project approver to confirm the intended use. Record the decision and keep the asset off the public page until the approval is clear.
- Audit
Compare the live public EPK with approved copy, assets, permissions, and contact details.
- Separate
Record public materials apart from private screener ownership, channels, and change decisions.
- Scope
Give the website team the EPK URL, requested edits, approved assets, and approvers.
- Test
Check the public page and inquiry route, then test private access only with authorization.
How Should You Handle A Private Screener Change?
Keep private access decisions out of the public asset register. Record roles and decisions, not passwords or real recipient names. The project owner chooses the channel and action; the person responsible for screener access confirms what the existing platform can actually do.
Do not assume that a link expires, that access can be revoked, or that replacing a cut automatically disables an older route. If the desired change depends on a platform control, confirm that capability before describing it as part of the process.
Record any replacement or revocation decision in the action column. Treat revocation as available only when the platform owner confirms that capability.
| Recipient category | Owner-approved channel | Credential owner | Change trigger | Owner-approved replacement/revocation action | Platform capability confirmation |
|---|---|---|---|---|---|
| Invited festival recipient | Record the private route approved by the owner | Name the authorized project role | A new cut is approved | Owner decides whether to replace the prior route | Confirm recipient scope and platform controls |
| Press recipient requesting a screener | Use the channel approved for press | Name the person responsible for access | Recipient or access details change | Owner reviews the handoff before sending again | Confirm who may authorize release |
| Project collaborator | Use the project-approved internal route | Record the responsible role privately | A credential or cut changes | Owner directs any replacement or correction | Confirm the platform permits the requested action |
| Unverified or misdirected request | Do not send access details yet | Contact the designated access owner | Recipient or request becomes clear | Set the handoff only after approval | Record the owner's decision and confirmed options |
Should You Make The Update Yourself Or Request Managed Help?
An owner edit is a reasonable fit for a straightforward public asset swap when you have site access, approved replacement files, clear usage permission, and confidence that the contact route will remain intact. Save the old and new URLs or versions in the register so someone can check what changed.
Managed website work may fit when several page elements need revision, the layout needs attention, links require maintenance, or you want an ongoing process for public updates. Storebox can scope public EPK page content, layout, links, and maintenance. Private screener controls, file hosting, uploads, custom forms, and third-party integrations are not assumed; describe the needed capability and confirm it separately.
Illustrative example: A producer discovers that the public page embeds an earlier trailer cut. The producer confirms rights and approves the replacement, then names an authorized screener owner to manage the private handoff. The website editor updates the public trailer link. An authorized recipient tests the private procedure, but no one assumes the old link can be revoked unless the platform owner confirms that capability.
For a proposal, provide the EPK URL, the public changes sought, the project goal, approved replacement assets, and who approves public materials and screener access. We can scope the website work in a Get Free Proposal request. The proposal is free; any website work is separately scoped. Current terms are on our plans and pricing page.
What Should You Test Before Sharing The Revised EPK?
Use four checks before sharing the page:
- The project owner approves each public asset, version, permission, and contact destination.
- The EPK is readable on mobile and desktop, and its live items match the asset register.
- Permitted public links and downloads open the intended materials; a test inquiry reaches the designated project inbox.
- The authorized screener owner approves and tests the private procedure. Keep credentials out of public page content and test access only with authorization.
Count a verified public EPK inquiry only after it reaches the project’s contact route and the owner confirms it is a real inquiry received through that EPK page’s contact route after the approved update. A click or form interaction alone is not enough. Keep inquiry records separate from screener access and festival outcomes.
Google’s SEO guidance notes that site changes can take time to appear in Search, and visibility is not guaranteed. If you track link clicks, treat them as interactions, not confirmed inquiries; Google Analytics events can measure interactions such as clicks, while the project owner confirms whether an inquiry arrived.
Frequently Asked Questions
What should you do if a still's publication rights are unclear?
Hold the still until the rights holder or authorized project approver confirms permission for the intended use. Note who needs to decide and leave the image out of the public update in the meantime. Having a file available does not establish permission to publish it.
Should the public EPK include a screener password?
Keep passwords and private access details out of public page copy and downloads. The project owner should choose how intended recipients receive access and name the person responsible for it. Confirm any limits or controls with the platform instead of assuming a link is private.
Can an EPK update get a festival to respond or select a film?
No. Website work can correct public information, assets, links, and contact details, but it cannot predict a festival response or selection decision. Use the festival’s own submission and communication instructions for those matters.
What will an EPK update cost, and what work can be included?
Storebox pricing and the work itself depend on the proposal scope; no specific EPK update price is supplied here. Share the actual page URL, requested public changes, approved assets, and any separate access requirements to request a proposal. Confirm the price and any private-access work before approving the project.
What if the current screener platform cannot support the requested change?
Do not promise the change until the platform owner confirms what is possible. Ask the project owner to choose an acceptable alternative, then confirm whether any website work or integration is technically in scope. Keep credentials and recipient details private while the decision is pending.