The Film’s Funding Depends on Partners Who Are Waiting for Each Other

Several conditional contributions can describe a promising financing conversation without making a film ready to proceed. To distinguish those situations, map what each contribution requires, who can confirm that requirement, and whether the chain reaches something independently achievable. A combined total cannot answer a question about dependencies.

The pitch then has a specific job: explain the present constraint and request the next decision that could change it. Sometimes that decision would make resources usable. Sometimes it would only establish whether a route exists. Both can be useful, provided the page does not turn the second into the first.

The fictional example below tests that distinction. It is a model of prerequisites, not an interpretation of a financing agreement. Applying it to real contributions requires the producer and qualified counsel to verify the status wording, conditions, and consequences against the actual records. The example has not received that specialist review.

First establish what “confirmation” means

Suppose a producer writes:

Two partners have confirmed their support. Together, their contributions complete the plan; each is waiting only for confirmation of the other.

This could conceal a circle. It could also describe conditions that can be satisfied through an agreed process. The word “confirmation” is doing too much work to tell us which.

Does Partner A need evidence that B is interested? A particular document? B’s contribution to be independently available? Has someone already agreed how the two decisions will be coordinated? A chart built before those questions are answered can misrepresent the situation just as easily as the optimistic paragraph.

For this exercise, make the assumptions explicit. A will not make its contribution available until B’s specified readiness condition has been satisfied. B will not make its contribution available until A’s corresponding condition has been satisfied. Neither condition is currently satisfied, and no alternative way of satisfying them has been established. These are invented teaching assumptions, not quoted contract terms.

Under those assumptions, one cannot become the starting fact merely because the other is drawn next to it. The problem is not a shortage of arrows. It is the absence of a confirmed starting point.

Different assumptions could produce a different answer. That is why the first task is to confirm the meaning of the conditions, rather than announce that every pair of conditional offers creates a deadlock.

Replace the momentum paragraph with a contribution record

Keep the original authorized record behind each summary. Record its date, the actual status wording, the proposed resource or verified amount, the conditions attached to it, any stated timing or expiry, and the person responsible for confirming a change. Where something is missing, write the question that needs answering. An unstated expiry is unknown, not unlimited.

Do not build a universal ladder in which every expression of interest, letter, offer, and agreement has a fixed place. The relevant issue is what this particular record establishes for this particular purpose. A document might be evidence for one recipient’s assessment without establishing that the production can spend the money today.

A public example makes that distinction concrete without defining all film finance. The BFI’s UKGSF International Co-production guidance separates a written conditional offer from the production finance agreement required before payment, with further payment conditions. That is the specified process for this program, not a universal meaning of “confirmed.”[^bfi]

For the fictional project, a working record dated September 19, 2026 might read:

No amounts appear because none are needed to test the dependency. In a real record, use verified amounts where they matter, but retain the conditions beside them. Do not value the assessment resources as though they were interchangeable with the production contributions.

Keep the internal record fuller than the external pitch. The working file may need the original correspondence and confirmation history. The recipient needs an authorized, accurate account of the decision in front of them—not private terms copied into a widely forwarded PDF.

Make the arrow mean one thing

For this chart, an arrow means “requires this other condition.” It points from the dependent item toward its prerequisite. It does not mean “pays,” “approves,” “happens next,” or “has agreed to.”

A’s readiness condition → B’s readiness condition
B’s readiness condition → A’s readiness condition

Neither condition is satisfied at the stated date.

Follow either arrow and you return to where you began. Under the declared assumptions, neither node can supply independent confirmation for the other.

Now compare a different, deliberately simplified sequence:

A’s condition → B’s condition → independently confirmed fact

Here, the last fact provides a starting point. If it fully satisfies B’s stated condition, and that in turn fully satisfies A’s, the modeled prerequisites can be resolved in sequence. This does not establish that approvals have been issued or money received. It tells you something narrower: the stated conditions no longer depend solely on each other.

That difference matters when choosing the next conversation. In the sequence, you may need confirmation of an action or document already capable of completion. In the circle, repeating the existing assurances does not change the prerequisites. Someone must establish a different condition, an accepted way of satisfying it, or a genuinely independent next action.

A real contribution can have several requirements. Show all those that affect the decision being presented. If A requires B and an approved schedule, the chart must not suggest that B alone is enough. Conversely, do not fill the page with unrelated production tasks. The map is an explanation of this dependency, not a substitute for the production schedule.

Test the smaller milestone before calling it a way forward

