The contract is signed, the kickoff is booked, and then the work stalls on day one because the logo files are in a format nobody can open, the brand guide does not exist, and the login credentials are sitting with someone who is on leave. Your team is billing hours to chase assets instead of building anything.
An email requesting client asset handover prior to project onboarding is one of the most underrated documents in a project. Most teams treat it as a formality and send it as an afterthought. The teams that send it early, structure it clearly, and track it properly start every project with a full week of recovered momentum.
The step-by-step sequence below covers when to send the request, how to structure the list so clients actually complete it, and what to do when the assets do not arrive. Three copy-ready templates handle the first ask, the structured tracker, and the escalation.
Why Missing Assets Stall a Project Before It Even Starts
Asset delays rarely look dramatic. Nobody announces that the project is behind because the font files never arrived. Instead, the first milestone quietly slips, the kickoff call gets pushed, and by week three the schedule has absorbed a delay nobody can point to.
The cost compounds in ways that are easy to miss:
- Idle capacity. Designers, developers, or writers are blocked on work that cannot start without source files.
- Compressed timelines. The deadline does not move, so the delay gets absorbed as pressure later in the project.
- Scope ambiguity. When assets arrive late and incomplete, teams improvise, and improvised work rarely matches the client's expectations.
- Rework risk. Building on placeholder logos, unlicensed fonts, or low-resolution images guarantees a second pass later.
- Blurred accountability. Without a written asset list, no one can prove which side caused the delay.
The fix is not a longer email. It is a shorter email sent earlier, with a list specific enough that the client knows exactly what to send and in what format.
Run the Asset Request as a Step-by-Step Sequence
The reason most handover requests fail is that they arrive as one long list with no deadlines and no owner. Break the process into steps and the completion rate climbs sharply.
Follow this order for every project:
- Send the list at contract signing. Include the asset requirements with the welcome email so the client can start gathering immediately.
- Confirm the single point of contact. One person on the client side owns the handover. A list sent to five people gets answered by none of them.
- Structure the list in a table or numbered checklist. Group assets by category such as brand, content, access, and technical, and state the required format for each item.
- Set one clear deadline. Tie it to the onboarding date rather than an arbitrary day, and give the client a realistic window to collect everything.
- Offer an alternative for anything they cannot find. Ask them to flag missing items rather than ignoring them. Known gaps are manageable; silent gaps are not.
- Confirm receipt item by item. A short reply marking each asset as received or outstanding closes the loop and keeps the list accurate.
- Escalate once, then start without them. If items are still missing at the deadline, name the schedule impact and either proceed with placeholders or shift the kickoff.
Two details make the biggest difference in practice. First, specify formats explicitly, because "send us your logo" produces a screenshot while "send the vector source file in SVG or AI format" produces a usable asset. Second, separate access credentials from creative files, since credentials usually involve a different person and a different approval chain.
Keep the whole request to a single screen. If the list runs longer than that, split it by phase and send only what is needed for the first milestone.
Copy-Ready Templates for Requesting Asset Handover
Each template below fits a different stage. Replace every bracketed placeholder, and adjust the asset list to match the actual deliverables in the scope.
Option 1: Warm Welcome and First Request
Use this immediately after the contract is signed. It doubles as a welcome message and an asset request, which makes the ask feel like part of onboarding rather than a delay.
Subject line options:
- Welcome aboard — next step is your asset list
- [Project Name] kickoff: assets we'll need from you
- Getting started on [Project Name]
Hi [Recipient Name],
We're excited to get started on [Project Name]. Before we kick off on [Kickoff Date], we'll need a few materials from your side so the team can begin without delays.
Here's what we need:
Brand assets
- Logo files in vector format (SVG, AI, or EPS)
- Brand guidelines or a style guide, if one exists
- Approved color codes and typography details
Content and copy
- [Content Item One]
- [Content Item Two]
Access and credentials
- [Platform or Account Access]
- [Analytics or Reporting Access]
Technical details
- [Hosting, Domain, or Environment Details]
- [Any Relevant Documentation]
If you can send these through [Preferred Method] by [Asset Deadline], we'll stay right on schedule for the kickoff.
If anything on this list doesn't exist yet or you're not sure who owns it, just flag it and we'll work around it.
Thanks,
[Your Name]
[Company Name]Option 2: Structured Tracker With Status Column
Use this once some assets have arrived and you need a single document that shows exactly what is still outstanding.
Subject line options:
- [Project Name] asset status — items still outstanding
- Asset handover tracker for [Project Name]
- Where we stand on project assets
Hi [Recipient Name],
Here's the current status of the asset handover for [Project Name]. Everything marked as outstanding is blocking work on [Specific Milestone].
Received
- [Asset One]
- [Asset Two]
Outstanding
- [Asset Three] — needed in [Format]
- [Asset Four] — needed in [Format]
- [Asset Five] — needed in [Format]
To keep the [Milestone] start date, I'll need the outstanding items by [Asset Deadline].
If any of these are proving difficult to locate, let me know which ones and I'll suggest alternatives. For anything that genuinely doesn't exist, we can note it as not applicable and move forward.
Could you confirm by [Confirmation Date] which items you can send and which need a different approach?
Thanks,
[Your Name]
[Company Name]Option 3: Firm Notice When the Deadline Has Passed
Use this when the asset deadline has passed, the kickoff is at risk, and a previous request has already gone unanswered.
Subject line options:
- [Project Name] kickoff at risk — assets overdue
- Final request: outstanding assets for [Project Name]
- Schedule impact from pending asset handover
Hi [Recipient Name],
I'm following up on the asset request sent on [Send Date]. Several items are still outstanding, and the [Kickoff Date] start is now at risk.
Still needed:
- [Asset One] — required in [Format]
- [Asset Two] — required in [Format]
- [Asset Three] — required in [Format]
If these arrive by [Final Deadline], we can hold the current schedule.
If they don't, here's what happens:
- Kickoff moves to [Revised Kickoff Date]
- [First Milestone] shifts accordingly
- Work continues only on [Unaffected Workstream], if applicable
If some items can't be provided, tell me which ones and we'll document them as unavailable and proceed with what we have.
Please reply by [Final Deadline] so I can confirm the schedule one way or the other.
Regards,
[Your Name]
[Company Name]What to Do When Assets Don't Arrive on Time
Waiting indefinitely is the worst option available. It costs you capacity, it costs the client momentum, and it teaches everyone that the deadline was optional.
Work through these steps in order:
- Send one structured reminder. Restate only the outstanding items, not the full list, so the client sees a short, finishable task.
- Offer to unblock it together. A fifteen-minute call with the right person often resolves access issues that ten emails cannot.
- Propose a workaround. Placeholder assets, a temporary font, or a staged handover lets the project move while the client gathers the rest.
- State the schedule impact in writing. Name the revised dates before they happen, not after.
- Document unavailable items as out of scope. If an asset does not exist, note it and confirm that the deliverable will proceed without it.
- Start what you can. Begin any workstream that does not depend on the missing assets, and tell the client exactly which one you started.
One question is worth asking directly when assets stall: is the delay a resourcing problem or a decision problem? Missing logos are a resourcing problem and resolve with a reminder. Missing approvals on which logo to use is a decision problem and resolves only when the right person makes a call.
Asset Handover Request Checklist
Run through this list before sending any asset request. It takes a minute and prevents the back-and-forth that eats the first week of a project.
- The request is sent at contract signing or earlier, not on kickoff day
- One named contact on the client side owns the handover
- Assets are grouped by category, such as brand, content, access, and technical
- Required formats are stated explicitly for every file item
- Access credentials are requested through a secure method, not email attachments
- The deadline is tied to the kickoff or first milestone date
- The client has an option to flag items they cannot locate
- The message fits on one screen, with longer lists split by phase
- Receipt is confirmed item by item as assets arrive
- Outstanding items are tracked as tasks with due dates in the project system
- Consequences of a missed deadline are stated factually, not as a threat
If assets remain outstanding past the final deadline, proceed with documented placeholders and confirm the revised schedule in writing. The project keeps moving, the client keeps a clear record of what is still owed, and your team stops paying for someone else's delay.
Frequently Asked Questions
Q: When should I send an asset request before project onboarding?
A: Send it at contract signing, not on kickoff day. Including the asset list with the welcome email gives the client time to gather materials before the start date. If that window has already passed, send the request immediately and tie the deadline to the first milestone.
Q: What should an asset handover email include?
A: Include a categorized list of required assets, the specific file format for each item, a single named contact on the client side, a deadline tied to the kickoff date, and a way to flag items that cannot be provided. Keep the whole request to one screen.
Q: How do I ask for client login credentials securely?
A: Request access through a password manager or a secure sharing method rather than email attachments, and say so in the message. Ask for role-based access where possible instead of shared passwords. Document who holds each credential so it can be revoked at project end.
Q: What if the client does not send the assets by the deadline?
A: Send one reminder listing only the outstanding items, then state the schedule impact in writing with revised dates. Offer a workaround such as placeholder assets so work can continue. Start any workstream that does not depend on the missing files.
Q: Should I start work before all client assets are received?
A: Yes, if part of the scope can proceed without them. Starting unaffected workstreams keeps the project moving and shows the client exactly what the missing assets are blocking. Confirm in writing which items are placeholders so nobody mistakes them for final deliverables.