Every sequence step carries two switches that decide who drives it forward. The combination most organizations actually want is the middle one, and it is also the one most often over-used.
This article is about deciding, step by step, which ones genuinely need you. It assumes you already know what the two switches are.
"Mark themselves as complete" on, "move themselves to the next step" off.
The person finishes the task on their own, and then waits for you to review it before they advance. It is the right answer whenever you would genuinely look at what they sent.
Ask one question: would I ever act differently based on what they sent?
If the answer is yes, review it. If the answer is no, let it run itself.
Steps that usually need review:
Steps that usually do not:
Every review step is a stop.
A sequence with six review steps needs six separate admin visits before one person finishes onboarding, and each of those is a place the person waits without knowing why. A sequence with one review step in the right place finishes overnight for everybody who does not need a second look.
That is the real trade. It is not about trust, it is about how many times a human has to open the account before someone can start.
Completed steps land on your My Tasks.
That is the list to work from. If nobody is watching it, review steps are exactly where people go quiet, and the person on the other end has no way to tell the difference between "being reviewed" and "forgotten".
Then the step is entirely yours: yours to complete and yours to move forward.
It appears on your My Tasks and it never prompts the person, because there is nothing for them to do. Use it for work that happens off-platform, such as a check you confirm elsewhere or a conversation you have in person.
Yes. The switches are settings on the step, not decisions baked into your sequence.
A reasonable way to start is to set review only where you are certain you need it, run the sequence with real people, and add review to any step that turns out to produce surprises. Loosening later is easier than discovering a backlog.