LinkedIn Requests on Your Last Day: A Better 3-Window Plan

Here is the short answer. Do not batch-send LinkedIn connection requests on your last day. Spread them across three windows: Week 1 of notice for the five to ten people you have already told; Week 2 for the broader map of twenty to thirty coworkers who shaped your time; and days three to seven after your last day for the quieter names you only remember once the dust settles.

Most people do it the opposite way. They sprint through their LinkedIn tab at 4:47 PM on their last Friday, send fifty requests in nine minutes, and then wonder why only twelve stick.

The problem is not the LinkedIn requests themselves. The problem is the timing, the batch size, and the empty default note that comes with each one.

Why last-day timing hurts you

Three things go wrong when the whole list goes out on the same afternoon.

You run out of attention. By request number fifteen you stop writing a personal note. By request number thirty you forget whose name you are even clicking on. The quietest people on the list, the ones who did matter but never shouted, are the ones who get hit at request forty-six when you are already mentally gone.

You look performative. A sudden burst of fifty requests from one account tells the algorithm, and anyone paying attention, that you just left somewhere. The requests arrive while your out-of-office is still auto-replying and your last Slack message is still unread. People accept them, then do nothing. The relationship goes to the same drawer as every other dormant LinkedIn connection.

You crowd out the real work. The LinkedIn farewell post, the private thank-you to your manager, the handover notes, the actual in-person goodbyes. These are the things that earn you continued goodwill. The connection-request sprint eats the time those deserve.

The 3-window plan that works

Split the list across three time windows. Each one does a different job.

Window 1 - Week 1 of notice: the five to ten people you have already told

These are the people who already know you are leaving. Your closest teammate, the manager you reported to, the two or three cross-functional partners you worked with every month, the mentor who moved orgs last year but still gets a holiday message from you. They know the news. The LinkedIn request is just the paperwork catching up.

Send these one at a time, with a two-line note. Something like: "Really grateful to have worked with you. Would love to stay connected here while I figure out what is next."

Spread across three or four days. Not all in one evening.

Window 2 - Week 2 of notice: the broader map of twenty to thirty

These are the second-ring people. Partners from other teams, the former skip-level who sponsored you once, the engineering lead you only worked with on one project but who really showed up, the finance person who always made time to answer your questions, the ex-report who moved on last year.

Here you want to send three to six a day. Still with a note. Still personal. The note can be shorter: "Enjoyed working with you on the launch. Would love to keep in touch."

If you cannot remember a specific thing to name, you probably do not need to send the request. A specific memory is the test for whether the connection is worth keeping warm.

Window 3 - Days 3 to 7 after your last day: the quiet cleanup pass

This is the window almost nobody uses, and it is the most valuable one.

In the three to seven days after you leave, your calendar surfaces people the final week drowned out. The person who covered on-call for you in April. The parental-leave coworker who was out during your notice but used to sit next to you. The intern you mentored two summers ago who is now a full-time engineer somewhere else. The vendor who became a real relationship over eighteen months.

These are the quietest contributors to your actual working life, and they are the ones a last-Friday sprint always misses.

Send these from your personal browser, with a slightly longer note. Something like: "Just wrapped up at the old company last Friday. Wanted to make sure we stay connected here now that we are no longer in the same system."

The window matters because by day three you have had enough sleep to think clearly, and by day seven you can name the people the final week did not have room for.

The harder problem underneath

Here is what every plan skips over. The LinkedIn tab is a filtered view. It shows you whoever you have interacted with on LinkedIn recently, whoever LinkedIn's own suggestions bubble up, and whoever has shown up in your feed this week. It does not show you the full map of who actually mattered to your working life over the last twelve months.

The full map lives in your calendar. Twelve months of one-on-ones, project meetings, standups you attended, lunches you took, interviews you did. The calendar is the honest record. Memory, Slack sidebar, and LinkedIn suggestions are the loud recent slice.

If you only use what is loud, you will miss five to fifteen people who genuinely shaped your two or three years. And you will remember them in the shower eight weeks later, when it is too awkward to send the request.

The note that actually lands

Four short sentences, in this order.

1. One real detail from your working relationship. "Loved working on the Q3 redesign with you." "Grateful you covered my shift that bad week in March."
2. Where you are at. "Wrapped up at the company last week." Or "Last day is Friday."
3. What you want from the connection. "Would like to stay in touch." No vague "let me know if I can ever help" promises.
4. A soft close. "Hope you are well." That is it.

About forty to sixty words. No "connecting with you on here!" subject line. No request from your work email account. No link to your farewell-list tool or your Substack or anything else you are launching.

If you cannot write the first sentence without reaching for generic praise, that is a signal. The connection is maybe not worth sending now. Send it in week three if the memory comes back, or let it go.

Three mistakes to avoid

Beyond the batch-timing issue, three specific mistakes to skip.

Sending the request with no note at all. LinkedIn makes this the default. Resist. A naked request from your personal account on your last day is slightly worse than not sending anything. The person reads it as "they are leaving and want a wider network" rather than "they want to stay in touch with me specifically."

Sending requests from your work laptop before your last day. Some companies monitor LinkedIn behavior through their SSO or endpoint tools. It is not usually a fireable issue, but it looks worse than it needs to. Use your personal browser and your personal email on LinkedIn for the connection sprint. Switch over now if you have not already.

Sending the request before you have told the person in person. This is the big one. If a coworker finds out you are leaving because they got a LinkedIn request from you on a Tuesday afternoon, that is a bad discovery path. Tell them first. The connection request is the follow-up, not the announcement.

Four edge cases

You were laid off and lost access the same day. You cannot do the three-window plan. Collapse it. Send fifteen to twenty requests over the next five to seven days, from your personal browser, in small batches of three or four per day. Lead each note with a specific memory. The sudden-exit framing actually makes the note easier to write.

You are moving to a direct competitor. Pull Window 3 forward. Send to internal-only coworkers in Week 1, before the news gets around. People are warmer to the request before they know where you are going. If they ask about the new company in a reply, tell them simply and keep moving.

You are at a small company where everyone knows everyone. You do not need the three-window structure. You can send twelve to twenty requests in one Tuesday evening the week after your last day. Still with a note. Still from your personal browser. Small-company exit culture is different; the batch size is forgivable because the news traveled fast anyway.

You work in a fully remote team where LinkedIn is the main surface. Push Window 1 forward: start with your closest teammates in week minus-two or minus-three, not during notice itself. Remote-first teams accept LinkedIn connections as the standard "we worked together" signal; there is less to be careful about than in an office-first team.

What good looks like four weeks later

By week four after your last day, you have sent about thirty to forty requests across the three windows. Each one has a personal note. You are not finishing the list in one afternoon. You are not sending anyone from the staying-in-touch list an empty default. And you have resisted the fifth-day burst of "I should probably add this one too" without writing anything meaningful.

You will miss a few names anyway. That is fine. The people worth keeping on LinkedIn will stay reachable through mutual contacts if you both want to be. The ones who were only in your network because of the shared company badge will drop out, and that is the system working correctly.

If you want to be careful about the full list, do a twenty-minute calendar scan one weekend evening with a tool that reads your calendar for you. Export the last twelve months, let it show you the names, and let that be the starting list for Window 2 and Window 3 rather than whatever LinkedIn happens to suggest.

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