Calendar-date events versus cycle-day events
Learn when to use a fixed calendar date and when to use a cycle-day event in a cycle-aware planning calendar.
Use a calendar date for a fixed day; use a cycle day for a relative day
A calendar-date event belongs to a real date such as August 20. A cycle-day event belongs to a relative day such as cycle day 15, so its displayed date follows the current planning estimate. Umorrow puts both on one calendar while keeping their meanings distinct.
Actual Umorrow workflow
- Open the event form from the Umorrow calendar.
- Choose Calendar date when the commitment has a fixed real-world date.
- Choose Cycle day when the plan should follow a relative day in the recorded cycle.
- Add the time and reminder behavior, then save.
- Review the event in the same calendar and timeline as other plans.
What changes when the cycle changes?
A fixed-date event stays on its chosen calendar date. A cycle-day event is resolved from the recorded cycle start and the selected cycle day. When a later cycle is recorded, future cycle-relative planning follows that newer context.
This is useful when the meaning of the plan is relative rather than monthly. It is not the same as repeating on the fifteenth day of every month.
A simple decision rule
If another person, booking, ticket, deadline, or reservation names a date, use a calendar-date event. If the plan only makes sense as “day 8 of the current cycle,” use a cycle-day event. If both matter, keep the fixed commitment on its date and use cycle-day context to review the calendar.
Why Umorrow shows both
Ordinary calendars understand dates, but they do not usually represent a personal cycle day as its own planning coordinate. Traditional trackers show cycle days, but often center health logs rather than ordinary events. Umorrow combines the two planning views without treating an event as a symptom entry.
Plan calendar dates and cycle days in Umorrow
Available for iPhone and Android. You can start locally without creating an account.