Keep your film
career recoverable.

A career needs an index above the current production

The short you are editing, the feature you are writing and the documentary waiting for access have different immediate needs. A shoot needs call sheets and versioned production documents. A career needs a way to recover the people, decisions, spending and finished work that survive those documents. Start with four linked records: people, project states, festival submissions and showable packages. Keep an identifier for each film so a sound recordist, receipt and master folder can refer to the same project without spelling its title differently in three places.

This guide rewrites the useful career-management questions in Storyflow's filmmaker organisation article, checks consequential vendor claims against current primary documentation and adds an editable, exportable archive. A single production app can contribute useful records without becoming the authoritative home of every career record. The workbench below makes its boundary visible: it calculates from what you enter; it does not fetch your accounts, inspect your films, verify festival eligibility or confirm that a screening link plays.

The practical test is a request arriving between projects: “Can you send work like this by tomorrow?” If the film exists but its master, current credits and screening access cannot be recovered, a finished production still creates a new administrative task. Similarly, an old call sheet may contain the right person's number but omit whether they recorded dialogue, what terms you agreed or why you would hire them again. Your archive should answer the next real decision rather than preserve files without context.

Choose a home by the operation you need

There is no defensible universal winner from these feature lists. Choose the smallest home in which the actual recovery task works. If your current Sheet already finds a reliable crew member and reconciles receipts, migrating it to a richer app might add maintenance before it adds value. If repeated contacts and submissions require copying the same names into many tables, linked records may remove that particular duplication. Keep the production software your collaborators already use when it continues to solve the current shoot.

Keep contacts with the memory that makes rebooking possible

A useful contact row has a stable ID, name, role, location, phone or email, films worked together, agreed rate and currency, terms, how you met, a short working note and the date the details were checked. Store a rate as a dated historical agreement, not a promise that the person still charges it. A blank rate means unknown, not free. Record only relevant professional notes and restrict access to private contact information when sharing the archive.

Include contributors, festival programmers, funders and collaborators as well as crew. A programmer's entry can retain the screening where you met and the relevant programme conversation; a contributor's entry can point to an access agreement without exposing sensitive interview material. “Met through Nia at the museum screening” preserves a useful introduction route that an email address alone loses. Professional contact context does not establish automatic availability or permission to share details.

For the fictional filmmaker Mara, contact C01 is Amira Lane, a Manchester sound recordist who worked on P01 and P03. The note reads: “Quiet approach with non-actors; asked for a room-tone hold before the last setup.” The historical agreement is £220 per shoot day plus approved travel, payable within fourteen days; it was checked at wrap on 2025-08-22. This is more useful than “good sound person,” because it explains when Mara would call Amira again. C02 is editor Leo Hart; his availability and current quote still need confirmation. The workbench's search examines the actual rendered names, roles, location, project IDs and notes, so searching Manchester or room tone recovers the relevant entered record.

Update the details at wrap while the production memory is fresh. Keep a new person's source call-sheet reference or how you met them; keep an existing person's new project association rather than making an accidental duplicate. The sample's semicolon-separated project IDs are deliberate links to the project index. An unknown film ID is rejected instead of silently producing an orphan contact. In a collaborative database, establish who can edit a rate, contact detail or subjective working note; a shared view need not expose the entire private registry.

StudioBinder's official product description describes transferable contacts integrated with production features. Celtx's Cast & Crew help documents contact details, availability and imports from projects you own or collaborate on. Its Catalog help documents basic inventory CSV exports and catalog imports. Use those concrete mechanisms when recovering production records; the existence of an import button alone does not prove continual cross-project synchronisation.

Give every project a present state and a next decision

Use states that mean something to your work. Idea means material worth retaining without an active development commitment. Development means someone is doing writing, access or financing work. Ready means the intended production can proceed once its stated trigger is satisfied. In production includes the work you define as the active production/post period. Distributing means the finished film is being shown, submitted or delivered. Shelved means you have consciously paused it. These are useful starting terms, not a claim that every filmmaker must use the same vocabulary. The workbench keeps custom state labels as entered text.

