Step 5 — Friday, calendar cleanup and welcoming a new hire
Find meetings you can decline, detect double bookings, and prepare onboarding for next week's new hire.
▶ What you learn — Cowork reads and judges your calendar and finds meeting times across multiple people. Until now it read and wrote; from here, it schedules.
Friday afternoon. Next week’s calendar is packed, and new hire Alex Chen starts on Monday.
5-1. Find meetings you can decline
Scenario 12
📌 What is happening
There are 34 meetings over the next 2 weeks. Some have no agenda, some have 18 attendees, and some are unrelated to your role. The problem is you must open them one by one to decide.
- 🎯 Expected output
- Table of decline candidates with reasons · calendar conflict flagged
- 💡 Efficiency point
- Meeting cleanup is work everyone needs but nobody does. Opening 34 meetings takes 30 minutes, and decline emails feel awkward, so people just attend.
- ⚠️ What to check
- One double booking is seeded. Check whether Cowork finds it.
Look only at my calendar for next week and show meetings I can decline as a table.
Criteria: no agenda / too many attendees / irrelevant to my role. Also flag calendar conflicts.
Do not touch focus time, and do not draft emails yet.
✅ Result check
- ⭐ Double booking — Northstar steering and Halcyon internal review are in the same time slot
- 3 recurring meetings with no agenda (18-person weekly Ops Sync, biweekly tooling review, weekly All-Hands replay)
- Did it leave focus-time blocks untouched?
If you need decline text — “Draft a polite decline email only for the Ops Sync item above. Say I will follow up through meeting notes.” This is faster than drafting 3–5 at once.
5-2. New-hire onboarding
Scenario 13
📌 What is happening
Alex Chen starts Monday as a Solution Engineer. You need required reading, intro meetings, a welcome message, and a 30/60/90-day plan.
- 🎯 Expected output
- Required-reading list + 30/60/90-day plan outline
- 💡 Efficiency point
- The 30/60/90 plan is based on the job description, so it is not generic. Most people rush it because they lack time.
- ⚠️ What to check
- Check whether it reflects the job description's 6 responsibilities and 3 90-day expectations.
Do not ask for five things at once — Asking for lists, 6 meetings, welcome message, intro post, and plan together overlaps calendar checks and document creation. Reading first, writing later.
For Alex Chen (Solution Engineer), who starts Monday, summarize only two things in chat.
① Required-reading list based on 07_Onboarding and 06_Policies (mark what to read on Day 1)
② 30/60/90-day plan outline based on the job description — 3 goals per period
✅ Result check
| Item | Expected value |
|---|---|
| Required reading | 6 items based on Onboarding_ReadingList.xlsx. Information Security Policy is Day 1 |
| 30/60/90 | Reflects the job description’s 6 responsibilities and 3 90-day expectations |
Continue one by one — “Schedule 30-minute intro meetings next week with Marcus, Priya, and Lena. Show me before booking.” / “Draft a Day-1 welcome message.” / “Draft a team-channel introduction.”
5-3. Fill the empty 30/60/90 document (optional)
Scenario 14 · Optional
📌 What is happening
Like the RCA in Step 4, Alex_Chen_30-60-90_draft.docx in OneDrive has only a title and is empty.
- 🎯 Expected output
- A plan document with all three periods filled
- 💡 Efficiency point
- Creating a new file and filling an existing file in its format are different tasks.
Fill Alex_Chen_30-60-90_draft.docx in my OneDrive Cowork-demo/OneDrive_Ava folder
with the plan you just made. For each period, include 3 goals and one line of evidence. Write into the existing file.
✅ Result check
- Are all three periods filled?
- Does each period include measurable evidence?
- Was the existing file edited, not a new file created?
What you verified in this step
- ✅ It reads the calendar and judges decline candidates
- ✅ It detects conflicts such as double bookings
- ✅ It checks multiple people’s calendars to find open time
- ✅ It creates a non-generic plan grounded in the job description
- ✅ Actions such as booking and posting go through approval
Go to Step 6 — Automation, make it run every week on its own.