Weekly meeting templates: three structures that actually work

Most weekly meetings occupy a strange middle ground between organised chaos and tedious predictability. Either there's no structure at all—just forty-five minutes of whoever shouts loudest—or you're trapped in the same rigid format you've been using since 2019, regardless of whether it still makes sense.

The thing is, weekly meetings serve different purposes depending on what your team needs right now. Sometimes you're planning what comes next. Sometimes you're reviewing what just happened. And sometimes everything's on fire and you need to actually solve a problem rather than just talk about it.

Using the same structure for all three scenarios is a bit like using the same recipe whether you're making soup, cake, or a Sunday roast. Technically possible, but the results will be disappointing.

Here are three straightforward templates that give you a proper shape to work with. Pick the one that matches what you're actually trying to accomplish, then adjust it as needed. None of this is complicated.

Template one: The planning meeting

Use this when you're looking ahead—deciding what to work on, who's doing what, and how to spend your collective time and attention over the coming week or sprint.

Start with context (5 minutes)

Begin by getting everyone on the same page about what's happening outside your immediate bubble. This might include updates from other teams, feedback from customers, changes to deadlines, or anything else that affects your priorities. Keep it brief. You're not discussing these things yet, just making sure everyone knows they exist.

Review capacity and commitments (10 minutes)

Go round the table—or the video call grid—and have each person say what they're carrying into the week. Who's got five hours tied up in meetings? Who's off on Thursday? Who's already committed to finishing that report that was due yesterday? This prevents you from planning as though everyone has forty pristine hours waiting to be filled, which they never do.

Set priorities (15 minutes)

Now decide what actually needs to happen this week. Not everything that could happen, or everything that someone, somewhere might want to happen. What needs to happen. Aim for three to five things. If everything's a priority, nothing is, etc.

Discuss them as a group. Make sure they're actually achievable given the capacity you just reviewed. If they're not, something has to give—either the scope of what you're trying to do, or other commitments need to shift.

Assign ownership and next actions (10 minutes)

For each priority, establish who's responsible and what the very next action is. Not the entire project plan, just the next physical thing someone needs to do. "Draft proposal" is better than "explore options." "Email Sarah for budget figures" is better than "investigate costs." Specificity saves you from turning up next week wondering why nothing happened.

Identify potential problems (5 minutes)

Quick round of "what might go wrong?" This isn't pessimism, it's just sensible. If someone needs approval from another department, flag it now. If there's a dependency on someone who's notoriously slow to respond, mention it. You can't solve every potential problem in advance, but you can at least see them coming.

Template two: The review meeting

This structure works when you're looking backwards—checking what got done, what didn't, and what you've learned that might change how you work going forward.

State what was supposed to happen (3 minutes)

Start by reminding everyone what you were aiming for. Pull up last week's notes if you have them. This takes thirty seconds per priority. You're just establishing the baseline so you can compare it to reality.

Report what actually happened (15 minutes)

Go through each item and say what the current status is. Finished, in progress, stuck, abandoned—whatever the truth is. No spin required. If something didn't get done, just say so. If it's half-done, say that. The purpose here is accuracy, not making everyone feel good about themselves.

This is reporting, not discussion. Save the conversation for the next bit.

Discuss variances and reasons (15 minutes)

Now talk about the gap between plan and reality. This is where you're allowed to dig into why something took three times longer than expected, or why that other thing turned out to be completely unnecessary once you actually started.

The point isn't to assign blame—it's to understand what's predictable and what isn't. If meetings always overrun your estimates, that's useful information. If a particular type of task always turns out to be more complicated than it looks, you can plan for that next time.

Extract lessons (10 minutes)

Ask the group: what should we do differently? This might be about process, communication, estimation, priorities, or anything else. You're looking for one to three concrete changes you can actually implement, not a philosophical debate about the nature of work.

Write these down somewhere you'll actually see them again. Ideally, build them into next week's planning meeting.

Acknowledge what went well (5 minutes)

End by noting what worked. Not in a forced, corporate "let's celebrate our wins" way, but just as a factual observation. If a new approach saved time, say so. If someone's contribution unstuck a difficult situation, mention it. This helps you repeat the things that are actually working, rather than accidentally abandoning them in the next round of changes.

Template three: The problem-solving meeting

Use this format when you've got a specific problem that needs collective brain power. Not planning future work, not reviewing past work—actually solving something that's stuck right now.

Define the problem clearly (5 minutes)

Start by stating the problem in the most specific terms possible. "Sales are down" isn't specific enough. "Enterprise sales have dropped 30% in the last quarter while small business sales stayed flat" is better. The more precisely you can describe the problem, the more useful the rest of the meeting will be.

Write it down where everyone can see it. This keeps you honest and prevents the meeting from drifting into solving a different, easier problem.

Gather relevant information (10 minutes)

What do you actually know about this problem? What data exists? What's been tried before? Who's affected? Get all the relevant information on the table before you start generating solutions. This stops you from solving imaginary problems or re-proposing things that already failed in 2022.

Generate options without evaluating them (10 minutes)

Now brainstorm possible solutions, but—and this is important—don't judge them yet. Just get ideas out. Stupid ideas are fine at this stage. Impractical ideas are fine. Ideas that would never get approved are fine. You're trying to generate options, not make decisions.

This is surprisingly hard for most groups because we're trained to immediately say why things won't work. Resist that urge for ten minutes.

Evaluate and narrow (10 minutes)

Now you can be critical. Go through the options and talk about feasibility, cost, time, risk, and likely effectiveness. Cross off the ones that clearly won't work. Combine similar ones. You're trying to get down to two or three viable approaches.

Decide and assign (10 minutes)

Pick one approach to try first. Doesn't have to be perfect—it just has to be better than doing nothing. Assign someone to own it, agree on what success looks like, and set a date to check whether it's working.

If you can't decide between two options, pick the cheaper or faster one to try first. You can always try the other one later if the first one doesn't work.

Using these templates in practice

None of these structures are sacred. If your team is three people, you can skip the "go round the table" bits. If your meeting is ninety minutes instead of forty-five, expand the sections that need more time. If something consistently doesn't add value, stop doing it.

The point isn't to follow a template religiously. It's to have a deliberate structure that matches what you're trying to accomplish, rather than just turning up and hoping something useful happens. Different purposes need different shapes. It's not complicated, but it does require choosing.

Related articles

-

Using RiOrganise

Run meetings, record minutes and turn action points into tasks with Work Together.

Explore Work Together