Pipeline
Statuses and approvals
On the web
Statuses at the top of the pipeline sets the columns your workspace walks and the rules that move cards along them. Everyone in the workspace shares them; editors change them.
Not captured yet
This picture is taken from the running app, not drawn by hand. Run npm run docs:shots to take it.
pipeline-statuses.png
A workspace starts with Idea, Scripting, Script approval, Filming, Editing, Review, Ready to schedule, Scheduled, Published and Rejected. Rename, recolor, reorder, add and delete them to match how you actually work.
| To | Do this |
|---|---|
| Rename | Click the name and type. Enter keeps it. |
| Recolor | Click the dot. |
| Reorder | Drag the handle. Drop it in another group to move it there. |
| Add | Add a status under the group it belongs to. |
| Delete | The trash icon. If cards are on it, pick where they go first; a card with no column is a card nobody finds. |
What a status does
| Behavior | What happens |
|---|---|
| Writes the script | With the script switch on below, a card moved here gets its script written, if it has none. |
| Review | Where cuts are uploaded and noted. |
| Ready to schedule | The column the team schedules from. |
| On the calendar | Where a card goes when Schedule makes it a post. |
| Published | Where a card goes by itself when its post goes out. |
| Rejected | Ideas that were turned down, kept so nobody pitches them twice. |
Each behavior belongs to one status. Giving it to another takes it from the first.
Approvals
Approval is its own thing, not a column: dragging a card into Script approval approves nothing. On each card, Approval is one of:
| Setting | Who signs off |
|---|---|
| No approval | Nobody. The card moves when you move it. |
| Anyone | The first person who can open the card and approves it. Anyone asking for changes sends it back. |
| Named people | Everyone on the list, members or a client's email. The workspace's default approvers are asked when you switch a card to this. |
An approver answers Approve or Ask for changes, with a note if it needs one.
A client who signs off by link
- 1Set Approval to Named peopleOn the card, under Approval.
- 2Type the client's email and press EnterThey join the list as waiting. The card's approval link is made then and there, or the one it already has is used, so a client asked twice gets the same address.
- 3Email it, or copy the linkEmail it opens a message already written in your own mail app, from your address. Copy the link is for a chat or a message you write yourself.
- 4They answer on the linkNo account and no password: they watch the latest cut, then Approve or Ask for changes, signing with the email you asked. Their answer lands on their row and in the card's log.
A client who answers you some other way, on a call or by replying to the email, can have their answer recorded on their row with Mark approved or Mark changes asked; the log keeps who recorded it.
An ordered ladder
Approval ladder on a status is a step-by-step version of Named people: an ordered list of who signs off before a card leaves that column, one step at a time. Each step is a named member, anyone holding a role (owner, admin or member), or the client, who always answers on the share link with no account. Nobody sees a later step until every step before it has said yes. Give it steps and the status becomes a gate; leave it empty and the column works exactly as it did before.
| What a step is about | When it opens |
|---|---|
| The cut (version) | Opens (or reopens, from the top) on its own the moment a new version is uploaded to a card on this status, unless auto-submit is off |
| The script or the brief | Opened by hand: Submit on the card's Approval section, once it is ready |
The last approval on the ladder hands the card to Everyone has approved's status below, the same as any other sign-off. Every step, and the hand-off, is written to the card's activity, so watching the log is watching the ladder move.
Moves that happen by themselves
| When | The card moves to |
|---|---|
| Approval is requested | The status you pick, so the board shows what is waiting on someone. |
| Everyone has approved | The status you pick, the moment the last yes comes in. |
| Changes are asked for | The status you pick, so a client's no lands where the fix gets made. |
| A card is moved into a status you pick | Nowhere; that move counts as approving it, for teams that sign off by dragging. |
Hold posts until they are approved
With this switch on, a card that asks for a sign-off keeps its post from going out until the last yes comes in; then it goes out at its time. The post's composer says it is waiting. If it is still waiting six hours after its time, it is marked missed with that reason, and you pick a new time. It is for clients who must see everything before it posts, and it is held by MORR's servers, so no device or teammate can post around it.
Scripts
The default length a card's script is written to, short form or long form, and the switch that writes a script when a card moves into the status that Writes the script. The switch is off to start, because plenty of videos are shot from a brief.