Sandwich generation eldercare
Shared Calendar for Sandwich-Generation Working Parents: Coordinate Eldercare Caregiver Rotations Across Sibling Corporate Calendars Without Leaking Work Details
A sandwich-generation working parent running an eldercare caregiver rotation for an 82-year-old parent with early-stage Alzheimer's is not building a family calendar. She is running a three-shift operation across a Fortune 500 Microsoft 365 tenant, a hospital-system Microsoft 365 tenant, a school-district Google Workspace tenant, a paid home health aide's personal Gmail, an aging parent's doctor-portal ICS feed, and an adult-day-program schedule. A shared calendar built for this reality treats cross-tenant calendar exposure anxiety and medication-window slippage as the design constraint, not a footnote to a generic family scheduling product. The pattern below is the manual method first, then where it actually breaks, then how WonderCal holds it at $4 per user per month without ever putting a comp discussion or a patient identifier on the family view.
Manual shared calendar tutorial for a three-sibling eldercare rotation
Run the manual method first. Every rule the family later expects a sync product to enforce has to be written down as an operating spec before any software can hold it. The working example is a US-based 45-year-old sandwich-generation working parent in a Fortune 500 role on Microsoft 365, coordinating care for an 82-year-old parent with early-stage Alzheimer's. The rotation includes sibling 1, a hospital-system physician on Microsoft 365 with PHI restrictions, sibling 2, a public-school teacher on a school-district Google Workspace with student-data restrictions, and a paid home health aide visiting four times a week on a personal Gmail. Layered on top: a rotating hospice, occupational therapy, and cardiology visit set that publishes ICS feeds from the doctor portal, and an adult-day-program pickup and dropoff schedule Monday through Friday.
Name the rotation outcome in one sentence
Write down what the rotation has to produce, in one sentence, before anyone opens a calendar. Something concrete: zero missed medication windows in a rolling 30-day period across two morning doses and one evening dose, or at least one named sibling responsible for arrival coverage every weekday between 7 a.m. and 7 p.m., or a paid caregiver arrival window confirmed 48 hours in advance every visit. A rotation without a named outcome drifts into whichever sibling has the softest work calendar that quarter, and that is the sibling who burns out. Name the outcome once, put it at the top of the shared calendar description, and reread it every quarter.
Build the required role and calendar matrix
List roles and calendars, not personalities. The rotation has to survive one sibling going on a hospital on-call week, one sibling on PTO for a school break, and one sibling stuck in a Fortune 500 board offsite with no phone. Every calendar in the matrix is a potential leak surface and a potential conflict source; naming them all up front means nothing gets discovered halfway through a hospice intake.
Role Primary calendar Status Representation rule Coordinating sibling (F500 working parent) Fortune 500 Microsoft 365 (parent-company tenant) Required Owns the rotation spec and the masked family view Sibling 1 (physician) Hospital-system Microsoft 365 Required PHI restrictions; on-call week inverts availability Sibling 2 (school teacher) School-district Google Workspace Required Student-data restrictions; fixed instructional day Paid home health aide Personal Gmail Required (4x/week) Sees masked Busy only; arrival window confirmed 48h prior Aging parent's doctor portal Doctor-portal published ICS Read-only source Hospice, OT, cardiology visits; one-way subscription Adult day program Program-published ICS Read-only source Pickup and dropoff windows Monday through Friday Fix the weekly rotation grid before touching individual events
Do not start with a doctor appointment. Start with a seven-day grid that assigns a named primary sibling to every daytime block Monday through Sunday, plus a named secondary backup for each block. In the working scenario the F500 sibling holds Monday and Tuesday daytime, the physician sibling holds Wednesday and alternating weekends (subject to on-call inversion), the school-teacher sibling holds after-school and Thursday, and the paid home health aide holds Monday, Tuesday, Thursday, and Friday morning arrival windows. Publish the grid to the pod before adding a single individual event. A rotation grid negotiated event-by-event teaches the family that the grid is optional, and the coordinating sibling absorbs every gap.
Create the shared eldercare calendar with a neutral name
Create a calendar named
Parent Care Rotation, notMom Alzheimer's Schedule. Calendar names leak. A calendar name that includes a diagnosis or a full first name becomes visible to every subscriber, including the paid home health aide's Gmail address book, and in some corporate free/busy views it renders on hover to the sibling's colleagues. The coordinating sibling owns the calendar. The two other siblings and the paid caregiver receive subscriber access only. Editors are limited to two adults. A shared eldercare calendar with five editors becomes a leak surface inside a single quarter and stops being a useful busy record inside two months.Mask every hold and log the source calendar key
Every hold on the shared eldercare calendar shows title
Busyor a neutral category label such asCare - AM,Care - PM,Appt, orAide. The record needs start, end, time zone, assigned role, source calendar key, and last-checked time. Do not copy patient MRNs, hospice-nurse names, medication brand names, prescribing physician names, student IEP references, work meeting titles, comp band figures, deal-team notes, or client references. The source calendar key is a short private reference such ascoord-f500-o365,sib1-hosp-o365,sib2-district-g,aide-gmail,portal-ics, oradp-icsso the coordinating sibling can trace a hold back to its origin without the calendar itself revealing work or medical detail.Subscribe to the doctor-portal and adult-day-program ICS feeds as read-only
The aging parent's doctor portal publishes hospice, occupational therapy, and cardiology visits as an ICS URL. The adult day program publishes pickup and dropoff windows as a second ICS URL. Subscribe both to the shared eldercare calendar as read-only sources with distinct color labels. Do not attempt to write appointments back to the portal; the portal is the record of truth for those visits. Confirm the subscription refresh cadence in the calendar client's advanced settings; both Google Calendar and Outlook default to a 12 to 24 hour refresh on subscribed ICS URLs, which is the single largest source of stale-appointment risk on the manual path.
Overlay sibling on-call, PTO, and DST as first-class events
The physician sibling's hospital on-call weeks are the single most disruptive event in the rotation because they invert availability for seven days at a time. Publish each on-call week as a recurring block on the shared eldercare calendar months in advance, and require the two other siblings to pre-commit to backup coverage for that week the moment the on-call schedule is posted. Publish sibling PTO the same way. Publish Daylight Saving Time transitions as annotated events so the 8 a.m. medication window does not silently move an hour when Sunday flips; the aide especially needs to see the DST shift confirmed rather than inferred.
Confirm the paid caregiver arrival window 48 hours in advance
The paid home health aide runs a schedule against multiple clients. She cannot reroute her Wednesday afternoon based on a Tuesday-night text. Publish the aide's next-week arrival windows on the shared eldercare calendar every Friday, and confirm any changes 48 hours in advance. The aide receives masked Busy blocks for sibling availability so she knows when a sibling can cover a swap and when the sibling is genuinely unavailable, without ever seeing the work meeting title behind the Busy. This one habit removes roughly two-thirds of the aide-related friction on the manual path.
Run cache, race, and cross-tenant tests before trusting the view
Test the ICS cache latency directly. Add a fake appointment to a test calendar, publish it to the ICS feed, and time how long it takes to appear on each sibling's subscribed view. On most corporate Outlook and Google Workspace clients that number is 12 to 24 hours; if the family's number is worse than that, the calendar is not fit for medication windows. Then open the shared eldercare calendar in two private browser windows and attempt to log the same hold at the same second. Only one hold should win. Repeat the test against the hospital tenant, which is often the account with the strictest free/busy publication policy. Ship nothing that fails these tests.
Name the audit owner and the escalation rule
The coordinating sibling owns the Sunday-night audit: verify next-week rotation grid, confirm aide arrival windows, refresh doctor-portal subscriptions, and cross-check sibling on-call and PTO. Write the escalation rule out loud: if a medication window looks at risk of slipping past fifteen minutes, the primary sibling calls the aide directly rather than waiting on a group text; if the primary sibling cannot be reached inside ten minutes, the backup sibling activates automatically. Silent slippage on a medication window is the failure. A named escalation with a defined recovery time keeps the parent safe and keeps the rotation from collapsing onto one sibling.
Why the manual eldercare shared calendar leaks work details
The manual method is useful because it forces the family to write the operating rules down. At three sibling corporate tenants plus a paid caregiver Gmail plus two ICS portals, it also puts the entire failure surface on one coordinating sibling. By the third month, the shared eldercare calendar becomes a part-time reconciliation job, and calendar exposure anxiety starts showing up in the coordinating sibling's work day as a background hum that never quite quiets. The leaks below are not hypothetical; they are the ones that show up first.
ICS 12 to 24 hour cache staleness
A published ICS feed is cached by the subscribing client. Google Calendar refreshes external ICS subscriptions on a schedule that typically lands between 12 and 24 hours; Outlook behaves similarly. When the physician sibling gets pulled into a 6 a.m. add-on shift on their hospital Microsoft 365, the availability change does not surface on the F500 sibling's subscribed view until the next cache refresh. If the coordinating sibling opens the family calendar at 7:30 a.m. to hand off the morning medication window, the physician sibling still reads as available. That is the exact failure mode a medication rotation cannot tolerate.
Outlook default free/busy sharing at the cross-tenant boundary
Outlook's default cross-tenant free/busy sharing often exposes not just busy state but subject lines, organizer names, and location strings. A Fortune 500 sibling who cross-shares availability with a hospital-system sibling and a school-district sibling can end up publishing meeting titles like Q3 Comp Calibration - IC5 Band, Board Prep - Deal Team, or Reorg Draft - Confidential straight into the other siblings' free/busy overlays. Neither the hospital IT team nor the school-district IT team is aware their user is seeing that data; the exposure is invisible to the sender until the day a screenshot ends up in the family group chat.
Category color and calendar name leaks
Even when meeting titles are masked, category color and calendar name still leak. A calendar named Deals - Confidential subscribed onto the school-teacher sibling's Google Workspace is itself a disclosure that a deals workflow exists. Category colors labeled Client A, Comp, Reorg, or Legal render on hover in most calendar clients and mirror across most sync products by default. On the medical side, a category labeled Hospice or Palliative on the physician sibling's hospital calendar can bleed onto the aide's Gmail view and change the emotional register of the aide's conversations with the parent in ways the family did not consent to.
Subject-line leaks on shared holds
A shared eldercare calendar with five editors is a slow leak of every hold anyone forgets to mask. A hospice nurse visit copied verbatim from the doctor portal exposes the parent's prognosis to the paid aide before the family has decided what to tell her. A physician sibling's Patient MRN 4471 - Post-Op Consult hold copied onto the family calendar publishes a patient identifier to a Gmail account that has no HIPAA obligation. A school-teacher sibling's IEP Review - Student J.M. hold copied to the family calendar publishes a student name in violation of district policy. Every one of these leaks is a policy event, not a cosmetic issue.
iCal subscribe pulling private and confidential titles
When a sibling subscribes to a raw ICS export of another sibling's work calendar, the subscription pulls whatever the sender has published. Marking individual events as Private in Outlook or Google does not always suppress the title on the outbound ICS feed depending on tenant policy and calendar-client version. The safe assumption is the opposite: assume every event title on a subscribed ICS feed is visible to every subscriber unless the calendar owner has explicitly configured a tenant-side privacy filter. Most sandwich-generation working parents discover this the week after they cross-subscribed a sibling to their work calendar for eldercare coverage.
Manual shared eldercare calendar versus OneCal versus WonderCal
These three options solve different parts of the sandwich-generation eldercare problem. The manual shared eldercare calendar expresses the rotation grid, the role and calendar matrix, and the escalation rule. OneCal offers a paid family-plan two-way sync at roughly a five-minute cadence, which is real progress over ICS but tends to hit a hard denial at hospital IT, school-district IT, and Fortune 500 IT because the OAuth consent request asks for broad tenant scope. WonderCal keeps masked busy state aligned across every connected sibling Google Workspace, sibling Microsoft 365, and paid caregiver Gmail in under a minute, using per-user OAuth that does not require a domain-wide install. Most three-sibling rotations end up running the manual role matrix as the operating spec and WonderCal as the sync layer underneath it.
3-way operating comparison for a sandwich-generation eldercare rotation
| Operational vector | Manual shared eldercare calendar | OneCal | WonderCal |
|---|---|---|---|
| Latency | A published ICS feed from a Fortune 500 Microsoft 365 mailbox, a hospital-system Microsoft 365 mailbox, or a school-district Google Workspace calendar is cached by every subscriber for roughly 12 to 24 hours. When the physician sibling gets pulled into an emergency add-on shift at 6 a.m., that change does not surface on the eldercare shared calendar until the next cache refresh, often after the 8 a.m. medication window has already passed. A three-sibling rotation covering an 82-year-old parent with early-stage Alzheimer's cannot survive on a 24-hour staleness budget. | OneCal advertises roughly a five-minute sync interval on paid tiers. That is a real improvement over ICS, but it comes with a broad OAuth request that hospital IT, school-district IT, and Fortune 500 IT typically flag on review. When the physician sibling switches to an on-call week and their availability inverts, a five-minute sync catches the change; the problem is getting the connector approved on the hospital tenant in the first place so the sync ever runs. | Masked busy blocks sync across every connected sibling Google Workspace, sibling Microsoft 365, and paid caregiver Gmail in the eldercare rotation in under a minute for most paths. The window in which a fresh work conflict on the F500 parent's calendar can still show as open on the caregiver rotation shrinks from a full day to about sixty seconds. That is the difference between the home health aide standing at a locked door at 9 a.m. and the aide getting a rerouted arrival window before leaving her prior client. |
| 2-Way Sync | A published ICS feed is one-way by definition. When the school-teacher sibling drops an adult-day-program pickup block onto the shared eldercare calendar, that block does not write back to the F500 sibling's Outlook or the physician sibling's hospital calendar; each sibling has to copy the hold into their own work calendar by hand. Miss the copy once, and a parent-teacher conference gets scheduled on top of a hospice nurse visit that was already committed on the shared view. | OneCal offers two-way sync, but the two-way path typically asks for broad calendar read/write scope on every connected tenant. A hospital-system security team reviewing a request that lets a third party write events into a physician's PHI-adjacent calendar almost always denies the install. The same request against a school-district tenant with student-data restrictions or a F500 parent-company tenant with strict external-sharing policy usually returns the same denial. | Two-way sync updates the masked block when a source event is created, moved, resized, or cancelled. The source calendar stays the record of truth. When the physician sibling books a cardiology consult for the parent, the caregiver rotation view updates in under a minute on the F500 sibling's Outlook, the school-teacher sibling's Google Workspace, and the paid caregiver's Gmail without any of those calendars gaining write access to the physician's hospital mailbox. |
| Calendar Privacy | A default Outlook free/busy share at a cross-tenant boundary often exposes meeting titles, organizer names, and location strings. The F500 sibling's Q3 Comp Calibration - IC5 Band hold, the physician sibling's Patient MRN 4471 - Post-Op Consult hold, and the school-teacher sibling's IEP Review - Student J.M. hold all leak straight into the eldercare shared calendar the moment any sibling copies raw ICS. Category colors and calendar names carry the same leak surface. | OneCal copies event titles by default when it mirrors between calendars. That default means the paid caregiver's Gmail can end up displaying Board Comp Discussion - Confidential from the F500 sibling and Hospice Intake - Metastatic from the physician sibling, which is both a work-privacy leak and a medical-privacy leak in the same view. The title-mask setting exists but is not on by default, so the first mirrored cycle is usually the one that leaks. | Destination calendars receive masked Busy blocks only. Meeting titles, attendees, locations, notes, video links, patient identifiers, comp band references, and student names stay in the source calendar. The paid home health aide on personal Gmail sees a Busy block on the F500 sibling's Wednesday afternoon and knows not to call for a swap; she never sees the client name, the comp discussion, or the hospice nurse's name that would otherwise cross the boundary. |
| IT Admin Blocks | Corporate mail gateways at Fortune 500 companies, hospital systems, and school districts frequently strip inbound ICS subscription URLs as suspicious, block outbound ICS publication as a data-loss risk, or quarantine the calendar-share invite entirely. A three-sibling rotation that depends on each sibling publishing an ICS feed off their work calendar hits three different admin policies, and at least one of them tends to be a hard no. | The OneCal OAuth consent request asks for broad calendar scope across the tenant. Hospital IT reviewing anything that touches a physician mailbox tends to deny by default under PHI risk framing. School-district IT reviewing anything that touches student-visible calendars tends to deny under FERPA framing. Fortune 500 IT reviewing anything with cross-tenant write scope tends to route to a security review that takes weeks and often ends in denial. | User-scoped OAuth means each sibling authorizes their own calendar individually, without a domain-wide admin install. The physician sibling can connect the hospital Microsoft 365 mailbox as a user without asking hospital IT to bless a tenant-wide connector, the school-teacher sibling can connect the district Google Workspace the same way, and the F500 sibling can connect the parent-company Outlook without triggering the security-review queue. The paid caregiver on personal Gmail is a standard consumer OAuth path. |
| Team Pricing | There is no software invoice, but the real cost is roughly 4.8 hours a week of Sunday-night reconciliation for the coordinating sibling, or about 156 hours a year of unpaid family-coordinator time. Add the cost of a missed medication window, a hospice nurse visit that overlaps a parent-teacher conference the aide cannot cover, and a physician sibling on-call inversion that nobody caught until Tuesday morning. That is the fully loaded price of "free." | OneCal prices per user and per connected calendar. Three siblings plus one paid home health aide plus a doctor-portal ICS plus an adult-day-program ICS is a lot of connected surfaces before the family has picked up a single medication reminder. On multi-tenant plans the monthly bill for a three-sibling rotation with two portals often crosses what an eldercare care-manager service would charge for the same hours of coordination. | $4 per user per month covers the cross-calendar masked busy-sync layer for the eldercare rotation. Three siblings plus one paid home health aide is $16 per month. Add the aging parent's doctor-portal ICS and the adult-day-program ICS as read-only sources at no per-source charge and the total holds. Weighed against 156 hours a year of Sunday-night reconciliation on the manual path, the sync-layer math is not close. |
How to choose a shared calendar for a sandwich-generation eldercare rotation
Keep the manual method when the rotation is genuinely simple: two siblings on the same tenant, no paid caregiver, no doctor-portal ICS, no adult day program, and the coordinating sibling has three focused blocks per week to audit the calendar. It is also the correct starting exercise for any family that has not yet written a rotation grid and a role matrix. A calendar sync product cannot enforce decision rights the siblings have not agreed on, and it cannot defend a medication window the family has not committed to as a rule.
Add OneCal when the two-way sync tradeoff is worth the admin friction and every sibling is on a personal or lightly governed tenant. OneCal's five-minute sync cadence is a real improvement over 24-hour ICS staleness, and its family plan pricing works for a simple two-sibling case. The failure mode shows up on multi-tenant rotations: hospital IT tends to deny the broad OAuth scope for a physician mailbox, school-district IT tends to deny the same request for anything student-visible, and Fortune 500 IT tends to route it to a security review that returns weeks later with conditions. OneCal also copies event titles by default, which means the first mirrored cycle is often the one that leaks the comp discussion or the patient identifier onto the family view.
Add WonderCal when the rotation spans two or more sibling corporate tenants, when at least one sibling is on a restricted tenant such as a hospital Microsoft 365 or a school-district Google Workspace, when a paid caregiver on personal Gmail needs to see sibling availability without seeing work meeting titles, or when the coordinating sibling has crossed roughly three hours a week of Sunday-night reconciliation on the manual ICS path. WonderCal uses per-user OAuth that avoids the domain-wide install, writes masked Busy blocks only, and holds sub-60-second sync across every connected calendar. At $4 per user per month, a three-sibling rotation plus a paid home health aide is $16 monthly. Weighed against 156 hours a year of unpaid reconciliation and the ambient cost of calendar exposure anxiety, the sync-layer math is not close.
The operator checklist before shipping the eldercare shared calendar
- The rotation outcome is named in one sentence at the top of the shared calendar description and matches the role and calendar matrix.
- Every required role has a named primary sibling and a named backup sibling; no permanent alternates, and no gaps on the seven-day rotation grid.
- Every conflict-holding sibling Google Workspace and Microsoft 365 account is represented as masked Busy holds only, with a private source calendar key held by the coordinating sibling.
- The paid home health aide sees masked Busy on sibling availability and never sees a work meeting title, a patient identifier, a student name, or a comp band figure.
- The doctor-portal ICS and adult-day-program ICS are subscribed as read-only sources with distinct color labels and known cache-refresh cadences.
- Sibling on-call weeks, sibling PTO, and DST transitions are published as first-class annotated events months in advance, not as texts in a group chat.
- Cache, race, and cross-tenant tests have passed against every required calendar, and the ICS cache latency has been measured directly rather than assumed.
- The coordinating sibling owns the Sunday-night audit; the escalation rule for a medication window at risk of slipping past fifteen minutes is written and rehearsed.
- No confidential work meeting title, no patient MRN, no hospice-nurse name, no student IEP reference, and no comp discussion detail appears on any calendar that mirrors outside the source tenant.
Final recommendation
Product Tevye answer: a sandwich-generation eldercare rotation is a multi-year operation, not a temporary coordination task. The rotation grid, the role and calendar matrix, the masked shared calendar, and the named escalation rule are the operating spec that keeps a parent's medication windows safe and keeps the coordinating sibling from absorbing 156 hours a year of unpaid reconciliation on top of a Fortune 500 role. Choose the shared calendar that keeps that spec current under real cross-tenant pressure across a hospital Microsoft 365, a school-district Google Workspace, a Fortune 500 Outlook, and a paid caregiver Gmail, not the one with the friendliest family-plan marketing page.
A family-facing calendar surface is only the visible layer. The operating system beneath it is the sibling agreement, the cross-tenant sync, the masking policy, and fresh busy state across every account that can invalidate a medication window or a hospice visit. Get the spec right, then pick the software that keeps the calendar layer honest at $4 per user per month rather than at the cost of a missed morning dose, a hospice nurse standing at a locked door, or a comp discussion title showing up on the paid caregiver's Gmail.
FAQ: shared calendar for sandwich-generation eldercare rotations
What makes a shared calendar work for sandwich-generation working parents coordinating eldercare?
A shared calendar for a three-sibling eldercare rotation has to hold four things at once: a medication administration window that cannot slip past fifteen minutes, a paid home health aide arrival window that lives on a personal Gmail, cross-tenant availability across at least two of a Fortune 500 Microsoft 365, a hospital-system Microsoft 365, and a school-district Google Workspace, and a masking layer that keeps confidential work meeting titles, patient identifiers, and student names off the family view. If any one of those four fails, the rotation defaults to whichever sibling has the flexible calendar that week, and burnout follows inside two months. See the private family work calendar sync pattern for the base masking approach that pairs with an eldercare rotation.
How does a manual ICS feed leak confidential work meeting titles onto the family shared calendar?
Outlook and Google both default to publishing the event title on an outbound ICS feed unless the calendar owner explicitly sets titles to Private or masks the free/busy detail at the tenant boundary. A Fortune 500 sibling who subscribes their spouse or a paid caregiver to a raw ICS export is publishing every meeting title, including comp discussions, client names, deal-team calls, and internal reorganization holds. Category color and calendar name leak in parallel: a calendar named Deals - Confidential is itself a disclosure. Compare how the same leak plays out on custody calendars in the split-custody parents corporate Outlook playbook.
Why does hospital IT usually deny a OneCal install for a physician sibling?
Hospital-system security teams review any third-party OAuth request against PHI risk framing. A broad calendar read/write scope on a physician mailbox is treated as a potential exfiltration path for patient identifiers that appear in appointment titles, room numbers, and MRN references. Even when the physician swears the family rotation only needs a masked Busy block, the admin-side consent screen shows the raw scope, and the ticket lands with a security analyst who has no context on the eldercare rotation. A per-user OAuth that does not require a domain-wide install avoids that queue entirely. The OneCal vs ICS working parent comparison walks through the tradeoffs on the family-plan side.
How should a three-sibling eldercare rotation handle a hospital on-call week where a sibling's availability inverts?
Treat the on-call week as a first-class calendar event on the shared eldercare calendar, not as a verbal agreement in a text thread. The physician sibling publishes a recurring on-call block that flips their default available windows to unavailable for that seven-day stretch, and the two other siblings each add a pre-committed backup block for the same week months in advance. The paid home health aide sees a shifted arrival window three days early instead of finding out at the door. Overlay Daylight Saving Time transitions on the same calendar so the 8 a.m. medication window does not silently move an hour when Sunday flips.
Can a paid home health aide on a personal Gmail be added to the same shared calendar without exposing sibling work meetings?
Only if the sync layer writes masked Busy blocks rather than copying event titles. A raw calendar share to a personal Gmail account from a Fortune 500 Outlook mailbox typically exposes free/busy plus subject lines at the cross-tenant boundary, which means the aide sees the comp discussion titles and the deal-team call titles that never should have crossed. A masked-Busy-only shared calendar shows the aide when to expect a covering sibling and when a sibling is genuinely unavailable, without exposing the underlying work meeting. See the availability calendar working parents free/busy privacy writeup for the free/busy defaults that make this safe.
When should a sandwich-generation working parent add WonderCal to the eldercare rotation?
Add WonderCal when the rotation spans two or more sibling corporate tenants, when at least one sibling is on a restricted tenant such as a hospital Microsoft 365 or a school-district Google Workspace, when a paid caregiver on personal Gmail needs to see sibling availability without seeing work meeting titles, or when the coordinating sibling has crossed roughly three hours a week of Sunday-night reconciliation on the manual ICS path. Keep whatever family-facing surface already works; fix the busy state underneath it. The working parents Outlook Google family privacy sync writeup covers the base pattern that this eldercare rotation extends.
Hold the eldercare rotation without leaking work details
WonderCal syncs masked busy blocks across sibling Google Workspace, sibling Microsoft 365, and paid caregiver Gmail accounts so a three-sibling eldercare rotation can hold under real cross-tenant pressure without copying confidential work meeting titles, patient identifiers, or student names onto the family view.
Start with WonderCal