Hi there,
You're reading Career Growth Guide. Each week, we take one small moment from a normal workweek and pull it apart. We look at what happened and how you can handle it better next Monday. These issues are written for people in their first few years at work, and each one is short enough to read between tasks. Small fixes like these add up, and over a career they can take you a long long way.
Today, we talk about the messages that reach you on your first morning of vacation. You'll end up with a six-line handover format and two files to attach every time.
Day one in Myrtle Beach
Sarah is a project coordinator at a design agency. Here's how she tells it.
"I'd done the handover. Or I thought I had. On Wednesday I sat with Jake and talked him through everything for twenty minutes.
"Thursday morning, I was at a beach café with my sister. My phone buzzed: 'Quick question, where's the client tracker?'
"By lunch there were four more. Where's the login? Which version did the client approve?
"Is Friday's invoice going out? Who do I ask in finance? By the fifth one, I'd stopped pretending I was on vacation."
Why the twenty minutes didn't work
Sarah's chat felt thorough. Jake nodded at every point, and he wasn't careless either.
He had his own work, plus hers, plus twenty minutes of half-remembered detail. But a conversation lives in two heads, and one of those heads was leaving for the beach.
Talking feels complete to the person leaving, because they already know the background. The listener hears it once, with nothing to search later. When a question comes up on Thursday, the only place to look is your phone.
Ivona Hirschi describes the same trap from a manager's side. In her article on handover habits, a colleague left early on a Friday, saying nothing was pending. Then something went wrong, nobody could find the files, and she ended up phoning them.
Small gaps like these add up across a team. In a Grammarly and Harris Poll study, business leaders estimated their teams lose 7.47 hours a week to poor communication.
The idea to take away: if it isn't written down, you haven't handed it over.
A real handover is a document your colleague can open without you.
The six-line handover
Use this for anything from a half day off to two weeks of PTO. Write one line per item, in plain words.
- What's live: each task, with one word for its status (done, waiting, or stuck).
- What's due while I'm away: each date and who receives each thing.
- Decisions already made: so nobody reopens them or asks the client again.
- Where things live: a direct link to every file and folder.
- Who to ask: one name per topic, and none of them are you.
Line one for Sarah might read: "Client brochure: waiting on client feedback; due back Monday." That's enough for Jake to know he only needs to watch the inbox.
Then add the sixth line, the one people forget: what can wait. List the things that look urgent but can sit until you're back. It stops your colleague from rushing work that nobody needs yet.
Sarah's version for Jake would have taken twelve minutes to write. Line four alone answers two of her five messages, and line five answers another.
Post the page in the project channel as well as your colleague's inbox. Then anyone covering can find it.
Two rules keep the page useful. Never write "it's in the drive," because that sentence answers nothing. And never write a task without a status, because "client deck" alone tells Jake nothing about what to do.
The two files to always attach
Links break, and folder permissions get missed. So attach two files directly to the handover every time.
Jake can open an attachment on his phone in an elevator. A link waiting on permission can't be opened anywhere.
The first is the latest version of anything live. Attach the actual file the client approved, with the date in the file name. "Brochure_v3_approved_Oct12" stops the "which version?" message before it starts.
The second is a contacts-and-access sheet. List each client contact, each approver, and each system you use. For every system, write how to get access.
Never paste passwords into this sheet. Write who can grant access or where the shared login lives in your team's password manager.
Name the files the same way every time, so people learn where to look. These two files cover the questions people feel most awkward sending. Nobody enjoys messaging a colleague on vacation to ask for a login.
How to hand it over
Send the document two business days before you leave. Ask your colleague to read it and reply with three questions. Answer each one inside the document, so the answers travel with it.
Then do a fifteen-minute call with the document open on both screens. Walk through it line by line. Anything new they ask goes into the document before you hang up.
On your last afternoon, update the status words in line one. Things change in two days, and a stale status sends people back to your phone.
Set an out-of-office that points to line five. "For the Henderson account, please contact Jake" saves him from forwarding every email.
Run one final test before you log off. Ask yourself whether they could get through Friday without messaging you. If you're not sure, the gap is usually in line three or line five.
For a half-day off, the same format takes four minutes. Fill in lines one, two and five, and send it in the team chat.
If you're leaving the job, stretch line three. Write the reason behind each decision as well as the decision itself, because the reasons leave with you.
When you come back from time off, ask for a reverse handover. Your colleague spends ten minutes walking you through what changed, using the same six lines.
Sarah's next vacation
Four months later, Sarah took a week off for her cousin's wedding. On Tuesday she sent Jake a six-line page and two attachments, and they spent fifteen minutes on a call.
Her phone buzzed once all week. It was Jake: "Invoice went out. Enjoy the wedding."
She hadn't even packed her laptop.
See you next week!
