A spanning event includes both the start date and the final date shown in the editor. Its complete range stays with the event even when the current calendar shows only one part of it.
Enter the first and final included dates
Add or edit an event and select its start date. Set the end date to the last day the event should occupy. For a trip covering March 24, March 25 and March 26, use 2027-03-24 and 2027-03-26. Do not enter March 27 just to make the range appear to include March 26.
The final date must not be earlier than the start, and both dates must be valid. If a field is invalid, correct it before saving. The form should explain the problem while preserving the value you entered, so you can see whether the mistake came from the date, year or ordering.
Read continuations across rows and months
A long event can cross the end of a calendar row. It can also begin in one month and end in another. Review the dates on both sides of the boundary. The change in visual position should not create a gap in the underlying event or change its final included day.
For a March 29–April 2 trip, open March and April when checking the whole event. A March page cannot show all of April’s dates inside its grid. Keep the event’s full range rather than shortening it to fit the current page; use the neighboring page or range to see the rest.
Keep overlapping plans separate
If another event happens during the span, add it as a separate event with its own date. For example, a review on March 30 can remain distinct from a March 29–31 trip. Use clear labels and inspect the date box where they overlap.
The calendar is a planning display, not a conflict-resolution service. It does not decide whether two plans can happen together. When several labels share a day, change the layout or amount of detail so the printed result remains readable without hiding the original dates.
Understand the exported ICS boundary
The editor’s end date is inclusive. ICS uses an exclusive end date: the first day after the event. A March 29–31 event therefore uses DTSTART;VALUE=DATE:20270329 and DTEND;VALUE=DATE:20270401. April 1 marks the end boundary and is not a fourth included day.
Use the ordinary inclusive dates in the editor and let the exporter handle the file convention. After importing the ICS file into another app, inspect the first and last included dates. If you read the file directly, remember the exclusive rule before concluding that the event was extended.
Check spanning events in the final output
Review the first date, a middle date and the final date in the preview. For multi-page calendars, move through every page touched by the event. Check the title, continuation treatment and any notes included in the output. An event should remain understandable even if a reader sees only one printed page.
Keep a JSON project backup before revising a large set of spans. An older PDF or image is a snapshot and will not reflect the changed range. Download a fresh output after editing, and compare the affected boundaries before replacing the previous printout.