Skip to content
Kaarne Superstore⌕
AI & Digital Tools

A Changed Appointment Needs One Authoritative Calendar Entry

A practical way to review a changed appointment: update the original record, check its resource dependencies and inspect the notification route.

Collage of a coordinator moving one calendar entry from its former position.

The site visit has moved to Thursday. One colleague sees the old Tuesday invitation, another has a new Thursday entry, and the coordinator has both. The change needs a clear record to point back to.

Decide what represents the appointment

In this illustrative field-service example, a coordinator receives a request to move a visit. Before creating a second calendar entry, find the existing appointment and check who may manage it. The aim is to revise the appointment the team already recognises. A separate reminder may be useful, but it should not masquerade as another version of the booking.

Separate the changed time from the changed commitment

Check the time, location, participants and practical dependencies. A Thursday slot with a different technician may require a different vehicle or room. Write the reason for the change where the team expects to find it, using only necessary working information. The revised entry should tell a colleague what they are expected to do, without requiring them to reconstruct an email exchange.

Inspect the notification route

EGroupware’s calendar documentation describes email notification of appointment changes and permissions for colleagues to view or manage calendars. Confirm the behaviour in your configured environment with a colleague before relying on it. A notification being sent does not establish that a recipient has read it or agreed to the new arrangement. Use your normal confirmation process when the commitment requires an explicit response.

Finish with a two-person check

Ask the colleague to open the appointment through their usual route and state the expected date, place and responsibility. Check any connected resource reservation separately. If an obsolete duplicate already exists, resolve it using the team’s agreed calendar process; do not leave both entries looking equally active. The observable finish is a shared understanding of one appointment, not merely a successful edit.

Evaluate the hosted package in context

See the EGroupware guidance for this team situation and the eCloud product overview. The checked base offer includes two concurrent users and 20 GB. Synchronising users consume concurrent access; optional services and extra capacity require separate selection.

Check the current EGroupware eCloud offer. Affiliate disclosure: we may earn a commission if you purchase through this link.

Continue with Two Concurrent Users: Plan Access Before You Connect Every Phone for a related decision.

Sources and scope

This guidance uses public vendor documentation checked on 18 November 2026. It is not a hands-on review of a configured customer installation.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.