A daily standup is a daily meeting of 15 minutes maximum where your team syncs on progress, the plan for the day and anything that's blocked. In agencies it does more work than in classic dev teams: it decides every morning which client project takes priority and where capacity is about to tip over. Here's how to run one without it turning into a status report, promise 🤞
[.no-toc]What is a daily standup?[.no-toc]
A daily standup is a daily team meeting, capped at 15 minutes, where everyone shares what they've finished, what they're doing today and what's blocking them. The name comes from standing up – people who stand talk less.
You'll find the same format under a lot of names: daily stand-up, daily scrum, just "daily", sometimes a huddle or a daily check-in. It started out as an event in Scrum, where it runs every day inside a sprint. These days teams far outside software development use it – creative, media, development, account management.
The core is always the same: a fixed time, a fixed format, a hard timebox. Everything else is up to your team.
What's the purpose of a daily standup?
The purpose is synchronisation, not reporting. The team decides together what gets today's limited hours and what's stuck – not who delivered how much.
A good daily standup does three things:
- Clarifies priorities: when three client projects pull at once, the standup decides which one wins today.
- Surfaces blockers: whoever is stuck says so in the morning – not three days later in the retro.
- Protects commitments: what the team promised the client gets checked against reality every day.
And three things it explicitly isn't: it's not a status report to the project lead, not a detailed discussion and not a planning meeting. The moment someone hears justification in a standup, you don't have a meeting problem – you have a leadership problem.
There are two established formats for the round itself. With round robin, each person reports in turn. With walking the board, you go through the tasks on your kanban board instead – right to left, so from "almost done" to "not started".
For agencies, walking the board is nearly always the better choice. Your people don't sit on one sprint, they sit on five client projects – a person-by-person round produces five mini status reports per head. The board round keeps the focus on what earns money: finishing tasks, not starting them.
Two efficiency levers genuinely work: a hard timebox and actually standing. A frequently cited University of Missouri study from 1999 found that stand-up meetings run roughly 34% shorter than the same meetings sitting down.
Which questions belong in an agency daily standup?
In short: The three classic standup questions aren't enough in an agency. What's missing are the questions about priority between client projects, about approvals stuck on the client's side, and about who actually has capacity today.
The three classic daily standup questions:
- What have I finished since the last standup?
- What am I working on before the next one?
- What's blocking me?
The three agency questions nobody asks – and they're the ones that count:
- Which client project takes priority if today gets tight? Dev teams have a sprint goal. You've got a relaunch, a retainer and a pitch competing for the same people.
- Where are we waiting on client feedback or an approval – and who chases it? The most common invisible blocker in agency projects doesn't sit in the team, it sits in client approval.
- Who's over- or under-booked today? Without that question, someone works hard on the wrong project while a deadline slips somewhere else.
At a glance: Three questions sync the work. Three more sync the business. Only together do they make an agency standup.
How do you connect the daily standup to capacity planning?
In short: The daily standup is the daily fine-tuning of your capacity planning. Your weekly plan says who has how much time on which project. The standup corrects that assumption against reality every morning.
Two time horizons that belong together:
- The planner covers weeks and months. This is where you spread real availability across projects, see your capacity utilisation rate and spot bottlenecks weeks ahead.
- The standup covers the next 24 hours. This is where you find out what today won't deliver: someone's off sick, a feedback loop dragged on, a client dropped in a rush request.
The decisive step happens inside the meeting, not afterwards: name the blocker, move the task, check the load, done. Push it to "I'll sort it later" and from tomorrow you're planning against stale numbers. That's exactly where capacity planning fails in most agencies – not for lack of method, but because the information is unreliable and out of date.
It feeds straight into billability. Someone who spends half a day waiting on an approval isn't utilised – they're blocked. And you catch that in the standup, not in the monthly report.
👉 We show how leading agencies set up their resource planning systematically in our webinars.
How do you run a daily standup remotely?
In short: Remote, the same 15 minutes apply but the rules get stricter: board on screen, fixed speaking order, blockers first. Going async only pays off once time zones or part-time patterns make a shared slot impossible.
Synchronous, on video:
- Share the board instead of narrating. Without a shared screen your standup turns into a podcast.
- Fixed speaking order, so nobody gets to say "I can go later".
- Blockers first, progress after – under time pressure the wrong thing gets dropped otherwise.
- Two minutes of small talk on purpose: for distributed teams it's the only informal moment of the day.
Asynchronous, in writing:
- One channel, one deadline – everyone posts their update before they start work.
- The same template for everyone, otherwise updates aren't comparable.
- One person reads and escalates, otherwise everyone writes into a channel nobody opens.
Async isn't an upgrade, it's a trade – real-time coordination for flexibility in time. When work is tightly interlocked, when the team is new and trust isn't there yet, and when blockers can't wait three hours, live stays the right call.
"The biggest sources of frustration in teams are dysfunctional communication, opaque processes, micromanagement and organisational chaos."
How do you keep every standup topic in one awork project?
In short: An awork project is the stage for your standup: the board for progress, blockers as real tasks with owners, the planner for capacity – all on one screen, no sticky notes and no screenshots.
Here's what that looks like in practice:
- Board view as the standup stage: walking the board happens directly in awork, from "in review" leftwards.
- Blockers become tasks – with an owner and a due date instead of a passing mention.
- A "waiting on client" label: stuck approvals become filterable. You can see at a glance how much work is sitting on the client's side.
- The planner right next to it: rebooking happens in the meeting, so your capacity planning stays live instead of a snapshot.
- A cross-project view for everyone working across several client projects – and still only one standup round.
- awork AI summarises what's changed since yesterday. Nobody needs to "prepare" any more.
What mistakes do agencies make in their daily standups?
Most standups don't fail on format, they fail because they become a status report to the project lead. The second biggest killer is overrunning.
The most common mistakes – and the fix for each:
- Reporting instead of syncing → rotate facilitation, run the board instead of the people.
- Detailed discussion → parking lot, then a follow-up with two people instead of eight.
- Too many attendees → ten people maximum as a rule of thumb, everyone else reads along.
- No visible board → share the screen, always.
- Blockers without an owner → every blocker gets a name, otherwise it doesn't exist.
- A standup with no consequence → if nothing gets replanned, it was just a ritual.
[.no-toc]Conclusion[.no-toc]
The daily standup is the one meeting where your team decides every day where its scarce capacity goes. Treat it as a status check and you'll burn 440 hours a year. Tie it to your capacity planning and it becomes how you steer the profitability of your projects.
Checklist for your next daily standup:
- Fixed time, fixed group, a hard 15 minutes
- Board visible to everyone, walking the board instead of person by person
- The three classic questions plus the three agency questions
- Every blocker gets an owner
- Priorities between client projects get said out loud
- Replanning happens in the meeting, not after it
- Detailed topics go to the parking lot
👉 A good standup takes 15 minutes and saves you three follow-up pings on Slack.
[.no-toc]FAQ[.no-toc]
What's the difference between a daily standup and a weekly status meeting?
A daily standup runs every day, takes 15 minutes maximum and syncs the next 24 hours. A weekly status meeting is longer, has an agenda and produces decisions. Put simply: the standup steers the day, the weekly steers the week.
Does my team need a daily if we don't run Scrum?
Yes. The format works independently of Scrum – especially in agencies, where several client projects run in parallel. You don't need a sprint goal for it, just a shared board and a clear priority for the day. More under agile project management.
How does a daily work with part-time or four-day weeks?
Put the standup at a time that covers every working pattern – usually late morning rather than 9:00. For days when people are off, a short written update in the same channel does the job. What matters is having only one place for updates.
Who facilitates the standup if there's no scrum master?
Someone from the team, on rotation. Deliberately not the person with line-management responsibility, or the format tips into a status check. Facilitation only watches two things: hold the timebox, and move detailed discussion to the parking lot.
Do you really have to stand up?
No, but it measurably helps. If you work remotely, the shared board view does the job standing used to do: it keeps attention on the work rather than the person.
Can clients or freelancers join the standup?
Freelancers in the middle of delivery: absolutely. Clients: better not, or your blocker round becomes a presentation. For transparency outwards, shared project views work far better – clients can check status whenever they like.
How long should a daily standup be at most?
15 minutes, whatever the team size. If you're blowing the timebox regularly, the meeting isn't too short – the group is too big or the topics are too detailed. Split the standup by team or project cluster instead.
