Hands-On: Schedule a Full Work Week
Put your calendar management skills to the test by planning and managing an entire work week from scratch.
Video
Watch the lesson video, then complete the reading and challenge.
Presentation Slides
Review the slides below, then complete the reading and challenge.

Lesson Notes
Read through the key concepts before you try the challenge.
Real-World Scenario
The Fragile Week vs. The Functional Week
Most people treat a calendar as a passive record of commitments. A professional treats it as active infrastructure. The difference between a fragile week and a functional week is visible the moment something unexpected happens:
- A fragile week has events without video links — someone sends a message 5 minutes before a virtual meeting asking for the Zoom link because it was never included in the invite.
- A fragile week has no buffer time — when a meeting runs long, the next meeting starts late, the next attendees are waiting, and the entire afternoon collapses.
- A fragile week has unresolved overlaps — two events at the same time with no documented resolution. Someone shows up to the wrong meeting.
- A fragile week has no out-of-office indication — the manager is traveling but the calendar shows them as available, so new meetings keep getting booked for times when they are on a plane.
- A functional week has fully built events — every invite has a title, attendees, video link, and agenda so no one needs to ask for details.
- A functional week has buffer blocks between meetings — they surface conflicts before they happen and give everyone transition time.
- A functional week documents every conflict resolution — when a meeting moves, the reason is logged and all affected parties are notified before anyone arrives at the wrong place.
- A functional week includes an out-of-office block — the manager's travel is visible on the calendar so no new meetings are booked into unavailable time.
Phase 1 — Building the Weekly Structure
Before placing any individual event, establish the structural elements that will hold the week together. Building structure first prevents conflicts before they arise:
- Create the out-of-office block first — mark the manager's travel as an all-day event from Monday through Friday, titled clearly: 'TOR Tech — Out of Office (Business Travel)'. This ensures no one books new meetings into unavailable time before you build the rest of the week.
- Place recurring events next — the weekly team standup and any other recurring commitments should be the fixed anchors of the week. These do not move. Build everything else around them.
- Add buffer blocks between meetings — after placing fixed meetings, insert 15-minute buffer blocks between any two meetings that are less than 30 minutes apart. A Tuesday schedule with a 10:00 AM call, an 11:00 AM presentation, and a 12:00 PM call needs buffers at 10:30 and 11:30.
- Block focus time — if your manager needs uninterrupted time to review materials, prepare for a presentation, or complete a deliverable, block it explicitly on the calendar before anyone else can schedule over it.
- Mark all-day deadline events — project deliverables, report submissions, and client milestones should appear as all-day events on the day they are due. Use a consistent naming convention: 'DEADLINE: Q2 Financial Report to CFO'.
Phase 2 — Scheduling Meetings Completely
Once the structural elements are in place, add the specific meetings to the week. Every event must be complete before you consider it done. An incomplete event is an unreliable event:
- Title — specific and purposeful. 'TOR Tech Q3 Client Check-In: Acme Corp' is complete. 'Meeting' is not.
- Attendees — add every person who needs to attend. Check their availability using the Find a Time feature before confirming the slot. If there is a conflict, resolve it before sending the invite.
- Location or video link — paste the full meeting URL directly into the location field. For in-person meetings, include the room name and floor. Never leave this field blank for a virtual meeting.
- Agenda in the description — even two or three bullets make the meeting purposeful. 'Review Q3 deliverables, Confirm next milestone dates, Assign open action items' is a complete agenda for a 30-minute check-in.
- Reminders — set at least one reminder per meeting. For external or high-stakes calls, set both a 24-hour and a 15-minute reminder.
- Verify every event before the week begins — scan the full week view on Friday afternoon. Every slot should have a title, a time, and a location or link. If any field is missing, fix it before Monday.
Phase 3 — Resolving and Documenting Conflicts
Even a well-built week will produce at least one conflict. Phase 3 is about identifying overlaps, resolving them using the prioritization framework, and documenting every decision so the record is clear:
- Scan for overlaps after placing all events — look at each day in the week view and visually identify any time blocks that overlap or sit back-to-back with no buffer.
- Apply the prioritization framework — external before internal, revenue-generating before administrative, urgent before important. Use this framework explicitly and document your reasoning.
- Move the lower-priority event — once you have confirmed the priority with your manager, move the lower-priority event and send a rescheduling email to all affected attendees with 2 alternative times.
- Log every conflict in the event description — add a brief note directly to the rescheduled event: 'Originally scheduled for Tuesday at 2:00 PM. Moved to Thursday at 3:00 PM due to client demo conflict.' This prevents confusion when attendees compare calendars.
- Confirm with all parties — do not consider a conflict resolved until every affected attendee has acknowledged the change. The calendar update alone is not enough for high-stakes meetings.
Phase 4 — Handoff Documentation
When you manage someone else's calendar for a full week, you are responsible for leaving a clear record of every decision you made. A handoff note ensures your manager returns to a calendar they understand and trust:
- Write a brief weekly summary — a short document (or email) covering: what meetings were scheduled, what conflicts were resolved and how, what deadlines are on the calendar, and any open items that need the manager's attention upon return.
- Flag unresolved items — if any meeting could not be scheduled due to persistent unavailability, note it explicitly in the handoff summary so the manager knows to follow up.
- Document any permissions granted — if you shared calendar access with a new team member or booked a meeting on behalf of an external party, note it in the summary so there are no surprises.
- Leave the calendar clean — delete any test events, draft holds, or tentative blocks that were not confirmed before the week starts. A cluttered calendar creates confusion.
- The professional standard — your manager should be able to read the handoff note and the calendar together and have a complete, accurate picture of the week without asking any follow-up questions.
Responsible Use
AI Assist
Knowledge Check
Why should you add buffer blocks between meetings on a shared office calendar?
Challenge
Apply what you've learned in this lesson.
Build a complete, functional work week (Monday through Friday) on a real or mock Google Calendar for a fictional TOR Tech manager who is traveling. Your calendar must pass every check in the five specifications below before you submit it:
- Create an out-of-office all-day block for the full week titled clearly with the manager's name and travel reason, plus at least one recurring team standup set to repeat weekly
- Schedule 2 complete client meetings — each with a descriptive title, attendees (fictional names and roles), a placeholder video link, and a 2-item agenda in the description
- Add 3 project deadlines as all-day events using the naming convention 'DEADLINE: [Deliverable Name] — [Recipient]'
- Add 15-minute buffer blocks between any two meetings separated by less than 30 minutes, and one 60-minute focus block protecting time for deep work
- Identify and resolve at least 1 scheduling conflict — log your prioritization reasoning in the rescheduled event's description and describe in 2–3 sentences what moved and why