Your finance manager just gave notice.

Two weeks. That’s what you have before six years of vendor knowledge starts walking out the door—the negotiation history, the relationship context, the auto-renewal windows they had memorized, the 22% discount they secured after two rounds of back-and-forth that nobody else knows about.

Most companies spend those two weeks on the wrong things: access revocation, HR paperwork, laptop returns. The vendor knowledge transfer gets a 30-minute exit interview, if it happens at all.

Here’s how to use the next 14 days more effectively.

What’s at immediate risk

Before you can protect anything, you need to know what’s actually in danger.

Renewal windows. Every vendor contract has a negotiation window—typically 60 to 90 days before the contract end date. Inside that window, you have leverage. Outside it, you don’t. Your finance manager knew which windows were coming up and which vendors were candidates for renegotiation. Without that knowledge, windows close quietly. You approve renewals on inertia.

Negotiated pricing. The discount your finance manager secured didn’t come with documentation. It lived in their notes, their memory, and their relationship with the rep who agreed to it. At the next renewal, you’re starting from list price unless you know what was achieved and how.

Vendor relationships. There’s the account manager and there’s the person who actually gets things done. Your finance manager knew which contacts to call when invoices were wrong, which reps had the authority to offer better terms, which relationships had goodwill built up over years. That context doesn’t transfer in a two-week offboarding.

The 14-day vendor handoff checklist

Work through this with your finance manager before their last day. Not all of it will be possible—six years of context doesn’t compress into two weeks—but the time-sensitive items need to be captured now.

Days 1–3: Surface the urgent items

  • List every vendor with a renewal in the next 120 days. Get the contract end date, the auto-renewal clause deadline, and the cancellation notice requirement for each.
  • Flag which vendors are candidates for renegotiation. Ask your finance manager directly: which of these should we push back on? Which ones have room on price?
  • Identify any active negotiations. Is anything currently in discussion? What’s the status? Who at the vendor company is involved?

Days 4–7: Capture the negotiation history

  • Document the current pricing and how it was achieved. For every significant vendor, write down: what you pay, what the list price is, and—crucially—how the current rate was secured.
  • Note what leverage exists at renewal. Usage data? Competitive alternatives? A prior commitment from the rep? Document what’s in your hand before the next negotiation.
  • Get the rep’s name and direct contact. Not the general support email. The specific person your finance manager calls.

Days 8–11: Map the relationship context

  • Who are the escalation contacts? When something goes wrong—a billing dispute, a missed SLA, a failed implementation—who do you call? Standard account management channels are not the answer.
  • What commitments were made informally? Verbal promises about pricing, service levels, or roadmap features don’t appear in contracts. Ask your finance manager to recall any commitments that should be on your radar.
  • Which vendors are underperforming, and why? Low adoption might be a product problem. It might also be a training gap that the previous manager was planning to address. Get an honest assessment before you make any replacement decisions.

Days 12–14: Document what you’ve captured

  • Create a vendor file for each significant relationship. One document per vendor: contact information, pricing summary, negotiation history, renewal schedule, and any context that affects decisions.
  • Assign interim ownership. Who is responsible for each vendor relationship after the finance manager leaves? Name a person. Not a team. A person.
  • Set renewal alerts. For any contract with an auto-renewal clause, put a calendar reminder 90 days before the contract end date. 60 days. 30 days. This is the minimum.

What you won’t be able to recover

Be honest about the limits of a two-week handoff.

Relationship context takes years to build. The rapport, the trust, the knowledge of which vendor contacts will go to bat for you—none of that transfers in two weeks. You’ll need to rebuild it, and that takes time.

The detailed negotiation history often can’t be fully reconstructed. If it wasn’t written down as it happened, pieces of it are gone. You can document what’s remembered, but the institutional knowledge that would have made you a stronger negotiator at the next renewal is partially lost.

This is why the handoff problem is ultimately a system problem, not a people problem. If you want vendor knowledge to survive employee transitions reliably, it has to be captured continuously—at the point of purchase, after each negotiation, through quarterly reviews—not reconstructed during offboarding.

For a full breakdown of what vendor knowledge loss actually costs and how to build a system that prevents it, read The Vendor Knowledge Blackout.

What comes next

The two-week handoff buys you time. It doesn’t solve the underlying problem.

The underlying problem is that your vendor knowledge lives with people, not in systems. When the next key person gives notice—and they will—you’ll be back in this same position unless you’ve built something that outlasts individuals.

VendorLog is built specifically for this problem. Not another contract database. A system that captures vendor knowledge at the point of creation—at purchase, at negotiation, at each performance review—so it’s there when you need it, regardless of who’s in the role.

Start with the free Complete Vendor Handoff Checklist — the 7-phase framework for capturing and transferring vendor knowledge in 48 hours.

Your people will leave. Your vendor knowledge shouldn’t have to.