"Just following up on this" is the most common sentence in freelance client communication, and it's a symptom, not a communication style. If you find yourself writing it often, the problem usually isn't the client — it's that your approval process makes saying "yes" harder than it needs to be.
Friction is invisible to the person who built the process
You know exactly which file is current, what changed since the last round, and what you need from the client. They don't. Every ounce of context that lives only in your head is friction they have to overcome before they can approve anything — and busy people default to postponing decisions that require effort to make.
The fix is almost always the same shape: move context out of your head and into the delivery itself.
Five changes that consistently speed up approvals
- Show only what needs a decision. If a client has to scroll past six irrelevant files to find the one you need approved, you've added a decision before the decision.
- State what changed, every time. "Updated based on your note about the header" takes ten seconds to write and removes a re-review of the whole deliverable.
- Make "approve" a single action. If approving requires replying to an email with specific wording, some fraction of clients will approve informally in a way you can't rely on later.
- Make the deadline explicit, not implied. "Let me know what you think" has no deadline. "This link is available for review through Friday" does.
- Close the loop visibly. When an approval happens, both sides should see it happen — not just the person who clicked the button.
What this looks like in practice
Picture two identical situations. In the first, you email a zip file with a note; the client has to download it, find the right subfolder, and reply in the thread to approve. In the second, the client opens a link, sees exactly one released version with a short note about what changed, and clicks Approve.
The work is the same. The approval speed is not — because you've removed every point where the client has to do work just to give you their attention.
Rejections are part of a fast process too
Speeding up approvals isn't only about getting to "yes" faster — it's about getting to a clear "not yet" faster too. A process that only has room for "approve" quietly pressures clients into silence when they're unsure, which is worse than a clean rejection with a reason attached. Give clients an equally easy way to say "this needs changes, here's why," and you'll find approvals speed up because rejections got easier, not despite it — clients stop sitting on ambiguous feedback they didn't have a clean way to express.
The underlying principle
Every piece of friction you remove from the client's side of the process shows up as faster turnaround on your side. It's not about being pushier. It's about designing the interaction so that the easiest thing for the client to do is also the thing that moves the project forward.