Beside the state, record the blocker, next action, owner, due date and last meaningful touch. “Documentary in development” is vague; “Access request paused; Mara will ask the archive manager about two interview dates on October 19” identifies a decision. A changed folder timestamp is not necessarily meaningful progress. An unknown historical date should remain blank until evidence supports it.

The review threshold is an entered planning preference. Set it to 90 days if a quarterly stale-project review suits you; the tool flags the age relative to your entered reference date. It does not decide that a 91-day project is dead. A film awaiting seasonal access can remain a deliberate commitment. A project touched yesterday can still deserve shelving if its finance or rights assumptions have changed. The list should help you ask the question rather than answer it from inactivity alone.

Shelving needs a date, a reason and a restart condition. In the sample P04, Canal Voices, is shelved on 2026-03-16 because the principal participant withdrew access. Its restart condition is a new willing participant and a revised access agreement. The research remains indexed. The entered decision prevents a vague “must get back to this” obligation while preserving an explicit route back. There is no universal correct number of live projects: two projects needing an hour this week can be manageable, while one production needing immediate legal and edit decisions can exceed your capacity. Compare actual next actions and available time.

Reconcile festival spending before judging your strategy

Set an amount and currency for a defined submission period before entering fees. Give every submission a film, festival, category, deadline tier, exact deadline date/time/zone, quoted fee, submission date, submission status, judging status, result date, platform, receipt reference and a reason. The reason is a short hypothesis: “Regional audience and documentary strand fit the film's local-access story,” rather than “looks prestigious.” Where an award qualification matters, record the actual official source, applicable edition and category as a claim to check.

Current FilmFreeway receipt help provides individual View Receipt and invoice/PDF options. It also documents Export All Transactions for a chosen start and end date, producing a CSV. Therefore the claim that FilmFreeway cannot tell you what you spent is an inaccurate basis for rebuilding your system. Export its receipts first. A separate career ledger adds a budget, missing-history marker, refunds, entries made elsewhere and your decision rationale. It should reconcile the platform's actual records rather than conceal them.

The workbench imports your actual receipt CSV through explicit mapping. It does not guess that a vendor's “Total,” “Date” or “Amount” column has a particular meaning. Choose the actual payment-date and amount columns, then any currency, receipt reference, project ID, submission ID and notes columns present. Where the file lacks your local project ID or currency, enter the fixed value consciously. Select the actual date format, decimal separator, thousands separator and whether negative amounts mean refunds. A unique local prefix creates transparent local transaction IDs; they are not claimed to be FilmFreeway IDs.

An import validates every mapped row and every project/submission reference before changing any transaction. A bad date, duplicate local ID or invalid amount leaves the previous ledger intact. The JSON backup retains the original uploaded CSV bytes, parsed text, header mapping and conversion settings; the retained-source button downloads the original bytes again. That provenance matters if you later discover that a supposed amount included tax, a bundle or an unrelated transaction. Do not use the example's small custom CSV as a claim about FilmFreeway's actual column schema.

Payments and refunds are separate signed effects on the total. The fictional P01 has payments of £35 and £25, with a £10 refund: £35 + £25 − £10 = £50 recorded net against an entered £150 festival budget, leaving £100. Its quoted £35 and £25 fees are displayed separately and are not added again to the paid total. P03's earlier receipts are missing; its spend-completeness value is unknown. “No transactions entered” means missing history unless you have explicitly confirmed that the relevant period is complete. Do not compare a complete £50 ledger with an unknown historical film as though both totals were measured.

The tool keeps currencies separate. A GBP entry and a USD entry do not become a fabricated GBP total. It does not retrieve exchange rates, predict acceptance or infer a festival return on investment. If you compare submissions between two films, account for their genre, programme fit, release stage, submission period and missing records. A lower spend with more acceptances is a description of those entered records, not proof that lowering spend caused better selection.

Deadline tiers are a real planning distinction, but the price difference is festival-specific. In an original fictional comparison, one category charges GBP30 early,45 regular and60 late: ten entries at30 allocate300, while ten at60 allocate600. That arithmetic teaches why the targeted tier belongs in the record; it is not a claim that every festival doubles its fee. At your entered cap, pause the next payment and record whether you will stop, replace a planned entry or explicitly approve a revised budget. A rejection is information to review, not an automatic reason to buy another entry.

