Collecting website content often becomes harder than anyone expects. Copy is spread across documents, the logo is in someone’s email and different people remember different versions of the service list.
You can make the work easier without writing the whole website yourself. Start with an inventory that tells everyone what is needed, where it is and who can approve it.
This checklist is for business owners and marketing teams preparing a new site or a redesign. It helps you gather material that can be used, rather than simply accumulate more files.
Begin with pages and audiences
List the pages you expect to need. Treat the list as a draft: the agency may recommend combining pages or separating information once it understands the visitors.
For each page, note its audience and purpose. A service page should help someone assess a relevant service. A team page might explain who they will work with. A contact page should make the next step clear.
If you cannot explain why a page exists, pause before collecting material for it.
Also identify important existing content. Useful FAQs, product specifications and articles should not disappear simply because they were written before the redesign.
The core content inventory
| Content group | What to gather | What to confirm |
|---|---|---|
| Business overview | Short explanation of the business, audience and location | Current wording and contact details |
| Services | Description of each service, fit, process and next step | Who checks technical accuracy |
| Team | Names, roles, bios and approved portraits | Who is currently part of the team |
| Products | Specifications, options, images and downloads | Current information and data owner |
| Proof | Work examples, permitted reviews and factual results | Permission and evidence |
| Contact | Phone, address, hours and enquiry destinations | Who follows up each route |
| Brand | Logo files, colours, fonts and usage guidance | Which version is approved |
| Policy information | Relevant notices and terms from the responsible adviser | Who approves them |
| Existing resources | Articles, FAQs, files and important page addresses | Keep, update, combine or retire |
The point is to expose the decisions. “We have product content” means little if it contains old specifications nobody has checked.
What a useful service-page brief contains
Ask the person who knows the service to answer these questions in plain language:
- Who is this service for?
- What problem brings them to you?
- What work is included?
- What is outside the scope?
- What information do they need before they enquire?
- What happens after the enquiry?
- What questions do staff answer repeatedly?
Rough answers are enough to start. They are usually more useful to a writer than polished paragraphs that do not explain the service.
If pricing varies, describe the factors that change it. Do not invent a standard package to fill a gap in the draft.
For specialist services, identify the person who must review the final wording. The copywriter can improve clarity; the business still needs to confirm the facts.
Gather proof you can stand behind
Collect project examples with a short account of the starting problem, your contribution and what was delivered.
Keep evidence with any measurable claim. A result needs a source and context; a confident sentence does not supply either.
Check review attribution and image permission. If another business helped deliver the project, record its role. This makes it easier to credit everyone accurately in the finished page.
You can also use proof that does not depend on a performance statistic: a clear explanation of the work, an approved screenshot or a documented process.
Mark anything that still needs permission or confirmation. That is easier to handle before a designer has built a section around it.
Prepare images for the places they will appear
Supply the best available originals rather than screenshots from a presentation or files copied from social media.
Keep descriptions with unfamiliar images so the team knows what they show. Record any usage restrictions. If the subject needs to sit to one side for a particular layout, discuss that before approving a tight crop.
Group photography by purpose: team, services, products, projects and location. A folder of fifty unnamed files creates more work than a smaller organised selection.
Our guide to preparing website images covers the practical file preparation. The designer should confirm the sizes and crops required for your actual layouts.
Keep one source of approved wording
A shared folder is useful only if people can tell what is current.
Use a simple naming convention and keep one approved version of each document. Mark working drafts clearly. Avoid sending several final-looking versions through separate email threads.
Agree who updates the master document when a decision changes. Otherwise the developer may enter wording that was superseded in a different conversation.
The same applies to specifications, team roles and contact information. These details can change during a project, so give them a final check before launch.
Use this page-by-page collection sheet
Copy the table into your existing document or spreadsheet. Add one row per page.
| Page | Visitor task | Existing source | Action | Content owner | Approver | Needed by | Status |
|---|---|---|---|---|---|---|---|
| Example: service page | Check whether the service suits them | Current page and staff notes | Update | Service lead | Project owner | Agreed date | Draft |
| Example: team page | Understand who they will work with | Bios folder | Check | Internal coordinator | Team lead | Agreed date | Awaiting photos |
These example rows are illustrative. Choose roles that fit your team.
Keep the status simple: missing, draft, under review or approved. Add the source location so someone else can find it. A colourful project board is less useful if nobody can locate the approved file.
What if you cannot get everything ready?
Tell the agency early. A complete content inventory is useful; a complete set of polished copy is not always necessary before the project starts.
Ask which pages need real content first. Representative material helps test a layout. A long product name, a technical table or a service with several audience groups may affect the design more than a short placeholder paragraph.
Some content can be completed later. Essential service information, contact details and claims that need approval should have clear deadlines.
Also clarify who is writing, editing and entering the content. Those are separate tasks. A website quote may include one and exclude the others.
Avoid these common collection mistakes
Writing every page before agreeing the structure. You may spend time on pages that are later merged.
Approving placeholder text. A layout can look finished while its essential information is still missing.
Copying claims from old material without checking them. Staff, capabilities and business details change.
Sending images without context. The team needs to know the subject, purpose and permission.
Expecting the developer to decide specialist facts. Assign the responsible reviewer.
A useful next step
Make the inventory first. Mark what you have, what needs work and who owns the answer. Then discuss it with the people building the site.
You can read about our web design services or send us your current website and content questions. A clear list of gaps is a useful starting point.


