Halmora gave every department a meeting budget. 7 of 7 went over.

The situation

291 people in operations, engineering, sales, supply chain and support functions, working from several offices and out with customers. Coordination between sites runs on Microsoft Teams calls and channels, and every department head believed their own team met less than the others.

There is no Slack and no GitHub here. Whatever Quorum measured had to come from Microsoft 365 alone.

What they set up

• Outlook calendars and Microsoft Teams attendance through Microsoft 365, read-only.
• 14 Microsoft Teams channels, opted in by an administrator and measured as counts and times only: message text is discarded on arrival.
• A budget of 40 meeting hours per person per month on each of the 7 departments, set by the administrators.

What Quorum showed

Quorum read the workspace as balanced — 9.6 meeting hours per person per week beside an active written channel — so the Overview kept meetings first with threads right beside them. 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 Halmora.

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

Teams channels with a published response timeMeasured

13Median first reply 0.0 working hours over 208 conversations. 23 places withheld under the floors of 5 conversations and 3 people.

Recorded attendance cost, last 30 daysMeasured

PLN 761,6533,967 of 4,743 meetings had attendance published by Teams.

Teams scored on the Load screenCount

320 strained or overloaded. 6 teams under 3 people were withheld rather than scored.

What they changed

1. A

   Read the month

   Each department head sees the budget on their team page and gets a monthly digest; the administrator sees every department side by side.

2. B

   Agree response times

   6 response agreements on Operations and its Teams channels: 0 met, 5 not met, 1 withheld under the floors. 8 reminders named the waiting conversation, never a person.

3. C

   Turn a series into a change

   A series behind an over-budget department can become a change with an owner, a guide and a confirmation — the same loop as a Meeting Reset.

The result

The argument about who meets most ended with one table: 0 of 7 departments within budget in September 2026, 7 over, with each department's thread cost beside it and never in it. Nothing has been confirmed as changed yet, so there is no observed change to report. A budget is measurement, never enforcement: Quorum holds read-only calendar access and blocks nothing.

Where this lives in Quorum

• Budgets

  Each department's month against its budget, with thread cost beside it.

• Conversations

  Response time per Teams channel and team, under the same floors.

• Teams and Load

  Hours, focus and load band per team at or above the floor.

• Outlook add-in

  A meeting's figures and the reader's own verdict, where the meeting is opened.

How these figures were made

The workspace behind Halmora 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.

Halmora 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.