Plan and maintain the site calendar as a team

Add the missing context

“Meeting Tuesday at 9” does not identify the site, people or meeting point. The calendar supports title, start, end, location, description, project and employees. Prepare distinctive names and permissions: read-only access can view appointments without changing them. See projects and team access.

Create a complete appointment

Use a precise title, dates and times, meeting point, project, participants and any preparation required. Add a reminder where useful. Save and reopen to verify. Unsaved form changes are not a confirmed appointment, especially after an urgent change.

Choose the useful view

Use month for the wider picture, week for the next days and list to read entries in sequence. Search and project, employee or type filters avoid maintaining separate lists.

The office checks dates and participants, site management adds location and preparation, and the team consults the current state. Creating a calendar does not automatically establish this responsibility.

Review recurring events and ICS imports

Set repetition, interval and end date. Editing a recurring appointment affects the entire series, so check several occurrences afterwards.

ICS provides a preview. Check titles and times, then confirm the selected entries. This is a file import, not ongoing synchronisation with an external calendar. Later changes in the external source require separate handling.

Planned does not mean completed

Record actual work in time tracking. A construction question can belong in chat, but if it creates an appointment, add that appointment explicitly.

The public calendar demo uses example data without registration and loses edits on reload. It does not modify a real company calendar. For business work, create an account with a 14-day app trial or request an introduction.