TillyGen and monday.com
monday.com shows status in colored columns anyone can read in three seconds. That readability is the point — the board reports on the production, the production runs on the plan.
What this is about
monday.com organizes work as boards with status columns, owners and dashboards across projects. Agencies use it to show clients and management where things stand without a meeting. A film production benefits from exactly that surface: one row per work package — concept, casting, location, shoot day one, edit, delivery — with a status color and an owner. The depth behind those rows is not monday.com material: which shot needs which lens at which location lives in TillyGen. The CSV import from Excel or a CSV file sets the board up; the status updates are human, weekly, deliberate.
An integration is good when nobody talks about it any more: the data is where it is needed and nobody exports anything.
What runs differently here
Where this differs from the general case:
- The board import from a CSV file creates rows from TillyGen data once — phases and dates arrive prefilled instead of typed
- Status columns answer the client's only real question — on track or not — without exposing the working plan
- A dashboard across several production boards shows the studio's whole slate, each board fed by its own TillyGen plan
- The TillyGen plan link sits in the board description for anyone who needs depth behind a red status
Step by step
This order gets you there fastest:
- Break the production into reportable packages — phases and milestones, not shots — and export that structure from TillyGen as CSV.
- Import the CSV into monday.com to create the board, map the date column to a timeline, and add a status column with your color convention.
- Put the TillyGen plan link into the board description, so depth is one click away when a status turns red.
- Update statuses on a fixed rhythm — weekly in prep, daily around shoot days — and resist mirroring plan details into extra columns.
- When dates shift in TillyGen, correct the affected rows in the same sitting; a status board that lags its plan reports fiction.
Common pitfalls
What most often goes wrong in practice:
- The board grows columns until it becomes a second plan — now every change needs entering twice, and one of the two places is always behind
- Client reads 'green' on a board nobody updated since the location fell through last Thursday
With TillyGen
The monday.com board is the production's public face; TillyGen is its working interior. Keep the board coarse and honest, keep the plan detailed and current, and let the link between them carry the traffic.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
How detailed should the monday.com board get?
As coarse as reporting allows: phases and milestones with status and owner. The moment a board row needs shot-level detail to make sense, that detail belongs in TillyGen, linked.
Does TillyGen push updates to monday.com by itself?
No native link exists. The board starts from a CSV import, and status updates stay a human act — or you wire the TillyGen API through an automation tool if the volume justifies it.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.