Metric Definition
Readiness before the room
Track from
Meeting preparation score
A meeting preparation score measures how ready a meeting is to be productive before it begins. It checks whether the agenda, the materials, and the attendees were in place ahead of time, so the meeting can spend its hour deciding rather than catching up. It is a leading indicator of whether the meeting will produce a clear outcome.
7 min read
What is a meeting preparation score?
A meeting preparation score measures how ready a meeting is to be productive before it begins. It scores the work done ahead of the meeting, the agenda, the pre-reads, the stated decisions, and whether attendees actually engaged with the material, into a single readiness number. A meeting that starts with a clear agenda, materials everyone has read, and a known set of decisions to make scores high. A meeting where the agenda is improvised in the first ten minutes scores low.
The score matters because preparation is the cheapest lever a team has over meeting quality. Most of what makes a meeting effective or wasteful is decided before anyone enters the room. When attendees arrive cold, the first portion of the meeting is spent on context that should have been read in advance, which crowds out the time available to actually decide. Measuring preparation makes that hidden cost visible.
Preparation score is a leading indicator. It does not tell you whether the meeting succeeded, it tells you whether it was set up to. That makes it useful in a way that outcome metrics are not. You can read a low preparation score the day before a meeting and fix it, whereas you can only read a poor outcome afterwards, when the time is already spent. Tracked across recurring meetings, it shows which ones are habitually under-prepared and quietly burning hours.
Preparation is not the same as outcome. A well-prepared meeting can still fail to reach a decision, and an under-prepared one can occasionally muddle through. The score measures readiness, not results, which is exactly why it is useful as an early warning rather than a verdict.
How to calculate a meeting preparation score
The score averages a small set of preparation signals, each scored as met or partly met, then expressed as a percentage. The simplest version weights four components equally. An agenda that went out in time, pre-reads shared with enough notice, the decisions the meeting must reach stated up front, and the share of attendees who actually engaged with the materials. A meeting that met three of the four cleanly would score around 75 per cent.
- 1
Agenda set in advance
A clear, ordered agenda circulated before the meeting, not assembled in the room. The agenda is the backbone of the score because everything else hangs off it. A meeting with no agenda cannot really be prepared for.
- 2
Pre-reads shared with lead time
Supporting documents, data, and proposals sent far enough ahead that attendees can read them. Sharing materials two minutes before the meeting counts as not shared, because no one has time to absorb them.
- 3
Decisions stated up front
The decisions the meeting is being called to make, written into the agenda. This tells attendees what they are preparing for and frames the whole session around a result rather than a discussion.
- 4
Attendees prepared
The share of attendees who actually read the materials and arrived ready to contribute. This is the hardest component to measure honestly but the most important, because circulated material that no one reads adds nothing.
You can extend the formula with components that matter for your context, such as whether the right people were invited or whether a previous meetings actions were closed before this one. Keep the set small. A score built from twelve micro-checks is precise but no one will maintain it. Four to six honest signals give you a number teams will actually keep up to date.
Meeting preparation score in a metric tree
A metric tree breaks the preparation score into the inputs a team controls, so a low score points to a specific gap rather than a general feeling of being unready. The headline score splits into three branches. Agenda quality, material readiness, and attendee readiness. Each then decomposes into the concrete actions that move it.
Agenda quality depends on whether an agenda exists, whether it is ordered by priority, and whether it names the decisions to make. Material readiness depends on whether pre-reads were created, shared with enough lead time, and concise enough to be read. Attendee readiness depends on whether the right people were invited, whether they had time to prepare, and whether they actually engaged with the material.
Metric tree insight
A high material readiness branch paired with a low attendee readiness branch is the most common failure pattern. The organiser does the work, shares a thorough pre-read, and the score still falls because no one reads it. The fix is rarely better documents. It is shorter pre-reads sent earlier, or fewer attendees who each genuinely need to be there.
Meeting preparation score benchmarks
Preparation scores are an internal measure, so there is no external standard to compare against. The ranges below describe how meetings tend to perform once a team starts scoring readiness honestly. The most useful comparison is a meeting against its own trend, because a recurring meeting drifting downward is a clear signal that the cadence has gone stale.
| Score range | Readiness level | Typical pattern |
|---|---|---|
| Below 40 per cent | Largely unprepared | No agenda or a last-minute one, no pre-reads, and attendees arriving cold. The first portion of the meeting is spent on context that should have been shared earlier. |
| 40 to 60 per cent | Partially prepared | An agenda exists but materials go out late or attendees rarely read them. The meeting can function but loses time getting everyone to a shared starting point. |
| 60 to 80 per cent | Well prepared | Agenda, decisions, and pre-reads are in place and most attendees engage with them. The meeting can spend its time deciding rather than catching up. |
| Above 80 per cent | Consistently prepared | Preparation is a reliable habit. Materials are concise and shared early, attendees come ready, and the agenda names the decisions to reach. These meetings tend to score highest on outcomes too. |
A perfect score on every meeting is neither realistic nor the aim. Some meetings are exploratory and need less formal preparation, and forcing a pre-read onto a quick check-in wastes effort. Apply the score where preparation genuinely changes the outcome, which is most decision and planning meetings, and accept that some sessions will and should sit outside it.
How to improve a meeting preparation score
Raising the score is about making preparation the default rather than an act of discipline. The most effective changes reduce the effort it takes to prepare, because preparation that depends on heroics will not hold. The four moves below map onto the branches of the metric tree and tend to compound.
Require an agenda to book the meeting
Make a stated agenda and a named decision a condition of holding the meeting at all. A meeting with no agenda either gets prepared or gets cancelled, and both outcomes are better than a meeting that begins with no plan.
Send shorter pre-reads earlier
A concise pre-read shared a day ahead is read far more often than a long one shared an hour before. Cutting material readiness down to what attendees will actually finish lifts the attendee readiness branch more than adding detail.
Invite only who needs to decide
Every extra attendee dilutes preparation, because more people share the same fixed reading time. Trimming the invite list to those who genuinely need to contribute raises engagement per attendee and the score with it.
Nudge attendees before the meeting
A reminder to the people who have not opened the pre-read, sent the day before, is cheap and effective. Catching unprepared attendees in advance is the whole point of measuring preparation rather than outcomes.
The score becomes most useful when it is connected to ownership rather than left as a manual checklist. KPI Tree lets you model the preparation score as a metric tree, with each branch assigned to the person accountable for it through RACI ownership. When the score for an upcoming meeting falls below threshold, the accountable organiser is pushed a notification while there is still time to act, rather than discovering the gap in the room. Tracking the score across recurring meetings then shows which cadences are reliably prepared and which are quietly decaying, so you can intervene before the outcome suffers.
Common mistakes when tracking a meeting preparation score
- 1
Scoring agenda existence, not agenda quality
Ticking a box because an agenda exists misses the point. An agenda that lists topics but names no decisions is barely more useful than no agenda. Score whether the agenda actually frames a result.
- 2
Counting shared as read
Assuming attendees read whatever was circulated inflates the score and hides the real problem. The hardest and most valuable component to measure is genuine engagement, not whether the email was sent.
- 3
Over-engineering the checklist
A preparation score built from a dozen micro-checks is precise on paper and abandoned in practice. Keep the components few and honest so the score stays current, because a stale score is worse than none.
- 4
Applying it to every meeting
Forcing a formal preparation score onto quick check-ins and exploratory sessions creates busywork and resentment. Reserve it for decision and planning meetings where readiness genuinely changes the outcome.
- 5
Treating a high score as success
Preparation is a leading indicator, not a result. A perfectly prepared meeting can still fail to decide. Read the preparation score alongside the outcome it predicts, never as a substitute for it.
Related metrics
Cycle time
Process speed
Operations MetricsMetric Definition
Cycle Time = Process End Time − Process Start Time
Cycle time measures the total elapsed time from the start to the end of a process. It is a fundamental operations metric used in manufacturing, software development, service delivery, and any context where the speed of a process directly affects throughput, cost, and customer satisfaction.
Sprint velocity
Agile planning metric
Operations MetricsMetric Definition
Sprint Velocity = Sum of Story Points Completed in a Sprint
Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.
First response time
Customer Support MetricsMetric Definition
FRT = Total First Response Times / Total Tickets With a First Response
First response time measures the elapsed time between a customer creating a support ticket and receiving the first substantive response from a human agent. It is the metric that shapes the customer's initial impression of the support experience and sets the tone for the entire interaction.
How to run a metrics review meeting
Metric Definition
Meeting preparation score measures readiness before the room, so this guide shows you how to turn that readiness into a review meeting that actually drives action.
Metric trees for operations teams
Metric Definition
This guide shows operations teams how to place readiness measures like meeting preparation score within a wider tree of operational drivers.
Catch under-prepared meetings before they start
Build a meeting preparation score tree that assigns each readiness branch an owner and pushes a reminder when an upcoming meeting is not set up to succeed.