FREE TOOL FIELD GUIDE

Website content checklist: what to collect before design starts

A practical checklist for page copy, brand files, images, approvals and access, with a free Gather readiness tool.

A website content checklist is a set of requests the client can act on. It should say what is needed, who owns it, and what counts as ready. A folder full of files is not enough if the homepage copy is still unapproved or nobody can open the image links.

01

Collect content against the agreed pages

Begin with the sitemap or page list in the project scope. For each page, request a headline, body copy, primary action and relevant images. Ask for one approved source document instead of asking the team to choose between email attachments.

Then collect shared materials: logo variants, brand guidance, business contact details and any approved policy text that the site will display. A project involving a store, migration or multiple languages needs additional questions tied to that work.

  • Page list and approved copy for each page
  • Brand files and licensed images
  • Contact details and primary calls to action
02

Separate missing, received and reviewed

Use Gather’s free Website client checklist to mark each of its six starting inputs Missing, Received or Reviewed. Received means something arrived. Reviewed means you checked it against the request. The tool does not inspect the files for you.

For example, a logo link can be received but still need review because it requires permission. A reviewed homepage document should have usable text and the right approver. Checklist counts help organize the work; they are not a weighted measure of launch readiness.

  • Open links using the delivery account
  • Check file format and usage permission
  • Confirm which version is approved
03

Ask for only what remains

Download the outstanding request from the free tool and edit it for the project. Name the missing item, accepted format and person responsible. Connect its due date to the milestone that depends on it.

If the project needs a custom list, use the Website content checklist starter. The free tool needs no account. A saved Gather workspace supports collecting text answers and file links through a client link; it does not host the actual files. Use platform invitations for access and never request passwords in a checklist.

  • Give each request an owner
  • Explain the dependent milestone
  • Review replies before marking work ready
KEEP READING

More from the journal.

All articles ↗
PUT IT TO WORK

Make your client’s checklist.

Use the free tool with your own details. Download what you make. Create an account to save work online, or keep using the free browser workspace. Download a backup whenever you need a separate copy.

Make a client checklist Try it with sample data ↗No account or card needed for the free tool.