TillyGen and ClickUp

What this is about

ClickUp positions itself as the everything-tool: spaces per client, lists per project, tasks with custom statuses, docs and time tracking attached. For an agency that shoots content among many other deliverables, this is the operational spine — capacity, billing and deadlines all hang there. A production plugs in at task level: phases from the TillyGen plan arrive via CSV import, statuses mirror the production phases, and the plan PDFs attach where account managers look. What does not move into ClickUp is the plan's interior: shot logic, day structure, and the call sheet chain stay in TillyGen.

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

In planning terms, that means:

• ClickUp's CSV import builds the production list from TillyGen data — phases, owners, due dates — inside the client's existing space
• Custom statuses named after production phases — briefing, planning, shoot, post, delivered — read correctly to account managers
• Time tracked on the production tasks meets the day estimates that came from the TillyGen schedule, which makes post-mortems honest
• The schedule and call sheet PDFs attach to the list's top task, one refresh per plan change

Step by step

This order gets you there fastest:

1. Create the production list in the client's space and define statuses along production phases instead of generic to-do labels.
2. Export the phase and deliverable structure from TillyGen as CSV and import it, mapping due dates and owners onto ClickUp fields.
3. Attach the current schedule PDF to the list's anchor task and link the TillyGen plan for anyone needing shot-level answers.
4. Let the agency machinery run — time tracking, workload, billing views — while every plan-level change happens in TillyGen first.
5. After each change, refresh the anchor task's attachment and adjust only the tasks whose dates actually moved.

Common pitfalls

What most often goes wrong in practice:

• ClickUp docs start hosting a parallel shot list because 'everything should live in one tool' — two months later the versions disagree
• Status automation closes tasks on due date while the shoot actually slipped a week — the dashboard celebrates a fiction

With TillyGen

ClickUp answers what the agency is doing this week; TillyGen answers what the shoot needs on Thursday. The CSV import sets the frame once, and the attachment refresh keeps the frame honest.

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.