Practical guide

All-Day Calendar Events: Show a Date Without Blocking Busy Time

An all-day date and a busy-time block are separate choices. TRANSPARENT keeps an event out of busy-time searches; OPAQUE is the default. Choose availability according to whether the event consumes your time, then verify the result in your actual calendar.

Calendar users checking event rules and practical date choices · 5 minute read · Published

All-day does not mean free

An all-day event uses a DATE-valued start instead of a clock time. Its transparency property answers a different question: should this event consume availability in busy-time searches? RFC 5545 defines TRANSPARENT for events that do not consume time and OPAQUE for events that do; OPAQUE is the default when the property is absent. [1]

An informational anniversary can remain visible without blocking your day. A real day away from work can use the same date representation and intentionally block availability. The title “holiday” does not decide which situation applies to you; the actual organization schedule and your absence do.

Decide what the entry is for

A date to remember

An informational birthday, observance or reminder can be transparent if it does not consume your time.

A day you are unavailable

An actual absence can be opaque when it should be detected as busy.

A general public-holiday calendar is not automatically a personal absence calendar. An office may remain open, use a different observed date or close only partly. Decide which calendar records facts and which represents your availability before copying an entire holiday list.

Transparency also does not decide whether someone may read the event, edit it or see its title. Those access questions require the calendar’s sharing and privacy controls. TRANSPARENT is a busy-search property, not a permission to publish event details.

Compare the same one-day interval

On a narrow screen, swipe within the table to read the remaining columns.

Original fictional date: 15 January 2027; exclusive end 16 January
PropertyInformational reminderActual unavailability
DTSTARTVALUE=DATE:20270115VALUE=DATE:20270115
DTENDVALUE=DATE:20270116VALUE=DATE:20270116
TRANSPTRANSPARENTOPAQUE
Meaning under RFC 5545Does not block busy-time searchBlocks busy-time search

Both files describe January 15 only. DATE-valued DTEND is exclusive, so January 16 is not part of the interval. A shifted date and an unexpected busy block have different likely fields to inspect: DTSTART/DTEND for dates, TRANSP and actual application availability controls for busy status. [2]

Inspect two complete practice files

These are fictional alternatives for one date, not two simultaneous events. There are no attendees, organizer, invitations or alarms. Choose one for an isolated test; importing both defeats the comparison by creating two separate example events.

Download practice informational all day (.ics)

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:1e436b9d985b1a500d03d6f0@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270115
DTEND;VALUE=DATE:20270116
SUMMARY:Practice - Informational date
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR

Download practice unavailable all day (.ics)

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:19608d27f91001c6ff6d5ded@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270115
DTEND;VALUE=DATE:20270116
SUMMARY:Practice - Actual absence example
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

Check the app’s result without exposing a calendar

First save an original export and inspect the selected event. Note its actual calendar, DATE start/end and explicit or absent TRANSP. Use a test calendar and the service’s supported availability view to compare the intended day. Do not publish a calendar or invite other people simply to test the property.

The standard describes busy-search semantics; an app may apply its own import mapping, default availability setting or calendar-level behavior. These specimens were structurally checked, but no client availability search was executed here. If the result differs, re-export the event if possible and compare the property with the supported editor setting.

Check that you are seeing the intended calendar rather than a second holiday or absence entry overlaid on it. A transparent reminder can coexist with an unrelated opaque absence on the same date. That overlap is not evidence that the reminder’s property was ignored.

Two complete decisions

I add a birthday reminder but remain available that day. Must it block the day?

No. A transparent informational event expresses that intent under RFC 5545.

Keep the DATE interval and set TRANSP:TRANSPARENT in the event representation or use the app’s corresponding supported availability choice. Then verify the real result. This does not change who can access the event’s details.

The source says Christmas is a holiday, but our office opens normally. Should copying it mark me busy?

Decide from your actual availability, not only the holiday’s name.

Keep an informational holiday date separate from a confirmed absence. If you are available, a transparent fact entry may fit; if you are actually away, an opaque absence can fit. Confirm the organization’s observed date and hours independently.

Keep date, availability and privacy as separate checks

Write three results: which dates the entry covers, whether it should consume busy time, and who may access it. Check each in the actual service. For a one-day shift, follow the all-day date guide; for apparent duplicate calendars, follow the import guide. A correct transparency property does not repair a wrong date or a duplicate import.

Sources and further reading

  1. RFC 5545 §3.8.2.7 — Time transparencyTRANSPARENT versus OPAQUE and the opaque default.
  2. RFC 5545 §3.6.1 — VEVENTDATE intervals, exclusive DTEND and informational versus busy events.