Meeting attendance rate

Meeting attendance rate is the percentage of invited or expected participants who actually attend a meeting, measured across a session or a series. If 40 people are invited to a town hall and 32 join, the attendance rate is 80 percent. The metric can be measured for a single meeting, averaged across a recurring series, or rolled up across a whole programme such as a training course or a webinar season.

The metric matters because attendance is a leading signal of relevance and engagement. People vote with their calendars. When attendance for a recurring meeting drifts down week after week, it usually means the meeting has stopped earning its slot: the agenda has gone stale, the timing clashes, or attendees no longer see why they need to be in the room. A healthy attendance rate is a sign that the meeting is delivering enough value to justify the time it asks for.

Attendance rate is most useful when paired with context. A recruiting interview no-show, a sales discovery call no-show and an internal stand-up no-show all read differently and call for different responses. The number is the same shape in each case, but what it tells you and who should act on it depends entirely on the type of meeting being measured.

The core calculation divides the number of people who attended by the number invited, then multiplies by 100. The accuracy of the metric depends less on the arithmetic and more on defining the inputs cleanly, because both the numerator and the denominator are easy to get wrong.

1. 1

   Define the invited population

   Decide who counts as invited. For a required meeting it is the full invite list. For an optional one, the expected population may be those who accepted the invitation rather than everyone who received it. The denominator you choose changes the meaning of the rate.

2. 2

   Set the attendance threshold

   Decide what counts as having attended. A common rule is presence for at least half the scheduled time, which excludes people who join briefly and drop off. Record the threshold so the metric stays consistent across sessions.

3. 3

   Count actual attendees

   Capture who met the threshold. Video tools can log join and leave times automatically, while in-person meetings need a sign-in or a manual headcount. Avoid counting people who were merely on the invite or dialled in but never engaged.

4. 4

   Calculate and trend the rate

   Divide attendees by the invited population and track the result over time rather than reading a single session in isolation. The trend across a recurring series carries far more signal than any one meeting.

A worked example shows why the denominator matters. A webinar sends 500 invitations, 180 people register, and 110 join live. Measured against everyone invited, attendance is 22 percent. Measured against those who registered, it is roughly 61 percent. Both are valid, but they answer different questions: the first measures how well the invite converted, the second measures how well registration converted to attendance. Reporting one as if it were the other is a common source of confusion.

A metric tree decomposes attendance rate into the stages that turn an invitation into a person in the room, and traces each stage back to the lever that drives it. This turns a single percentage into a diagnostic, because a falling rate can be located at the exact stage where people are dropping out.

The first level splits attendance into the funnel it really is: invites sent, invites accepted, and accepted invites that convert to actual attendance. Each stage decomposes into the factors that move it. Acceptance depends on how relevant the meeting feels and how well the timing fits. Conversion from acceptance to attendance depends on reminders, competing priorities on the day, and how easy it is to join. The leaf level holds the operational levers you can actually pull.

The tree separates a relevance problem from a logistics problem. If attendance is low because few people accept in the first place, the fix sits with the agenda and the audience. If people accept but do not show, the fix sits with reminders, timing and join friction. The two failures look identical in the headline number and need opposite responses.

Attendance benchmarks depend heavily on the type of meeting and whether it is required or optional. A mandatory internal session sits at a very different level from a free public webinar. The figures below are typical ranges rather than fixed targets, and the more useful comparison is always a meeting against its own past performance.

Read these as starting points, not pass marks. A required meeting at 88 percent may be fine if it is large and global, where time zones make full attendance impractical. The benchmark that matters most is the trend: a recurring meeting sliding from 95 percent to 70 percent over a quarter is telling you something well before it crosses any external threshold.

Improving attendance rate means fixing the right stage of the funnel rather than reaching for the same lever every time. The tree tells you whether the problem is that people are not accepting, or that they accept and then do not show. Each points to different actions.

The metric tree approach starts by finding the stage with the biggest drop, then acting on the leaf beneath it. If acceptance is the weak stage, the lever is the agenda and the audience. If accepted-to-attended is the weak stage, the lever is reminders and join friction.

KPI Tree lets you connect each stage of the attendance funnel to the person who owns it, with RACI ownership on every node so the accountable owner for a meeting series or a programme is explicit. When attendance for a series moves outside its expected range, the platform pushes that change to the owner instead of waiting for someone to notice the empty seats. The verified impact loop then checks whether a change, such as adding reminders or trimming the invite list, actually lifted attendance, so a real improvement is not confused with a quiet week.

1. 1

   Using the wrong denominator

   Measuring against everyone invited and against everyone who registered produce very different numbers. Mixing the two, or quietly switching between them, makes the metric impossible to compare across meetings and over time.

2. 2

   Counting brief joiners as attendees

   Someone who joins for ninety seconds and leaves is not really an attendee. Without an attendance threshold, the rate flatters meetings that people drop in and out of, hiding genuine disengagement.

3. 3

   Reading a single meeting in isolation

   One low session can be a clash, a holiday or bad luck. The signal lives in the trend across a series. Reacting to a single data point leads to changes that solve a problem that was never really there.

4. 4

   Treating low attendance as a discipline problem

   Chasing people to attend a meeting they keep skipping treats a symptom. Falling attendance is usually feedback that the meeting has stopped being worth the time, and the fix is the meeting, not the attendees.

5. 5

   Ignoring the difference between meeting types

   Holding a free webinar to the same standard as a required internal meeting sets a target it can never hit, while letting a slipping mandatory meeting look acceptable. Benchmark each type against its own norms.