Larkmoor asked every standing meeting to justify itself. Its organizers retired 25.

The situation

Most of the week at Larkmoor happened in meetings: standups, staff meetings, program reviews and project syncs that had outlived their projects. People came into the office mid-week and worked from home the rest of it, so nearly every meeting was a Microsoft Teams call, and nobody could say what the standing ones cost or whether they still earned their slot.

The administrators had already declared the rules they wanted: a meeting-free Friday, notice for new meetings and a weekly cap. What they lacked was a way to see whether the rules held, and a way to change the calendar that did not start with a memo from the top.

What they set up

• Microsoft 365 calendars, read-only, with Microsoft Teams attendance, so recorded cost comes from who actually joined rather than who was invited.
• Jira, so cross-team requests show how long they wait for a first reply.
• Slack, to reach organizers privately. Thread measurement stayed off: this project was about meetings.
• A cost band for every role, so booked time could be priced. People without a band stay visibly unpriced rather than counted as free.
• The rules they had declared, for Quorum to measure and never enforce.

What Quorum showed

Quorum read the workspace as meeting-heavy — 14.5 meeting hours per person per week over the last 28 days — so the Overview, the report and the assistant led with meetings. The reading changes the order and the headlines, never a figure: a reader who scrolls finds the same numbers whatever leads.

Computed by Quorum on the example workspace modelled on Larkmoor.

Meeting cost is measured and thread cost is modelled. Quorum shows them side by side and never adds them together.

Recorded attendance cost, last 30 daysMeasured

$2,330,8267,799 of 9,373 meetings had attendance published by Teams. The rest stay unmeasured rather than counted as zero.

People with a cost bandCount

566 of 582Time of people without a band counts as unpriced, and the coverage notice says so.

Teams scored on the Load screenCount

652 strained or overloaded. 9 teams under 3 people were withheld rather than scored.

Recurring series in the resetCount

186Engineering's active series, each owned by its organizer: 73 owners in all.

Jira projects with a published response timeMeasured

4Median first reply 0.0 working hours across 111 requests; 7 projects withheld under the floors.

What they changed

1. A

   Launch the reset

   An administrator launched a Meeting Reset over Engineering 28 days before these figures were read. Owners were asked to skip their series for 7 days before deciding, and a 30-day measurement window follows the deadline.

2. B

   Let each owner decide

   Each of the 73 owners got a private link listing their own series and nothing else. They answered for 115 of 186 series (62% of those with an owner): 56 kept, 34 changed and 25 retired. 71 had no answer by the deadline, and the reset screen lists them for follow-up rather than counting silence as a yes.

3. C

   Send a guide, not a judgement

   Every change became an approved plan with its owner — 49 in all — and each owner privately received a change guide: which meeting, what to change and how to do it in Outlook. The organizer edits the calendar; Quorum never does.

4. D

   Confirm it happened

   An administrator confirmed 21 changes on the day the calendar changed; 28 are still waiting and are not measured yet. 25 retirements were confirmed by the calendar itself: no occurrence came due after the answer.

The result

In this example, the organizers did what they answered. Retired series were taken out of the calendar, so 140 occurrences were never held, and shortened series ran at half length from the day they were confirmed (125 occurrences). That behaviour is part of the example, not a prediction by Quorum.

Computed by Quorum on the example workspace modelled on Larkmoor.

Booked cost in scope, 13 days each sideModelled

$136,839 before → $118,194 afterBooked time priced by cost band, the same number of days before launch and after the deadline. A model of the calendar, kept apart from recorded cost and never added to it.

Observed cost change, confirmed changesMeasured

-$3,382Recorded cost per occurrence after the confirmed day against before it, over 19 of 21 changes. 21 rest on fewer occurrences than a firm comparison needs, and the report says so.

Observed cost change, confirmed retirementsMeasured

-$12,461Recorded cost over 13 days before launch against the same days after the deadline, for 24 of 25 retirements; the others could not be compared from measured attendance.

These are observed cost changes in an example workspace — not savings, and not proof that the reset caused them. Quorum keeps them apart from the modelled figure, never annualizes them and keeps any increase visible.

Next for Larkmoor: the measurement window runs on, the waiting changes are confirmed or dropped, and the same loop is ready for Sales, the department whose people now spend longest in meetings.

Where this lives in Quorum

• Overview

  Led with meeting cost, because the workspace read as meeting-heavy.

• Meeting Reset

  Scope, progress by the owner's unit, who still owes an answer, and the result with its modelled and measured sides apart.

• The owner's reset page

  One private link per owner, with their own series and nothing else.

• Change guide

  Sent through every private channel that reaches the owner, built from measured facts only.

• Report

  The reset summary leadership reads, with the same caveats as the screen.

How these figures were made

The workspace behind Larkmoor was generated by Quorum's archetype harness — the synthetic companies the product is tested against — shaped to match the company's size, departments and tools, and seeded on Oct 11, 2026. Every figure on this page was then computed by Quorum's own analysis on that data and is read from a file this page cannot change. What the people in the example did — who answered, which changes they made, the settings their administrators chose — is part of the example and is stated where it matters.

An example is not a customer result, a benchmark or a forecast for your organization.

Larkmoor is an example company. Its name and story are invented to show how Quorum works; every figure on this page was computed by Quorum on a workspace modelled on it, seeded on Oct 11, 2026.