Teams reach for automations hoping to work faster, which is the wrong thing to expect from them. An automation cannot edit, write or decide. What it can do is remove the ten seconds of admin at each handoff, and remove the times somebody forgets the handoff entirely.
That second part is where the value is. Work rarely stalls because a step is slow; it stalls because nobody noticed the step was ready to start.
The moments worth a rule
A task changes hands a handful of times, and those are your rules — the cut lands and someone has to review it internally, internal review clears and the client has to see it, the client answers and the editor has to act, the client approves and the rest of your tools should know.
Everything between those moments is craft, and rules have nothing useful to say about it.
Three questions before you write a rule
Have I done this by hand more than twice? If not, you are automating a guess about your own process.
Is the answer always the same, with no judgement in it? “Move to In review when a cut is uploaded” always has the same answer. “Send it to the client” does not.
If it fires at the wrong moment, is it cheap to undo? Changing a status is cheap; emailing a client is not. That third question is the one that decides how carefully you build the rule, because a rule that only moves fields inside your workspace can be wrong for an afternoon, and a rule that reaches a client is wrong in front of the client.
Check the built-in switches first
Above your own rules, Workspace Settings → Automations has a Built-in automations section: Automatic review status, Move to in progress on timer start, Leave planned phase on timer start and Clear internal blocker on timer start.
These are switches rather than editable rules, and they already cover a fair amount of what teams sit down to build. Read them before writing anything.
Rules are reversible
Every automation has an Active toggle, so when you are unsure whether a rule belongs, turn it off for a week and see whether anyone misses it. Automations are per workspace and only admins and owners can edit them, which keeps the list short enough to actually read.
Tip: Name rules after the moment rather than the mechanism. Cut lands → internal review tells the next admin what the rule is for; Set blocker on upload only tells them what it does.
What’s next
Don’t build from zero: Start from a preset and trim it.