Optimise Your Film Festival With The Film Festival Evolution Check
Does the way your festival works still fit?
Film festivals often evolve over time. The way work gets done becomes more complex. New tools are added, responsibilities change and more teams need to share and update the same information.
That can work perfectly well. But you feel that at some point you need to or even must optimise your film festival, how it currently is organised. Because it can mean staff spend more time copying information, checking different versions, maintaining spreadsheets or coordinating work between systems.
Optimise your film festival by answering 5 questions
The Film Festival Evolution Check helps you to optimise your film festival by checking how recurring tasks are organised, and if that way of working still fits.
After five short questions, you receive:
- the operational Model that best describes how your festival works;
- practices from other Models that are already present;
- practical guidance based on where work is running smoothly and where friction may be growing.
No score. No ranking. No assumption that you need to change.
Optimise your film festival in 5 questions · About 2 minutes · Immediate result
What does the Evolution Check look at?
The five questions look at how recurring festival work is handled: the tools teams use, whether responsibilities and processes are defined, how information moves between teams and systems, and whether experience from one edition is used to improve the next.
Your result is not a score. It identifies one of five operational Models that best describes how most recurring work is organised.
The operational Models we’ve defined are:
Ad hoc · Tool-supported · Structured · Integrated · Adaptive and data-informed
A later Model is not automatically better. A festival can work effectively in any Model when that way of working fits its needs. Read more about this in the FAQ.
Why operational fit matters to optimising your film festival
A process that worked well a few years ago may require much more effort today.
More films, guests, venues, colleagues or external systems can mean that the same information has to be used in more places. Teams may start copying data between tools, maintaining parallel files or spending extra time checking whether changes have reached everyone who needs them.
That does not automatically mean the festival needs new software or a different Model.
The useful question is whether the way work is organised still supports what the festival needs to do.
Frequently asked questions about the Evolution Check
How is the result calculated?
The check uses five questions to help you optimise your film festival.
The first four look at digital tools, agreed ways of working, how information is managed and exchanged, and whether teams use experience to improve recurring processes.
These answers determine the operational Model that best describes the festival.
The fifth question asks whether the current way of working still fits. This does not change the Model. It changes the advice you receive about what to look at next and what could help to optimise your film festival.
What are the five operational Models?
The Evolution Check uses five Models to describe different ways recurring festival work can be organised:
Ad hoc
Work depends mainly on direct communication, individual knowledge, spreadsheets, email and shared folders.
Tool-supported
Dedicated tools support important processes, but information and workflows are still often managed separately.
Structured
Teams follow defined, repeatable processes. Responsibilities are clear and important information is stored and updated in agreed places.
Integrated
Information can be reused between teams and systems without repeated copying, exporting, re-entry or checking.
Adaptive and data-informed
Teams also use reporting, evaluation and experience from previous editions to adjust recurring processes and improve how work is organised.
These Models are not a ranking. A later Model is not automatically better. A festival can work effectively in any Model when that way of working fits its needs. By using these models, we help you optimise your film festival.
Is a later Model always better?
No.
A later Model usually involves different ways of managing processes and information, but that does not mean every festival needs them.
For example, connecting several systems may reduce manual work in a festival where the same information is used by many teams. In another festival, separate specialist tools and simple manual transfers may work perfectly well.
Change is useful to optimise your film festival when it solves a real operational problem, not because another Model appears later in the sequence.
What if our festival uses practices from several Models?
That is normal.
The result identifies the Model that best describes the underlying way most recurring work is organised. It can also recognise practices from other Models that are already present.
For example, a festival may mainly use separate specialist tools while some processes already reuse information between systems. These practices do not automatically change the overall Model, but they can provide useful examples when reviewing other workflows.
Is this a maturity assessment?
No.
The check does not give your festival a maturity score or place it on a scale from less developed to more developed.
It identifies one of five operational Models that best describes how most recurring festival work is organised. Any of these Models can work well when it fits the festival’s needs.
Does the check recommend Fiona?
Not automatically.
The purpose of the check is to help you understand how your festival currently works and whether anything needs attention to optimise your film festival.
If your answers suggest that a change could be useful, the result may explain where Fiona could support particular workflows. This can include sharing film, screening, guest or accreditation information between processes, reducing repeated manual transfer or connecting Fiona with other systems.
If the current way of working already fits well, changing systems simply for the sake of change is not the goal.
