A work calendar can look clear while a personal appointment already occupies the same time. OGAD (Off Grid AI Desktop) can compare events from connected accounts with a local model and produce a list of candidate conflicts.
The result is only as complete as the calendars you include. Google reads in this release cover the connected account's primary calendar. Outlook can list calendars and read a selected one. Name the scope and time zone before asking for conflicts.
Download OGAD | Desktop beta 122 release notes
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@getoffgridai.co, join our Slack community, or talk to us on Reddit.
Define what counts as a conflict for you
Start with overlapping timed events. Two intervals overlap when each starts before the other ends. Back-to-back events may not overlap, but they can still leave too little time for travel or preparation.
Choose any buffer explicitly. For example, require 15 minutes between video calls and 30 minutes before an off-site appointment. These are your planning rules, not facts inferred from the calendar title.
Keep all-day entries separate until you decide how they affect availability. A birthday reminder and an all-day leave event should not automatically be treated as the same kind of block.
Connect the intended calendars
Install OGAD, select a local tool-capable model, and connect the required accounts through Pro Integrations. Label them clearly, such as “Work Microsoft” and “Personal Google.”
For Microsoft, list the calendars and select the intended work calendar. For Google, confirm that the personal events are in the primary calendar. A secondary shared Google calendar is outside this guide's verified read scope.
Check one known event from each source. If the assistant cannot find those examples, fix the scope or connection before trusting an empty conflict list.
Request the event table first
Ask for a bounded read:
Read Work Microsoft's selected work calendar and Personal Google's primary calendar for 19–23 October 2026. Show start, end, title, source account, calendar, and source link where available. Display all times in Asia/Kolkata. Keep all-day entries separate and state any source that could not be read.
Use your own dates and time zone. Include both ends of each event. A list with only start times cannot support an accurate overlap check.
Inspect the table before analysis. Check a recurring meeting and an appointment with a different original time zone. A changed occurrence matters more than the recurring series' usual schedule.
Compare overlaps and short gaps separately
Then ask:
From this checked event table, list exact timed overlaps. In a second section, list gaps shorter than my 15-minute preparation buffer. Show both event names, the shared or missing time interval, and both source accounts. Do not create or move events.
Keeping the two lists separate makes the result easier to act on. A true overlap requires a different decision from a short but possible handoff between meetings.
If an event ends at 10:00 and the next starts at 10:00, that is back-to-back under the interval rule above. It may violate your buffer, but the assistant should not invent a positive overlap duration.
Verify each candidate in the source apps
Open the original events and check the date, time zone, occurrence, and attendance status. The assistant may see an event you declined or a calendar item that serves only as a reminder. Decide how those entries should count in your own plan.
For each real conflict, identify which commitment is flexible and who needs to be contacted. Ask for a draft message if useful, but review it before sending.
The direct calendar tools described here are read-only. A suggested alternative time is not a changed meeting or a sent invitation. Apply the chosen change through your calendar's normal process or a separately reviewed supported action.
Check completeness before calling a day free
Calendar tools return limited result sets. Google reads return up to 50 events per request in this release. For a dense week, split the range into days and check the returned coverage.
If a connection failed, the correct result is “that calendar was not checked,” not “no conflicts.” Ask for a scope line at the top of the output that names the sources successfully read.
Also include commitments that never reached a calendar if they matter to your decision. A local model cannot detect an appointment that exists only in your memory.
Fix common false positives
| Problem | Useful correction |
|---|---|
| Times look shifted | Use one explicit display time zone |
| All-day reminders block every meeting | Review all-day entries separately |
| Duplicate invitations create duplicate conflicts | Compare event identities and source copies |
| A cancelled occurrence is still counted | Re-read the current occurrence in the source |
| Travel time is missing | Add a stated buffer or explicit travel event |
Fetching current calendar data requires internet even if analysis runs locally. If you use a remote model, the event data is processed through that selected endpoint instead.
Make the next planning check repeatable
Save the account scope, time zone, and buffer rules that worked. Reuse them for a new week, or test a God routine that prepares the same review while the computer and accounts are available.
Connect your calendars in OGAD and inspect one day's overlaps first. Confirm the candidates in the source calendars before using the method for a full week.