In a separate fictional retrospective, filmmaker Arun has complete period records for two campaigns. Orchard Steps has six submissions, GBP180 net and one selected screening; Quiet Room has four submissions, GBP100 net and one selected screening. Recorded selection proportions are1/6, about16.7%, and1/4,25%; mean recorded net cost per entry isGBP30 andGBP25. These are worked descriptions, not evidence that reducing entries caused acceptance. Review actual programme fit and results, including whether rejections cluster among larger festivals while smaller regional programmes show interest. Do not turn that pattern into a claim of predetermined eligibility or quality. This separate illustration is not included in Mara's restore file and does not add invented receipts to her ledger.

The workbench's comparison sums all entered payments/refunds and all entered budget allocation rows for a project/currency. Its scope field is an explanatory note, not a date filter. If you intend an Autumn2026-only comparison, include the corresponding receipt period and allocations, or maintain a clearly scoped separate backup. It does not silently assign historical transactions to a campaign based on their dates. Record the period's completeness before using the remaining-budget figure as a decision.

Preserve deadline time and result meaning

FilmFreeway's deadline help currently states 11:59 PM Pacific Time on the listed day. In the workbench a FilmFreeway example therefore uses 23:59 and America/Los_Angeles. Do not replace that with your laptop's local midnight. Enter another platform's actual zone and wall time when they differ. The Luxon conversion shows the entered instant in UTC and exports it to an ICS calendar. Calendar import does not itself prove that notifications are enabled or that the festival still accepts your category.

For an illustrative November 8, 2026, 23:59 America/Los_Angeles deadline, the UTC instant is November 9 at 07:59. This is a fictional festival row, not a live festival announcement. The source retains its entered zone even though ICS represents the instant in UTC. Ambiguous or nonexistent daylight-saving wall times are rejected for clarification; silently choosing one offset would hide an important deadline assumption. A row with no deadline remains unknown and produces no calendar event.

FilmFreeway distinguishes submission status from judging status in its official status guide. A submitted film in consideration is not the same as a selected film, and selection is not an award. Keep incomplete-material requests, withdrawal and disqualification separate from judging outcomes such as undecided, selected or not selected. The sample uses these distinctions as entered observations, without manufacturing an external verification.

For Academy or BAFTA aims, consult the current category-specific official rules and qualifying evidence. Academy submissions guidance explains qualification proof, including qualifying festival award confirmation where the category requires it. BAFTA's official Film information links the separate short-film and animation rulebooks. A festival's appearance on a list, your screening acceptance and your film's eventual awards eligibility are different assertions. Preserve the edition/category/source rather than copying an unqualified “Oscar qualifying” badge into your career archive.

Build the package you can actually show

Keep a recoverable high-quality master and the appropriate streaming version. A sharing link is an access route, not your only master. Retain a trailer or an intentionally chosen short extract when useful; the original's two-minute extract is a conditional presentation option, not a universal festival requirement. Likewise five to ten print-ready stills can be a useful starting brief, including a portrait and an establishing image, but each recipient's specifications govern the delivery. Add approved key art or a poster, correct credits, a one-line logline, one-paragraph synopsis, director statement and technical details: runtime, aspect ratio, sound, language and subtitle availability.

The asset records keep location, share URL, access condition, last manual link check and next intended check. A private link may fail because of a changed password, account restriction, hosting plan, privacy setting or deleted upload. Open the actual link as the intended recipient and play the film before a real delivery. An annual archive review can be a useful baseline, but a check from eleven months ago does not certify today's share. The workbench displays your entered check dates without pretending to test the link.

FilmFreeway supports a digital press kit, including trailer, stills, headshot, biography, news links and attachments. Use that supported feature for its intended recipients. It is still sensible to keep independently recoverable master locations and versioned written copy, because a platform kit is not evidence that your local files can be restored. Do not describe the platform as having no package capability simply to justify a separate archive.

