Calendar records organisational events, their participants, times, places and connections to work.
A calendar entry here is not a colored block on a grid — it is a typed record with attendees, a venue, an outcome, and connections to the work it concerns. This manual covers the occurrence, its series, and its wiring.
What you record
The occurrence
| Field group | What it holds |
|---|---|
| Identity | Title, description, reference code |
| Classification | The event type (meeting, review, deadline, celebration — your types), status, outcome, priority level |
| Time | Start, end, all-day flag, duration, the time zone, "show as" (busy/free) |
| Buffers | Minutes before and after — the travel and prep time the calendar respects |
| People | The organizer, the attendees (a governed attendee list, not a cc line), the max attendee count |
| Place | The venue (a typed venue record) or a location text; the virtual meeting link |
| Recurrence | Whether it repeats, the series master, the recurrence description |
| Outcomes | The outcome notes, the action items count, the estimated cost |
Every timestamped happening in the organisation can be one of these — and because they are typed records, "when did we review that contract?" is a query, not an archaeology dig.
Series and recurrence
Repeating occurrences are defined once, as a series, and occur as governed instances — the weekly ops meeting, the monthly review. Check the configured handling of series changes, individual exceptions and earlier occurrences.
Reminders
Each occurrence carries reminder records — who gets reminded, when, how. The nudge is data too.
What you can do
- List, search, filter — by type, status, organizer, attendee, date range; bulk actions
- Create, update, view — the standard patterns; the validation and permissions configured for the operation
- Manage attendees — the governed attendee list, with the max-count guard
- Set recurrence — series master, instances, exceptions
- Relate — the wiring below
What it connects to
| Target | Examples of the connection |
|---|---|
| Employees | The organizer, the attendees — connected to their records |
| Venues | The room or site that hosts it (availability checked through the configured scheduling workflow) |
| Works | The work items the meeting advances or decides |
| Projects | The project the occurrence belongs to |
| Communication | The threads and meeting notes it produced |
| Categories | Your event categories, assignable through the wiring |
Where it feeds
Held events are the temporal half of the evidence: cadence readings (which routines actually run), meeting density, the time between occurrence and effect — configured evaluations draw from these records. The temporal hub story is the platform page; this manual is the working surface.
The pattern note: same four-part structure — record, do, connect, feed. The calendar manual is where the temporal pattern shows: time as records means time can be read — trajectory, cadence, clustering — rather than merely displayed.
Implementers configure your event types at adoption — the reviews, cadences, and celebrations your operation actually runs; consultants help define which event types are worth holding as records (the ones the readings need).
No record is an island
Every occurrence relates to its attendees, its venue, the work it advanced, the threads it produced. The calendar is not a personal grid here — it is the shared time the organisation runs on, held where the readings can see it.
Review the record and its context before deciding what to do next.
Works → · Venues → · All manuals → · The Calendar platform page →
Check your work
Before changing a recurring review, inspect the series and the affected occurrence. Confirm the time zone, attendees and venue, then check which future instances changed. A scheduled event is not evidence that a meeting was held or that its decisions were acted on.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.