The Week Before You Give Notice: What to Quietly Do

Here's the short answer: in the week before you give notice, do four quiet things. Export the artifacts that are yours. Draft the resignation letter and schedule the meeting. Pick the day and time, with your boss's calendar in mind. And make a private list of the people you want to say a real goodbye to. The two weeks after are much calmer when this week is already done.

Most people start the clock at the resignation meeting. The real clock starts about seven days earlier, in the quiet gap between I'm leaving and they know.

That gap is your only private week. Once the news is out, every half-hour gets claimed by someone else: a wrap-up meeting, a handover doc, a lunch, a Slack thread, a well-meaning coworker who wants to catch up before you go. You don't get another window to think slowly.

What follows is what to do with it. Think of it as a seven-day plan, but compress or stretch depending on how fast you need to move. The order matters more than the exact days.

Day 1 and 2: Export what's yours

The things that belong to you are tangled up with things that don't. Pull them out while you still have full access. If you wait until after the resignation meeting, access can get revoked within hours.

Pull together:

• A one-page brag doc of the five or six things you did that you'd actually mention in an interview, with real numbers. You've probably been building this already. If not, there's a short format for it: a one-page brag doc is enough.
• Your performance reviews, downloaded as PDFs. Not links. Actual files on your machine.
• Kind words: screenshots of the three or four Slack messages, review quotes, or client emails you'd want to see again on a bad week. Save them somewhere outside work.
• Personal contact info for ten people. Not a mass contact export. Ten names, personal email or number, in a note.
• Your calendar, exported as an .ics file. This is less obvious than the others but worth doing. The calendar is a map of who you spent real time with over the last few years, and that map is useful for the goodbye list later.

Nothing here is proprietary. It's your work, your words of praise, your contacts, your meetings. You're not taking anything that doesn't belong to you.

Day 3 and 4: Draft the letter and book the meeting

The resignation letter is three sentences, maybe four. Thanks, last day, open to helping with the handover. That's it. Write it this week, not the morning of the meeting, so you're not editing adrenaline into it.

Then book the meeting. Put it on your boss's calendar directly, titled something innocuous. Quick chat, catch-up, 15 min. Twenty-five minutes, morning, in a room with a door. Not Friday afternoon, not before a big review, not before their flight.

Picking the day is its own small question. There's a short argument for Tuesday or Wednesday in this piece on the best day to give notice. The short version: avoid Monday morning (bad news hits a full week), avoid Friday (news festers over the weekend), aim for mid-week morning.

Resist the urge to pre-send the letter. The meeting happens live, then the letter follows as the written record.

Day 5: Make the private goodbye list

This is the one piece of the prep that quietly takes the longest, and the one almost nobody does early. The reason is simple: once the news is out, the people in front of you are the ones you'll say goodbye to. Not the ones you should.

What usually happens is that your attention gets claimed by whoever messages you first. The coworker who sends a long heartfelt note. The teammate who asks for coffee. The person two rows over who always had something to say. None of this is wrong. But it means the quiet people, the ones who shaped how you think without ever making a show of it, don't make the cut. You run out of time.

The way around this is to make the list before the news breaks, when your brain is still ordered by who actually mattered rather than who is in your inbox.

Fifteen to twenty names. First-name basis. Spread across the companies and teams you've been through, not just the current one. For each one, a one-line note: what I'd thank them for. Not a draft message yet. Just the raw list.

If you want help building that list from your calendar export, It Was Great Working With You reads an .ics file and finds the people you spent the most 1:1 time with over the years. It's genuinely useful for this step because you'll see names you had forgotten, and remember why they mattered.

Build the list first. The messages come later, in the two-week window, when you'll have the time and energy to write them properly.

Day 6: Protect your energy and don't tip anyone off

This is the day most people trip. You've done the hard thinking. The news feels inevitable. It's tempting to let one or two people in, usually a work friend, usually over drinks.

Don't. Even a trusted colleague can let something slip in a Slack thread, forward a message, or get asked a direct question they feel awkward dodging. If your boss hears the news from someone else first, your resignation meeting is a different, worse conversation.

The simplest way to do this is to keep the week looking normal. Normal 1:1 cadence. Normal lunchtime. Normal replies in Slack. Say yes to the small things. Decline anything that commits you two weeks past your intended last day without a hedge.

Also protect your sleep. The resignation meeting is a short conversation, but it eats more energy than you expect. You want to walk in rested.

Day 7: Resign

The last step is short, which is the whole point of the prep. Walk into the booked meeting, say the sentence you've been drafting, give the letter, agree on the broad outline of the handover, leave. Then send the letter as a follow-up email the same hour. There's a minute-by-minute version of the day in this hour-by-hour guide to the day you give notice.

By the end of day 7, you have: the news out, the letter on record, a draft handover plan, a brag doc on your personal drive, a kind-words file somewhere safe, a goodbye list of fifteen names, and the two weeks ahead that aren't swallowed by admin.

Common mistakes in the quiet week

A few patterns show up often enough to flag.

Over-exporting. You don't need every file. You need the five or six that matter. Downloading a hundred documents you'll never open adds noise and, in some roles, risk. Be selective.

Writing the goodbye messages too early. The list, yes. The actual messages, no. Written on day 5, they'll sound stiff and generic. Written in the final week, with the actual last-day feeling behind them, they'll land better.

Telling a recruiter you've started yet. If a new job is lined up, keep the start date buffer honest. Agreeing to a Monday start the week after your last day sounds smooth but leaves zero room for a long goodbye lunch, a quiet week off, or a slower handover if asked. Build in at least three or four days.

Pre-apologizing. You haven't done anything yet. Walking around looking guilty in week minus one tips people off and primes the resignation meeting as sad rather than steady.

What if you have less than a week

Sometimes the timeline collapses. A new offer with a hard deadline. A manager who's about to go on leave. A personal reason. In that case, compress to two days.

Day 1: do the exports (brag doc, reviews, kind words, calendar) and draft the letter in the evening. Day 2: build the goodbye list in the morning, book the meeting for the afternoon, resign. Everything else can roll into the two-week notice window. The compressed plan is lighter but keeps the two things that are hard to redo later: the exports (because of access) and the list (because of attention).

If you can't even manage two days, do the list and the exports. The letter can be two sentences on the fly, but the list and the files are the pieces that are hard to recover from if you skip them.

One short last thought

The reason this quiet week matters isn't optimization. It's that leaving well is mostly about who you say goodbye to, and giving yourself the room to think about that properly, before the noise starts, is the whole trick. The admin is the easy part. The people are the point. If you want help making the list before the news goes out, It Was Great Working With You is the fastest way there.

Further reading: The people you'll forget to say goodbye to when you leave your job.