Six client email examples for briefs, missing files, progress, scope, blockers and review requests. Keep ownership and the next action clear.
These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.
Understand the desired result before proposing work.
Hello [name], Thanks for outlining [project]. To understand the work, could you share the main audience, the intended outcome, and any existing material I should review? [your name]
Tailor the questions to the work. Ask about a deadline without treating it as an accepted delivery date.
Get the specific files needed for the next step.
Hello [name], For the next step on [project], I need [specific files or information]. Could you share the current versions and note which one should be treated as final? Thank you, [your name]
Specify file types only when needed. Use the client’s approved sharing method.
Explain completed work and the immediate next action.
Hello [name], Here is a brief update on [project]. Completed: [verified work]. Next: [next action]. Input needed: [question or none]. [your name]
Keep completed and planned work separate. Remove the input line if no response is needed.
Recognize a change without accepting it automatically.
Hello [name], Thanks for the additional request about [change]. I’ll compare it with our current agreed scope and outline any effect on the work before we decide how to proceed. [your name]
Check your actual agreement. Add costs or dates only after evaluating and confirming them.
Make a dependency visible before work stalls.
Hello [name], I can continue with [available task], but [blocked task] depends on [missing input]. Could you share it or let me know who can help? I’ll review the plan once it is available.
Separate work you can do from blocked work. Do not invent a revised deadline.
Get an actionable review of a draft.
Hello [name], The draft of [deliverable] is at [link and version]. Could you review [specific aspect] and add comments in [agreed place]? I’m looking for feedback on [question] before the next stage.
Limit the review to the current stage. Use the handoff collection for final file delivery.
Freelance work brings familiar conversations with different details. Save the questions that help you understand a brief, then adapt them to the client and project. Use fields for names and milestones to make omissions easier to notice.
Prices, delivery dates, revision limits, and rights must come from your actual agreement. These examples do not establish terms or make legal commitments on your behalf.
Use a folder for a client only when it improves retrieval; tags can describe shared purposes like files or progress. A reusable signature avoids maintaining the same closing in many snippets.
Review every response before sending. PhraseShelf stores this organization locally and does not share a workspace or synchronize changes with clients.
Copy an example, choose New snippet, give it a title and enter its suggested alias in Shortcuts and aliases. Paste into Plain text, edit the details, then choose Save snippet. Test it in Help & practice with the alias followed by Space.
For changing details, replace each bracketed label with a real field in the visual editor. Keep punctuation in the adjacent text segments. Preview a short and a long answer, then review the final message before using it. Choose a different alias if the suggestion already exists in your library.