Return to the fictional project. The producer proposes an edit assessment of existing footage to identify what additional material, if any, the next version would need. The limited task has its own confirmed resources: a paid editor’s agreed assessment time, access to the relevant working media, and the ordinary viewing setup required for that scope. These are explicit fictional assumptions, not resources supplied by A or B.

The output is a short editorial assessment, not a completed film, a new financing commitment, or proof that production can begin. Its usefulness is equally specific: it could replace an unresolved question about the next edit with a defined set of creative choices.

The dependency is now:

Edit assessment → separately confirmed assessment resources

A’s condition → B’s condition → A’s condition

The assessment is possible within its stated scope. The production circle remains.

Calling the task a smaller milestone does not make it a financing solution. It gives the producer an independently achievable piece of work that may inform a later decision. Neither partner has agreed, in this example, to change its condition in response to the result. The pitch must not imply that finishing the assessment will automatically release A or B.

Now introduce a variant. The proposed assessment actually requires a specialist facility included only in B’s unavailable contribution. Perhaps the producer described a simple viewing assessment but the agreed question cannot be answered without that facility. The new dependency is:

Edit assessment → confirmed assessment resources AND B’s condition
B’s condition → A’s condition → B’s condition

The smaller task has re-entered the same circle. Its modest size, short duration, or attractive deliverable does not remove that dependency.

At this point, there are two honest possibilities within the example: redefine the assessment so it genuinely uses only the separately confirmed resources, or stop presenting it as immediately achievable. Redefinition must preserve a useful question. An assessment that avoids the unavailable facility but can no longer answer the question is not an equivalent milestone.

This is the test worth making before writing “Your participation unlocks the next stage.” Name the stage, trace its actual prerequisites, and say whether the recipient’s decision would satisfy them—or merely start another discussion about them.

A coordinated conversation changes the question, not the status

A joint discussion with the relevant confirmation owners could be useful when separate conversations keep returning the same condition. Its purpose is to clarify what each party needs and whether an acceptable process can be established. It is not itself the missing agreement.

The producer can prepare a short agenda around the exact uncertainty: what does A need from B; what does B need from A; who can confirm the meaning of each condition; and what information can be shared between them? The participants should be able to identify which answers they can supply and which require someone else’s decision.

That is more precise than arranging a meeting “to finalize the financing” when no route to finalization has been established. It also prevents a scheduling success from becoming a financing claim. “Both contacts have agreed to discuss the conditions” records an action. “Both contributions are now confirmed” asserts a different result.

If the discussion produces a revised condition, update its source record and the dependency chart together. Do not simply redraw the arrow to show the outcome you prefer. The new arrangement, its authority, and its consequences need verification; a writer should not invent a financing instrument or contractual mechanism to make the page resolve neatly.

The relevant pitch request might therefore be permission to arrange the discussion and circulate an approved summary. That is a bounded request with a useful outcome, even when nobody can yet promise that the conversation will release funds.

Check what each proposed action actually changes

The dependency test run for this article makes these distinctions explicit. It starts with only the facts marked as separately confirmed, then repeatedly checks whether all of a node’s prerequisites are present. A condition with no documented starting fact is not treated as satisfied merely because the diagram contains it.

The test was run against six fictional scenarios. It also checks that an empty dependency entry does not become automatic confirmation and that an unknown prerequisite is rejected.[^test]

These are results about the specified logical model, not observations of a production. The test cannot tell you whether a real letter is binding, whether the people involved will agree, or whether a project should accept a particular arrangement. Those are not hidden features waiting to be added to the chart. They require different evidence and judgment.

The practical gain is that the wording of the next request can now match the actual branch. An assessment request promises an assessment. A coordination request promises a conversation about the conditions. Neither is dressed as completion of the financing plan.

Write the decision request with its limit attached

A replacement for the opening momentum paragraph could read:

Status as of September 19, 2026. Contributions A and B remain contingent on each other’s specified readiness conditions. Neither is presently available under the assumptions recorded here. Separately confirmed resources would support a limited edit assessment before September 30; that work would identify editorial options but would not satisfy either production-funding condition. We are asking the two designated contacts to review an authorized summary of the dependencies and identify whether a coordinated discussion could establish a workable next decision.

This is fictional example wording, not a clause for a financing document. It tells the recipient what is known, what remains unresolved, and what their next action is supposed to accomplish.

If the actual request is approval of the assessment rather than coordination between partners, change the last sentence accordingly. Do not put both decisions into one vague “support the next stage” request. A recipient needs to know whether they are being asked to approve work, confirm a condition, or participate in a discussion.

