Asset Collection & Client Expectations — Best Practices

Overview

A recurring source of project delays and rework is starting design and development before all client assets — photography, copy, brand materials — have been collected and approved. The ^[1] is a clear case study: stock photos and AI-generated images were rejected late in the project because the client's preference for region-specific photography was never surfaced upfront. Similar risks exist on any project where asset ownership is ambiguous at kickoff.

This article captures the lessons learned and the recommended process going forward.

The Core Problem

When a project begins without confirmed assets, the team fills the gap with placeholders (stock photography, AI-generated images, draft copy pulled from reference sites). This creates two compounding risks:

1. Subjective late-stage rejection. Clients may not know what they want until they see what they don't want. Placeholder assets invite feedback that restarts design work.
2. Unclear source of truth for copy. On VCEDC, the client referenced multiple conflicting sources — emails, Word docs, Excel files, an existing website, and AI-generated drafts — with no single authoritative version. This caused repeated revision cycles.

The result is wasted design effort, developer rework, and strained client relationships.

Best Practices

1. Collect All Assets Before Design Begins

Do not start visual design or page layout until the following are confirmed and in hand:

• Photography: Client-provided images, licensed stock selections, or explicit written approval to use stock/AI imagery
• Logo and brand files: Vector files, brand guidelines, approved color palette
• Copy: Final or near-final text for all pages, or a clearly designated single source of truth
• Video and media: Any embedded video content or downloadable files

If the client cannot provide assets, the project timeline should reflect that dependency explicitly.

2. Establish Photography Preferences at Kickoff

Photography is the most common source of late-stage surprises. During the kickoff meeting or discovery phase, ask directly:

• Do you have existing photography you want us to use?
• Are you comfortable with stock photography? If so, do you have style preferences?
• Are there geographic, cultural, or brand-specific requirements for imagery (e.g., "must show our actual location/team/product")?
• Are you open to AI-generated imagery?
• Would you consider a professional photo session? (See note on photography upsell below.)

Document the answers. If the client says stock is acceptable, get that in writing so there is a reference point if preferences shift later.

VCEDC example: The client ultimately rejected stock and AI images because they didn't reflect the specific character of the "Northwoods" region. This preference was never articulated until late in the project. Asking the question explicitly at kickoff would have surfaced this constraint before any design work was done.

3. Designate a Single Copy Source of Truth

Before writing or placing any copy:

• Ask the client to provide a single document (Google Doc, Word file, etc.) that represents the final or working copy for each page.
• If multiple sources exist (old website, emails, previous drafts), ask the client to consolidate them into one document before work begins.
• Note the date and version of the document used. If the client later references a different source, point back to the agreed document.

4. Run a Kickoff Asset Review Meeting

For projects of meaningful scope, hold a dedicated asset review session early in the engagement — before design begins. Include:

• The client (decision-maker and any content owner)
• The designer
• The account manager / project lead

In this meeting, walk through each page or section and confirm what assets exist, what needs to be created, and who is responsible. A mood board review can be part of this session, but the primary goal is asset inventory and sign-off, not aesthetic preference.

Note: The VCEDC project did include a mood board exercise, but the client found the tool overwhelming and the session did not result in clear asset commitments. A simpler, more direct asset checklist conversation may be more effective than a formal mood board tool for some clients.

5. Set Explicit Expectations on Stock vs. Custom Photography

Many clients are uncomfortable with stock photography but unwilling to invest in a photo shoot. Address this tension directly and early:

• Explain that stock photography is a cost-effective placeholder, but custom photography produces better results and stronger brand alignment.
• If budget allows, propose a photography session as a project add-on.
• If the client declines custom photography but also rejects stock, document that tension and escalate — do not absorb unlimited revision cycles as a result of an unresolved client decision.

Signs You're in Trouble

Watch for these signals that asset collection was insufficient:

• Designer is using placeholder images more than two weeks into the project
• Client is referencing "another version" of copy that the team hasn't seen
• Feedback includes phrases like "that doesn't look like us" or "where did you get that?"
• Client provides new images after design is already approved

If any of these appear, pause, surface the issue to the account manager, and re-anchor on what assets are actually available before continuing.

Related

• ^[2] — the broader pre-launch quality checklist that includes asset readiness as a gate
• ^[3]
• ^[4]