How to get website content from clients

1. Agree the sitemap before the chase

Content requests only make sense against named pages. If “About” is still optional, do not ask for a finished About draft. Lock the page list in the SOW or kickoff notes first.

2. Ask for facts, assets, copy, and a decision maker

A useful first package is: business/contact facts, logo/source assets, copy for each approved page, licensed photos, team bios/portraits when needed, and one final decision maker. Vague “send us everything” emails create thrash.

• Prefer original vectors over screenshots.
• Require rights notes on photos.
• Name one approver; list consult-only people separately.

3. Show examples and acceptance criteria

Clients finish faster when they see a good answer and know what “done” means. Upload success is not the same as asset approval, so say that out loud in the Ask.

4. Remind only while they own the next action

Automated follow-up helps when status, assignee, and quiet hours are respected. Pause chase on submission, help requests waiting on your team, extensions, or project pause. After submit, your review is the next action. Do not keep blaming the client.

See how Yori handles this in product: Collect, chase, prove.