# What to Do When a Client Gives You Assets Late (and Keeps Missing Deadlines) > About Dora: Dora is the AI account manager for teams that do client work. An agentic client portal: Dora briefs every request and gets it signed off, and your team or your own AI agents do the work. Edin Abazi · Published 2026-11-11 · Updated 2026-11-11 > When a client sends assets late, pause the work that depends on them and confirm in writing that the delivery date moves by the same number of days. Prevent repeats by writing asset due dates into the contract and kickoff, collecting everything in one request, and automating reminders. Escalate early with a direct conversation before applying contract terms. The launch is two weeks out, the design is waiting on a logo, and the copy that was promised on the 3rd still hasn't shown up. You've sent three friendly emails, and each got a cheerful "sorry, tomorrow!" back. Meanwhile your designer is booked on something else starting Monday. When clients aren't providing assets on time, the short answer is this: **pause the work that depends on them, tell the client in writing that your delivery date moves by the same number of days, and send a structured reminder naming what's missing and the new deadline.** Then fix the cause by writing asset due dates into the contract and automating the reminders. My view: late assets are a project-risk problem, not a personality problem. Most clients are busy, not difficult. The fix is a system (written deadlines, automatic nudges, and a status view that shows the client as the blocker), because chasing by hand only teaches clients that deadlines are optional. Here's the five-step late-asset playbook we'll walk through: 1. Write the client's deadlines into the contract and kickoff. 2. Collect assets through one request with a due date, not scattered emails. 3. Automate reminders tied to each due date. 4. Show who the work is waiting on in a shared status view. 5. Escalate early with a direct conversation, then apply boundaries. ## Why do clients deliver assets late in the first place? Usually they forgot, they're busy, or nobody ever pinned down a deadline. It's rarely malice. A marketing manager with forty open tabs doesn't wake up planning to sink your launch. A quick note on evidence: the sources I lean on here, from [Aiwyn](https://www.aiwyn.ai/resources/articles/reasons-clients-dont-pay/) and [TaxDome](https://taxdome.com/blog/prevent-clients-not-paying-situations), are about late *payments*, not late assets. The underlying behavior is the same, so I'm applying it by analogy. Don't read any of it as a statistic about asset delivery. ### The usual causes Aiwyn lists forgetting as one of the common reasons clients don't act on time. TaxDome points to the lack of a clear policy, unclear communication, and lack of urgency. Translate those to asset requests and you get a familiar picture: - **Forgetting:** the ask was buried in a kickoff email from three weeks ago. - **No clear policy:** nobody said what happens if the logo arrives late. - **Unclear communication:** "send us your brand stuff" could mean one file or forty. - **No urgency:** the client doesn't feel the cost of delay, so other tasks win. There are also warning signs worth watching. A [Medium list of red flags](https://wittgeo.medium.com/top-10-red-flags-youre-wasting-time-with-a-client-and-how-to-avoid-them-b23cee63ffe2) names delayed responses and avoided status updates as early signals of a difficult client. It's an opinion piece, so treat it as a prompt to pay attention, not a rule. And you're not alone. A [Facebook group thread](https://www.facebook.com/groups/2815042615255352/posts/24716002424732723/) shows practitioners asking how to handle late clients, with answers all over the map. It proves people struggle with this, not that any one fix is best. ### What you need before you start Three things make everything below work: - A **signed scope** so everyone agrees what's being delivered. - A **list of needed assets**: logos, copy, photos, logins, brand guidelines. - A **named client contact** who owns getting them to you. Picture a web agency with a site build stalled because the logo, copy, and login details are three weeks late, all chased by email. That's our running example. ## Step 1: How do you build client deadlines into the project? Put asset due dates, and the consequence of missing them, in the contract and the kickoff. TaxDome's point about unclear policy applies directly: if nobody wrote down the rule, you can't fairly enforce it later. ### Client responsibilities clause Add a short clause to your agreement. A typical version says assets are due within a set window, for example 5 to 10 business days from kickoff, and if they aren't, the schedule moves. Have a lawyer review the final wording, since terms vary by jurisdiction. ### Hard stops and schedule shifts The delivery date should shift by the exact number of days the client is late, and you should say so in writing every time. You can also add a pause or restart fee for when a delay forces you to rebook your team, but only if it's in the contract up front. [The Sales Blog](https://www.thesalesblog.com/blog/what-to-do-when-your-clients-waste-your-time) advises disclosing a hard stop in advance, so the conversation never starts with a surprise. It's a 2012 sales piece, so I'm borrowing only the general principle: tell people the limit before they hit it. ### Make assets a start condition Better still, make key assets a prerequisite for starting phase one. If the logo and brand guide are needed to begin, don't schedule the designer until they arrive. For help collecting complete inputs, see [a creative brief clients actually fill in](https://dora.work/blog/creative-brief-template-clients-fill). Here's kickoff wording you can steal: > "To hold the launch date of June 12, we need your logo files, final homepage copy, and hosting login by May 20. If anything arrives later, the launch date moves by the same number of days, and I'll confirm the new date in writing the same day." This is the contrarian bit, and it's a tradeoff: the tone is firmer at the start. But it's far easier to set it in the kickoff than after the first missed date. ## Steps 2 and 3: How do you collect assets in one place and automate the nudges? Make one request per asset set, each with an owner and a due date, and schedule reminders against those dates. That replaces "did you get my email?" with a tracked item that everyone can see. ### One request, one due date Scattered emails are where assets go to die. Instead of five threads, send one checklist or portal request: logo files (owner: Priya, due May 20), homepage copy (owner: Dan, due May 20), hosting login (owner: IT contact, due May 18). Each item has a person and a date. ### Reminder schedule that works Aiwyn notes that regular reminders make clients aware of pending items and due dates. The source is about invoices, so I'm applying the principle by analogy: busy people forget, and a nudge keeps the item visible. A simple cadence: 1. **Three days before:** a friendly heads-up with the list. 2. **On the due date:** "Today's the day for these two items." 3. **One day after:** what's still missing, and the impact on the launch date. 4. **Every few days after:** a short repeat until it's resolved, then escalate (Step 5). ### Example reminder message > "Hi Priya, we're still missing the logo files and homepage copy. Both were due May 20. Per the kickoff, the launch date has moved from June 12 to June 15 so far. If we have both by Friday, we can hold June 15. Can you confirm?" It names what's missing, the impact on the date, and the new deadline. No guilt, no essays. You can do all this by hand, but it eats hours. Dora asks the client for what's missing, and clients can reply by email through email intake, so they never have to log in anywhere. Or set up a portal and let Dora handle the asking: try Dora free. Your first client is free, forever. ## Step 4: How do you show clients who the work is waiting on? Use a shared status view that labels every item as either waiting on client or waiting on team. Visibility does the awkward part of chasing for you, because nobody has to nag when the board says it plainly. ### Name the blocker without blame A status line like "Waiting on client: logo files, 12 days" is neutral. It's a fact, not an accusation. Compare that with the third "just circling back" email, which is a small personal dig. This also helps you spot patterns. The Medium list mentioned earlier treats delayed responses and avoided status updates as warning signs. A visible status makes those patterns obvious, instead of living in your inbox. ### What the status view should show Keep it simple: - Each item, its owner, and its due date. - Whether it's waiting on the client or the team. - How many days it's been waiting. - The current delivery date, updated when it shifts. A client portal gives clients that visibility without exposing your internal project board. A weekly summary recaps what's done and what's open, so the blocker shows up in their inbox every week. Back to the web agency. The illustrative setup: one asset request with due dates, automatic reminders, and a status view reading "waiting on client." The expected outcome is fewer forgotten items and fewer personal chase emails. I'm not claiming a measured result here; I'll cover how to measure it below. The same logic applies after assets, when feedback goes quiet. If that's your next problem, read our take on [an approval process that doesn't stall when clients go quiet](https://dora.work/blog/client-approval-process-guide). ## Step 5: What do you do when a client still misses the deadline? Act early with a direct conversation, then pause dependent work and apply the contract terms. Don't wait until the launch date is at risk to say something real. ### Escalation checklist An [American Bar Association piece](https://www.americanbar.org/groups/gpsolo/resources/magazine/2026-may-jun/client-doesnt-pay-wants-you-keep-working-what-do-when/) on clients who fall behind in paying says to have an early, direct conversation. It's written for lawyers, but the principle carries over: silence makes it worse. Here's the order I'd follow: 1. **Pause dependent work.** Keep going only on tasks that don't need the missing assets. 2. **Confirm the new date in writing.** Same day, no ambiguity. 3. **Send the structured reminder:** what's missing, the impact, the final deadline. 4. **Call, or contact someone senior** on the client side, such as the person who signed the contract. 5. **Apply the pause or restart fee,** if your contract includes one. 6. **Restrict new work** if the pattern persists. For step 6, a [Reddit thread on a late-paying client](https://www.reddit.com/r/smallbusiness/comments/erosok/huge_client_not_paying_on_time/) suggests restricting future work until the client catches up. That's anecdotal forum advice about payments, so adapt it carefully. For assets, it might mean not scheduling the next project until the current one has what it needs. Quiet clients are a close cousin of this problem. Nudges and auto-approval after a set number of days (Dora's default is 7) are a good model for items that shouldn't wait forever. See approvals for how that works. ### When to set firmer boundaries Sometimes the pattern doesn't change. [Karbon's piece on clients not worth the hassle](https://karbonhq.com/resources/how-to-avoid-clients-not-worth-the-hassle/) argues that saying no can protect the value of your business. Treat that as a last resort, after documented reminders, a direct conversation, and applied contract terms have all failed. ## What mistakes make late assets worse? Most of the damage comes from things we do, not things the client does. These are the ones I see most. - **Working around missing assets for free.** You guess at the logo or use placeholder copy, then redo it. That's rework and scope creep dressed up as helpfulness. - **Setting no written deadline** and expecting the client to know. TaxDome's point about unclear policy applies here. - **Chasing across email, chat, and calls,** so nothing is tracked and nobody knows the real status. - **Waiting too long for the first direct conversation.** The ABA's early-conversation principle exists for a reason. - **Confusing a one-time slip with a pattern,** or ignoring a real pattern because the client is nice. Some of this also comes down to tooling. If you're using a portal and clients still don't engage, check whether you're making [common client portal mistakes small agencies make](https://dora.work/blog/client-portal-mistakes-small-agencies). ### How to tell if it's working I won't promise you a number. Measure your own. Look at the last 5 projects and record two things: the average days late per asset, and the number of manual chase emails per project. Then run the playbook on the next 5 projects, about one quarter, and compare. Request due dates and completion timestamps in your portal or a simple spreadsheet are all the instrumentation you need. If days late and chasers both drop, the system is working. If not, check whether the deadlines were really in the kickoff. Or let Dora ask the client for what's missing, remind them before each due date, and show who the work is waiting on. Try Dora free; your first client is free, forever. What's the longest you've ever waited on a single logo file? ## FAQ ### What should I do when a client doesn't send assets on time? Pause the work that depends on them, confirm in writing that the delivery date moves by the days lost, and send a structured reminder with the new deadline. Then have a direct conversation early rather than waiting for the date to be at risk. ### Why do clients deliver assets late? Mostly because they forget, they're busy, or the deadline and the consequences were never made clear. Sources on late payments from [Aiwyn](https://www.aiwyn.ai/resources/articles/reasons-clients-dont-pay/) and [TaxDome](https://taxdome.com/blog/prevent-clients-not-paying-situations) point to forgetting, unclear policy, and unclear communication, and I'm applying those to assets by analogy. ### How do I get clients to send files and content on time? Set due dates in the contract and kickoff, collect everything in one request with owners and dates, and automate reminders tied to those dates. A visible status view showing what's waiting on the client adds gentle pressure without personal chasing. ### What should a client responsibilities clause in an agency contract include? Asset due dates, a feedback window, the schedule shift that applies if they're missed, and optionally a pause or restart fee. Have a lawyer review the wording before you use it. ### Should I keep working while waiting for assets? Don't guess or work around missing pieces for free, because that usually leads to rework and scope creep. Continue only work that doesn't depend on the missing items, and log the delay in writing. ### When should I stop working with a client who keeps missing deadlines? Only after documented reminders, an early direct conversation, and applied contract terms have all failed. [Karbon](https://karbonhq.com/resources/how-to-avoid-clients-not-worth-the-hassle/) argues that saying no can protect your business, but treat it as a last-resort boundary, not a first move. ## References 1. [9 simple reasons clients don't pay—and what to do about it](https://www.aiwyn.ai/resources/articles/reasons-clients-dont-pay/) 2. [6 Tactics to Prevent "Clients Not Paying" Situations After Your Work Is Done](https://taxdome.com/blog/prevent-clients-not-paying-situations) 3. [Top 10 Red Flags You're Wasting Time with a Client and How to Avoid Them](https://wittgeo.medium.com/top-10-red-flags-youre-wasting-time-with-a-client-and-how-to-avoid-them-b23cee63ffe2) 4. [What's the best strategy when clients don't pay on time?](https://www.facebook.com/groups/2815042615255352/posts/24716002424732723/) 5. [What To Do When Your Clients Waste Your Time](https://www.thesalesblog.com/blog/what-to-do-when-your-clients-waste-your-time) 6. [What to Do When a Client Doesn't Pay but Wants You to Keep Working](https://www.americanbar.org/groups/gpsolo/resources/magazine/2026-may-jun/client-doesnt-pay-wants-you-keep-working-what-do-when/) 7. [Huge client not paying on time : r/smallbusiness](https://www.reddit.com/r/smallbusiness/comments/erosok/huge_client_not_paying_on_time/) 8. [Learn to say no: How to avoid the clients not worth the hassle](https://karbonhq.com/resources/how-to-avoid-clients-not-worth-the-hassle/) ## Questions ### What should I do when a client doesn't send assets on time? Pause the work that depends on them and confirm in writing that the delivery date moves by the days lost. Send a structured reminder that names what's missing and the new deadline. Then have a direct conversation early, before the date is at risk. ### Why do clients deliver assets late? Usually they forget, they're busy, or the deadline and consequences were never made clear. The article draws on sources about late payments and applies those causes to assets by analogy. Clear policy and clear communication are the main fixes. ### How do I get clients to send files and content on time? Set due dates in the contract and kickoff, then collect everything in one request with an owner and a date for each item. Automate reminders tied to those dates. A shared status view showing what's waiting on the client adds pressure without personal chasing. ### What should a client responsibilities clause in an agency contract include? It should include asset due dates, a feedback window, the schedule shift that applies if items are missed, and optionally a pause or restart fee. The clause should be reviewed by a lawyer because terms vary by jurisdiction. Writing these terms up front makes them enforceable later. ### Should I keep working while waiting for assets? Avoid guessing or working around missing pieces for free, since that usually leads to rework and scope creep. Continue only the tasks that don't depend on the missing items. Log the delay in writing as you go. ### When should I stop working with a client who keeps missing deadlines? Only after documented reminders, an early direct conversation, and applied contract terms have all failed. Saying no can protect your business, but it should be a last-resort boundary rather than a first move. ## Sources - [9 simple reasons clients don't pay—and what to do about it](https://www.aiwyn.ai/resources/articles/reasons-clients-dont-pay/) - [6 Tactics to Prevent "Clients Not Paying" Situations After Your Work Is Done](https://taxdome.com/blog/prevent-clients-not-paying-situations) - [Top 10 Red Flags You're Wasting Time with a Client and How to Avoid Them](https://wittgeo.medium.com/top-10-red-flags-youre-wasting-time-with-a-client-and-how-to-avoid-them-b23cee63ffe2) - [What's the best strategy when clients don't pay on time?](https://www.facebook.com/groups/2815042615255352/posts/24716002424732723/) - [What To Do When Your Clients Waste Your Time](https://www.thesalesblog.com/blog/what-to-do-when-your-clients-waste-your-time) - [What to Do When a Client Doesn't Pay but Wants You to Keep Working](https://www.americanbar.org/groups/gpsolo/resources/magazine/2026-may-jun/client-doesnt-pay-wants-you-keep-working-what-do-when/) - [Huge client not paying on time : r/smallbusiness](https://www.reddit.com/r/smallbusiness/comments/erosok/huge_client_not_paying_on_time/) - [Learn to say no: How to avoid the clients not worth the hassle](https://karbonhq.com/resources/how-to-avoid-clients-not-worth-the-hassle/) [Try Dora free](https://dora.work/sign-up): your first client is free, forever.