The weekly operations meeting is where an ops leader finds out whether the week is going to plan — and fixes it if it isn’t. Done badly, it’s an hour of status updates nobody needed to hear live. Done well, it’s a fast check of the numbers, a short look at what’s coming, and most of the time spent solving the two or three problems that would otherwise bite next week.
This guide gives you an agenda, explains what each part is for, and shows how to run it as a sync in Clarion.
Who should be in the room
The people who own the operations numbers — usually the ops leader plus the leads for each area (fulfilment, service delivery, support, purchasing). Five to eight people is ideal. If someone attends only to listen, send them the summary instead.
A weekly operations meeting agenda
Sixty minutes, same day and time every week:
| Step | Time | What happens |
|---|---|---|
| Scorecard | 10 min | Each owner reads their number: on or off target. No discussion. |
| Wins & notables | 5 min | Good news, customer feedback, anything people need to know. |
| Capacity and schedule check | 5 min | Is next week’s load within capacity? Any known gaps — leave, supplier delays, peak days? |
| Milestone updates | 5 min | Each quarterly project owner says on track or off track. |
| Action items | 5 min | Last week’s to-dos: done or not done. |
| Challenge discussion | 25 min | Work the most important problems, in priority order, to a decision. |
| Summary | 5 min | Read back the new action items and rate the meeting. |
The proportions matter more than the exact minutes. Reporting takes about half the meeting; solving gets the rest. If your challenge discussion keeps getting squeezed to five minutes, the reporting steps are running long — cut discussion out of them.
Why each step is there
Scorecard. Your operations scorecard — on-time rate, cycle time, backlog, defects — read out by each metric’s owner. Anything off target becomes a challenge, not a conversation.
Capacity and schedule check. This is the step most generic meeting templates leave out, and it’s the one that matters most for operations. Five minutes looking forward catches the staffing gap or supplier slip before it becomes a missed delivery.
Milestones. Quarterly improvement projects — a new warehouse layout, a supplier switch, a support tooling change. A one-word status from each owner. Detail only if something is off track.
Action items. Accountability for last week’s commitments. “Done” or “not done” — if not done, it either gets a new date or becomes a challenge.
Challenge discussion. The core of the meeting. Pick the most important issue, find the root cause, decide what to do, and turn the decision into an action item with an owner. Then the next one.
Setting it up in Clarion
Create the sync. Create a sync for your operations team with a cadence of Weekly (daily, bi-weekly and monthly are also available), a day, time and duration. See schedule a sync.
Customise the agenda. Every new sync starts with six steps — Scorecard, Wins & Notables, Milestone Updates, Action Items, Challenge Discussion and Summary. Open the sync’s details to edit its Agenda: rename, reorder and retime steps, or type a title and click Add to create your own step — here, “Capacity and schedule check”. Custom steps show your title, description and a notes box during the meeting.
Any step can also carry content shown to everyone above that step — briefing text, a checklist, images or links. For the capacity step, a short checklist (“Leave this week? Supplier ETAs confirmed? Peak days?”) keeps it fast. See customize the sync agenda.
If every team in the company should start from the same shape, an owner or admin can set it once in Settings → Sync Agenda. New syncs copy that default; existing syncs keep their own agenda.
Running it live
Click Start Sync. Whoever starts it is the facilitator: they move through the steps, and everyone who clicks Join Sync follows along on the same step. See run a live sync.
- In the Scorecard step, owners can record this week’s number right there if they haven’t already.
- In Challenge Discussion, the team can vote on which challenges to take first, add action items to a challenge, and resolve it when it’s solved. See vote and escalate challenges.
- Use quick add during the meeting to capture an action item or challenge without leaving the sync.
- In Summary, each attendee rates the meeting from 1 to 10, and for a team sync the summary is posted to the team’s Hub — so anyone who missed it can catch up.
Daily huddles
Many operations teams also run a short daily huddle. Create a second sync with a Daily cadence and a 15-minute duration, and cut its agenda down to Scorecard (daily metrics only), a custom “Today’s priorities” step and Challenges. Keep the weekly meeting for anything that needs more than a minute.
Common mistakes
- Problem-solving during the scorecard. The moment someone explains why a number is red, the meeting has derailed. “Off — added to challenges” is the whole answer.
- Too many challenges, none solved. Solving two properly beats touching ten. Use votes to choose, and carry the rest to next week.
- Decisions without owners. Every resolved challenge should leave behind at least one action item with a person and a date.
- Moving the meeting. A weekly meeting that moves every other week stops being a rhythm. Protect the slot.
- Never checking the rating. If the meeting averages a 6, ask why. It’s the cheapest feedback you’ll get.
For the general version of this meeting, see run the weekly sync.