How Unmeet detects calendar decay without recording a single word.
Unmeet is built around a simple premise: calendar metadata already contains the evidence needed to spot recurring meetings that have drifted from their purpose.
Read-Only Metadata Sync
During onboarding, Unmeet requests only calendar.events.readonly scope. We inspect master recurring rules (RRULE) and expand historical instances over your chosen 30, 60, or 90-day window.
Deterministic Debt Scoring
Each recurring series with 3+ invitees receives a deterministic Calendar Debt Score (0–100) across six transparent signals. Unconfirmed RSVPs are treated as uncertainty—never conflated with declines.
Organiser-Confirmed Action
When you choose to optimise a series—moving weekly to biweekly, shortening duration, pruning selected attendees, or setting an end date—Unmeet previews affected occurrences and verifies the change.
Inside the Calendar Debt Score (0–100)
We never use opaque black-box AI to score your meetings. Every point is calculated deterministically and normalised when historical data is partial.
Measures weighted RSVP declines across recent instances, weighting required invitees higher than optional attendees.
Tracks instances moved from their original start time or cancelled within the audit period.
Identifies attendee bloat where group size has expanded well beyond decision-making thresholds.
Flags long-running series (6–12+ months) that lack an UNTIL date or scheduled review checkpoint.
Accounts for unconfirmed (needsAction) or tentative responses as uncertainty—never as proven absence.
A weak signal checking whether the invite contains a structured objective or linked document.
Why inspecting only the master event fails.
In Google Calendar, a recurring meeting consists of a master event holding the RRULE and individual instance exceptions when people decline a specific week or reschedule an occurrence. Unmeet analyses the expanded instances across your audit window so your RSVP participation trends and reschedule rates reflect reality.