A project workflow is the sequence of steps a project moves through from start to finish, with an owner for each step, a clear handoff between steps and a rule for when each step is done. It answers three questions for everyone on the project: what happens next, who does it, and how we know it's finished.
A project plan says what you'll deliver and when. The workflow says how the work moves. When the workflow is written down, people stop asking "is this ready for me yet?" and work stops waiting in someone's inbox. This guide covers how a project workflow differs from a plan and a process, the stages most projects share, five worked examples, and a template you can copy.
Project workflow vs project plan vs process
The three terms get mixed up, and the difference matters when you sit down to write one.
| Term | What it answers | Example |
|---|---|---|
| Project plan | What will we deliver, by when, with which budget and people? | "Launch the new pricing page by March 14, with design, copy and engineering." |
| Project workflow | In what order does the work move, who owns each step, and what triggers the next one? | "Copy draft, then legal review, then design, then build, then sign-off. Each step starts when the one before it is approved." |
| Process | How do we do this kind of work every time? | "Our standard website change process", which every web project reuses. |
Put simply: a process is the reusable recipe, a workflow is that recipe applied to one project, and the plan adds the dates, budget and scope for this particular project. Once a workflow runs well a few times, it's worth saving as a process so the next project doesn't start from a blank page.
The stages of a typical project workflow
Most project workflows, whatever the industry, follow the same five stages. The names change; the shape doesn't.
- Intake. The request comes in and someone decides whether to take it on. Output: a yes or no, and a named project lead.
- Scoping. The lead defines the goal, the deliverables, the constraints and who needs to be involved. Output: a short brief or charter everyone agrees to.
- Production. The work itself, usually split into several steps with different owners. Output: drafts, builds or deliverables.
- Review and approval. The people who can say yes check the work against the brief. Output: an approval, or a clear list of changes.
- Delivery and close. The work goes live or goes to the client, and the team records what was decided and what they'd change. Output: the delivered work and a short wrap-up.
The steps inside production are where projects differ most, so that's where your workflow needs the most detail.
Project workflow examples
Five common projects, written as workflows. Each step has an owner and a "done when" rule, which is the part most workflows leave out.
Example 1: IT or software project workflow
- Request and triage (product manager). Done when the request has a priority and a target release.
- Requirements and acceptance criteria (product manager with the tech lead). Done when engineering agrees the criteria are testable.
- Design and technical approach (designer and tech lead). Done when both are reviewed and any open risks are written down.
- Build (engineers). Done when the code is merged and passes automated tests.
- QA and user acceptance (QA, then the requester). Done when the acceptance criteria pass.
- Release and monitor (tech lead). Done when it's live and nothing critical is open after a set period, such as 48 hours.
- Retrospective (whole team). Done when the decisions and follow-ups are recorded.
Example 2: Marketing campaign workflow
- Campaign brief (marketing lead). Done when the goal, audience, budget and success metric are agreed.
- Messaging and creative concept (copywriter and designer). Done when the lead picks one direction.
- Asset production (copy, design, video). Done when every asset on the list exists in draft.
- Review and approval (marketing lead, then brand or legal if needed). Done when every asset is approved.
- Launch (channel owners). Done when everything is scheduled or live.
- Results review (marketing lead). Done when the numbers are compared with the success metric and the lessons are written down.
Example 3: Client project workflow at an agency
- Client onboarding (account manager). Done when contacts, access, goals and the approval process are confirmed.
- Discovery (strategist). Done when the client agrees with the findings.
- Proposal of direction (strategist and creative lead). Done when the client chooses a direction.
- Production (delivery team). Done when the work is ready for client review.
- Client review rounds (account manager). Done when the client approves, with a limit on rounds agreed at onboarding.
- Handover and wrap-up (account manager). Done when files are delivered and the client has signed off.
The client review step is where agency workflows slip. Agree the number of review rounds and the turnaround time for feedback in step 1, not halfway through the project.
Example 4: Product launch workflow
- Launch goals and tier (product marketing). Done when the team agrees how big the launch is and what it should achieve.
- Positioning and messaging (product marketing with product). Done when the core message is approved.
- Readiness (support, sales, docs). Done when help articles, sales notes and support macros are ready.
- Launch assets (marketing). Done when announcement, emails and pages are approved.
- Go/no-go (launch owner). Done when every readiness item is green, or the date moves.
- Launch and follow-up (whole team). Done when the first-week results are reviewed.
Example 5: Employee onboarding workflow
- Pre-start setup (HR and IT). Done when accounts, equipment and the first-week schedule are ready.
- First day (manager). Done when the new hire has met the team and knows their first goals.
- First-week training (buddy and subject experts). Done when the training checklist is complete.
- 30-day check-in (manager). Done when goals for the next 60 days are agreed.
- 90-day review (manager and HR). Done when the review is recorded.
How to design a project workflow
Start from a project you've already run, not from a blank page. Your team has a workflow already; it just isn't written down.
- List the steps in order. Walk through the last project of this type and write down each thing that had to happen. Merge steps that one person does in one sitting. Split steps where the work changes hands.
- Give every step one owner. Several people can contribute, but one person is responsible for saying the step is done. "Marketing" isn't an owner; "Lena" is.
- Write a "done when" rule for each step. This is the most useful line in the whole workflow. It stops work from being half-handed over.
- Mark the handoffs. For each step, note who is waiting for it and how they'll know it's their turn. Most delays happen between steps, not inside them.
- Mark the approvals. Note which steps need a yes from someone, who that is, and how long they have to give it.
- Decide what carries forward. Each step should pass its decisions to the next, so nobody has to re-ask what was agreed.
- Run it once and fix it. After the next project, ask where work waited and where people were unsure. Adjust the steps, then save the workflow for reuse.
Project workflow template
Copy this table into a document or spreadsheet and fill one row per step. Keep it to a page. If it's longer, some of those steps are tasks inside a step.
| # | Step | Owner | Input needed | Done when | Hands off to | Approval? | Typical time |
|---|---|---|---|---|---|---|---|
| 1 | Intake and decision | Project lead | Request | Request accepted or declined | Project lead | Sponsor | 1–2 days |
| 2 | Brief or charter | Project lead | Request, constraints | Goal, scope and success measure agreed | Production owner | Sponsor | 2–3 days |
| 3 | Production step 1 | Name | Approved brief | Draft ready for review | Production step 2 | No | — |
| 4 | Production step 2 | Name | Output of step 3 | Deliverable ready for review | Reviewer | No | — |
| 5 | Review and approval | Reviewer | Deliverable, brief | Approved, or changes listed | Project lead | Yes | 2 days |
| 6 | Delivery | Project lead | Approved deliverable | Delivered or live | Whole team | No | 1 day |
| 7 | Wrap-up | Project lead | Decisions, results | Lessons and follow-ups recorded | — | No | 1 hour |
Start the first steps from a template
The project charter template and the project brief template cover steps 1 and 2, and the project wrap-up template covers the last one. Open them in the process library and run them with your team.
How a project workflow runs in Nova
In Nova, each step of a workflow is a session: a live meeting, a workshop or async work with its own steps, owners and dates. On the project board, you connect one session card to another. A connection can send the first session's conclusions into the next one, under Previous conclusions and decisions, and it can set a date dependency, so the next session starts a set number of days or hours after the first.
The parts of the template above map onto Nova like this:
- Steps and owners. Each session has leaders and assignees, and each step inside it can be assigned to specific people or to Nova AI. Assigned work shows up on each person's Tasks, Sessions and Calendar pages.
- Handoffs. In a step's assignees, turn on Notify assigned when previous step is complete. The next owner gets an email when the step before theirs is done, and the step appears in their Mentions panel.
- Approvals. Add a step of the type Approve / decline to the review session. The reviewer approves, declines or sends items back with notes, right in the session.
- Dates that move together. With date dependencies, change the start date of the first session and the rest of the workflow shifts to match. Tasks inside a session can follow it with Date automation.
- A record of decisions. Session conclusions appear in the project's Decision log, next to the wins, blockers and date changes you log along the way.
When the workflow has run well once, save it. Open the project menu and select Save multi-session process (this needs Nova Pro). Your next project of this type starts from the same sessions, steps and connections, and you can choose whether it keeps the same team and AI coworker assignments. You can also start a project from a process when you create it, under Start with a project template (optional). For setting up a whole department at once, see workspace templates.
Common project workflow mistakes
- Steps with no "done" rule. Work gets passed on half-finished, then comes back. Every step needs one sentence that says when it's finished.
- Shared ownership. When two people own a step, each assumes the other will move it. Name one owner and list the contributors separately.
- Invisible handoffs. The step is done, but the next person doesn't know. Notify the next owner automatically, or at least name who tells them.
- Approvals with no deadline. A review that can take "whenever" is the most common reason projects slip. Agree a turnaround time up front.
- Too much detail. A workflow with 40 steps won't be followed. Keep the workflow to the steps where work changes hands, and put the rest in task checklists.
- Never updating it. The workflow should change after each project. If nobody has edited it in a year, it probably describes how work used to happen.
Frequently asked questions
What is a project workflow?
A project workflow is the ordered set of steps a project moves through, with one owner per step, a clear rule for when each step is done, and a handoff to the next step. It describes how the work moves, while the project plan describes what will be delivered and when.
What is the difference between a workflow and a process?
A process is the reusable way your team does a type of work. A workflow is that process applied to a specific project, with real people, dates and deliverables. Teams usually improve a workflow over a few projects and then save it as their standard process.
What are the main stages of a project workflow?
Most project workflows have five stages: intake, scoping, production, review and approval, and delivery and close. The production stage is where projects differ most, so it usually holds most of the steps.
How many steps should a project workflow have?
Usually between five and twelve. Include a step wherever the work changes hands or needs an approval. Smaller pieces of work inside a step belong in that step's task list, not in the workflow itself.
How do I make a project workflow reusable?
Write it as a template with roles instead of names, run it on a real project, fix what didn't work, then save it where the next project can start from it. In Nova, you save a project as a multi-session process, and new projects start from the same sessions and connections.