There are four types of meetings that show up in every well-run company, and each one exists to answer a different question on a different time horizon.
The weekly meeting answers: are we on track this week? The monthly review meeting answers: are we trending in the right direction? The quarterly meeting answers: are we working on the right things for the next 90 days? And the annual planning meeting answers: are we pointed at the right destination? Each type has a distinct purpose, a distinct rhythm, and a distinct failure mode when it gets used for the wrong question.
Most teams do not have a problem scheduling meetings. They have a problem knowing what each meeting is actually supposed to produce.
Weekly meeting
The weekly meeting is the operating heartbeat of any functional team. It should run on the same day, at the same time, every week without exception. When it moves around, it stops being a heartbeat and becomes an appointment, which means people prepare less, commit less, and drift more between sessions.
A good weekly meeting has three parts: a scorecard review, an issue list, and a to-do review. The scorecard review takes five to ten minutes and walks every measurable number the team owns. Each number gets a red, yellow, or green rating. Red and yellow numbers go onto the issue list.
The issue list is where the real work happens. Not in the discussion of every item, but in the prioritization of the top three. Every issue on the list gets one line: here is the problem, here is what we think caused it, here is who owns the fix. Then you move to the next one. The goal is decisions, not discussion.
The to-do review closes the loop. Every action item from last week gets a check or a no. If it is a no, it either carries forward with a new owner or gets dropped. No item should carry forward more than twice without a real conversation about why.
At Sneeze It, Radar runs our weekly meeting data. Bogdan, our COO, owns the operational scorecard. Janine owns the financial rows. Tally pushes the KPI values automatically so nobody is manually entering numbers the morning of the meeting. The meeting itself takes forty-five minutes. That is not a coincidence. Forty-five minutes is achievable without shortcuts when everyone shows up with their numbers already in front of them.
How to start a meeting
The single biggest driver of meeting quality is how you start it. A meeting that starts with "so, where are we?" signals that nobody is sure what the meeting is for. A meeting that starts with a thirty-second headline round signals the opposite.
Here is a reliable way to start any team meeting: state the time box, state the desired output, and let each person say one relevant headline before the agenda begins. The time box keeps the room honest. The desired output keeps the conversation oriented toward a decision rather than a debrief. The headline round surfaces information that might change the agenda order.
For a weekly scorecard meeting, the opening sounds like: "We have forty-five minutes. We are here to identify the top three issues from this week's numbers and assign owners. Headlines: anything that changes the order of what we are looking at?" That is twenty seconds. The meeting is already running.
Do not open with recaps of the last meeting. The to-do review at the end of that meeting was the recap. Do not open with announcements that could be an email. Announcements are noise that borrow time from decisions. And do not open with a five-minute wait for people who are late. If the meeting starts on time three weeks in a row, late arrivals stop happening because the room has demonstrated it does not wait.
The discipline of how you open meeting types transfers to every other type. The variables change but the structure does not: time box, output, brief context, go.
Monthly review meetings
Monthly review meetings exist to zoom out one level from the weekly grind and ask whether the direction is right, not just whether execution is on track.
A weekly meeting can look clean while the business drifts. You can hit every to-do and hold every green number for four weeks while the underlying trend is quietly moving the wrong direction. The monthly review is the meeting that catches that.
The core of a monthly review is a trend read, not a point-in-time read. Where was this number eight weeks ago? Where is it now? Is the slope pointing toward the annual goal or away from it? A single red number on a weekly scorecard is noise. The same number trending red for three weeks in a row is a signal.
Monthly reviews should also check whether the priorities set at the last quarterly meeting are still the right ones. Something changes every month. A client exits. A hire gets made. A market signal shows up. The quarterly goal does not automatically update when those things happen. The monthly review is the moment to ask whether any 90-day priority needs to be reconsidered before the next quarterly session.
Keep monthly reviews between sixty and ninety minutes. If the weekly meetings are running properly, there should not be a backlog of deferred issues that turns the monthly into a four-hour session. If there is a backlog, that is itself the issue worth surfacing.
Meeting goals
Every meeting type needs a single clear goal, stated before the meeting starts and verified at the end.
For a weekly meeting, the goal is to identify and assign the top issues from the week's data. For a monthly review, the goal is to verify that the quarterly priorities are still correct given the last thirty days of data. For a quarterly meeting, the goal is to set or reset the 90-day priorities and make sure every seat on the chart has a clear ownership stake in them. For an annual planning session, the goal is to agree on where the company is pointed and what the coming year needs to produce.
When a meeting does not have a stated goal, it defaults to the most vocal person's agenda, which is rarely the team's highest-value conversation.
Goal-setting for a meeting is not the same as building an agenda. An agenda is a list of topics. A goal is the decision or output the meeting needs to produce. Every agenda item should connect to the goal. If you cannot explain how a given agenda item helps produce the stated output, that item does not belong in the meeting. It belongs in a Slack message or an email.
At Sneeze It, Dash publishes data before every meeting that touches performance numbers. The published state means nobody spends meeting time retrieving or debating the baseline. The meeting goal is visible before the session starts, and the first five minutes are spent checking whether the pre-read changed anyone's view of what the most important issue is. That is a replicable practice regardless of whether you have agents or not.
Quarterly meeting
The quarterly meeting is the most underrated type of meeting in a growing company. Most teams either skip it or run it as an extended weekly review. Neither produces what the quarterly is designed for.
A quarterly meeting has one primary function: setting the 90-day priorities that every seat on the chart is accountable for, and making sure those priorities are grounded in the actual state of the business rather than what the business was in the prior quarter.
Gino Wickman's EOS framework calls these 90-day priorities Rocks, and the framing is exactly right. Rocks are the things that if you do not move them this quarter, nothing else matters. The quarterly meeting is where you identify the three to seven rocks for the company and assign ownership. Everything else that comes up during the quarter is sand. Sand fills the time left over after the rocks are placed.
A quarterly session typically runs four to eight hours, off-site or at minimum in a different room than the one used for weekly meetings. The change of space signals a change of time horizon. Weekly thinking and quarterly thinking require different postures, and the environment helps shift between them.
The outputs of a good quarterly meeting are: a reviewed scorecard from the prior quarter (what did we say we would do and what actually happened), a refreshed set of 90-day rocks with named owners, and a clear restatement of the company's one-year goal so the new rocks are obviously connected to it. If you cannot draw a line from each rock to the one-year goal, the rock does not belong on the list.
If you want to see how OTP structures 90-day priorities alongside the weekly scorecard, this post on putting AI agents and humans on the same scorecard shows what a unified quarterly-to-weekly accountability loop actually looks like in practice.
Frequently asked questions
What is the difference between a weekly meeting and a monthly review meeting? A weekly meeting is a short, data-driven pulse check focused on the current week's numbers and resolving the top two or three issues before they compound. A monthly review zooms out to check whether the trends over the past four weeks are pointing toward or away from the quarterly priorities. Both are necessary. They answer different questions.
How long should a weekly team meeting be? Forty-five minutes is the right target for most teams. If your weekly meeting regularly runs ninety minutes or more, the problem is usually one of three things: too many agenda items, decisions being made by committee instead of by the seat that owns the number, or issues getting discussed without being formally put on an issue list and prioritized before debate begins.
What should meeting goals look like? A meeting goal is a single sentence describing the decision or output the meeting needs to produce. "Review last week" is not a goal. "Identify the top three issues from last week's data and assign an owner to each before we leave" is a goal. Goals that describe outputs produce sharper meetings than goals that describe topics.
How often should a company run quarterly meetings? Four times a year, aligned to the calendar quarter or the company's fiscal quarter. The gap between quarterly meetings is ninety days by design. Shorter gaps do not give enough time for the priorities to produce visible results. Longer gaps allow the team to drift without a formal reset point.
What is the right way to handle an issue that comes up in the wrong meeting type? Put it on the issue list and defer it to the meeting type it belongs in. A strategic question that surfaces in a weekly meeting belongs in the quarterly session, not the forty-five minutes you have right now. Trying to resolve a quarterly-scale question in a weekly meeting is where two-hour weekly meetings are born.
Run it in OTP
OTP connects your meeting cadence to your org chart. Weekly scorecard data, quarterly rocks, and team-level issue tracking all live in the same system as the seats that own them, so the right meeting gets the right data without anyone assembling a pre-read the morning of.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me this week's scorecard and flag any numbers that are off target."