For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Create an event linked to the right record and verify its timing, timezone and recurrence before others rely on it.
Before you start
Identify the parent project, policy or other record the event belongs to. Agree the event purpose and time with the relevant people. Check that calendar functionality is available for your organisation and that you have permission to create the event.
The creation form requires a parent context. A personal overview calendar is not a reason to create an event with an arbitrary business association.
Create the event
- Open the intended record's calendar or contextual event-creation action.
- In Create New Event, enter a clear title and the supporting description needed to understand the purpose.
- Set the start and end dates and times. Check whether the all-day option is appropriate.
- Review the Timezone explicitly. Do not assume the default matches your office or the meeting participants.
- If the event repeats, enable recurrence and select the offered repeat pattern. Review the resulting intention carefully before saving.
- Confirm the parent record and any other required fields, then choose Create Event.
- Open the saved event and check the date, time, timezone, recurrence and association.
An event record is not, on its own, proof that an external calendar invitation or conferencing link has been sent. Verify any separate communication your team requires.
Change an event
Open the event and its edit control. Review the existing values before changing the title or timing, then save and reopen the result.
For repeating events, inspect the scope of the offered change before proceeding. Do not assume an edit applies only to one occurrence, or to every occurrence, unless the current control states that. If scope is unclear, ask the event owner before changing it.
Check it worked
The event appears in the intended calendar at the expected local time and opens the correct parent context. Verify a date near a timezone or daylight-saving boundary particularly carefully.
If people need notice of a change, confirm that separately. A saved edit does not prove everyone has seen the new arrangement.
If something goes wrong
| Problem | Next action |
|---|---|
| End time is rejected | Check date order, all-day state and timezone |
| Event appears on the wrong day | Compare saved timezone and displayed local time |
| Creation lacks parent context | Return to the owning record and start there |
| Recurrence scope is unclear | Stop before changing the series and seek clarification |
Human judgement matters
Calendars coordinate work but do not establish attendance, completed reviews or approval. Record those outcomes through their proper workflows.
What next?
For the wider context, see Use collaboration and personal tools. Use the event's supported meeting-intelligence workflow if an authorised transcript and reviewed outputs are needed.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message. Never share passwords, session details or confidential evidence in an open support request.