Producing nearly 30 independent films a year requires more than filmmaking talent. It requires a scheduling operation that can track which students are available, assign the right people to the right roles across multiple productions, and manage timelines that can stretch across more than one semester — all without creating conflicts that disrupt a student’s academic commitments or a production’s momentum.
For FSU’s College of Motion Picture Arts, that operation had been running on spreadsheets. OrangeDot replaced it with something purpose-built for the problem.
What We’ll Cover
- About FSU’s College of Motion Picture Arts and the scale of their annual production program
- Challenge 1: Coordinating 150 students across 30 productions in spreadsheets with constantly changing data
- Challenge 2: No conflict detection and no visual timeline view spanning multiple semesters
- How OrangeDot built a custom-coded interactive Gantt application on monday.com
- The combined impact: live conflict detection, drag-and-drop scheduling, and data that’s finally reliable
About the Client
The Florida State University College of Motion Picture Arts is one of the country’s leading film schools, enrolling over 200 undergraduate and graduate students pursuing Bachelor and Master of Fine Arts degrees in Tallahassee, Florida. The program is built around hands-on practice: students develop their craft by actually making films, executing real productions throughout their degree program rather than studying filmmaking in the abstract.
Each year, the program produces close to 30 independent films. Students move through the program in cohorts, with each cohort taking on production-related work every semester. Both undergraduate and graduate students contribute to these productions in multiple roles — and understanding which students have the capacity, the right skill set, and the availability for any given role is a critical operational function that has to work reliably across the entire program.
A Scheduling Problem That Spreadsheets Couldn’t Solve
FSU’s scheduling challenge was a genuinely complex one. It wasn’t just about assigning names to roles — it required tracking availability across nearly 150 students, managing timelines that spanned semesters, cycling cohorts through the program while keeping all the data current, and catching conflicts before they disrupted a student’s academic workload or a production’s schedule. Spreadsheets had always been the tool for this work. They were also, increasingly, the problem.
Coordinating role assignments across nearly 150 students and multiple simultaneous productions required managing an enormous volume of data that was constantly in flux. Students cycled through cohorts each semester, availability changed, and production timelines shifted. Any given piece of information in the spreadsheet could be outdated by the time someone needed to rely on it.
The multi-semester nature of film production added another layer of complexity. Scripting and pre-production might happen in one semester; principal photography in another; editing and post-production down the road. A student committed to a role in the fall might need to be tracked against availability in the spring or even the following year. Maintaining that continuity across semesters in a spreadsheet was not just cumbersome — it was nearly impossible to do accurately at scale.
The result was a scheduling process that consumed significant manual effort, produced unreliable data, and left the team without the clear capacity visibility they needed to make confident role assignments across the program.
Spreadsheets can store data about student availability and role assignments, but they can’t reason about it. They can’t tell you whether a student is already committed to another production during the same time block, or flag when a multi-semester role assignment creates a future conflict. At the scale of a 150-student program producing 30 films a year, the manual work required to do that reasoning manually isn’t just slow — it’s error-prone in ways that affect real students and real productions.
Without a system that could understand a student’s existing commitments, the FSU team had no reliable way to catch scheduling conflicts before they occurred. A student could be assigned to overlapping roles across two productions, or committed to work in a semester where they had other academic requirements, and the spreadsheet offered no signal that anything was wrong. Conflicts were discovered after the fact — if they were discovered at all.
The absence of a visual timeline view compounded the problem. Film productions have a natural chronological structure — development, pre-production, production, post-production — and understanding how those stages overlapped across 30 simultaneous productions, mapped against 150 students’ availability windows, required a spatial view that rows and columns simply couldn’t provide. The team was trying to manage a multi-dimensional scheduling problem with a two-dimensional tool.
A scheduling system that can’t enforce constraints isn’t really a scheduling system — it’s a record-keeping system that still puts the full burden of conflict detection on the people using it. When the data is as complex and dynamic as it is at FSU, the cognitive load of manually detecting conflicts across 150 students and 30 productions isn’t just impractical. It’s a systematic source of errors that affects students and productions every semester.
The solution: a custom-coded interactive Gantt application built on monday.com
Custom development beyond monday.com’s native capabilities
OrangeDot recognized early in the engagement that the FSU team’s needs went beyond what monday.com’s native features could provide out of the box. The solution required a purpose-built interface — one that combined the platform’s robust data infrastructure with a custom-coded, interactive application layer designed specifically around how the FSU production scheduling process works.
Interactive Gantt chart with click, drag, and drop
At the center of the solution is a customized Gantt chart view that displays all roles across every active production on a visual timeline. The team can see the full picture of who is assigned to what and when — and can adjust timelines by simply clicking, dragging, and dropping roles or productions directly on the chart. What previously required manual cell-by-cell editing in a spreadsheet is now a visual, intuitive interaction that takes seconds.
Live conflict detection with error messaging
When the team attempts to assign a student to a role that overlaps with an existing commitment, the system immediately surfaces an error message and prevents the assignment from being made. Conflicts can no longer slip through. The team always knows whether a student is available for a given time block before the assignment is confirmed — not after they’ve already been scheduled.
Semester-based views and custom field filtering
The application supports customized views organized by semester, making it easy to focus on what’s happening in the current production cycle without the noise of past or future assignments. Custom fields — including production cycle, cohort, and role type — can be used to filter the data into exactly the view the team needs for any given planning task. The complexity of 30 productions and 150 students is always manageable because the team controls what they see and when.
The combined impact
Scheduling that’s faster, more reliable, and conflict-proof
The new application is significantly faster than the spreadsheet process it replaced, cutting the time and manual effort required to assign students to roles across multiple productions. More importantly, the data it produces is reliable in a way that the spreadsheets never were — because the system enforces the constraints automatically rather than depending on someone to catch conflicts manually.
Live conflict prevention, not after-the-fact discovery
The shift from reactive conflict management to proactive conflict prevention is the most meaningful operational change the new system delivers. The FSU team can now assign students to roles with confidence, knowing that if an assignment creates a problem, the system will tell them immediately — before it affects a student’s schedule or a production’s timeline.
New capabilities that spreadsheets couldn’t offer
Beyond the speed and reliability improvements, the application gives the FSU team capabilities that simply didn’t exist before: a visual Gantt view of all productions and roles, drag-and-drop timeline adjustment, semester-based filtering, and a single central hub that reflects the current state of the entire production program at any given moment. The gap between what the team needed and what their tools could do has been closed.
30 films produced annually · 150 students coordinated across overlapping productions · Multi-semester timelines tracked in one visual application · Conflict-free scheduling enforced by the system, not manual review
FAQs
Why build a custom application instead of using monday.com’s native Gantt view?
monday.com’s native Gantt view is a powerful general-purpose tool, but FSU’s scheduling requirements were specific enough that a purpose-built application was the right approach. The ability to detect conflicts in real time, enforce capacity constraints at the student level, and surface immediate error messages when an invalid assignment is attempted required logic that goes beyond what native Gantt functionality supports. OrangeDot used monday.com’s infrastructure — its data storage, APIs, and platform capabilities — as the foundation for a custom-coded interface built exactly around how FSU’s production scheduling process works.
How does the system handle timelines that span multiple semesters?
The application was designed with multi-semester production lifecycles as a core requirement. Roles and production stages can be scheduled across any time range, and the system tracks student commitments continuously — not just within a single semester view. When a student is assigned to a role that extends into a future semester, their availability during that period is updated in the system immediately, so any subsequent assignment attempt that overlaps with that commitment will trigger a conflict error regardless of when the conflict falls.
Can the application accommodate the cycling of new cohorts into the program each semester?
Yes. As new cohorts enter the program, their student records are added to the system using the same data structure as existing students. Their availability windows, role histories, and semester commitments are tracked from the moment they enter the program, and they appear in the conflict detection logic immediately. The semester-based view and production cycle filtering make it straightforward to separate new cohort activity from ongoing productions managed by more advanced students.
Is this type of custom development appropriate for organizations that aren’t ready for a fully custom-built system?
OrangeDot’s approach was to build on monday.com’s infrastructure rather than build something entirely from scratch — which means the FSU team benefits from monday.com’s reliability, security, and ongoing platform development while using an interface tailored to their specific needs. This hybrid approach gives organizations access to custom functionality without the overhead and maintenance burden of a fully bespoke system. For organizations with standard scheduling or project management needs, native monday.com features are often the right starting point — custom development is most valuable when the problem is genuinely specific enough to justify it.
Final thoughts
The challenge FSU brought to OrangeDot wasn’t a failure of effort or organization. Their team was doing everything they could with the tools available to them. The problem was that the tools available — spreadsheets — weren’t capable of solving the problem they were being asked to solve. No amount of careful manual work can make a spreadsheet detect conflicts in real time or render a multi-semester Gantt chart that responds to drag-and-drop.
Sometimes the right solution is a platform configuration. Sometimes it’s a workflow redesign. And sometimes — when the problem is specific enough and the requirements go far enough beyond what existing tools can do natively — the right solution is a custom-coded application built on a solid foundation. That’s what this engagement required, and that’s what OrangeDot delivered.
If your organization has a scheduling or coordination challenge that your current tools can’t solve, we can help you figure out what the right solution actually looks like. Talk to an OrangeDot expert →