Calendar Events: time connected to the work

Record meetings, reviews, deadlines, and other occurrences with the people, work, projects, and venues they concern.

Record meetings, reviews, deadlines, and other occurrences with the people, work, projects, and venues they concern.

Calendar Events is HEPO's shared module for dated occurrences such as meetings, reviews, deadlines, milestones, and celebrations. An event has a type and context: the people involved, the work it concerns, the project it serves, and the place where it happens.

Teams use those records to organise activity and find the context of an earlier occurrence. The same records can contribute to configured process or cultural analysis where their meaning and use are appropriate.

Find the review behind a decision

A project owner asks when a contract was reviewed. A connected event can lead to its participants, the relevant work, the venue, and the meeting notes or communication associated with it. The reviewer follows the recorded connections instead of relying on the calendar title alone.

An invitation describes intended participation. Attendance and a documented decision supply different information. The event record should not silently turn one into another.

What an event connects

Context Why it matters
Type and timing Distinguish a review, deadline, meeting, or recurring practice
People Identify the participants relevant to the occurrence
Work and project Find the effort the event concerns and any recorded follow-up
Communication Read the notes, discussion, or decision linked to the event
Venue Identify the physical or virtual place

The shared event model helps several modules refer to the same occurrence. It does not imply automatic capture of every conversation or synchronisation with every external calendar. Implementation establishes the scheduling connections the organisation needs.

Use time with a defined question

A process owner may examine review cadence or the interval between a meeting and the next recorded action. A P&C practitioner may consider participation in an agreed practice. Such readings depend on relevant timestamps, complete enough records, and clear definitions.

Calendar events are one source of time context. Work transitions and process execution also have their own timestamps. Process Evidence explains how those sources contribute to a reading.

Configure the organisation's actual routines

The organisation names the event types and relationships that matter. Implementers connect scheduling and configure the supported event surfaces. Start with a recurring review: create the event, relate its work and participants, record the follow-up, and check what a later reviewer can find.

Presence records working styles and attendance; HR Time Management defines schedules and time rules; Venues provides the place reference. Together they give an occurrence its working context.

Operational Core | Platform overview