Your content request email needs an answer, not a nudge

A content request email should end with a task your client can answer, not a reason to send another email. Name the material, give them a working destination and a date, and explain what their reply lets you do next. The templates below cover the first request through the final receipt, including the awkward middle when some material has arrived but you still can’t use it.

You don’t need a firmer version of the same message every time. After a client sends a folder, the next email should acknowledge that folder. If you need a decision about workshop details, asking for “the remaining content” sends them back through work they’ve already done.

Which email should you send?

Choose the template from the project’s current state. Don’t send the full sequence automatically.

What you know	Email to use	The reply you need
Collection hasn’t started	Initial content request	Named materials in the agreed destination
Some material has arrived	Partial submission receipt	Only the outstanding items
An answer or file isn’t usable	Specific correction request	A corrected fact or replacement file
The agreed date is approaching	Before-deadline reminder	Delivery or notice that the date won’t work
The date has passed	Overdue content request	A realistic delivery commitment
Someone else needs to decide	Approval owner request	A named decision-maker and review date
The client has proposed another date	Revised schedule confirmation	Agreement on the new delivery and milestone
The requested batch has arrived	Receipt and next-step confirmation	Any correction to your handoff summary

These are original sample emails. Replace every bracketed field, remove irrelevant lines, and add your usual signature before sending. Dates should include the month; “next Friday” becomes ambiguous when someone forwards the message later.

Initial email asking a client for website content

Send this after you’ve agreed the pages and writing responsibilities. The email introduces the request; it shouldn’t contain an entire questionnaire or every file specification for the project. Point it to one place where those details live, such as a shared folder or a client content collection link.

Subject: [Project name] website: content needed for [milestone]

Hi [Client name],

We’re ready to collect the material for [pages or batch]. For this delivery, we need:

• [Specific business facts or agreed copy, with a short answer guide]
• [Named image or document, with its intended use]
• [Decision that the client needs to confirm]

Add these here by [date]: [content request link]. The request includes the details for each item.

[Writer’s name or team] will turn your answers into the page copy. Your role is to supply the information and review the draft.

This delivery lets us [specific next milestone]. If the date doesn’t work, reply with the date you can commit to so we can plan the work.

Thanks, [Your name]

Change the writing sentence if the client supplies finished copy. Don’t promise drafting unless it’s included in the scope. If you haven’t settled that responsibility, resolve it before sending the request.

For example, imagine a fictional pottery studio preparing a Classes page. Your list might request the beginner class duration, maximum group size, what participants take home, and an original photograph of the teaching space. “All class content and photos” hides those requirements. The website content questionnaire can help you write the linked questions; keep this email focused on the delivery.

Email after the client sends some of the content

A partial submission needs a receipt before it needs a reminder. Say what arrived, then narrow the request. This prevents a client from resending the same folder because they can’t tell whether you saw it.

Subject: [Project name] content received: [remaining item] still needed

Hi [Client name],

Thanks for sending [received material]. I’ve added it to [page or project record], so you don’t need to send it again.

We’re still missing [specific item]. Add it to [direct destination] by [date]. For this item, we need [brief answer or file requirement].

We can now [work enabled by the submission]. [Missing item] is needed before we can [dependent task].

If someone else holds that information, tell me who will provide it and when.

Thanks, [Your name]

For the pottery studio, a folder of classroom photographs doesn’t answer whether firing is included in the beginner class. Acknowledge the pictures and ask that question directly. Don’t attach the original full checklist as though nothing has arrived.

“Received” also doesn’t mean “approved.” Use it to confirm possession; explain any remaining review separately.

Email requesting a corrected detail or usable file

Sometimes you have a response, but it can’t support the page yet. Name the defect without turning it into a verdict on the client’s effort. “The information needs work” gives them no way to finish.

Subject: [Page name]: clarification needed on [item]

Hi [Client name],

I have [submitted answer or filename]. Before we use it on [page or section], I need [specific correction].

[Explain the uncertainty or file problem in one sentence.]

Can you [precise action] by [date]? Add the answer or replacement here: [direct destination]. This replaces [earlier answer or file]; the other material is already recorded.

Once that’s confirmed, we can [next task].

Thanks, [Your name]

Suppose the studio’s booking page says a class lasts 75 minutes, while its attached flyer says 120 minutes. Ask which duration the new website should publish. Don’t quietly choose the newer-looking file or ask the owner to rewrite the whole class description.

