TEAM SCHEDULING
Give a meeting its own place in the work.
Create a timed or all-day team event with participants, location, notes and optional customer or project context.
A calendar block rarely explains the whole meeting
A useful meeting record tells the team why it is happening, who is involved and which work it concerns. Tsumira’s internal event is a business record as well as a time on the calendar. It can carry a title, timing, participants, place, notes and optional customer or project reference. Those details remain available when somebody needs to prepare, follow up or understand a cancellation.
Choose a real time or an all-day period
Timed events have a start and end instant, while all-day events use dates. The event keeps a timezone context rather than relying on the server’s local clock. Decide which representation fits the activity: a discussion at a particular hour is different from an all-day planning period. Check the end as well as the beginning and use a title that explains the meeting’s purpose to the people seeing it.
- Timed and all-day events
- Start and end information
- Event timezone context
Bring the business context into the event
A location, notes and optional customer or project reference make the meeting more than a label on a grid. The connected records are resolved under the current person’s access rather than becoming a universal shortcut into private information. Use the notes to prepare the discussion, and link the relevant work where available. Participants can then see the event’s own context without copying the entire customer record into the meeting description.
- Place and preparation notes
- Optional customer and project references
- Access-aware connected records
Review the current proposal and collect open questions.
Cancel explicitly instead of silently deleting
The supported lifecycle distinguishes scheduled and cancelled. A meeting that people have been told about is cancelled through its reviewed command, not quietly removed as if it never existed. The event remains a record with its conversation, and participant notifications can communicate the change. When editing a current event, the implementation checks its version so concurrent changes are not mistaken for a fresh update to the same state.
- Scheduled and cancelled states
- Preserved record and conversation
- Participant notifications and version checks
A concrete workflow
Define the meeting
Choose a meaningful title, timed or all-day period and the relevant place or notes.
Choose the participants
Add the appropriate active team members, remembering that the organizer also participates.
Connect and review
Link visible customer or project context where helpful and check the creation before applying it.
Keep the event current
Review changes and use explicit cancellation when the meeting will no longer take place.
An illustrative working example
Illustrative workflow: a customer-project planning meeting
A project manager creates an internal planning event for the delivery team. The event links the accessible project and customer, includes the meeting room and a short agenda, and names the participating colleagues. If the discussion must be cancelled, the manager uses the cancellation flow. The event history and conversation remain understandable rather than disappearing from the record of the project.
Questions about this topic
Can I create an all-day event?
Yes. The event model distinguishes all-day dates from timed start and end instants. Select the form that matches the planned work.
Does a customer link invite the customer externally?
The internal event uses team memberships as participants. A customer reference supplies context; do not interpret that reference as a general external invitation.
Can a cancelled meeting disappear without a record?
The implemented lifecycle uses cancellation rather than deletion. The event and its conversation remain available under their access rules.
Does a project reference give participants access to the entire project?
No blanket access is implied. Related customer and project information is resolved with the current person’s permissions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Calendar
Workflow concept: Compare an internal meeting’s title and actual start/end before scheduling.
Outlook
Workflow concept: Review the intended internal appointment before creating the event record.
Zoom
Workflow concept: Keep a reviewed external meeting entrance in the event’s preparation context.