How to Collect Brand Assets From Clients Without Chasing

Collecting brand assets is the part of onboarding where projects quietly stall. You need logos, fonts, photos, copy, and logins; the client sends a blurry logo from an email signature and goes quiet. The fix is a system that asks for everything once, in the right format, with a single deadline, so chasing stops being your job.

This guide gives you the complete asset list, the exact way to request each type, and the workflow that makes assets arrive without follow-up.

Quick summary

• Asset delays are the most common cause of stalled onboarding.
• Ask for everything at once, in one link, with a clear deadline tied to the timeline.
• Specify the format you need (vector logo, not a screenshot) so you don't get unusable files.
• A client portal gives clients one place to upload, replacing the email attachment scramble.

Why chasing assets fails

The usual approach is to ask for assets as you discover you need them: a logo today, fonts next week, the login when you hit a wall. Each request is a new email, a new wait, and a new chance for the client to lose momentum. By the third request, you're the nag and the project is behind.

The root problem is that you're asking piecemeal and vaguely. "Can you send your logo?" invites the wrong file. A system fixes both: ask completely, and ask specifically.

The complete brand asset list

Request these in one go. The format column is what saves you from unusable files.

Asset	Format to request	Where the client finds it
Logo	Vector (SVG, AI, or EPS) plus PNG	Their designer or brand folder
Brand colors	Hex codes or a brand guide	Brand guidelines or prior designer
Fonts	Font files or license names	Brand guide or marketing team
Photography	High-res originals, not web-compressed	Photo library or photographer
Existing copy	Editable doc, not a PDF	Marketing or website
Product or service info	Spec sheets, pricing	Sales or operations
Account access	Admin logins or invites	IT or the account owner
Existing assets to reuse	Source files where possible	Prior agency or in-house team

The two rows that cause the most pain are the logo (people send a tiny JPG from a website) and fonts (people forget licensing). Naming the format up front prevents both.

The request that actually works

A good asset request does four things: lists everything, specifies format, sets a deadline, and explains the consequence of missing it. Bundle it with your intake questionnaire so the client does it all in one sitting.

"To start on time, we need your brand assets by [date]. Here's the full list with the format we need for each: [link]. Anything missing by [date] may push the timeline, since we build around these. If something's hard to find, tell me and I'll help track it down."

That last line matters. Some assets are genuinely hard for clients to locate, and offering help converts a stuck client into a moving one instead of a guilty one who avoids you.

Set a deadline with a real consequence

A deadline without a consequence is a suggestion. The honest, non-aggressive consequence is the timeline: work that depends on assets cannot start until they arrive.

• Tie the asset deadline to the project start, not an arbitrary date.
• State plainly that missing assets move the start, not your fault, just cause and effect.
• Send one reminder a couple of days before the deadline, not a stream of nags.

This reframes chasing as protecting the client's own timeline, which is far more motivating than "just checking in."

Give clients one place to upload

Email attachments are where assets go to get lost. A client portal gives the client a single upload destination, keeps every file in one searchable place, and means you never dig through your inbox for "the final final logo." It also creates a record of what was provided and when, which settles the occasional "we did send that" disagreement.

If you've automated onboarding, the asset request can fire automatically when the contract is signed, with reminders built in, so collection happens without you initiating it each time.

Handle missing or low-quality assets

Even with a good system, some assets won't arrive or won't be usable. Decide your fallback before you need it.

• No vector logo exists. Quote logo recreation as a small add-on rather than absorbing the work silently.
• No brand guide. Treat brand definition as in-scope work and price it; don't guess and hope.
• Low-res photos only. Offer stock or a shoot as a paid option, and document that you flagged it.

Naming these as scope items protects your margin and keeps a known scope of work intact instead of quietly doing extra work for free.

When a formal asset system is the wrong choice

Not every project needs this.

• You already have the assets. For a repeat client, reuse what's on file instead of re-requesting it.
• The project doesn't use brand assets. Some work (strategy, audits, consulting) needs information, not logos and fonts.

The honest caveat: a strict asset-collection system can make a small, friendly project feel bureaucratic. If a long-term client just needs one quick graphic, a polished asset-request portal link is overkill and slightly cold. Match the formality to the size of the job; a system this thorough is for real projects, not five-minute favors.

Frequently asked questions

What brand assets should I collect from a new client?

Collect the logo in vector format plus PNG, brand colors as hex codes or a brand guide, fonts with their licenses, high-resolution photography, editable copy, product or service information, and any account logins you'll need. Request them all at once with the required format specified so you don't receive unusable files like a tiny logo screenshot.

How do I stop chasing clients for assets?

Ask for everything in one request instead of piecemeal, specify the exact format for each item, set a single deadline tied to the project start, and explain that missing assets move the timeline. Give clients one upload destination like a client portal, send just one reminder before the deadline, and offer help finding hard-to-locate files.

What format should I ask for a client's logo in?

Ask for the vector source file, such as SVG, AI, or EPS, plus a high-resolution PNG. Vector files scale without losing quality and are what you need for most design and print work. If the client only has a small JPG or a screenshot, treat recreating the logo as a small paid add-on rather than absorbing it.

What if the client never sends the assets?

Send one reminder before the deadline, then make the consequence concrete: work that depends on the assets can't start, so the timeline shifts. For assets that don't exist or are too low quality, offer paid fallbacks like logo recreation, brand definition, or a photo shoot, and document that you flagged the gap so it stays a scope decision rather than free work.

Related guides:

• The client onboarding questionnaire (with sample questions)
• Client portal software: what it is and how to choose
• The agency client onboarding process, step by step