Here is literal copy for the fictional P01, Last Bus Home. Logline: “When the final bus is cancelled, a night cleaner and a teenage passenger must decide whether to trust each other for the walk home.” Synopsis: “After finishing a late shift, Imani finds the bus stop empty except for Arun, who has missed his last connection. Their uneasy walk through closing shops becomes a negotiation over shortcuts, phone calls and what each is willing to reveal. At the bridge they choose separate routes, carrying a small new understanding rather than a solved relationship.”

Director statement, first paragraph: “I wanted the journey to remain ordinary enough that the audience notices the decisions inside it. The empty stop is a practical inconvenience before it becomes a test of trust. We rehearsed the walk as a sequence of changing distances rather than a series of speeches.” Second paragraph: “Working with a compact crew let us preserve the pace of the street and avoid turning the neighbourhood into scenery. The final separation matters because connection does not erase each person's boundaries. The film offers a brief shared route, not a rescue.”

Entered credits and technical record: Written and directed by Mara Ellis; produced by Nia Cole; cinematography by Ben Vale; sound by Amira Lane; edited by Leo Hart. Fictional runtime 11:42, aspect ratio 1.85:1, stereo mix, English dialogue, English subtitle file prepared. Rights note: music and participant permissions require the actual project file review before distribution. These filled values are teaching material, not credits for a real released film. The downloadable portfolio includes this complete copy in its package row.

Plan package assembly at delivery while credits and files are recoverable. One conditional two-hour allocation is thirty minutes for written copy, twenty for credits/specifications, thirty for master/streaming versions, twenty for stills/key art and twenty for recipient-access checks:120minutes. This is a scheduling illustration, not a benchmark. A missing old drive, incorrect credit or rights query can turn later reconstruction into a working day or longer. An annual check of eight links at an assumed two-and-a-half minutes each allocates twenty minutes, but troubleshooting needs extra time and today's actual share still requires its own check.

A coherent four-year, ten-project portfolio

The following is a fictional career index with five finished productions, two active projects, two ideas and one consciously shelved documentary. Finished is a production-history fact here; the current state can still be Distributing. “Completed packages” are entered records, not remotely inspected files.

P01, P03 and P09 have filled package records. P02 and P10 need a conscious package decision. Three of five finished productions have packages entered; that is 60% of this fictional portfolio, not an industry baseline. The feature and the short in post are the two active commitments. The documentary is shelved, not silently counted as a third active obligation. The table, narrative and actual ten-row downloadable source agree; every separate project remains a separate record.

The sample supplies three meaningful contacts rather than fabricating dozens of filler people. Add your own call-sheet records as you recover them. The counts exist to explain the workflow, not to suggest a normal crew size. If the earliest submission year is unrecoverable, keep the affected project's historical completeness unknown and record the search you performed. An approximate recollection may become a clearly labelled note, but should not become an apparently invoiced amount.

Compare the record systems without losing their mechanics

Sheets or another spreadsheet: start with stable IDs and separate tables, not one giant note column. Keep filters for state and last touch. Google Sheets has conditional notifications for eligible work/school accounts, so a blanket “no reminders” claim is too broad. Those notifications are triggered by supported changes; a volatile TODAY calculation while a file is closed does not create a reliable timed deadline alarm. Use a real calendar for the confirmed deadline and verify the imported event. Preserve an unmodified receipt export before cleaning columns.

Notion: a project database can link development notes and a contact database; filtered views can separate shelved films from live work without deleting either. Notion's offline help says desktop/mobile app members can download pages, while browser offline access is not offered. Databases initially download the first fifty rows of the first view; additional pages and rows require attention, and downloads are device-specific. Download the actual treatment, linked contact pages and essential records on the device you will use, then test them offline. AI and embedded online services do not become offline because a page is downloaded. A general claim that Notion cannot work offline would miss the current feature and its actual limits.

Airtable: link contacts to projects and submissions to films, then roll up linked amounts where that matches your ledger design. Airtable's linking-record help and rollup guide describe those operations. A lookup is not automatically a sum. The plans overview currently lists 1,000 records per base and 1 GB attachment storage for Free, rather than 1,000 records for each table. Contacts, projects, submissions and payment rows consume the shared record allowance. Do not make a large video attachment plan fit inside a database merely because the written rows fit.

