Check a meeting proposal against constraints

Use the practice organisation and source records from lesson 1.

All practice records are synthetic. Work manually or with an optional AI assistant; no paid product, external account or connected inbox is needed.

Open the source pack · Download the workflow templates

Learn

A meeting proposal must satisfy everyone’s availability and the executive’s rules. Use intervals rather than vague phrases such as “Tuesday afternoon.” Check the date, duration, participants, time zone, busy periods, buffers and lunch before suggesting a slot.

In real work, ask for missing time zones and verify local-time conversions for the actual date in the calendar tool. Do not guess from someone's city or use a remembered UTC offset across daylight-saving changes. This exercise already supplies UTC, so no conversion is needed.

Worked example

E2 requests 30 minutes within 14:00–16:00. Morgan's 13:00–14:00 meeting makes the next start 14:15 with the required gap. Sam is busy until 14:30. Morgan's 15:30 meeting means a new meeting must end by 15:15. Therefore the common feasible window is 14:30–15:15. A 14:30–15:00 proposal fits; 15:00–15:30 fails Morgan's buffer.

There is more than one valid start if minute-level scheduling is allowed: any start from 14:30 through 14:45 inclusive fits. Do not claim the worked example is the only possible time.

Try it

Check these candidates and give the failing constraint if any: 14:00–14:30; 14:30–15:00; 14:45–15:15; 15:00–15:30. Write a draft scheduling note containing a proposed date and time, attendees, duration, source IDs and “pending approval.” Do not create an invitation.

Reusable scheduling checklist

Date and source | Time zone | Duration | Required people | Busy intervals | Buffers | Other constraints | Feasible options | Approval status

Course sources and teaching notes.