Write one calendar description that survives every invite

Calendar descriptions do not share one rich-text contract

Google Calendar's Events API says an event description can contain HTML. Microsoft Graph event bodies can be HTML or text. The interoperable iCalendar standard represents DESCRIPTION as text. A description that looks correct in its source calendar can therefore arrive with raw tags, changed spacing or a flattened agenda elsewhere.

For an invite that crosses organisations and calendar clients, clean plain text is the dependable baseline. Keep section labels, short bullets, paragraph breaks and full link destinations.

Google Calendar Events API · Microsoft Graph: create an event · RFC 5545 iCalendar

Use a description, not a miniature document

An event description should answer what the meeting is for, what needs preparation and where the working material lives. Large headings, complex tables and deep nested lists add fragility without making the invite easier to act on.

Convert headings into compact labels. Flatten a small table into one labelled line per row. Write links out explicitly so the destination survives a plain-text calendar or forwarded invitation.

• Purpose
• Agenda
• Preparation
• Owner
• Working links

Pasteful does not access the calendar

The calendar workflow only formats the description in the browser and copies it. It does not read calendars, create events, invite attendees or send text to a server.

Paste the result into a test event and inspect the invitation in a second client when the meeting is important. Cross-client behaviour can change, and an actual invite remains the most reliable final check.

Open meeting notes to calendar description