Airtable Team is currently $24 per billable collaborator per month on monthly billing, or $20 per month equivalent on annual billing. Team commenters as well as creators/editors can be billable; read-only users are not the same role. Two annual Team seats therefore mean $480 per year, three $720, five $1,200 before tax. These are conditional seat calculations using the cited current plan, not a prediction of your invoice or a claim that every filmmaker needs a paid base. A one-person archive and a crew's editing access may have very different cost requirements.

StudioBinder and Celtx: use their production-native contacts, call sheets, scheduling and reports when those are already part of the shoot. Capture the old contact's professional context before the project is buried. StudioBinder's public pricing reader did not expose a verifiable plan price in this research, so no old £/$ starting price is repeated as current. Celtx's catalog/contact imports are concrete recovery paths, while a studio-user invitation list is a different object from the cast/crew registry. Export or copy the supported actual records and test the operation in your account before replacing a functioning production workflow.

FilmFreeway: retain the platform as a submission service and kit delivery surface. Export transactions for the actual relevant period and map them honestly into your own local project IDs. Keep the platform's submitted/judging distinctions and reference the actual receipt. It does not need to be your whole creative-development workspace for its receipt exports to be useful. Other submission routes can exist: the New Zealand Film Commission's festival marketing guide discusses multiple platforms. Avoid treating one marketplace as the only possible route or assuming all festivals use the same cutoff time.

Storyflow: use boards for premise, references, beat development and pre-production; attach or link the career record where a board needs it. The official Help Center documents PNG/SVG/PDF board export and view/edit sharing; it qualifies live multi-editor presence and roles as Max Team Workspace capabilities. Do not infer equivalent team operations from a free invitation alone. Do not assume an AI response automatically searched every career project, updated a relational database or reconciled receipts. Supply the actual relevant current-board/document context, then retain a written decision in the authoritative record.

The current official pricing describes paid early access, a future Free plan and free collaboration by invitation. Individual Plus is $9.99 monthly or $95.88 annually, Pro $19 monthly or $168 annually, and Max $49 monthly or $468 annually. Annual figures are upfront commitments, not monthly invoices; invited collaborators and paid individual seats are different conditions. A filmmaker considering Plus for templates should compare its actual creative-development value with a free existing ledger, rather than assuming the subscription replaces submission reconciliation. The old free-plan banner is not current purchase evidence. Creative thinking and career bookkeeping can cooperate without pretending they are the same feature.

The original filmmaker article describes active-board context plus one Tactic and up to three @-mentioned documents. Preserve that practical context-selection idea rather than replacing it with “ask AI.” For P05, a filled review can use the Beat Sheet Tactic and the outline-version2, access-notes and financing-assumptions documents. Ask: “Which North Window beat depends on the unconfirmed access assumption? Name the document and the next decision; do not invent secured access.” Keep its response as a review proposal, not a confirmed production fact. Current pricing/help confirms contextual @references broadly; this research did not independently establish the numerical1/3 limit in the current application. Check the actual context panel when selecting those materials, and do not imply the assistant read the whole career archive.

Six filled creative-template applications

Pre-Production Board — P06, The Spare Key: owner Mara; entered production/post stage; latest cut reference “P06 cut 04”; blocker “sound handoff awaits picture change list”; next action “Mara sends Leo the cut-04 change list on October 15.” Group the intended locations, crew and permissions around that specific film. Link contact C02 and the project record, so the board helps the next handoff rather than replacing the career index.

Shotlist — P06: shot 12 is an interior hallway close-up of a key turning; lens/coverage choice remains an entered production assumption; Leo's edit note asks for a clean action before the door opens. The row's next decision is whether the available take supports that cut. Preserve the chosen take and source clip reference in the production record, then retain the relevant package/master location when delivery finishes. A career contacts table is not a shotlist.

Storyboard — P05, North Window: frame A shows the visitor outside the flat; frame B isolates the unlit window; frame C holds the empty doorway after the visitor leaves. The actual decision is to withhold the inside view until the next scene. Mara owns testing that sequence against the second-act outline on October 19. Retain the reasoning beside the board version so a financing revision does not leave an unexplained set of images.

