The Meeting Frequency Calculator looks at one specific question inside meeting economics and synchronous-vs-async work: what do your meeting economics actually add up to? Instead of a vague feeling, it converts the everyday signals you already notice — % that is one-way information transfer, attendees, share visibly doing other work, content needs a human voice? — into a single score you can track, compare and act on.
The model is built on loaded-cost accounting, synchronous-communication necessity analysis and context-switching research, the same foundation as our flagship meeting calculator. Each input is weighted by how strongly that factor predicts real outcomes in the research; the formula and every weight are published below, so you can see exactly why your score is what it is — and argue with it if you like.
Adjust the sliders to match your situation honestly and the score updates live, along with the strongest factors pushing it up or down. Like everything on Quirkulator, the computation runs entirely in your browser: nothing you enter is ever transmitted or stored.
The formula
w1·broadcast- % that is one-way information transfer — 0 = all discussion, 10 = pure broadcast (weight +1.1)
w2·attendees- Attendees (weight +0.4)
w3·multitask- Share visibly doing other work — the room voting with its laptops (weight +0.7)
w4·sensitivity- Content needs a human voice? — 10 = sensitive/personal delivery (weight -0.6)
w5·decisions- Real decisions needing the group live (weight -1)
σ, μ- Sigmoid squash to 0–100, centered on typical values
How it works, step by step
- Rate each input honestly — the Meeting Frequency score is only as good as your self-assessment.
- Watch the live score and note which factor the result panel names as your strongest driver.
- Read your band below — each range comes with a concrete recommended next step.
- Change one input to simulate a change in behavior and see how much the score moves — that sensitivity is the real insight.
- Re-take the assessment after a few weeks; trends across readings mean far more than any single score.
Worked examples
A low-signal scenario
With every input set well below typical — the quiet version of this situation — the model returns 24, landing in the “Legit meeting” band. High interaction, real decisions, or content that needs a human voice — this is what meetings are for. The cost buys something async cannot.
A high-signal scenario
Push the main drivers well above typical and the score rises to 60 — the “Email in disguise” band. Near-zero interaction and decisions, with visible multitasking — the room already voted with its laptops. Convert to async and reclaim the hours; the recurring version is quietly costing a salary.
How to read your score
Frequently asked questions
What does the Meeting Frequency Calculator score tell me?
It estimates the probability this meeting could have been asynchronous — high when the session is mostly one-way broadcast with few live decisions and visible multitasking, low when it involves real-time decisions, negotiation or sensitive delivery.
Is my meeting data stored?
No — everything computes locally in your browser; your org chart never leaves the page.
Is a daily standup just an email?
Only if it is a status broadcast. A short standup that surfaces blockers needing live coordination earns its cost; a long one where each person recites yesterday is the highest-scoring genre here.
Why are recurring meetings so expensive?
The cost is invisible and compounding: a weekly hour with ten people can burn a hire’s worth of salary per year while feeling like "just an hour." Annualizing the cost is what makes the waste visible.
How is a meeting’s true cost calculated?
Attendees × duration × loaded hourly rate (roughly salary × 1.4 for benefits and overhead). An eight-person hour at typical salaries runs into the hundreds of dollars before counting the focus lost to context-switching.
Do pre-reads and agendas help?
Where genuinely adopted, a pre-read reliably shortens meetings by starting room-time at the discussion instead of the download. Its failure mode — nobody reads it — is fixed by opening with a few minutes of silent reading.