Dubsado Delivery Workflow: How to Manage the Active Work Phase for Any Service Business

The delivery phase is driven by how long it takes you to complete the work — and it tends to be the phase where communication drops off the most. You’re heads-down doing the work. Your client is waiting. Without intentional touchpoints built into the workflow, they’re left wondering if anything is happening. That’s not a premium experience. It’s also completely fixable.

This is post five in my Dubsado Workflow Series. If you’ve been following along, you’ve already covered how to plan before you build, the inquiry workflow, the booking workflow, and the onboarding workflow. This post picks up the moment the active work begins — and covers everything that happens between starting the work and handing over the final deliverable.

Before we get started — hi, I’m Colie James, Certified Dubsado Specialist and host of the Business-First Creatives podcast.

The onboarding workflow made sure you had everything you needed to start. This post covers what happens next — the active work phase, how it differs depending on your business type, and how to build a Dubsado workflow around it.

What the Delivery Phase Actually Is

This sounds obvious until you try to build a workflow around it — and then suddenly it’s not obvious at all.

The delivery phase is everything from the moment you start doing the thing they paid for to the moment the final work is in their hands and accepted. That sounds simple. But where it starts depends entirely on your business.

For photographers and other scheduled service providers — session-based photographers, coaches, VIP day providers — delivery begins on the date of service. The session day. The VIP day. The coaching kickoff call. Whatever the scheduled event is, that’s your trigger.

For web and brand designers, delivery begins on your official design start date. The day you open the file and start building. Not the day they signed the contract — that’s booking. Not the day you finished collecting their assets — that’s onboarding. The day you actually start designing.

For SEO strategists like Brittany — delivery begins when the research starts. Keyword research, competitor analysis, auditing existing pages. Before a word of content gets written, the research phase is already delivery. That’s when you’re actively doing the work they paid for.

And onboarding ends the moment you have everything you need to start. If you’re still collecting information from your client during the delivery phase — still waiting on assets, still chasing down questionnaire responses — your onboarding workflow isn’t doing its job.

Why does this matter for Dubsado? Because your delivery workflow is built around these boundaries. Get them wrong and you end up with actions firing at the wrong time, clients falling through gaps between phases, or one giant workflow that nobody can untangle when something breaks.

What Every Delivery Workflow Has in Common

The delivery phase looks different across business types — but every delivery workflow shares the same bones.

A clear trigger. For scheduled services, this is the project date — Dubsado fires the workflow based on the date of service. For designers and SEO strategists, it’s a project status change that signals active work has begun. Either way, something specific and reliable needs to kick this off.

Communication during the work. The biggest mistake service providers make in the delivery phase is going completely silent. You’re heads-down doing the work. Your client is waiting. Without intentional touchpoints built into the workflow, they’re sitting there wondering if things are on track. Every delivery workflow needs at least one mid-delivery check-in — not a request for anything, just a “here’s where we are and what happens next.”

A final delivery email. Whatever you’re handing over — the gallery, the files, the website, the content — the delivery email is not just a link. It acknowledges the work, gives clear instructions on what to do with it, and sets up what comes next. This email is doing more than you think.

A handoff to offboarding. The delivery workflow ends and the offboarding workflow begins. Most people don’t plan this transition and clients fall right through the gap. Build the trigger explicitly — a project status change, a form completion, a manual start. Don’t leave it to chance.

One thing worth naming before we get into the specifics: the delivery workflow will likely have more manual steps than your inquiry or booking workflows. Revision rounds, design approvals, photograph retouching — these can’t be automated because they depend on you indicating the work is complete before the next step can fire. That’s not a flaw in your setup. That’s the nature of the delivery phase. The goal isn’t to automate everything — it’s to automate what can be automated and use to-do tasks and approvals to prompt yourself through the steps that can’t be.

The Photographer Delivery Workflow

For photographers, delivery is relatively linear — you show up, you do the session, you edit, you deliver.

The trigger: The date of service — session day for portrait, family, and brand photographers, wedding day for wedding photographers. In Dubsado, workflow actions can be timed off the project date, which means you set it once and it fires on schedule automatically.

What the workflow contains:

A day-after email goes out the morning after the session. Thank them, tell them how much you loved it, restate your delivery timeline clearly. This one email eliminates most of the anxious “when will we get our photos?” messages that show up two weeks into editing.

A product highlight email fires 2-4 weeks after the session, before the gallery is delivered. It spotlights albums, print credit, and premium products. The goal is to get clients thinking about products before they’re overwhelmed by images — because once the gallery lands, everyone just wants to download everything and the upsell window closes fast.

The gallery delivery email is the most important email in the sequence. Not just a link. A warm, intentional message with clear download instructions. And for photographers — the review ask belongs here. At the moment they’re opening images of their kids or their wedding day, that’s when you ask. Not a week later in the offboarding workflow. Right now, at peak emotion.

For the full wedding photography delivery sequence including every email in order, read: How to Nail Your Photographer Gallery Delivery

