You move your gym session from 7am to 9am. Now your post-workout smoothie at 8am is stranded — sitting two hours before the workout it is supposed to follow. Your 30-minute commute home from the gym is also wrong. And the shower you blocked at 8:45 needs to shift too.
In any calendar app you have used before, you fix each of these by hand. Click the smoothie, drag it to 10am. Click the commute, drag it. Click the shower block, drag it. Four events. Four manual adjustments. For one change.
This is what linked events solve. When events depend on each other, moving one moves the others. Automatically, correctly, without you touching each one.
No calendar app does this. UCals does.
What Linked Events Actually Are
Linked events are calendar events with a declared dependency. One event is the anchor. The others are relative to it — they happen before or after it, at a fixed offset.
The concept is simple. Your post-gym smoothie is not at 8am. It is 30 minutes after gym ends. Your meeting prep is not at 1:30pm. It is 30 minutes before your 2pm investor call. Your airport transfer is not at 10am. It is 2 hours before your 12pm flight.
When you think about these events, you already think in dependencies. The smoothie does not exist independently of the gym. The prep time does not exist independently of the meeting. They are paired.
But every calendar you have ever used forces you to pretend they are independent. Each event gets a fixed time. When the anchor moves, the dependent events stay put. You become the human sync engine, manually propagating every change across related events.
Linked events eliminate that work. You declare the relationship once. The calendar maintains it forever.
How It Works in Practice
In UCals, linking events is a conversation. You tell the calendar about the relationship, and it remembers.
Creating a linked event
“Add a protein shake 30 minutes after gym.”
That is it. The shake is now linked to the gym. It does not have a fixed time — it has a relative position. Thirty minutes after gym ends, whatever time gym ends.
Moving the anchor
“Move gym to 9.”
The gym moves to 9am. The protein shake moves to 10am (assuming a one-hour gym session). You changed one event. Two events moved. The relationship holds.
Moving a chain
Some dependencies are longer than two events. A morning routine might look like this:
- Gym at 7am (1 hour)
- Protein shake at 8am, linked to gym (15 minutes)
- Shower at 8:15am, linked to protein shake (30 minutes)
- Commute at 8:45am, linked to shower (45 minutes)
“Move gym to 10.”
All four events shift. Gym to 10am, shake to 11am, shower to 11:15am, commute to 11:45am. One sentence. Four events. Zero manual adjustments.
Linking existing events
Already have events on your calendar that should be linked? Say so.
“Link my prep time to my investor call.”
The prep time is now anchored to the investor call. Move the call, the prep follows. Cancel the call, the prep goes too.
Five Scenarios Where This Changes Everything
Linked events are not a niche feature. They show up constantly in real schedules — especially for self-employed professionals who manage complex, non-corporate days.
1. Exercise and recovery
Most people who exercise regularly have post-workout routines. A shake, a stretch, a shower, a meal. These are not independent activities. They follow the workout.
Without linked events: You move your workout. Then you remember to move the shake. Then the shower. Then you realize you forgot the meal prep block and it now overlaps with a client call.
With linked events: You move the workout. Everything downstream adjusts. The chain is maintained. You think about this zero additional times.
2. Flights and travel logistics
A flight is rarely just a flight. There is the airport transfer, the check-in buffer, the pre-flight lounge time, the post-landing Uber, the hotel check-in.
Without linked events: Your flight time changes (as flights do). You open your calendar and manually adjust the transfer, the buffer, the lounge, the Uber, and the check-in. Five events, each requiring mental math to recalculate the correct time.
With linked events: The flight time changes. Every logistical event around it shifts to maintain the correct offset. The transfer is still 2 hours before departure. The Uber is still 45 minutes after landing. You update one event. The rest follow.
3. Meeting preparation
Serious meetings require preparation. An investor call needs a pitch review. A client presentation needs a dry run. A sales call needs research time.
Without linked events: You block 30 minutes before the meeting for prep. The meeting gets rescheduled to Thursday. You forget to move the prep block. Thursday arrives and you walk into the investor call cold.
With linked events: The prep time is linked to the meeting. When the meeting moves, the prep moves with it. You never walk in unprepared because you forgot to update a calendar block.
4. Classes and commutes
If you take lessons — language classes, music lessons, tutoring sessions — there is usually a commute involved. The commute depends on the class time.
Without linked events: Your Thai lesson shifts from 6pm to 7pm. You forget to update the commute block. Your calendar now shows you “free” at 6:30pm, and you accept a call that conflicts with your travel time.
With linked events: The lesson moves. The commute moves. Your calendar accurately reflects when you are actually available.
5. Back-to-back client work
Consultants and freelancers often stack client sessions with buffer time between them. Session, break, session, break.
Without linked events: One client reschedules. You manually shuffle every subsequent session and break. For a day with four clients and three breaks, that is seven events to adjust.
With linked events: The first session moves. Every subsequent session and break cascades forward. Your day restructures itself around the change.
Why No Other Calendar Does This
This is worth explaining because it is not obvious. Linked events seem like a straightforward feature. Why has nobody built them?
Traditional calendars store events, not relationships
Google Calendar, Apple Calendar, Outlook, and every other mainstream calendar app stores events as independent records. Each event has a title, a start time, an end time, and some metadata. There is no concept of “this event depends on that event.” The data model does not support it.
Adding linked events to Google Calendar would require a fundamental change to how events are stored and synced. It is not a feature you can bolt on. It is an architectural decision.
Rule-based schedulers optimize, not link
Tools like Motion and Reclaim take a different approach. They automatically schedule tasks based on priorities, deadlines, and available time. This is useful for a different problem — finding time for things. But they do not model explicit dependencies between specific events.
You can tell Motion that a task is high priority and due Friday. You cannot tell it “this task must happen exactly 30 minutes before my 2pm meeting, and if that meeting moves, this task should move with it.” That is a relationship, not a priority.
It requires understanding intent
Linked events only work well in a conversational interface. The calendar needs to understand what you mean by “add a shake after gym” — specifically, that “after gym” means a time-relative dependency, not a suggestion about ordering.
Traditional calendar UIs (forms, drag-and-drop, context menus) have no natural way to express dependencies. Where would you click to say “this event follows that event”? You would need a complex UI for relationship management — which adds friction to an app designed around simplicity.
A conversational interface makes this natural. “Link my prep time to my investor call” is a clear instruction. The AI parses the intent, creates the dependency, and maintains it. No new UI elements needed.
UCals was built for this
UCals models events with relationships from the ground up. The data structure supports dependencies natively. The conversational interface makes creating and managing links natural. And the AI engine propagates changes through the dependency chain automatically.
This is not a feature that was added later. It is part of how the calendar thinks about time.
How to Set Up Linked Events
If you are using UCals, linked events work through conversation. There is no settings page or configuration screen. You talk to your calendar.
Method 1: Create a linked event from scratch
Tell the calendar what the new event is and what it depends on.
“Add 30 minutes of prep before my investor call on Thursday.”
The calendar creates a prep block that ends when the investor call starts. If the investor call is at 2pm, prep is at 1:30pm. Move the call to 3pm, prep moves to 2:30pm.
“Add travel time after my last meeting on Friday.”
The calendar calculates travel time from the meeting location to your next destination (or home) and links it to the meeting.
Method 2: Link existing events
Already have both events on your calendar? Declare the relationship.
“Link my warm-up to my gym session.”
“My airport transfer depends on my flight.”
“Tie the client debrief to the client meeting.”
Each of these creates a dependency. The second event’s time is now relative to the first.
Method 3: Create a chain
Build a multi-event sequence in one instruction.
“After my morning run: stretch for 15 minutes, then shower for 20 minutes, then breakfast for 30 minutes.”
Four events. Three links. One sentence. Move the run, and the entire morning cascade shifts.
Modifying links
Change your mind about a dependency? Say so.
“Unlink the shake from gym.”
The shake becomes an independent event at its current time. Moving the gym no longer affects it.
“Change the prep time to 45 minutes before the call instead of 30.”
The offset updates. The relationship persists.
What Linked Events Do Not Do
It is worth being clear about the boundaries.
Linked events do not auto-create dependencies. The calendar does not guess that your shake depends on your gym. You tell it. This is intentional — false dependencies would be worse than no dependencies.
Linked events do not resolve conflicts for you. If moving a chain of events creates an overlap with something else on your calendar, the calendar shows you the conflict. It does not silently rearrange unrelated events to make room. You decide how to resolve it.
Linked events are not task scheduling. They do not find the best time for something. They maintain relative timing between specific events. If you need the calendar to find an open slot, that is a different feature. Linked events are about preserving relationships, not optimizing placement.
The Larger Point
Calendars have been static for decades. You place events on a grid. When something changes, you manually update every affected event. The calendar has no understanding of why events are where they are or how they relate to each other.
Linked events are a step toward a calendar that understands structure — not just times and titles, but relationships and dependencies. A calendar that knows your prep time exists because of your meeting, and your transfer exists because of your flight.
This is a small but meaningful shift. It moves the calendar from being a display of your schedule to being a model of your schedule. Displays show you what is there. Models understand why it is there, and what should happen when something changes.
UCals is $15 a month. $10 a month billed annually. 14-day free trial, no credit card required. macOS.
Frequently Asked Questions
What are linked calendar events?
Linked events are calendar events with a declared dependency. One event is the anchor, and the others maintain a fixed time offset relative to it. When the anchor moves, all linked events move with it automatically. For example, if your protein shake is linked to your gym session (30 minutes after), moving the gym from 7am to 9am automatically moves the shake from 8am to 10am.
How do I create linked events in UCals?
Through conversation. Say something like 'add 30 minutes of prep before my investor call' or 'link my warm-up to my gym session.' The calendar creates and maintains the dependency. You can also build chains: 'after my run: stretch 15 minutes, then shower 20 minutes, then breakfast 30 minutes.' No forms, no settings pages -- just tell the calendar what depends on what.
Can I link events that already exist on my calendar?
Yes. If you already have both events on your calendar, tell the AI about the relationship: 'link my prep time to my investor call' or 'my airport transfer depends on my flight.' The calendar creates the dependency and maintains it going forward. You can also unlink events at any time by saying 'unlink the shake from gym.'
Does Google Calendar support linked events?
No. Google Calendar, Apple Calendar, Outlook, and other mainstream calendar apps store events as independent records with no concept of inter-event dependencies. Adding linked events would require a fundamental change to their data model. This is one of the features that only works in a calendar built around AI conversation from the ground up.
What happens if linked events create a conflict?
UCals shows you the conflict. If moving a chain of linked events causes an overlap with another event on your calendar, the calendar flags it. It does not silently rearrange unrelated events. You decide how to resolve the conflict, either by adjusting the anchor event or moving the conflicting event.
Is there a limit to how many events I can link together?
No fixed limit. You can create chains of any practical length -- a four-event morning routine, a six-event travel day, or any sequence that reflects how your day actually works. Each event in the chain maintains its offset relative to the one before it, so the entire sequence shifts when the first event moves.
UCals team
Building the AI calendar assistant for your entire life. Bootstrapped, profitable, and shipping fast.
Want to see how UCals handles other calendar tasks through conversation? Read our guide on natural language calendar management or see how UCals compares to Motion and Reclaim.