Gmail, Calendar, and Drive stay exactly where they are. Tidemere walks through the official door Google gives every serious application, reads what you share, and presents it as one view of the day, for every role in the operation.
Google gives every application a free, official door into Calendar. With your permission, Tidemere walks through it: it reads the calendars you approve, presents them in one calm view, and writes new events back where they belong. This is the same method every serious scheduling product uses.
The assistant who lives in Google Calendar keeps living there and misses nothing. The chef who prefers a printed sheet keeps the printed sheet. Tidemere becomes the place where it all makes sense at once, and it works even if some of the household never opens it.
Shared calendars merge into the estate view, and the daily digest can arrive as a clean morning email for anyone who prefers the inbox to an app.
For households without Notion or a database of their own, Drive is the repository. Procedures and documents stay in your folders; Tidemere surfaces the current version to the right role and never keeps a permanent copy of its own.
A household that keeps its lists in a Sheet keeps the Sheet. Each morning Tidemere reads it and builds the day; at close, the results write back, filled in cleanly.
The moment an event changes in Google, Google taps Tidemere on the shoulder and the update appears within seconds. On a steady rhythm, Tidemere also asks what changed since it last looked. Every dependable integration runs the pair.
The sync runs in both directions. An event created in Tidemere lands on the right Google calendar automatically, carrying an internal tag so the two systems never duplicate an event or chase each other in a loop.
Google Calendar has no concept of roles, departments, or discretion. That layer is the product.
The nanny sees childcare. The chef sees service. Nobody sees the principals' travel unless their role allows it. Discretion is enforced by the application, quietly.
One calm morning summary of the day ahead, and a warning when a shift or a school pickup has nobody assigned to it, before it becomes a problem.
Culinary, facilities, childcare, and security on a single timeline, so handoffs stop living in text threads and everyone works from the same picture.
Your existing Google calendars appear as the merged estate view. Nothing changes about how anyone works.
Staff begin creating schedules and events in Tidemere. Everything lands back in Google automatically, so nobody is left out.
Scheduling lives in Tidemere: the schedule builder, conflict checks, coverage gaps. Google becomes the mirror for anyone who prefers it.
If your household never leaves Google Calendar, the product still works. That is the point.
From Tidemere settings, or approved once for the whole organization by your Workspace administrator.
Google itself shows the consent screen and you choose which calendars Tidemere may see. Everything else stays invisible to us.
A secure token that works only for the calendars you approved, revocable at any moment from your own Google settings, with no call to us required. Tidemere never sees or stores your Google password.
Microsoft 365 and Notion expose the same kind of door, and Tidemere connects to them the same way. Mixed households are normal, and a household with no systems at all runs on native Tidemere until the day it wants one.
A conversation starts with the calendars your household keeps today, and what one calm view of them would change.