Some photographers, like Maddie Peschong, include a content usage guide as part of their brand photography delivery workflow. Clients receive it before or alongside the gallery so they know exactly how to use their images for marketing from day one.

The Designer Delivery Workflow

For designers, delivery isn’t a single moment. It’s a phase — sometimes a long one — with multiple checkpoints. First presentation, revision rounds, approvals, and finally the file handoff. Each of those checkpoints is a workflow action in Dubsado.

The trigger: Your official design start date — a project status change that signals you’ve opened the file and started building.

What the workflow contains:

A kickoff or start email that sets expectations for the delivery phase. What are you building, in what order, and when will they see the first version? Clients who know what to expect during the active work phase don’t send anxious check-in emails two weeks in.

Revision rounds managed through forms — either a questionnaire for structured feedback or a sub-agreement for a signed approval. The next step in the workflow triggers when that form is completed. Not off “after all previous actions complete” — off form completion. This is the smarter move because the moment a client submits their feedback, the next round starts without you having to manually move anything.

Reminders for incomplete forms fire if a client hasn’t submitted feedback within 48-72 hours using “form not completed” as the trigger. This is what keeps projects moving without you chasing anyone.

The final delivery email — clear instructions on how to access, download, and use the files. What format everything is in. What they should do first. Don’t make them guess.

One thing worth noting: even within the same business, the delivery phase can look completely different depending on the service. A designer who offers both VIP days and full custom projects can’t run them through the same delivery workflow. The trigger is different. The communication is different. The approval process is different. One workflow trying to cover both will break for at least one of them. Build a separate delivery workflow for each service type — and if you’re not sure which forms you need for revision rounds and approvals, this post on Dubsado templates for designers covers exactly that.

The SEO and Content Delivery Workflow

For SEO strategists and content creators, delivery doesn’t have a single handoff moment. It’s ongoing — it starts with research and unfolds over time.

The trigger: A project status change when research begins — keyword research, competitor analysis, auditing existing pages. This is when active delivery starts, before any content is written or delivered.

What the workflow contains:

A research delivery email — here’s what we found, here’s what it means for your strategy, here’s what we’re building toward. Clients who understand the research phase trust the work that follows.

Content delivery touchpoints as content is created and delivered. Each piece isn’t just a file drop — it comes with context. What this post targets, why, how to use it. That context is what makes the delivery feel like a service instead of a transaction.

A monthly check-in or report covering how the work is performing and what the plan is for next month. For retainer clients, this isn’t optional — it’s what keeps the relationship active and gives the client something concrete to point to when they’re deciding whether to continue.

A renewal or continuation prompt. If the client is on a retainer, when does the conversation about continuing happen? Build it into the workflow so it doesn’t get missed and you’re not scrambling to bring it up before the engagement ends.

For retainer-based providers, the delivery workflow runs in cycles rather than having a clear endpoint. The handoff to offboarding only happens when the engagement ends — which means the workflow needs to be designed to repeat or continue, not to close.

The Mistakes I See Most Often in Delivery Workflows

Going silent during the active work. No check-ins, no touchpoints, clients left wondering if anything is happening. A delivery workflow without mid-phase communication is just a delivery email with extra steps.

Timing everything off “after all previous actions complete” instead of the project date or form completion. One incomplete step freezes everything downstream. If a to-do task doesn’t get checked off, the delivery confirmation never sends. Time your actions off something reliable.

No clear trigger for when delivery ends and offboarding begins. This is where clients fall through most often. The gallery was delivered, the files were handed over, the website went live — and then nothing. Plan the transition explicitly.

For designers: not using form completion as the trigger for revision follow-ups. If your reminders are set to fire off “all previous actions complete” with an approval, you’re manually approving every reminder before it sends. That defeats the purpose entirely. Watch the form. Let it fire when the form isn’t completed.

Sending the gallery delivery email from Dubsado when your gallery platform already sends it. PicTime and Pixieset both send gallery delivery notifications. If your Dubsado workflow is also sending one, your client gets it twice. Decide which system is sending the delivery notification and turn the other one off.

Building one delivery workflow for all service types. A photographer’s delivery workflow applied to a design project doesn’t work. A VIP day workflow applied to a three-month retainer doesn’t work. Build a separate workflow for each service type — it’s more setup upfront and a much more reliable system after.

Ready to Build?

If you’ve made it through the first five posts in this series, you’ve got the full framework — inquiry, booking, onboarding, delivery. The last phase is offboarding: reviews, referrals, and making sure the relationship doesn’t just end when the work does. That’s Post 6: How to Turn Happy Clients Into Your Best Sales Strategy

If you want to know how your delivery workflow is actually performing — and where it’s quietly losing clients between phases — a Client Experience Audit will tell you exactly that.

Ready to build the whole thing properly: Systems in Session.

Not ready for either yet: Workflows and Automation Guide.

FAQ for Dubsado Delivery Workflows