A client asking to skip a review step, an approval, a discovery call, usually isn't trying to cut corners maliciously. From where they sit, the step looks like a delay standing between them and the thing they actually want. They don't see what the step protects, because they've never seen it fail.
Holding the line well means making that invisible value visible, not just insisting the process exists for a reason.
The client isn't trying to cause a problem
Treating a request to skip a step as disrespect toward your process tends to create friction that wasn't necessary. Most clients asking to skip something are just trying to move faster and don't yet understand what the step is actually protecting against.
Explain why the step exists, not just that it's required
"That's just our process" doesn't answer the client's real question. "This review step is what catches [specific problem] before it becomes expensive to fix" does. A concrete reason is far more persuasive than an appeal to process for its own sake.
In Stelaah, a project's stages and required approvals are visible on the record itself, so a client can see the step is a standard part of how work moves, not an arbitrary delay invented for them. See how projects works.
Offer a faster version of the step instead of none
Where possible, offer a compressed version of the step rather than skipping it outright: a fifteen-minute review instead of a full one, an async approval instead of a scheduled call. This respects the client's urgency while still protecting whatever the step exists to protect.
Name the specific risk of skipping it
If a client insists on skipping the step entirely, name the specific consequence plainly: "without this review, the risk is [specific outcome]." A vague warning is easy to dismiss; a specific one gives the client real information to weigh.
Let them choose, with the risk clearly on record
Once the risk has been named clearly, in some cases the client's decision to proceed anyway is genuinely theirs to make. Confirm it in writing so the choice, and the risk it accepted, is on record rather than something that gets relitigated if it goes wrong.
A simple checklist
If you do nothing else, do these five things:
- Assume good intent, not disrespect, behind the request.
- Explain the specific reason the step exists, not just that it's policy.
- Offer a faster version of the step before agreeing to skip it.
- Name the specific risk plainly if they still want to skip it.
- Confirm the decision and its risk in writing if you proceed.
Do that, and holding the line on a step stops feeling like bureaucracy and starts feeling like the client's own informed decision.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