Beat Sheet Filmmaking — P05: opening beat “the caretaker finds a letter addressed to a previous tenant”; midpoint “the visitor recognises the handwriting”; ending beat “the letter is returned without a confession.” Development question: does withholding the writer keep the caretaker's choice understandable? A beat sheet can hold that creative question; the project index holds its owner, current blocker and next review. Do not fabricate an approved screenplay from a filled outline.

Filmmaking Moodboard — P07, Green Ticket: collect the green bus interior, sodium-lit stop and coat texture as visual directions. Label each reference with source and intended use: lighting mood, palette or costume texture. The note reads “Keep the stop practical, not dreamlike.” Reference images do not automatically grant reuse rights. The idea stays Idea until someone commits to a development action; collecting attractive images alone does not make it Ready.

Film Plan — P04, Canal Voices: purpose “a short documentary about competing memories of the canal route”; access condition “new willing participant and revised agreement”; owner Mara; state Shelved; shelving date 2026-03-16; restart decision “review only after the access condition is met.” Keep the archived research and permissions history. This is a completed conditional plan for a paused film, not a fictional promise that access will return. All six applications refer to actual sample project/contact IDs in the downloadable portfolio.

A monthly review and a first afternoon

One possible monthly hour allocates ten minutes to project states, fifteen to submission results and receipts, fifteen to contact changes, and twenty to stale decisions or package gaps. The arithmetic is 10 + 15 + 15 + 20 = 60 minutes. This is a conditional routine for a small maintained archive, not a time-saving guarantee. Choose a repeatable review day and move work that cannot be completed in that session to a specific action with an owner. A larger backlog or missing masters can require substantially more time.

In the first ten minutes, inspect every active next action and any entered age flag; keep an intentionally waiting project waiting, or record a shelving decision. In the next fifteen, reconcile real receipts and result notices rather than changing selection statuses from memory. In the contact segment, add the new wrap association and check changed details. In the remaining segment, open the actual high-priority screening link as the intended recipient or schedule a missing master recovery. The review should create fewer ambiguous obligations, not another weekly essay about the system.

For a first three-hour afternoon, use the first hour to list films and choose honest states. Leave unsupported last-touch dates blank. Inspect an old project by its actual blocker and next action, not simply its age. Use the second hour to recover people from the last four call sheets, consolidate real duplicates and retain unknown terms as unknown. In the third hour, export platform transactions and collect other receipts, enter campaign budgets, then list which finished films lack a showable package. Do not promise to rebuild every old package in that same hour.

Prioritise the missing package that demonstrates the work you want next. P02 may matter for a new narrative commission; P10's old music video might not. Record a decision not to rebuild P10 now instead of leaving it as a perpetual failure. Even a filmmaker with one live film benefits from the contact history, finished package, shelved access note and next idea. Start with the first paid submission if a spending decision already exists; there is no magic minimum of five entries or five films before records become useful.

Use the workbench without losing your own source

Load the fictional portfolio to see all ten project records and the filled package copy. Edit the CSV tables or upload your own supported JSON backup. Required header names are documented in each source table; additional columns are retained. IDs stay strings, preserving identifiers such as 001. Foreign project/submission references are checked. Export the complete JSON as the recovery artifact, each source CSV as the editable table interchange, Markdown as a human-readable review, and ICS as entered deadline instants.

The archive is browser-local in use; the page does not send your entered tables to a provider. Download a backup before closing the tab because this tool does not silently promise persistent storage. A CSV export carries the entered values and can contain formula-like text; use your spreadsheet's safe text-import controls for untrusted records. The JSON preserves the complete source plus original receipt imports and mappings. The rendered cards and calculations are derived views; a restore regenerates them from that source.

The instructional video demonstrates a concrete four-part sequence: recover Amira's rebooking context; reconcile P01's £50 net without double-counting quoted fees; keep P04 shelved with its explicit restart condition; locate P01's package while checking the actual link outside the tool. The portrait version is separately composed for readable phone text. Captions and the written equivalent preserve the same four decisions. Neither a teaching video nor a passing export proves an external festival acceptance or that every useful idea in the source has been independently reviewed.