Glossary
Approval record
An approval record is the stored decision: who decided, when, whether they were a member or a door, and whether the outcome was approve, reject or request changes. It is what you still have when the people have left the thread.
Approval stage
An approval stage is a workflow stage whose type is approval. When an item enters it the engine opens an approval, and the item cannot leave through the approved transition until a decision is recorded with who and when.
Audit log
The audit log is append-only. Decisions, door changes, agreed-round changes and other events are written with who and when. Nothing in it is edited or deleted from the application. Data export includes it.
Automation rule
An automation rule is written as a sentence, compiled, translated back so you can see what it understood, and simulated over the last month of the workspace before it runs. You see how many times it would have fired and on what, while it is still cheap to fix.
Bottleneck
A bottleneck is the stage that holds work longest, shown as median time in stage over a window you pick. If client review sits at four days against a 72-hour default, that is a number from the last month of projects, not an opinion.
Client analytics
Client analytics show which counterparties take longest to decide and which ask for the most rounds, so the next quote is built on the record rather than on memory. The numbers come from approval windows and round counts already stored on the work.
Frame-accurate review
Frame-accurate review means the player steps at the source frame rate of the file, so a note on frame 1,314 is on that frame and not the one beside it. 23.976 and 29.97 are included. This is not a comment on a rounded second.
Gate stage
A gate stage holds the work until a condition is true. The scheduled stage in the campaign pack will not move to live until the publish date is reached, so a card cannot be dragged live early.
Portal door
A portal door is how someone outside the workspace sees work and decides, without an account and without a seat. It is a code, a link, a phone number that receives a one-time code, or an email address, with permissions the workspace chose.
Process audit
A process audit is a proposal that points at a stage whose median time is consistently over its service window and suggests a change to the definition. It is a suggestion you can accept or ignore, not an automatic rewrite of the workflow.
Publish gate
A publish gate is a gate stage that will not let the work go live until a publish date is reached. The campaign pack uses scheduled to live; the social content batch pack uses scheduled to publish. Dragging the card does not satisfy the date.
Review stage
A review stage is an internal look before the work is shown to the client or the next gate. It does not open an approval on entry. A path labelled changes requested typically returns the item to the work stage that produced it.
Revision round
A revision round is a counted pass of client changes against the number the quote allowed. Tasked derives used from review decisions: a session that ended in a request for changes or a rejection consumes a round; an approval consumes nothing.
Rework stage
A rework stage is the stage an item returns to when an approval or a review asks for changes. Client review on the design pack names revisions; release approval on the software pack names in progress. The loop is data on the workflow, not a habit.
Risk score
A risk score is a number derived from named reasons, not typed by hand. Behind pace against the deadline, overdue tasks, blocked tasks, and an approval left waiting for days each add points, and the reasons sum to the score you see.
Saved view
A saved view is a board, list, table, timeline or calendar arrangement with its own filter and sort, kept and shareable. A queue of incidents grouped by assignee is a saved view. The Monday meeting list is another. JQL is not a language here.
Service window (SLA)
A service window is the number of hours a stage is expected to take, stored on the workflow definition. Commercial script approval is 48 hours; wedding final cut approval is 120; incident reported is 8. These are template defaults and every project can change them.
Share link
A share link is a way to hand a file or a gallery to someone without a door: it can carry a password, an expiry date and a download switch, and it can be revoked. It is for delivery, not for a recorded approval.
Timed note
A timed note is a comment anchored to a moment in a file: a frame in a video, a drawing on a still, or a mark on a PDF page. The person who opens the note lands on that frame or that pixel, not on a paragraph that tries to describe it.
Version compare
Version compare opens two cuts or two proofs side by side so the difference is visible, and it can carry notes from the earlier version onto the next one. Nobody has to re-read the last round to check what was addressed.
Weekly owner report
The weekly owner report is a message to the owner of the organisation with the portfolio, the bottlenecks and the risk list, so the Monday conversation starts from the same numbers the screens already show. It is not sent to every member.
White-label portal
A white-label portal presents the client door in the studio's brand. It is a Business plan feature at $249 per month, together with the public API and integrations. The door itself still works on every paid plan without white-label.
Work item type
A work item type is the shape of a piece of work: task, bug, story, epic or request. Each type owns its fields. A bug asks for severity and steps to reproduce; a story asks for acceptance criteria; a request records the channel and who asked.
Work stage
A work stage is where the job is done: brief, edit, in progress, produce, investigating. It can create tasks with a role, an estimate in minutes, and a service window in hours. Leaving it may require the checklist to be done.
Workflow template
A workflow template is a built-in pack of stages, roles, service windows, transitions and approval points. Tasked ships sixteen: five video packs, ten profession packs, and a generic fallback so a software project cannot silently inherit a commercial board.