One engine, many professions
The same workflow engine that runs a commercial from brief to delivery also runs a software change from intake to release, a design request from concept to final files, and an incident from report to customer verify. Stages have types (work, review, approval, gate, done), an approval stage refuses the exit without a recorded decision, and the person who decides can do it through a door with no account. Video is the first profession the engine was tuned for, not the only one it can carry.
7 min read
What the engine actually is
A workflow is a list of stages and the transitions between them. Each stage has a type: work, review, approval, gate or done. Work stages create tasks with a role and, where the pack sets one, a service window in hours. Review stages are internal. Approval stages open an approval on entry and refuse the approved transition until a decision is recorded. Gate stages hold the work until a condition is true, such as a publish date being reached. Done is the end.
Sixteen built-in packs use that same object. Five of them are video (commercial, wedding film, corporate video, social content batch, documentary). The others are software, sprint, bugfix, release, design request, campaign, test cycle, incident, project delivery, approval flow, and a generic fallback so a software project whose template is missing cannot silently inherit a commercial board.
A rejection or a request for changes sends the item to the rework stage the pack names. That loop is data on the workflow, not a colour someone remembers to set.
- Stage types: work, review, approval, gate, done
- Approval opens on entry; the engine refuses the exit without a decision
- Sixteen packs, one engine; generic is the fallback, not a video board
Work items that are not all the same card
Every workspace starts with five kinds of work item: task, bug, story, epic and request. A bug asks for severity (blocker, major, minor, cosmetic), steps to reproduce and where it was found. A story carries acceptance criteria and story points. An epic carries a goal and a target date. A request records the channel, who asked, and a reference. Custom fields extend any of them.
The hierarchy is built in: an epic contains stories, a story contains tasks. Video work still uses tasks; software and QA use bugs and stories on the same board; support uses requests. The engine does not care which type is on which stage, which is why one product can carry more than one profession.
The person outside the workspace
A client, a brand owner, a legal reviewer, a customer confirming a fix: none of them need a seat. They receive a door with a code, a link, a phone number or an email address. Through it they can watch, leave notes, upload, download, and press approve, reject or request changes, with the permissions the workspace chose for that door.
A door expires on the date that was set and can be revoked. There is no per-client charge. Plans are priced per workspace by active projects, storage and members. Clients and approvers do not count as members.
What every profession still shares
Board, list, table, timeline and calendar views are saved and shared. Search covers tasks, projects, comments and files and returns an answer, not only a list. Analytics show median time in each stage, which counterparties take longest to decide, and a risk score whose reasons add up to the number on screen. The weekly owner report carries the same figures.
A rule is written as a sentence, compiled, translated back so the author can see what it understood, and simulated over the last month before it runs. Automations, search and analytics are included from the Professional plan ($99 per month). The public API, webhooks and a white-label portal are on the Business plan ($249 per month). Starter is $29 per month with a 14-day trial at $0 on Starter's limits and no card.
What this page is not claiming
There is no native mobile app; the product is responsive in the browser. There is no marketplace of apps. There is no JQL language, no CMDB, no Advanced Roadmaps, no Tree view, no RICE or MoSCoW scoring. A sprint-shaped workflow pack exists; a sprint as an object with start and end dates does not. Time tracking, CSV import, and a Gantt chart with dependency arrows are not here. GitHub is not integrated; the public API and webhooks are what a team uses to wire its own bridge.
Those absences are listed so a reader can choose honestly. The six articles that follow this one show the engine on software, design, marketing, QA, support and a generic approval, with the same honesty.
Questions that keep coming up
- Is Tasked still a video product?
- Video is the first profession it was built for, and the five video packs, the frame-accurate player and revision rounds are still there. The engine, the work item types and the doors are not video-only.
- Do I buy a different product for software or support?
- No. The same workspace can run more than one pack. A studio that also ships software can open a software project beside a commercial without a second account.
- Which plan do I need for analytics and automations?
- Professional, at $99 per month. Starter at $29 still records stage intervals on every project; the aggregate analytics view and automations are what Professional adds.
- Is there a GitHub integration?
- Not yet. The public API and webhooks are available on the Business plan for a team that wants to wire its own bridge.