Your flight just got delayed two hours. You know what comes next. Not the flight itself — that part is out of your hands. The cascade. The airport pickup that now arrives too early. The hotel check-in window you will miss. The dinner reservation that made sense at 7pm but makes no sense at 9pm. You open four apps, send three messages, and spend twenty minutes rebooking things that should have moved on their own.
Linked calendar events solve this. When one event moves, every event connected to it moves with it. No manual rebooking. No chain of corrections. One change, and the rest follow.
No consumer calendar app has this. UCals does.
The Cascade Problem
Every scheduling chain has a dependency structure. Events do not exist in isolation — they depend on each other. But every calendar app treats them as if they do. Each event is an island. Move one, and the others sit there, wrong, waiting for you to fix them by hand.
Here is what the cascade problem looks like in practice.
The travel chain
You have a trip to Bangkok next Thursday. Your calendar looks like this:
- 2:00p — Flight BKK, Terminal 2
- 5:30p — Airport pickup, Arrivals gate 4
- 7:00p — Hotel check-in, Sukhumvit Soi 11
- 8:30p — Dinner reservation, Gaggan Anand
The airline pushes your flight to 4:00p. In Google Calendar, you update the flight. Then you open the pickup event. Change it to 7:30p. Open the hotel check-in. Change it to 9:00p. Open the dinner. Cancel it — 10:30p is too late. Four events. Four rounds of click, edit, save.
And that is assuming you remember all of them. Most people fix the flight and forget the pickup until they are standing at arrivals wondering where the car is.
The work chain
Your Wednesday has a common pattern:
- 1:00p — Prep slides for client presentation
- 2:00p — Client presentation, Zoom
- 3:00p — Follow-up notes and action items
The client asks to move the meeting to 3:30p. You update the meeting. But now your prep block is too early — ninety minutes of dead space between prep and presentation. And the follow-up block overlaps with your 4pm. Three events to fix because one moved.
The family chain
Thursday afternoon:
- 3:15p — School pickup
- 3:45p — Soccer practice dropoff
- 5:00p — Pick up from soccer
- 5:30p — Start dinner
Soccer practice gets pushed to 4:30p. Now the dropoff time is wrong, the pickup time is wrong, and dinner prep starts too early. Four events, all connected, all wrong.
These are not edge cases. This is how real schedules work. Events depend on other events. Calendars pretend they do not.
What Linked Calendar Events Actually Do
Linked events create explicit dependencies between calendar entries. When the anchor event moves, every event in the chain adjusts automatically.
In UCals, you set up links through conversation:
“Link my airport pickup to my flight.”
Done. Now when the flight moves, the pickup moves with it — same offset, same relationship. You told the calendar once. It remembers forever.
The system preserves the time relationship between events. If your pickup was scheduled for 30 minutes after landing, it stays 30 minutes after landing regardless of when the flight actually arrives. If your hotel check-in was 90 minutes after the pickup, that gap is maintained.
One change. Four updates.
Here is the Bangkok trip again, with linked events:
Your flight moves from 2:00p to 4:00p. You update one event. UCals cascades the change:
- 4:00p — Flight BKK (updated)
- 7:30p — Airport pickup (auto-adjusted, +2 hours)
- 9:00p — Hotel check-in (auto-adjusted, +2 hours)
- 10:30p — Dinner reservation (auto-adjusted, +2 hours)
Four events updated. One action. Zero forgotten pickups.
You can review every cascaded change before it sticks. UCals shows you the before-and-after for each linked event, and you can say “undo” to reverse the entire chain.
Who Needs This (and Why Nobody Has Built It)
The Google Calendar community forums have threads requesting linked events going back years. The feature does not exist in Google Calendar, Apple Calendar, Outlook, Fantastical, or any consumer calendar app.
The only product that addresses event dependencies is DayBack Calendar, a Salesforce and FileMaker add-on built for enterprise resource scheduling. It costs $39 per user per month and requires a Salesforce or FileMaker installation. It is not a personal calendar.
UCals is the first consumer calendar with linked events. Here is who benefits most.
Travelers
Every trip is a chain. Flight, transfer, accommodation, activities. One delay breaks all of them. If you travel more than a few times a year, linked events save you the rebooking scramble every time an airline changes your schedule. UCals also calculates travel time between events using Mapbox, so your buffer blocks adjust with the chain.
Freelancers and consultants
Client meetings come with prep and follow-up. When the meeting moves, the prep block and follow-up should move with it. Without linked events, you reschedule three events every time a client asks “can we do 30 minutes later?”
Parents
School schedules, activities, and meals form tight chains. One change — practice moved, school out early — cascades through the afternoon. Linked events keep the chain intact without you manually recalculating every slot.
Event organizers
Setup, event, teardown. A three-event chain where the middle event dictates everything. If the venue becomes available an hour later, linked events shift setup and teardown automatically.
How to Set Up Linked Events in UCals
You create links through natural conversation. No configuration screens. No drag-and-drop dependency builders.
Link two events:
“Link my airport pickup to my Bangkok flight.”
Link a chain:
“Link prep time, client meeting, and follow-up notes together.”
Link with a specific offset:
“Add a 30-minute buffer between my flight landing and the airport pickup.”
Break a link:
“Unlink dinner from the hotel check-in.”
Links work with per-day recurring events too. If your Monday workout has a linked smoothie run afterward, moving Monday’s workout moves Monday’s smoothie run — without affecting Wednesday’s workout chain.
Before and After: A Real Travel Day
Without linked events (Google Calendar)
Your Tuesday looks like this:
| Time | Event |
|---|---|
| 10:00a | Flight to Lisbon, $340 |
| 2:30p | Airport taxi, $25 |
| 3:15p | Hotel check-in, Alfama |
| 5:00p | Walking tour, Bairro Alto |
| 8:00p | Dinner, Belcanto, $85 |
The airline emails: flight delayed to 12:00p. Here is what you do:
- Open flight event. Change to 12:00p. Save.
- Open taxi event. Calculate new arrival time. Change to 4:30p. Save.
- Open hotel event. Change to 5:15p. Save.
- Open walking tour. Realize it conflicts with the new hotel check-in. Reschedule or cancel.
- Open dinner. Check if 8:00p still works with the compressed afternoon. Decide to keep it.
- Worry that you missed something.
Elapsed time: 8-10 minutes. Steps: 12+. Anxiety: moderate.
With linked events (UCals)
Same flight delay. You say:
“Flight moved to 12pm.”
UCals updates the flight and cascades:
- Taxi shifts to 4:30p
- Hotel check-in shifts to 5:15p
- Walking tour shifts to 7:00p (or flags the conflict)
- Dinner at 8:00p flagged as tight
You review the changes. Say “looks good” or adjust the dinner. Done.
Elapsed time: 15 seconds. Steps: 1. Anxiety: none.
Why Other Calendar Apps Do Not Have This
Building linked events requires a fundamentally different data model. Traditional calendar apps store events as independent objects — a title, a time, a date. There is no concept of relationships between events.
Adding linked events to Google Calendar would mean redesigning the event data structure, the sync protocol, the mobile and web clients, and the interaction model. For a free product serving two billion users, that is a massive engineering investment for a feature most users do not know they want until they experience it.
UCals was built with event relationships as a core concept, not a bolt-on. The AI assistant understands dependencies natively — when you say “link these events,” it does not just store a pointer between two database entries. It understands the temporal relationship and maintains it across changes.
This is the advantage of building a calendar from scratch in 2026 instead of iterating on a product from 2006.
Frequently Asked Questions
What are linked calendar events?
Linked calendar events are events with explicit dependencies -- when one event's time changes, all connected events adjust automatically. For example, if your flight is linked to your airport pickup and hotel check-in, delaying the flight by two hours shifts the pickup and check-in by two hours as well. UCals is the first consumer calendar app with linked events.
How do linked events differ from recurring events?
Recurring events repeat on a schedule (daily, weekly, monthly). Linked events are connected to each other by time relationships -- they may or may not recur. A flight, airport transfer, and hotel check-in are linked events that happen once. A weekly workout followed by a linked smoothie run is both recurring and linked. The two features solve different problems and work together in UCals.
Can I cascade calendar changes automatically?
Yes, in UCals. When you link events together, changing the time of one event cascades the change to all connected events automatically. You update the anchor event, and UCals adjusts every downstream event while preserving the time gaps between them. You can review all cascaded changes before confirming, and undo the entire chain with one command.
Does Google Calendar support linked events?
No. Google Calendar does not support linked or dependent events. Each event is independent -- moving one event has no effect on any other event. Users have requested this feature in Google's community forums for years, but it has not been implemented. UCals is the first consumer calendar to offer linked events with automatic cascading.
What calendar apps support events that move together?
As of 2026, UCals is the only consumer calendar app with linked events that cascade changes automatically. DayBack Calendar offers event dependencies, but it is an enterprise add-on for Salesforce and FileMaker starting at $39 per user per month. No other personal calendar -- Google Calendar, Apple Calendar, Outlook, Fantastical, or Motion -- supports events that move together.
UCals team
Building the AI calendar assistant for your entire life. Bootstrapped, profitable, and shipping fast.
Move your flight. Everything else adjusts. Try UCals free for 14 days — no credit card required. $15/month after that.
Learn more about how UCals handles travel time between events and per-day recurring events.