The third reminder won't get your client's content

It’s Thursday. The homepage design was approved three weeks ago, and your latest message still says, “Any update on the content?” If a client won’t send website content, stop asking for the whole website. Identify the next missing decision or file, ask one named person for it by a specific date, and tell them what happens to the schedule if it doesn’t arrive.

You can usually make progress on part of the site. You can’t honestly keep the original launch date while the material that determines the pages is missing. Those are two different conversations, and treating them as one is how a two-week wait turns into six months of polite reminders.

Find the actual blocker before you write again

Open the sitemap and mark what you have, what you can draft, and what only the client can confirm. “Waiting on content” hides too much. The client may have sent enough to build the Contact page while the Services page is missing prices, or they may have sent copy that nobody on their side has approved.

Make a short list of specific blockers. For a five-page site, it might be: final names for three services, the public phone number, two original team photos, and approval of the About page. Separate those from work you can do yourself, such as turning an existing brochure into a first draft. If your list contains “all website copy,” the request is probably still too large to answer.

Check the scope before changing the work. Did the client agree to write final copy, provide raw facts for your team to write, or approve copy written by a separate writer? If the contract says “client supplies content” but no one agreed what that means, resolve that ambiguity in a short call. Don’t quietly take on copywriting and then discover at the end that it was never priced or approved.

The page-by-page website content template gives you a field-level list if your current request is just a page name and an empty document. Use only the fields that block this project now. Sending a new forty-question form to an already delayed client can restart the same problem under a different name.

Ask why they haven’t sent it

Silence doesn’t tell you whether the client is busy, confused, waiting on a colleague, or unable to produce what you asked for. Each situation needs a different fix. Ask a direct question with easy options:

What’s holding up the Services page: deciding which services to feature, finding the details, or finding time to write them? Short notes are enough if you want us to draft the page.

If they can’t write polished copy, collect raw answers by phone or from material they already use in sales. If they need internal approval, ask who can make the final decision and when that person can review it. If the original photos don’t exist, agree on a different image plan before you finish a layout built around them. A fourth reminder won’t create a photo or settle a disagreement between two directors.

Keep the response channel simple. If you already have a shared place for content, such as a content collection portal, send a direct link to the missing page. If the client answers better by email, accept the answers there and move them into your project record yourself. Your immediate goal is to remove the blocker, not to win an argument about tools.

Replace the broad request with one small delivery

Choose the smallest set of answers that lets you advance the next page. You can still show the client the full list of outstanding work, but make the next action unmistakable. “Send the website content by Friday” requires them to plan the entire job. “Confirm these three service names by Friday” can be done between meetings.

A useful rescue email has five parts: what you already have, the exact missing item, who should answer, a date, and the effect on the build. For example:

Subject: Two answers needed to finish your Services page

Hi Maya,

We have the three service descriptions from your brochure. To finish the Services page, can you confirm (1) which service should appear first and (2) whether emergency visits are still offered? A one-line reply from you by Friday, October 2 is enough.

If those answers come in Friday, we can send the page for review on Tuesday. If you need more time, reply with a date you can make and I’ll update the page schedule.

The dates and dependency matter more than a stern tone. The client can now answer the question, delegate it, or name a realistic date. You also have a record of what was requested and what part of the work depends on it.

Send one request to one accountable contact. You may need facts from a sales manager and photos from an office manager, but someone on the client side should own gathering them. Copying five stakeholders on every reminder lets each person assume another one will respond.

Offer a way out of the writing task

Sometimes the client has the information but cannot turn it into website prose. Give them a smaller role. Ask for a ten-minute call about the service, a voice note answering three questions, or permission to use an existing proposal as source material. Your team can draft from that material if writing is in scope.

Make the handoff explicit. “You tell us the facts, we draft the copy, you approve the final page” removes a job the client may never have been equipped to do. If copywriting is outside the agreed work, offer a priced addition or a writer referral. Get agreement on the scope and fee before doing the writing.

Don’t treat a call as a substitute for confirmation. After the call, send the two or three facts you heard back to the client, along with the page they affect. Ask them to correct anything inaccurate. This matters when a casual answer such as “we serve the whole state” would become a public claim on the website.

For a repeatable collection process on future projects, see how to get website content from clients. On a stalled project, use just enough structure to finish the next decision.

Move the schedule when the dependency moves

Don’t keep a launch date on the calendar as a gesture of optimism. Work backward from the missing input: how long will your team need to write or place it, check it in the design, get approval, and test the page? If the client sends a hero photo on the original launch day, it isn’t ready to publish merely because the file exists.

For example, suppose the content was due September 18 and the planned launch was October 9. The Services details arrive October 2. If drafting, design adjustment, review, and testing take seven working days, the old launch date no longer reflects the work. Tell the client the earliest realistic review and launch dates. If you have other projects booked, offer the next available production slot rather than promising an immediate restart.

Keep working only where the missing content doesn’t force guesses. You can set up hosting, build a shared footer from confirmed contact details, or test a completed page. You shouldn’t publish invented service claims, put stock photos in place of promised team portraits without agreement, or present placeholder copy as approved copy. Hidden assumptions create rework and can put wrong information in front of customers.

Know when to pause the project

If a specific request, a simpler way to answer, and a clear due date still produce no response, stop reserving indefinite production time. Send a written status note that names what is complete, what remains blocked, the date work will pause, and the terms for restarting. Use the pause, payment, and rescheduling terms you actually agreed to. If the agreement has no delay provision, discuss and document the next arrangement rather than inventing a penalty after the fact.

You can write it without blaming the client:

Subject: Website project status and next production slot

Hi Maya,

Home and Contact are ready for your review. Services is waiting on the two confirmations requested on September 25, and About is waiting on the approved team photo. We can’t finish those pages or keep the October 9 launch date without them.

If the items arrive by October 2, I can confirm a revised schedule. Otherwise, we’ll pause the remaining build on October 5 and book the next available slot once the materials are ready. I’ll send a summary of completed work and the open items at that point.

Follow through on the date you set. A pause isn’t a threat to get a reply; it’s an accurate description of your capacity and the project’s state. When the client returns, review what has changed. A new service list, a different approver, or an expired photo permission may mean the remaining work needs a new estimate.

Prevent the same six-month wait on the next site

At kickoff, agree who supplies facts, who writes copy, who approves each page, and when the first small delivery is due. Start collecting before the design is finished. Make each request concrete enough that a client can answer it without imagining the final layout or writing an entire page from scratch.

You won’t eliminate every delay. A client may still change direction or disappear for a month. But when every missing item has an owner, a date, and a visible effect on the build, you can act on the real blocker. The project either moves forward or pauses on terms both sides can understand.