Usage, plans, and overage

The Usage page gives admins a clear picture of what the workspace has generated and what it costs, so there are never surprises on the invoice. It is admin-only because it is billing information. Members who open it see a friendly gate instead.

What counts as a briefing

One briefing is one successfully generated podcast episode for one attendee. A meeting with five attendees that completes fully counts as five briefings. Episodes that fail are not counted. Usage is tallied per calendar month in UTC.

Plans and allowances

Each plan includes a monthly allowance of briefings, and briefings beyond it bill at the plan's overage rate:

| Plan | Included briefings per month | Overage per briefing | |---|---|---| | Lite | 10 | CHF 2.00 | | Team | 120 | CHF 1.75 | | Business | 400 | CHF 1.40 | | Scale | 1200 | CHF 1.10 | | Enterprise | Custom | Custom |

Enterprise plans have no fixed allowance and are never charged overage here.

Reading the Usage page

The summary shows the current month's briefings against the allowance, any overage so far, and the cost of that overage. A trend graph shows usage over your workspace's whole lifetime, switchable between Hourly, Daily, Monthly, and Yearly views. Quiet periods are shown as zero rather than skipped, so equal steps on the graph always mean equal time.

Below the graph, the most recent generation runs are listed with the meeting they belong to, how many attendees were on it, how many episodes completed, and how many briefings the run added to the tally. Every number on the page traces back to a real meeting.

Rescans and repeat generations

Re-running generation for a meeting only bills the difference. Quorum remembers how many briefings a meeting has already counted, so a repeat run that produces the same five episodes adds zero new briefings, and one that succeeds for an attendee who previously failed adds only that one. You are never billed twice for the same episode.

Keeping usage predictable

• The attendee list is the multiplier. A workspace-wide meeting via @all generates one episode per member, so use it deliberately.
• The calendar import protects you from accidental double-billing by refusing to import the same Teams occurrence twice.
• If the month is running hot, the trend graph shows exactly which days and which meetings drove it.