Where figures are essential, place the relevant condition on the same page and close enough that the figure cannot easily be read as immediately usable funding. A distant qualification does little to correct a large total labeled “secured.” The design should preserve the distinction the wording has earned.

Keep a changed fact from leaving an unchanged promise

Date the map and identify the owner of each confirmation. When a prerequisite expires, is withdrawn, or changes meaning, revisit the dependent claims before reusing the summary.

In the fictional example, the separate assessment resources are confirmed only through September 30. After that date, the producer cannot carry “assessment possible now” into a new pitch without renewed confirmation. The test recomputes the result without that starting fact; the dependent assessment disappears, while the A–B circle remains unresolved.[^test]

Waiting can also be an honest next action, but name what is being awaited. “We are waiting for A’s designated contact to clarify whether the specified evidence would satisfy its condition” is different from “We are waiting for the funding to come through.” The first identifies an answer that could change the map. The second assumes an outcome the current record has not established.

The finished page does not need a resolved circle. It needs an accountable one: a dated status, traceable conditions, and a decision that means what the pitch says it means.

Sources

[^bfi]: British Film Institute, “Applying for UK Global Screen Fund (UKGSF) International Co-production”, section 7, “Conditions of funding.” Inspected September 19, 2026. This program-specific example is not advice on an individual project’s finance documents.

[^test]: Dependency test run for this article on September 19, 2026: six fictional scenarios, each built from the conditions and starting facts described above. The results record, per scenario, which conditions the model treats as satisfied and which it does not, including how it handles an empty dependency entry and an unknown prerequisite. No real contributions, agreements, or financing outcomes are represented.

Frequently asked questions

When do two conditional contributions become a deadlock rather than a process that still needs coordination?

When mapping conditions reveals no independent starting point. In the teaching assumptions, A will not make its contribution until B's specified readiness condition is satisfied, B will not until A's corresponding condition is satisfied, neither condition is currently satisfied, and no alternative way of satisfying them is established. Under those assumptions, one cannot become the starting fact merely because the other is drawn next to it. But 'confirmation' can also describe conditions satisfiable through an agreed process, so confirm the meaning of the conditions rather than announcing that every pair creates a deadlock.

What belongs in a working contribution record?

Date, actual status wording, proposed resource or verified amount, conditions attached, stated timing or expiry, and the person responsible for confirming a change. Where something is missing, write the question that needs answering. An unstated expiry is unknown, not unlimited. Keep the internal record fuller than the external pitch; the recipient needs an authorized, accurate account of the decision, not private terms copied into a widely forwarded PDF.

What does an arrow mean in the dependency chart?

In this chart, an arrow means 'requires this other condition' and points from the dependent item toward its prerequisite. It does not mean 'pays,' 'approves,' 'happens next,' or 'has agreed to.' A circle returns to where it began; a sequence reaching an independently confirmed fact can resolve the stated prerequisites in order, but it does not establish that approvals have been issued or money received. If a contribution has several requirements, show all that affect the decision, and do not fill the page with unrelated production tasks.

Can a limited edit assessment solve the funding circle?

It can be independently achievable if it uses only separately confirmed assessment resources, and its output is a short editorial assessment, not a completed film, a new financing commitment, or proof that production can begin. Neither partner has agreed to change its condition in response to the result. If the assessment actually requires a specialist facility included only in B's unavailable contribution, it re-enters the same circle; the honest options are to redefine it so it genuinely uses only the confirmed resources while preserving a useful question, or to stop presenting it as immediately achievable.

What did the dependency test establish about real funding?

The test ran six fictional scenarios against a specified logical model, repeatedly checking whether all of a node's prerequisites are present. It does not tell whether a real letter is binding, whether the people involved will agree, or whether a project should accept a particular arrangement. It also checks that an empty dependency entry does not become automatic confirmation, that an unknown prerequisite is rejected, and that when the assessment-resource confirmation expires, the dependent assessment is no longer supported while the A-B circle remains unresolved.

Further reading

• Two Film Financing Offers Raise the Same Amount. What Obligations Change? — Turn here when two conditional offers look equivalent; it shows how to compare conditions and timing, and why a stage label is not a confirmed cash-receipt date.
• Who Is Actually Attached to Your Film? Write a Useful Package-Status Page — Read this to build the dated status page the dependency map implies, pairing each open item with the decision it blocks and naming who can confirm it.