Repeating events use a date rule, not a position in the printed grid. Choose Weekly, Monthly or Yearly, then review the dates that rule produces in the range you need. Dates that do not exist are skipped rather than moved.
Choose the repeat rule
Open the event and select a repeat option. Weekly returns on the chosen weekday. Monthly returns on the chosen day of the month. Yearly returns on the chosen month and day. Keep the original start date and any end-of-repetition date clear so the preview has a defined range.
A visible time label remains text on each occurrence. It does not add a time zone, a reminder or a timed appointment. If the event spans several days, review how the repeated spans appear as well as the starting dates. Repetition should not hide an overlap that matters to your plan.
Understand months without the chosen date
A monthly event on day 31 skips months that have fewer days. For an event beginning January 31, 2027 and ending its repetition on June 30, the starting dates are January 31, March 31 and May 31. February, April and June are skipped.
This rule does not mean “the last day of each month.” It does not move an occurrence to February 28 or April 30. If you need those particular dates, enter the actual dates or a suitable set of separate events. Read the next-dates preview before saving so you can catch a rule that differs from your intention.
Understand a yearly February 29 event
A yearly event on February 29 appears in a leap year that contains that date. It is skipped in a non-leap year. A birthday calendar can preserve February 29 in its yearless layout, while a dated 2027 calendar cannot place that date in the grid.
If you want to mark a separate celebration on February 28 or March 1, add that chosen date explicitly. Keeping the original anniversary rule and the particular celebration separate prevents the calendar from silently changing a date that may matter to you.
Review several occurrences
Check more than the first date in the list. Include a month boundary, a shorter month and, for yearly events, a leap-year boundary when relevant. Changing the week start only rearranges the grid; it should not change the dates generated by the repeat rule.
When editing a repeating event, review the title, first date, rule and end range together. A change can affect many visible occurrences. Save a JSON project backup before a substantial revision if you may need the previous rule later. Do not rely on an old PDF as the editable record.
Check the selected export range
Before downloading ICS, review which occurrences belong to the selected date range. An empty month can be the correct result of a skip rule. Event CSV retains the source event records and their repeat rules; it is not the same list as the expanded ICS occurrences. A calendar-app import is a file transfer, not a live connection to the MonthSprig project.
After importing an ICS file elsewhere, check a few expected dates and the final included day of any spanning occurrence. The receiving app controls its import and display behavior. Keep the original MonthSprig project so you can change the rule and produce a new file when needed.