A single application for principals and estate directors, offering a clear view of every property, every department, and every open item, gathered into one considered place.
Most principals do not want to manage the details of their homes. They want to know the details are handled.
Tidemere Residences gives the principal a clear view of every residence: current status, what is scheduled, and what needs attention, without requiring involvement in the operation. A concern can be flagged directly, reaching the right person without becoming a chain of calls. An urgent matter is surfaced immediately, and routine items collect into a clean daily summary, reviewed when the moment is right.
Status across all properties in one view: who is present, what is scheduled, and what has been flagged, without anyone having to be asked for a summary.
Surface a request or concern once. It reaches the right person without a chain of calls or a thread that has to be followed across three applications.
The operation is running, and the application shows you so directly that no one had to remember to send an update.
Not every household needs this section. For the ones that do, the same application extends to the day-to-day of childcare: a daily handoff between caregivers, a profile that travels with each child, and a calm, curated view for the parent.
Shift notes, a task list, and a shared calendar for play dates, appointments, school, and meals keep the day organized without a separate system. Each child has a profile built in: allergies, preferences, wardrobe sizing, and notes that any caregiver stepping in can read in seconds.
The way most private households operate today is not broken. It works, but only through the sustained effort of one or two people who carry the whole picture in their heads and reassemble it from a dozen separate sources every morning.
Requests arrive in Slack. Confirmations sit in email. The schedule is maintained in Google Calendar. Procedures are in a shared drive that is reorganized each year. Financial summaries arrive as attachments. The chef communicates by text. The groundskeeper leaves notes in a binder.
None of those tools are wrong. The problem is that the picture they produce, the one someone needs to act on, has to be pulled together by hand, every day. That work falls on the director. Tidemere Residences is built to hold that picture instead.
Four systems brought into one considered application: communication, coordination, documentation, and financial visibility.
Urgent items are routed to the director as they happen. Everything else collects into a single clean summary delivered once each morning. The director sees the full picture without being buried in a continuous stream. The principal sees what matters to them, and only that.
Chef and culinary, service, housekeeping, nannies, facilities, grounds, and activities: each team works within its own space inside the application. Tasks are assigned and tracked at the department level. The director sees the full cross-department picture, while each department head sees only what belongs to their team.
Standard operating procedures, checklists, and recurring protocols can live wherever the household already keeps them, including Notion. Tidemere reads the original without altering it; only the people the household designates can edit it. Each day, the current version generates a fresh, assigned task list for that team, and a recap of what was completed is sent back to the same source by evening. A housekeeping checklist kept in Notion, for instance, becomes the day's assignments. The original itself is never touched.
There is no payments feature here, and no need for one. The household's accountant or family office keeps financial records exactly where they already do: email, a shared folder, an existing reporting tool. Tidemere helps configure what gets shared, then renders it as clean, readable charts the principal and director can understand at a glance. If that connection is ever turned off, there is nothing left on Tidemere's side to see. The data was always theirs. Tidemere simply gave it a clearer shape.
Most private households already run inside Google Workspace or Microsoft 365: email threads, shared calendars, stored documents, in some cases years of institutional knowledge organized exactly the way the household has chosen to organize it.
Tidemere Residences does not ask you to abandon that. It connects to those environments, surfacing email, calendar events, and shared documents inside the application. The result is one fewer place to look, and one more thing the director does not have to translate from one system into another.
The same principle applies where the household keeps its documentation. If standard operating procedures and checklists already live in Notion, Tidemere connects there as well, reading the current version to generate that day's task list and writing back a same-day recap once the work is complete. The original is never edited by Tidemere. The household keeps exclusive control over what the standard says, and only the daily lists generated from it ever change hands.
Tidemere does not set out to become the place where your household's information lives. It is the place where the noise of it becomes legible: a single view assembled from systems you already use, rather than a new archive added to the pile.
Email, calendars, shared documents, and procedures kept in Notion are connected through the same kind of secure access most software uses to talk to Google Workspace or Microsoft 365. Tidemere reads what it needs to render your view and writes back only what you've asked it to generate: a daily task list, a completed recap. It does not keep a permanent copy of your source documents.
If a connection is ever turned off, there is nothing left behind to retrieve. The standard operating procedure stays in Notion. The calendar stays in Google. The financial reports stay in the folder your accountant already uses.
This matters most for the information closest to your family: schedules, allergy notes, anything involving your children. Wherever possible, that information is read, displayed, and discarded rather than stored. Households with their own IT infrastructure can configure a portion of the system to run on servers they control.
Tidemere Residences is not a template. It is configured in conversation, around your properties, your departments, your existing staff structure, and the rhythms of your operation that already work.
A single estate with a small team and a multi-property compound with sixty people are different operations. The application's structure, its roles, departments, access levels, and workflows, is defined during setup rather than imposed by a preset. The result is an application built to fit the household it serves.
One system. Appropriate visibility at every level, defined during setup and enforced by the application.
Property status, the daily digest, urgent flags, and financial charts. Present when something needs attention; quiet when it does not. No operational detail unless they choose to look for it.
Each department lead manages schedules, task assignments, and documentation for their team, without seeing what belongs to another. Clean lines, no overlap, no unnecessary visibility.
Every department, every property, every person. The director holds the complete operational view: the one place where everything is visible and nothing has to be reassembled by hand.
Tidemere Residences began with years spent inside the daily operations of one of the most complex, multi-residence households in the world: coordinating staff, schedules, vendors, and the small details a family never sees, because that is the job.
Even with good people and good intentions, things slipped through. A guest's allergy missed. A schedule conflict discovered too late. A standard that existed somewhere, followed inconsistently, because no one place held the current version. Tidemere was built to close exactly those gaps: the tool this team wished had existed at the time.
Tidemere does not begin with a download or a trial period. It begins with a conversation, one in which we understand your properties, your people, and your existing systems before anything is configured. From there, configuration typically takes one to two weeks, followed by another one to two weeks alongside a member of our team as your household settles in. Quiet to adopt, and careful not to add to the noise it is designed to replace.
Request a conversationFrom the principal's phone to the director's desktop. Each one is a working interface mockup, ready to open directly in your browser.