Free Client Asset Request Checklist for Web Designers

Before you send the list

Add the project name, the person responsible for answers and an agreed due date. Mark which items are required to start work and which are optional. For each planned website page, identify who will supply the copy and who can approve it.

The examples below describe what to ask for, not a requirement to collect every asset. If a client does not have something, ask them to say so rather than leaving the request unexplained.

Logos and brand assets

• Primary logo: the approved logo, preferably an SVG or a high-resolution PNG with a transparent background. Ask for the original, not a screenshot.
• Alternate logo versions: any approved light, dark, horizontal, stacked or symbol-only versions. Ask the client to label when each version should be used.
• Brand guidelines: the current PDF or a link to the approved guidelines, including any restrictions on logo use.
• Brand colors and fonts: color values, font names and links to their sources, if applicable. Confirm that the project has the necessary font licenses before using them.

Website copy and business information

• Company description: a short explanation of what the business does, who it serves and where it operates. Ask for approved wording or clearly label it as a draft.
• Services: a list of services with a description for each. Include prices, locations or eligibility details only when they are intended for publication.
• About content: the business story, relevant background and team biographies needed for the agreed pages.
• Contact details: the public email, telephone number, address and opening hours that should appear on the site. Distinguish these from private project contacts.
• Calls to action: the action visitors should take on each key page, such as booking a consultation or requesting a quote, and the destination link if one already exists.

Photos and images

• Team photos: original portraits or group images, with the names and roles needed for captions. Confirm permission to publish them.
• Product or service photography: original images, labeled by product or service. Ask about crops, image credits and usage restrictions before placing them.
• Portfolio or project images: approved examples with a project name, short description and any required credits. Check whether client approval is needed before publication.

Request original-resolution files where practical. Images copied from a social feed or pasted into a document may not be suitable for the intended layout.

URLs and references

• Social media profiles: the full URLs of public profiles that should be linked from the site.
• Existing website: its URL, plus notes about pages or content that must be kept, replaced or removed.
• Reference or inspiration links: a small set of URLs with a sentence about what is useful in each—navigation, tone, layout or content. References are direction, not permission to copy another site.

Documents and approved project materials

• Brochures: the current approved version, with a note saying whether it is source material or a download for website visitors.
• Product PDFs: relevant specification sheets, catalogs or instructions. Confirm that their details are current before publishing them.
• Other approved project materials: any additional content named in the brief, with its intended use and approval contact. Leave out unrelated archives.

Keep credentials out of the asset checklist

Do not ask clients to upload account passwords, recovery codes, API keys or other sensitive credentials through a normal asset-request form. Arrange access through an appropriate secure credential-sharing method or the service’s own access controls instead.

Send clear instructions, then check what is missing

“Please add the assets below beside each request. Use approved versions where available, label drafts clearly, and tell me if an item is not ready. The required items are the ones we need to begin the next stage.”

Keep received items visible so the client does not resend them. Review their contents before treating them as ready for production, and follow up with a short list of outstanding requests.

For the full process, read how to collect files from clients without endless emails. You can also see how Gathercove’s collection workflow works.