Offline Meeting Response Auditor

How to use Offline Meeting Response Auditor

Compare a shortlist of meeting options after responses have been collected elsewhere. Keep yes, maybe, no and unanswered separate, identify which required participants block confirmation, and export the full vote matrix without hosting a poll or accessing anybody’s calendar.

1. Enter exact participant IDs, required flags, explicit UTC candidate slots and already collected responses.
2. Choose the minimum confirmed attendance and JSON evidence or the complete CSV matrix.
3. Review confirmed, conditional and optimistic flags and required-attendee blockers before deciding elsewhere.

Good to know

• 1–50 participants, 1–50 candidate slots, 0–2,000 unique participant/slot responses and 100,000 JSON characters. IDs are exact unique nonblank strings of at most 100 characters without controls. Every participant must explicitly declare required as a boolean. Only exact lower-case yes, maybe and no are votes.
• Slots use strict Gregorian UTC whole-second timestamps YYYY-MM-DDTHH:mm:ssZ, years 0001–9999, with positive duration of at most 24 hours. Local floating clocks, offsets, fractions, repaired dates and leap seconds are refused. No timezone guessing or DST conversion is performed.
• Quorum is an exact integer from 1 through the declared participant count. Missing responses stay unanswered. Maybe is only conditional, and optimistic unanswered capacity is separately labeled. Duplicate response pairs are refused, not silently overwritten. CSV is formula-protected and carries the literal vote matrix; JSON adds source-response provenance.
• The workbench does not run a public poll, verify real availability, contact participants, synchronize calendars, send invitations or reserve a time. Candidate options remain independent and source-ordered, so overlapping alternatives are not treated as bookings.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.