How to handle a client who wants everything in writing before starting

A client insisting on written confirmation for every detail before work begins is usually protecting themselves, from ambiguity, from an internal audit requirement, from a past experience where a verbal agreement caused a real problem. Treating the request as excessive caution rather than a reasonable ask makes an easy accommodation feel like friction.

Accommodating it well isn't about resisting the extra step. It's building it into the workflow so it doesn't become a bottleneck.

Usually protecting themselves from ambiguity, not testing your patience

The instinct to get everything in writing usually comes from the client's own risk tolerance or past experience, not from a specific concern about you. Recognize it as a reasonable, self-protective habit rather than a personal statement about the relationship.

Build written confirmation into the existing workflow, not a separate burden

Requiring a separate written sign-off process for every decision adds real friction if it's bolted onto an existing workflow as an afterthought. Build confirmation into the normal flow of work, a written recap at the end of a call, a confirmed decision log, rather than a distinct extra step.

Keep each confirmation short and specific, not a formal document every time

A short, specific written confirmation, "confirming we agreed on X," satisfies the underlying need without requiring a formal document for every small decision. Keep the format lightweight so it doesn't become its own source of delay.

Explain the tradeoff plainly if it genuinely slows the project down

If written confirmation for every single detail genuinely adds meaningful delay to the timeline, say so plainly rather than absorbing the slowdown silently and letting the client assume nothing changed. A clear tradeoff conversation is better than a quietly missed deadline.

Use the written record to your own advantage too, not just theirs

A written trail protects you as much as it protects the client, especially if a dispute ever arises about what was actually agreed. Treat the practice as mutually useful, not a concession made only for their benefit.

A simple checklist

If you do nothing else, do these five things:

• Recognize the request as self-protective, not a judgment of you.
• Build confirmation into the normal workflow, not a separate step.
• Keep each written confirmation short and specific.
• Say plainly if it genuinely adds meaningful delay to the timeline.
• Use the written record to protect yourself too, not just them.

Do that, and a request for everything in writing becomes a lightweight habit, not a bottleneck on the project's actual progress.