Inbox course 03 — Manage follow-up and calendar commitments
Mail often starts work that continues elsewhere: a review to track, a missing document to obtain or an appointment to arrange. Inbox's attention flags and Calendar help organise that work, but they do not replace a clear owner or a checked result. This chapter connects the message to an accountable next action and explains how to read calendar planning without confusing it with a live meeting.
Part of Inbox module course
Owned follow-up appointment planning and recovery
Mail often starts work that continues elsewhere: a review to track, a missing document to obtain or an appointment to arrange. Inbox's attention flags and Calendar help organise that work, but they do not replace a clear owner or a checked result. This chapter connects the message to an accountable next action and explains how to read calendar planning without confusing it with a live meeting.
In this chapter
- Identify what has actually been agreed
- Create or update the correct work record
- Read Calendar as an appointment plan
- Prepare the interval and audience before saving
- Reconcile changes and cancellations without duplicates
- Recover uncertain work at the right level
- Complete the Inbox workflow
Identify what has actually been agreed
A requester asks for an output. A reviewer examines it. An action owner is accountable for a next step. “Could you review this?” is a request; “I will review version C by noon UTC on Friday” accepts that bounded review. It does not also accept responsibility for making revisions.
Keep the exact material version, output and timing together. A reply about version A is not automatically approval of B. A promise to review later is not evidence that review happened. When responsibility or timing is conditional, preserve the condition and resolve it rather than silently filling the gap.
Decide who owns tracking the response. That can be you even when someone else owns the substantive review. A tracking task may finish by recording the received result or a clear unresolved state and next check; it should not claim the review itself was performed by the tracker.
Create or update the correct work record
Open Board in the intended workroom and find the approved existing Board. Search for matching work before creating another task. A filtered empty list does not prove there is no existing action.
For a new authorised task, use the available Create route to open New Task, verify Board, and enter a specific Task Title. Include in Description the request reference, exact version, expected output, responsibility boundary and finish condition. Do not copy an entire private email chain when a concise necessary reference and summary will do.
Use Assign Members for the verified eligible responsible person under your team's process. A named recipient in an email is not an automatic task assignee. Due Date is a separate planning field; where it stores only a calendar day, retain a precise timed commitment and timezone in the description or supported scheduling record. A later tracking check must not silently replace the requester's earlier deadline.
Keep planned work in an appropriate state such as Backlog. Save through Create Task or the existing task's update action, then retrieve the exact item through Board. Compare the title, full description, assignee, date and state. If reload opens a blank New Task form, search for the saved item rather than assuming it disappeared.
Read Calendar as an appointment plan
Open Inbox → Calendar. The observed view offers Month, Week, Day and Today, with an hourly grid. Check the date and view before concluding an appointment is missing. Find an existing event by its date and full title before deciding whether a new one is needed.
An appointment records a plan. Its organiser is responsible for that plan; Guests are invitees; the meeting destination determines where it will happen. Room access and live attendance are separate. Zero guests can suit a solo rehearsal but does not by itself prove the room is private.
The illustrated New Event route uses Calendar's add control, including a floating plus in Week view. Confirm the actual current control before using it. The form includes the selected calendar, Event title, Start, End, duration shortcuts, Repeat and Meeting type. The External Link branch exposes a meeting-link input, Location, notes and Guests, followed by Create Event. Internal Workroomly meetings use an available approved room selection when that route is loaded.
Do not treat preselected values from an earlier opener as clean defaults. Read the entire form, including fields below the visible area, before saving. The selected calendar and organiser identity matter as much as the title.
Prepare the interval and audience before saving
Write the intended date, start, end and named timezone first. A 09:00–09:30 interval is 30 minutes. A shortcut such as Tomorrow 9AM depends on the interface context; compare the resulting actual values rather than assuming they match your plan.
Use Does not repeat for a one-off event where available. A recurring appointment needs separate review of the rule and resulting occurrences. Choose the actual approved room or verified external link. Do not paste a guessed address or switch providers to bypass an unavailable internal service.
Review title, calendar/organiser, endpoints, timezone context, recurrence, destination, description and Guests before the authorised create/save action. Empty Guests avoids inviting people in a solo practice; it does not certify room privacy. An external invitation is a separate audience commitment and must use verified recipients.
After saving once, find the exact appointment in Calendar and reopen it. Compare all intended fields, not just a compact card. If an internal room also shows a Schedule view, compare the same event there without assuming every view has already refreshed.
Reconcile changes and cancellations without duplicates
For an authorised reschedule, identify the existing appointment and the exact change. Preserve which fields should remain unchanged. Use the currently supported edit route, save once and reopen the record. Do not create a replacement solely because a secondary view appears stale.
If Calendar and the saved editor show 09:00–09:30 while room Schedule shows 09:00–10:00, preserve both observations. Do not alter the correct 30-minute interval merely to make the secondary display look right. Check identity and timezone context, then ask the organiser or support process to reconcile the discrepancy.
Similarly, a cancelled event can disappear from Calendar while a stale room card still offers Join. Do not join a cancelled appointment or repeat cancellation as a refresh. Cancel Event, where the supported route offers it, is a consequential change to the plan, not a diagnostic tool.
A retained appointment does not prove invitation delivery, guest acceptance, attendance, working audio or meeting completion. Use the Meet workflow for those separate outcomes.
Recover uncertain work at the right level
When a draft, send, task save or appointment produces an unclear result, identify the exact record and inspect what already exists before repeating the action. A saved read view, usable edit view and outgoing message are different checkpoints. A calendar card and a live participant list are also different evidence.
Preserve the prepared text and original values. Record the intended action, observed state and missing result for the responsible owner. Retry only after establishing the first action did not execute and the operation remains appropriate; unresolved uncertainty is not permission to create another item.
Complete the Inbox workflow
Use a fictional request to review a 30-minute agenda, with no authority to revise it or book a meeting. Identify the correct mailbox, current version and response audience. Prepare the complete reply, explain how you would verify a saved editable draft, and separate sending from delivery and acceptance.
Then define a tracking action with an owner and exact next check. If an appointment is needed later, prepare its interval, recurrence and audience independently. Your expected result is an accurate current request, a complete controlled response and a reliable next-action plan. Mail flags, task states and appointment cards should support that result, not stand in for it.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.