You can have a great design system, a clean component library, and a perfect deployment pipeline—and still miss your website launch date because a client has not sent their copy.
This is not a technical bug. It is a content intake problem.
If you build websites for clients, here is a simple process you can reuse to collect logos, text, photographs, and approvals without turning every project into an endless email thread.
Why a shared folder is not a complete intake process
A folder answers where files live. It does not tell you:
- Which files are still missing.
- Which page each piece of copy belongs to.
- Whether an image is approved for publication.
- Who should provide or review an item.
- What needs correction before development can move forward.
Adding another chat thread usually makes this worse. A better approach starts with structured requests.
Step 1: Turn vague requests into individual deliverables
Instead of asking for "all website content," create a short checklist that a busy client can understand.
For a small services website, try:
| Area | Request | Expected format |
|---|---|---|
| Brand | Primary logo | SVG, PNG, or high-resolution image |
| Home | Main headline and introduction | Short text |
| Services | Service names and descriptions | Text per service |
| About | Company story and team information | Text and optional photos |
| Contact | Public contact details and opening hours | Text |
| Portfolio | Approved project photographs | Image uploads |
| Compliance | Required legal/privacy information | Client-approved text |
Keep the requests concrete. "Write an About page" can be intimidating; "Tell us in 3–5 sentences what your company does and whom it helps" is easier to answer.
Step 2: Establish a single source of truth
Choose one place for the client to submit information. It might be a project portal, form, or dedicated collection link.
The goal is not to force the client to adopt your project-management stack. They should be able to click a link, understand the next task, and submit their content.
For internal tracking, give each request a status:
- Requested — still waiting for the item.
- Received — provided but not yet reviewed.
- Revision needed — there is a specific correction to make.
- Approved — ready to use.
A collection process that makes missing items visible will be more useful than a random pile of uploads.
Step 3: Reduce the effort required from the client
A few details make a big difference:
- Use plain-language labels, not internal jargon.
- Explain what a good answer looks like.
- Let clients provide partial information and return later, where possible.
- Make the process work on mobile.
- Avoid unnecessary sign-ups when the client simply needs to upload a file or submit text.
Your client is probably not thinking about your sprint board. They are thinking about running their business.
Step 4: Agree on a realistic submission deadline
Content is a dependency. Treat it as part of the project timeline.
At kickoff, identify the minimum content needed to start design and the final content needed before launch. Explain the consequences of missing each milestone.
For example:
Please send the logo and primary page copy by Tuesday. We can begin layout work once those arrive. Remaining photos and final approvals can follow by Friday.
When following up, list only the missing pieces. It is easier to act on "We still need your logo and three service descriptions" than "Just checking in."
Step 5: Keep review and approval separate from collection
"Uploaded" does not mean "approved."
A photo might lack permission for use, a service description might still be a draft, and contact details might be out of date. Record approvals explicitly rather than assuming that any submitted file is final.
For regulated businesses, get the appropriate legal and privacy information reviewed by the responsible people; a collection checklist cannot replace legal advice.
A message you can send to your next client
Hi [Name],
To keep your website project moving, I prepared a simple checklist of the content we need.
Please use this link to provide the texts, photos, logo, and business details: [link].
You can start with what you already have. Our first content milestone is [date].
If any request is unclear, just reply here and I'll help.
The tool I'm building around this workflow
I'm working on ParaDocs, a bilingual (French/English) tool for freelancers and web agencies. You prepare the content requests, send a single link, and keep track of what a client has submitted. Clients can provide text and files without creating an account.
It offers a 14-day free trial. I mention it because I'm involved in the project, not as an independent recommendation.
Question for fellow developers and agency owners: what is the most painful part of getting content from clients—collecting it, chasing missing items, or getting final approvals? I'd love to hear what workflow works for you.
Top comments (1)
The 'tell us in 3 to 5 sentences what your company does' rewrite is the useful bit. Clients stall on blank pages, not on effort. The four statuses help a lot too. I'd add an owner name per row, because 'Revision needed' sitting with nobody assigned is how a launch slips another two weeks.