A weekly operations meeting should resolve shared work through clear decisions, named owners, due dates, and a written action log. Review earlier commitments, identify blockers, and agree what happens afterward instead of using the whole meeting for routine status reports.
The sample agenda below is designed for a small business coordinating current work. It gives you a structure for preparing the discussion, documenting commitments, and carrying unresolved questions into an assigned follow-up.
Decide what deserves meeting time
Invite the people responsible for the work being discussed and anyone needed for a decision. Ask participants to update their open actions before the meeting. That lets the conversation begin with exceptions rather than a spoken tour of everyone’s week.
Put items on the agenda when they require a choice, a handoff, or help removing a blocker. Share routine information in the written update. If an item has no clear purpose, ask what the team needs to do with it before giving it meeting time.
Ask for a short agenda submission that identifies the issue, the decision needed, and any material people should read. A topic label alone leaves the group to discover the purpose during the meeting. If the item is only an update, place it in the written record and reserve discussion for questions that require coordination.
Check whether the people present can make the requested decision. If an essential owner is absent, decide whether the group can clarify the question or whether the item should wait. Don’t spend the whole meeting debating an option that no one has authority to approve. Record who must be involved and what information they need before the following discussion.
Review earlier commitments without losing their history
Open the action log and examine work due since the previous meeting. Mark completed items with a reference to the result. For unfinished work, record the reason and the decision about what happens now.
Don’t silently replace an old due date. Keep a note of the change so recurring delays remain visible. The purpose is to understand workload and dependencies, not to turn the log into a performance judgment without investigating the circumstances.
Use a completion standard that fits the action. Sending a request, receiving an answer, and implementing a decision are different results. The log should show which one was promised. If the action was written too broadly, clarify it before judging its status, and record the change so the original commitment remains understandable.
When work is delayed, identify the obstacle before selecting a new date. A missing approval, a changed priority, and an unrealistic estimate require different responses. Reassigning the same date pattern without understanding the cause doesn’t resolve the dependency. Ask what must change for the revised commitment to be achievable and record that condition beside the action.
State blockers as requests for a decision
Ask the owner to explain what is stopped, what information or resource is missing, and who can resolve it. “The project is behind” gives the group little to act on. A named dependency and a specific request are easier to address.
If the group can’t resolve the item, assign someone to obtain the missing answer and choose a follow-up date. Move a detailed discussion involving only a few people into a separate conversation, with its purpose and participants recorded.
Keep the description focused on the work rather than on a person’s presumed motives. State the missing input or unresolved choice, explain its effect, and identify the decision the group can make. If the cause is uncertain, record an investigation task instead of declaring an explanation as fact. This keeps a coordination meeting from becoming an argument about assumptions.
Separate immediate decisions from work needed to support them. The group may be able to choose an owner for gathering information even when it cannot yet approve a plan. Record that smaller commitment explicitly. An item can leave the meeting with a useful action without being falsely marked as resolved.
Give each action one accountable owner
Record a named owner, a due date, and the evidence that will show completion. Contributors can help, but the action should still have one person responsible for coordinating its delivery.
Atlassian’s roles-and-responsibilities guidance distinguishes roles from specific responsibilities and calls for identifying unassigned work. Use that distinction when an item falls between functions. Don’t record “the team” as owner when no individual has accepted the action.
Ask the proposed owner to confirm the commitment and identify any dependency before the discussion moves on. Naming someone in the notes isn’t the same as checking that they understand the expected result. If several people contribute, record their contributions while retaining one person responsible for coordinating the action and reporting its status.
Use a due date that reflects the sequence of work. If the action depends on another answer, record that dependency and its expected date as well. Avoid setting several dependent actions to the same deadline without discussing how they can be completed in order. A clear sequence gives the owner something more useful than an urgent label.
Try a focused sample agenda
The timing below is a suggested starting point, not a rule or a claim about the ideal meeting length. Adjust it to the decisions your business needs.
| Agenda item | Sample time | Required output |
|---|---|---|
| Review prior commitments | 5 minutes | Completed items and explained delays |
| Address blockers | 10 minutes | Decision or assigned follow-up |
| Agree current priorities | 10 minutes | Owners, dates, and dependencies |
| Read back commitments | 5 minutes | Confirmed action log |
Connect current priorities to your existing business plan. The site’s 90-day cash-flow planning article provides a related resource for looking beyond the current week. If the team keeps adding work without removing or rescheduling anything, pause to examine capacity. A meeting can’t make an overloaded plan achievable merely by recording more commitments.
At the start, identify which items must be addressed during this meeting and which can move if time is needed elsewhere. During the discussion, return to the required output: a decision, an owner, or a specific request for information. The sample timings are there to help you notice drift, not to force a decision before the necessary facts are available.
Use a separate follow-up conversation when a detail affects only part of the group. Record its purpose and who will arrange it before moving on. Otherwise, “take it offline” can become a polite way to leave the issue unassigned. Keep the result connected to the main action log so the wider team can see when the dependency has been resolved.
Maintain one action log and recap
Use the log during the meeting so participants can correct misunderstandings before leaving. Keep decisions separate from proposals that still require approval.
| Action or decision | Owner | Due date | Completion evidence | Status or dependency |
|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ | ______ |
Send a brief recap with the agreed decisions, unresolved questions, and location of the log. Avoid creating a second list that will diverge from the first. At the following meeting, return to the same record and update it.
Read the commitments back before closing. Ask participants to correct the task wording, owner, date, and completion evidence while everyone is still present. This is also the point to distinguish a proposal from an approved decision. A note that records an option as a commitment can send work in the wrong direction after the meeting.
Keep the recap brief and point to the current log rather than copying a second version into every message. If a commitment changes between meetings, update the record with the reason and inform the people affected. The following meeting should begin from that current record, including decisions made during the week, rather than from an outdated snapshot of the previous conversation.
What should every meeting action include?
- A specific task or decision.
- One named owner.
- A due date and relevant dependency.
- Evidence that will show completion.
Judge the meeting by the work it clarifies
After a few meetings, review whether the format helps people resolve dependencies and understand commitments. Shorten or remove agenda items that don’t support those purposes. Keep the written record current so the meeting produces decisions the business can actually carry out.