For an image, name the file and its problem: “classroom-preview.jpg is a cropped preview; we need the uncropped original for the wide Classes image.” Give the client a recognizable file to replace, rather than an abstract request for “better assets.”

Reminder before the content deadline

Use this when the due date is approaching and the request is still outstanding. Check the destination first. A reminder for something already uploaded makes the client do your bookkeeping.

Subject: [Project name]: [item] due [date]

Hi [Client name],

[Item] is due [date] for [milestone]. We have [received material]; only [remaining requirement] is outstanding in this batch.

Add it here: [direct destination].

If you can’t deliver by that date, reply with a proposed date before [planning cutoff]. I’ll check what that means for [dependent milestone].

Thanks, [Your name]

Keep the existing thread if it still describes this delivery. Start a new one when the action has changed enough that the old subject is misleading. “Classes facts needed” shouldn’t become the permanent subject for an unrelated launch approval.

Don’t soften an actual deadline with “whenever you get a chance.” A date and a clear route to renegotiate it are courteous enough.

Overdue email that asks for a delivery commitment

Once the date has passed, you need information for scheduling. State the missed date and the task waiting on it. Avoid treating silence as evidence that the client doesn’t care.

Subject: [Project name]: delivery date needed for [missing item]

Hi [Client name],

We haven’t received [item], which was due [date]. [Dependent task] is waiting on it.

Reply by [response date] with a delivery date you can commit to. If you can’t supply the item, say what’s unavailable so we can discuss an alternative.

The submission destination is [direct link]. Once we know the delivery date, I’ll confirm the revised timing for [milestone].

Thanks, [Your name]

The response date and delivery date do different jobs. The first tells you when to expect a scheduling answer. The second tells you when the material will exist. Keep both visible if you need a commitment before the client can finish gathering it.

If the client still doesn’t respond, use the workflow for a client who won’t send website content to decide how to handle the stalled project. Another copy of this email won’t make that decision for you.

Email when the content needs someone else’s approval

A client contact may have collected everything while an owner or instructor still needs to confirm it. Ask for that decision explicitly. Don’t send a collection reminder to someone who has completed their part.

Subject: [Page name]: who can confirm [decision]?

Hi [Client name],

We have the material for [section]. The remaining decision is [specific question], which needs confirmation from [role or person, if known].

Can you coordinate that confirmation by [date]? Send the answer in [record or destination], and include the name of the person who confirmed it.

If another person should make this decision, reply with their name and expected review date. We’ll use that date to plan [dependent task].

Thanks, [Your name]

For the pottery studio, the instructor might need to confirm whether beginner students can collect their fired pieces or pay for shipping. That isn’t missing copy. It’s an unresolved business decision, and the email should name the person who can settle it.

Email confirming a changed content deadline

When the client proposes another date, close the loop. Accepting a later content delivery doesn’t automatically mean accepting the original build or launch date.

Subject: [Project name]: revised content and [milestone] dates

Hi [Client name],

Thanks for confirming that [item] will arrive by [new delivery date]. I’ve updated the content schedule.

With that delivery date, we’re planning [next milestone] for [revised date]. This allows time for [actual remaining work]. The previous [milestone date] is replaced by this schedule.

The remaining delivery is [specific item], submitted through [direct destination]. Reply if this summary differs from your plan.

Thanks, [Your name]

Only put dates in this message that your team can support. If you need to check capacity first, replace the milestone paragraph with: “I’ll confirm the revised [milestone] date by [date] after checking our production schedule.” Don’t invent a precise date just to make the template look complete.

Email confirming the content batch is complete

Stop chasing when the batch arrives. Send a receipt that marks the boundary of what you’ve received and what happens next. If more pages remain, say this batch is complete rather than declaring all website content finished.

Subject: [Project name]: [content batch] received

Hi [Client name],

We now have [named materials] for [page or batch]. Nothing further is needed from you for this collection step.

We’ll [review or draft task] next and send [specific output] by [date]. You’ll then review [what the client needs to check].

The material we’re using is recorded here: [destination or version link]. If you notice a factual error, reply with the affected item and its correction.

Thanks, [Your name]

Before sending any template, open its link as a recipient, check the outstanding items, and replace every placeholder. Then read the final request on its own. Your client should be able to tell what to send, where it belongs, and when it’s needed without searching the old thread.