How calendar import works

Overview

When you import a .ics calendar file, Meetingrid reads the events in it and turns them into grid availability -- no AI involved, just deterministic date/time math. Calendar import is only available for meetings tied to a specific week, month, or day, since that's what lets an event's real date line up with a slot on the grid.

Only the relevant dates are used

Events are clipped to the exact week, month, or day the meeting covers. Anything outside that range -- last month's events, next year's events -- is discarded immediately and never stored, since it has no bearing on this meeting.

Recurring events

Recurring events (weekly standups, biweekly syncs, and so on) are expanded first, then only the occurrence(s) that fall inside the meeting's window are kept. A weekly event that repeats all year only contributes the single week that matters.

Timezones

• If the meeting has timezone awareness turned on, event times are converted to your local timezone before being placed on the grid, the same way the rest of the grid is displayed.
• If timezone awareness is off, event times are taken at face value -- whatever wall-clock time was written into the calendar file is used as-is, with no conversion.

Merging overlaps

Events across all uploaded files are combined and overlapping or touching time ranges are merged into single continuous busy ranges before anything is placed on the grid.

"Busy" vs "free" calendars

By default, time covered by a calendar event is treated as busy, and everything else becomes available. Some people keep the opposite kind of calendar -- only their available slots are entered as events. Toggling "Calendar events mean I'm free" inverts the logic: only the times actually covered by an event are offered as available.

Privacy

Uploaded files are parsed in memory and discarded immediately after the request completes. Nothing from your calendar file is written to disk or kept beyond the derived availability you choose to accept.