What happens, when, and who owns it.
One production plan for the whole event, in the same workspace as the crew. Tasks, times, departments, suppliers and status, instead of a shared sheet that several people are editing at once.
One plan instead of a shared sheet.
Every row carries the work, the time, the owner and the part of the production it belongs to. Edited in place, while the production is running.
The work itself
What needs doing, what is needed for it, and a comment when the row needs explaining. Rows are edited in place, so a change during build-up takes a click instead of a new version of the file.
Dates, times and deadlines
A planned date, a start time, a deadline and planned hours. Work that has run past its deadline is marked on the row rather than found later.
Owners, not initials in a cell
One or more named people responsible for a task, and one or more departments that own it. Both are real records, so the plan filters down to what a person or a department is actually holding.
Status the whole team reads the same way
Unconfirmed, not started, ongoing, ok, follow-up and completed. Six states in the order work actually moves through, with priority from low to critical.
Organised the way the production is.
The plan borrows the structure the workspace already has, rather than asking you to invent a second one.
Departments that hold people
Departments are their own structure with their own members, and they nest. A task can sit with one department, several, or all of them at once.
The phases the project already uses
Every task belongs to a phase of the project, so the plan narrows to the stretch you are in: whatever your production calls build-up, show days and tear-down.
Suppliers on the tasks they deliver
A task carries the supplier responsible for it, from the supplier register or as free text. A separate supplier view lists what each one is on the hook for, by date, ready to print.
A plan you can work from at 06:00.
The plan is a working surface while the production runs, not a document that goes stale after the first morning.
A day view for the floor
Pick a day and work the list. Start a task with a headcount, close it with a comment, or mark it done in one tap. Ordered by priority first, then by time.
Down to your slice in one go
Filter by department, responsible, supplier, phase, location, type, label, priority and status, and search free text across the plan. Finished work is out of the way by default.
The crew on the same plan
Shifts scheduled for the project appear on the plan as locked rows, so the work and the people booked to it sit in one view instead of two systems.
Bring the sheet you already run on.
Most productions arrive with a production sheet that works. It comes across as it is, without a rebuild.
1. Paste or upload
Paste straight out of the sheet, or upload a CSV with commas or semicolons. There is a template if you would rather start from one.
2. Settle the ambiguous column
Every distinct value in the sheet's department column is resolved as a department, a location, or both, before a single row lands. Values nobody has classified stop the import instead of being guessed at.
3. Import as one batch
Rows arrive together as one recorded batch. A status the plan does not recognise is kept in the comment rather than forced into the nearest one.
Production plan is part of HR Cluster Ops.
Not a separate product and not a separate subscription. Ops workspaces switch it on when they want it, and it runs on the same projects, locations, people and suppliers as the rest of the platform.