Approval workflows
Approval workflows that move work forward, not sideways.
Reviews and approvals are where work waits longest. Usually not because the reviewer is slow, but because nobody can tell whose move it is after the feedback arrives. Relay makes the next step part of the review itself.
An approval should change the work's state, not just end a conversation.
The problem
Feedback without a next step is not a review.
The common failure is not missing feedback — it is feedback that lands somewhere without changing anything. Comments in three places, an approval given verbally, a file that is still sitting in the reviewer's hands while the owner assumes it moved on.
The second failure is quieter: a reviewer becomes a de facto owner because the tool moved the work to them and never moved it back.
- Scattered feedback
- Comments live apart from the work.
- Pseudo-owners
- The reviewer ends up holding the work.
- No next step
- Approved, but nobody knows whose move follows.
Review
Send for review. Stay the owner.
Sending for review moves the action to the reviewer and leaves ownership with you. They see it under Needs you. If they request changes, it comes back to you with the feedback attached. If they approve, the work moves forward — still under a clear owner.
Tuesday, September 8
Good morning, Maya.
Here’s what needs you, what you chose, and what is moving with someone else.
Needs you
0Today
1Homepage copy
Website refreshplanned for todaydue Friday
MS
Waiting on someone else
0Upcoming
0Homepage copy sits under Today because Maya planned it for today. Due Friday.
The loop
Three outcomes, each with an obvious next move.
A review round in Relay can only end in a way that names the next person. That is what stops work sitting in a reviewed-but-unmoved state.
- Changes requested
- Back to the owner, with the feedback on the work.
- Approved
- The work moves forward under the same owner.
- Resent
- Returns to the reviewer for another look.
Multiple reviewers
Approvals stack without stacking owners.
Marketing and creative work often needs more than one sign-off: brand, then legal, then a stakeholder. Because a review never transfers ownership, each of those rounds can happen without the owner changing and without anyone having to reclaim the work afterwards.
The owner keeps it in Waiting on someone else while a reviewer has it, so the queue of sign-offs is visible rather than remembered.
Project Pulse
Approvals are the status update.
Each send, change, and approval is an event, so Project Pulse can show what needs attention, what moved, and what is next without anyone writing it down. Status comes from what happened, not from someone rewriting what happened.
Project Pulse · today
Website refresh
A live read of what needs attention and what moved.
On track
“The homepage is in review and the launch work is moving on schedule.”
Updated today by Maya
Needs attention 2
- Homepage copy · Maya owns it · Sarah has it for review
- Packaging feedback · changes came back to Maya
Recent movement
- MOMaya passed Photography selects to Alex2h
- SCSarah approved Email campaignyesterday
Best practices
Principles for approvals that do not stall.
A good approval workflow is less about the number of steps and more about every step ending in a clear next move.
- Name the reviewer
- Ask a specific person, not everyone who might care.
- Keep the owner fixed
- Review changes who acts, not who is accountable.
- Feedback on the work
- Keep comments with the thing being reviewed.
- End every round explicitly
- Approved or changes requested, never just silence.
- Sequence sign-offs
- Run brand, legal, and stakeholder rounds one at a time.
Example
A campaign asset through two sign-offs.
A designer owns a paid social asset that needs brand and then legal approval. She sends it to the brand reviewer, who requests a change; it comes back to her with the note attached. She revises and resends, and brand approves.
She then sends it to legal. Throughout, the asset stays hers, it sits in her Waiting while a reviewer has it, and each outcome is recorded — so anyone checking the project sees where the asset is without asking.
Explore Relay
Keep reading
Run your next approval in Relay.
Start free, send a real piece of work for review, and see the next move stay obvious the whole way through.
Free for solo use. Team starts with 14 days free — no card required.