Tasks
Track the work, not just the gear — rewires, repairs, renders, approvals.
What tasks are for
The rest of the app tracks things a project needs. Tasks track work someone has to do: rewire the FOH rack, RMA a dead panel, render the lobby plate, get the rigging plot signed off. Every project has a Tasks tab.
A task carries a type, and the types are the vocabulary of an actual shop rather than generic tracker verbs — Build, Install, Rewire, Repair, Scenic, Rigging; Shoot, Lighting, Sound, Prep, Strike, Safety; VFX, Edit, Render, Asset; Bug, Test, Purchase, Document, Approval, General. Each has its own icon, so a board reads at a glance.
Filing one
Add task on the board opens a short wizard: what it is and its type, then who it's for and when it's due, then two optional steps — is it about specific items, and does it need any extra properties. Both optional steps skip in one click, so a plain task is still about three.
For rapid capture there's a quick-add field at the top of the board: type a title, press Enter, done. Change your mind and want the full form? More options… carries what you've already typed straight into the wizard.
Raising a task from where you found the problem
Most work gets noticed while you're looking at something else. Right-click a node on a Routing or Flow diagram and choose Create task — the task remembers which node it came from, and if that node is a buying-sheet row it links the row too, so the cost rollup works immediately.
In Docs, highlight any passage and a Create task button appears above the editor. The task quotes what you highlighted and names the document.
None of this writes anything to the diagram or the document — the link lives on the task. Delete the node or rewrite the paragraph later and the task still reads as what you meant, instead of leaving a marker pointing at nothing.
Subtasks
Any task can be broken into steps. Add them from the task's own panel, tick them off there or on the board, and the parent shows how far along it is — "3/7 subtasks". Steps inherit their parent's type unless you change it.
Nesting stops at one level on purpose. A punch-list is read top to bottom, and a tree of sub-sub-tasks is harder to work than the list it replaced.
Pointing a task at real things
A task can name the buying-sheet rows it's about. Those rows then show the task back on their own detail drawer, so someone opening an item sees the work outstanding against it without going looking.
Give a task the Purchase type and link some rows and it totals them for you: what's still to buy, how many units are already in hand, and the full cost. The numbers come from the sheet itself, so they can never drift from it — and budgets stay where they belong, on the project.
On a project with subprojects, a task can name which subproject it concerns. It stays on the parent's board and also appears on that subproject's own, marked as coming from the parent — so neither side has to remember to check the other.
Assigning and finding your work
Assign a task to anyone in the workspace, give it a due date and a priority, and it turns up on their My Tasks page — everything assigned to them across every project, overdue first. The sidebar shows a count of what's been assigned to you since you last looked; opening the page clears it.
Overdue only ever means open work past its date. A task that's done or cancelled is never overdue, however late it was.
Letting anyone report a bug
Intake link on the Tasks tab creates a public form — a URL and a printable QR poster — that anyone can use to report a fault without an account. Tape it to a rack at a show and a passer-by can tell you the left screen is dead; it lands on this project's board as a BUG task like any other.
You choose what the form says: its heading, a message, a contact email for anything urgent, and optionally a webhook that fires on each report. All of it stays editable afterwards, so fixing a typo never means reprinting the QR.
Revoking the link stops it instantly and any printed QR goes dead — reports already received stay on your board. Links are throttled per hour, so a link left up in public can't be used to flood you.
Everything else on a task
- Status — To do, In progress, Blocked, In review, Done, Cancelled. Finishing one stamps when.
- Custom properties — the same freeform fields library items use, for whatever your shop tracks.
- Comments — a thread per task, the same as on a BOM row.