Email Templates for Requesting Materials From Clients

Clients ignore vague requests buried in a busy inbox. These five copy-paste templates — request, two reminders, an escalation, a thank-you — fix that.

Why the first email usually fails

Most "please send over your logo and photos" emails get skimmed once and then buried by the next twenty messages that land in the client's inbox that day. It isn't that the client doesn't care about the project — it's that the request didn't ask for anything they could act on in the ninety seconds they had free. A vague ask produces a vague non-answer, or no answer at all, and three weeks later you're the one explaining to your own client why the site isn't live yet.

The fix is mostly structural, not tonal. A request that gets answered has:

Everything below builds on that structure. Copy the templates, fill in the brackets, and keep the tone as written — polite and specific reads as competent; apologetic and vague reads as optional.

Subject lines and thread hygiene

Reply in the same email thread every time instead of starting a new one. A client who has three separate threads about "the logo" cannot tell which one is current, and neither can you when you search your own inbox six weeks later.

Subject line rules that hold up across all five templates:

Stage Subject pattern Why
Initial request {project_name} — a few things we need to get started Names the project, not you or your company; frames it as a short list.
Gentle reminder Reply on the same thread, unchanged subject A reminder is not new information; a new subject line makes it look like it is.
Firm reminder Reply on the same thread, or prefix with Action needed: if it's been over a week The prefix should be rare enough that it still means something when it appears.
Escalation {project_name} is on hold — need {items} to continue States the consequence plainly instead of implying it.
Thank-you Reply on the same thread Closes the loop the client can see, which matters more than it sounds.

The templates

Placeholders are in {braces}. Delete anything in a template that doesn't apply to your project rather than leaving it half-filled — a template with unfilled brackets reads worse than no template at all.

1. Initial request

Subject: {project_name} — a few things we need to get started

Hi {client_name},

To get {project_name} moving, I need the following from you:

- {item_1} (e.g. your logo, ideally the original SVG or AI file)
- {item_2} (e.g. 5-10 photos of {subject})
- {item_3} (e.g. your current opening hours / pricing / bio text)

{one_sentence_reason_it_matters, e.g. "The logo drives the whole color
palette, so it's the one thing I can't start without."}

Whatever you have is fine — I can work with rough drafts and will follow up
with questions rather than waiting for something perfect. If you can get this
to me by {deadline}, we stay on track for {milestone}.

Thanks,
{your_name}

2. Gentle reminder (first follow-up)

Send this if nothing has arrived after 2–4 business days. Keep it short — a long reminder reads as nagging; a short one reads as a nudge.

Subject: (same thread)

Hi {client_name},

Just a quick nudge on the list from {day_of_week} — still need:

- {remaining_item_1}
- {remaining_item_2}

No rush if you're mid-week busy, but flagging it so it doesn't slip past
{deadline}. Happy to hop on a 5-minute call if that's faster than typing it
all out.

{your_name}

3. Firm reminder (second follow-up)

Send this 5–7 days after the first request, or 3–5 days after the gentle reminder if the deadline is close. The tone shifts from "nudge" to "this is now affecting the timeline" — still polite, but no longer soft.

Subject: Action needed: {project_name}

Hi {client_name},

We're now {days_overdue} days past the date we'd hoped to have these, and it's
starting to push the whole timeline back:

- {remaining_item_1}
- {remaining_item_2}

If something's blocking you on any of these — you don't have the file, you're
not sure what I mean, whatever it is — just reply and tell me. That's faster
for both of us than guessing.

If I don't hear back by {new_deadline}, I'll need to push {milestone} out
accordingly.

{your_name}

4. "We're blocked" escalation

Send this only after a firm reminder has gone unanswered and a real deadline is now at risk. This is the one email in the set that states a consequence rather than just implying one — use it sparingly, because it only works if it's rare.

Subject: {project_name} is on hold — need {items} to continue

Hi {client_name},

I want to flag clearly rather than let this drift: {project_name} is paused
until {items} come in. I can't {specific_next_step, e.g. "build the homepage
layout" or "set up the payment page"} without them.

If the original deadline of {deadline} no longer works on your end, that's
fine — just tell me the real date and I'll replan around it. What I want to
avoid is discovering the delay only when we get close to launch.

If it would help, I'm glad to jump on a call this week to walk through
exactly what's needed and knock it out together.

{your_name}

5. Thank-you and confirmation

Send this the moment everything (or a meaningful batch) arrives. It costs thirty seconds and does two things reminders can't: it closes the loop visibly, and it gives you a paper trail of what you actually received, in case a version gets superseded later.

Subject: (same thread)

Hi {client_name},

Got everything — thank you! Confirming what's in:

- {item_1}: received
- {item_2}: received
- {item_3}: received

I'll take it from here. Next you'll hear from me is {next_milestone}, around
{date}.

{your_name}

How much time to leave between reminders

There's no universal number, but a cadence that works for most small web and design projects looks like this: first reminder at day 2–3, second at day 5–7, escalation around day 9–12 if the deadline allows it. Compress that for a hard launch date; stretch it for a client you know is slow but reliable — chasing a dependable client on a tight schedule reads as distrust, not diligence.

If you're running several projects at once, this is also where manually tracking "who did I email and when" stops scaling. A scheduled reminder cadence — send at T+2 days, T+5 days, T+9 days, then weekly — removes the part of the job that's pure bookkeeping rather than judgment. BriefGate's chase engine runs exactly that kind of schedule automatically, stopping the moment an item arrives and handing the intake back to you if it stalls, so you're not the one deciding each morning whether today's the day to send template #3.

When the missing item is a login, not a file

If what's stuck is a password or an API key rather than a photo, don't use these templates as written — asking for credentials over email creates a plaintext copy that sits in an inbox indefinitely. See How to Get Client Logins Securely for the safer alternatives and what to do once you've received one.

These templates cover the email side of the conversation. For the wider process — what to ask for, in what order, and how to validate what comes back — see How to Collect Documents From Clients.

Where BriefGate fits

These templates work as-is over plain email — nothing here requires any tool. Where they start to feel manual is at the fourth or fifth concurrent client, when remembering who's overdue and drafting the reminder yourself becomes the job. BriefGate turns the item list into a typed checklist your client fills in on a portal page, sends the reminders on the schedule above under your name, and hands your agent (or you) back structured data instead of a folder of attachments to sort through. It's the same request, automated rather than retyped. See what BriefGate does or start with a restaurant, advisor, or club project template if you run the same kind of project repeatedly.