What does it mean to inherit suppliers and contracts that no one has managed?

It means becoming responsible for agreements, suppliers, or spend that were never properly governed, usually without a handover and often without any record of what exists, or at least where to find it. It falls to whoever owns supplier relationships, and in some cases, they're the first person to be in the role. When a new procurement lead picks it up, they didn't create it, and in many cases, nobody had pulled everything together in the first place. There are usually three situations: No reliable count of suppliers No clear owner against each relationship No views of what renews or lapses A messy system is still a system: the information exists, it's badly organised, and one determined afternoon improves it for everyone. What you have inherited is often a different story because the information was never captured in a system of truth, so there is nothing to tidy. Figuring out what you have is the job itself at first.

Why is it a connectivity problem rather than a filing problem?

No one can answer questions about your inherited suppliers and contracts because of where the documents are stored. Filing is just one of the organisation's problems to address. The real problem is that no one unified the decisions. The suppliers check, the agreed terms, the money that went out, and what came back. Someone recorded each somewhere for their own purposes. Reorganising documents doesn't fix that. You can put every agreement in one folder, name them consistently, and still not be able to say whether the supplier you pay has current insurance or whether you've ever claimed the service credits you negotiated. You're earlier on then, working through best practices. The most useful practice at this stage is finding where the joins are missing before standardising a workflow you don't have yet.

What breaks in supplier and contract management before the workflow?

You often hit three common breaks before you standardise your workflow. Due diligence and the contract Signature and delivery What you agreed and what you pay What breaks between due diligence and the contract? Someone likely did initial supplier checks: a credit report, a security questionnaire, or a reference call. Usually the problem is that the concerns raised never made it into the agreement as a clause, condition or right to audit. The organisation carries a risk once identified but now forgotten. So the evidence of the check is there, but there's no trace of it in the contract. What breaks between signature and delivery? A signed agreement is a list of promises in both directions, and most require action afterwards. Provide an annual certificate Hold a quarterly review Notify you before a price rise Once the contract is filed, those commitments go quiet, nobody follows up, and the value negotiated stops arriving. What breaks between what you agreed and what you pay? You never checked whether the rate you negotiated matched the rate you were charged. Somebody won a tiered discount, a capped uplift or a set service of credits; the agreement was filed, and the invoices arrived. Nobody has compared the two since. A volume tier was reached eighteen months ago and never applied. An uplift capped at CPI that came through several points above it. A rebate that triggers annually and has never been invoiced for. Service credits negotiated but not once claimed.

How did I end up responsible, and how does it change what I do first?

Growth outpaced the process. The process was broken, or a rule existed that nobody followed. Buying happens around you, with people raising their own purchase orders. The same supplier appears three times under slightly different names, and nothing is formally closed. There's a temptation to publish a new rule because it feels like progress and costs nothing to produce. Though it usually backfires, and you'll find yourself in the same loop. A rule nobody can enforce, applied to a process nobody can see, teaches the business to route around you, and an ignored policy is worse than none. Earn the right to set rules by being the person who can already say who bought what, from whom, and on what terms. A predecessor left or retired. Expect the paperwork to exist and the reasoning behind it to be gone. Why that supplier was chosen What was agreed verbally alongside the contract Which relationships are fragile What the last renewal settled What was traded to settle it Start with what only they knew, and treat it as decaying data. The people who worked with your predecessor still remember those conversations, but they'll remember them less well each month, so document and record the conversations before you build the spreadsheet. If they left behind two systems, or a configuration nobody understands, hold off on deciding whether to fix or replace it until you know what it contains and whether that information is still correct or outdated. Explore our 90-day plans to help you organise your data .

What can I do in the first two weeks, with no budget or system?

This largely depends on how much you already know about the suppliers and contracts you inherited. If you can't name your suppliers yet or say what renews next, the first month is discovery rather than delivery. Explore our questionnaire and 90-day plans to build an action plan. Though, your first two weeks should focus on establishing your renewal and notice-period exposure. This is the only part with a clock attached, so any delay has a price, and it needs nothing more than access and a spreadsheet initially to work out potential upcoming renewals.

How do you find what renews next when there's no register?

Work backwards from money and from people. Ask finance for the last 12 months of supplier payments, sorted by value: anything material enough to matter is paying somebody. Then take the top 30 by value and ask whoever owns each relationship two questions: When does it end What notice do we have to give? The answers may be patchy, but it will still show you which agreements sit closest to a deadline. Chase the contract itself only where the answer is uncertain, and the value is high. Reading everything could take a month with little return; reading the six that matter most will take an afternoon.

What should the interim tracker contain?

Keep as few fields up to date as you can. Supplier, what they do, internal owner, annual value, end date, notice period, where the document lives. That answers the questions you will be asked, and it's the reason to resist a twenty-column version: a tracker with too many fields decays within a month, and a decayed tracker is worse than none. People will trust it, and it’s much easier to maintain. A spreadsheet is the right tool at this stage. Plenty of organisations run a serious operation this way for a year before moving, and tracking contracts in a spreadsheet is a legitimate interim as long as you are honest about it being one. A shared board with columns for what is coming up, what is being chased and what is settled beats a more elegant system you have to ask for budget for early on. Once you can see the pattern, you can get ahead of renewals and stop them from becoming a series of emergencies.

What should be purposefully set aside for the next stage?

Anything without a deadline or material exposure. Duplicate supplier records Inconsistent naming Documents in the wrong folder No template library These are real problems, but they're not urgent, and every hour spent on them is an hour not spent on the thing with a date attached.

In what order should I sort out inherited suppliers?

Establish who your suppliers are What was agreed with them What is being spent and delivered Each stage produces the information the next one needs, so any other sequence means doing most of the work twice, usually once people have stopped being patient. A common instinct is to start with the documents, because gathering them feels like progress you can show. Documents without a supplier list have no shape. You can't tell which of the 400 files matter, so you treat them all as equal. Establish who your suppliers are Create a deduplicated list of who you pay and who has access to your data, systems or premises. At this stage it's the list itself, with no assessment or risk tiering attached. Payment data gets you most of the way, and the gaps are the interesting part. Done enough is one name per organisation, an owner against each, and a rough annual value. Everything else depends on it too because you can sort by importance instead of treating every relationship the same. This is the foundation of building a supplier management program that survives its first year. Establish what was agreed Terms, dates and obligations for the material relationships, and nothing more. You're looking at extracting around eight fields from each agreement that carry real value or real risk: parties, dates, notice, value, uplift mechanism, liability position, obligations for either side, termination rights. It's where any gaps in the first stage surface: if the supplier list was wrong, you extract terms for relationships that no longer exist and miss ones that do. Where a supplier looks materially risky, and no assessment exists, run one; a standard set of due diligence questions is faster than designing your own. Establish what is spent and delivered Reconcile the money and the performance against what was agreed. Now that you know who they are and what was promised, the invoices become readable: the uplift applied without notice, the service credits never claimed, the licences paid for and not used. This is a variance you can explain across the top 20 relationships. This is where the work starts paying for itself, and it becomes the evidence base for whatever you propose next. The supplier management platform you eventually adopt makes this continuous and checked as invoices arrive, but the sequence doesn't change: if you load it with the wrong supplier list, it produces confident but wrong answers faster. What does it cost to do this in the wrong order? Time, mostly. It could take several months to tidy up, and when your first renewal arrives, you can't negotiate because you don't know what was agreed.

How do I centralise contracts stored across email and shared drives?

Start by working outward from your supplier list rather than inward from folders. No search will find every contract if they're named inconsistently, saved as scans, or exist in someone's inbox. Take the relationships that carry risk, ask each internal owner for the agreement, and chase what is missing one at a time. If you know who your suppliers are, they'll have a copy of the original agreement too. If you can't find the information internally, start by asking the counterparty for a copy.

Procurement teams

Your first 90 days in a new procurement role.

You've inherited the responsibility for suppliers with problems that predate your start date. What should you establish and fix in your first 90 days to prepare your data for future audits and potential auto-renewals?

Take the questionnaire Explore 90 day plans

Solutions Page_Procurement_Hero Banner Header

Questionnaire result

Mostly "I'd have to check" answers.

What should your first 90 days in procurement look like if you can't yet say what you have?

Find what has a deadline before you organise anything. You can't look up a renewal date without a supplier register, so create a payment list and ask two questions about the thirty supplier relationships that matter. By day 90, you should be able to answer the five questions above, which is a lower bar than tidy records and the right one to aim for.

Read this first if two or more of your answers were "I'd have to check", whatever else you answered. Blind spots set your first month, no matter how much of the rest you know.

Days 1 to 30. Find what has a deadline.

What renews or lapses in the next 90 days has a risky commercial deadline. Everything else on your list will still be an issue in a fortnight. The difficulty is that you can't look up a renewal deadline without a supplier register, and the workaround is to sort twelve months of supplier payments by value, which shows you where to start when you inherit contracts and suppliers nobody managed well before.

What belongs to this month in particular is the discipline of stopping once you have the top thirty, and asking each of them two things and no more.

When does this end?
What notice do we have to give?

There's a temptation to keep going until the list feels complete, but it might take almost a year, and the top thirty relationships will carry most of your value and most of your risk.

Expect patchy answers and maybe a few suppliers with nothing at all. A list with holes still shows you which agreements are closest to their deadline. A relationship nobody wants to claim is usually the one worth looking into first.

The first month buys you choices. Find a renewal notice window while it's still open, and you have time to keep it, renegotiate, or cancel the contract, rather than letting it roll over with an unexpected invoice landing on finance's desk and the business committed to another term.

Days 30 to 60. Fill in the picture behind the dates.

You can usually expect three gaps here.

Relationships nobody owns (or wants to)
Payments nobody can explain
Suppliers with access to your systems, premises or data who haven't been checked

Work through them in this order, as ownership lets you hand off the second two points to the relevant department and people.

Days 60 to 90. Turn the list into a record.

The list you build will decay quickly, and the final issue is deciding where it lives, who maintains it, and how few fields it can carry while still answering the question you're routinely asked.

A spreadsheet is a reasonable answer for where it lives at this stage, as long as you're open about it being interim, and tracking contracts in a spreadsheet shows where that stops working.

You have a legacy supplier management system in place.

Accepting this system can sometimes be a trap. If you've been handed a tool that somebody configured and then left, you'll need to learn to use it before you know what it should contain, and you'll spend weeks understanding a configuration that might not survive the first year. Do your diligence on renewal dates and create your initial list first, then decide whether the tool can handle it.

By day ninety, you should be able to answer the five questions in our questionnaire. That is a lower bar than having your supplier list under control and complete, and it's the right choice for the first quarter. Nothing is getting worse unseen, and you can describe what you have if somebody asks.

If somebody asks for progress at the end of the month, show them a list of what renews before a named date. A non-specialist can see that it's finished. A piece of data-quality work won't be, no matter how much it matters. When that conversation comes up, how you tell your board or senior team what you inherited without sounding like an excuse depends on how you frame it.

Questionnaire result

Mostly "No" answers.

What should your first 90 days in procurement look like if nothing is in place?

If you're not spending the first month just finding things out, you can run two things at once. Set up your renewal exposure and a single route for new requests within the first thirty days. Then build the supplier list and the terms behind it. It's the order that's going to matter more than the pace at this point.

If two or more of your answers were "I'd have to check", read finding out what you have first.

Days 1 to 30. Two jobs running in parallel.

Job one: Find out what renews or lapses in the next 90 days. This is the only part of the plan with a timer attached. This gives you time to avoid an unexpected invoice and cost landing with finance. It means you'll have the time to review, keep, renegotiate or cancel. It means you have choices, and you've immediately thought commercially about the business.
Job two: Create one place for new requests to arrive. Through a named person, a short form, and a stated turnaround time. The second job feels like admin, but it's the foundation for everything that comes after. It's how new commitments stop being invisible while you're busy fixing the old ones.

Days 30 to 60. Creating a list and the terms.

Build a deduplicated supplier list, with an owner assigned to each supplier name. Then identify the agreements behind the relationships that carry real value or real risk, and pull out key fields and metadata.

Who signed
Dates and whether it renews itself
Notice period
Value (what you're actually paying)
Uplift mechanism (how the price can rise)
Liability (could it be a commercial or legal problem?)
Obligations on either side
Termination rights

This metadata answers most questions people will ask you, and extracting it is the quickest way to report and respond.

Days 60 to 90. Creating controls you can support.

Now you can start introducing rules because you can see the process they apply to. The supplier setup gate is the cheapest control in the organisation. Nothing gets paid unless it was set up, and nothing gets set up without an owner, and a check proportionate to what the supplier can access. Building a supplier management program covers what comes after that.

Avoid publishing a new policy in week one.

Rules feel like progress to you and usually only cost time to produce; however, a rule applied to a process nobody can see yet teaches the business to route around you. The practical version for your first 90 days is to create a record where you can quickly and easily see the most important data, and earn the right to set the rules and processes people follow.

What you're aiming to do by day ninety is something that will still be there and working in six months. That test is harder than it sounds. Most of what you build in the first quarter begins to decay, either because it has too many fields to maintain or because nobody can say whose job it is to maintain it. Get the owners in place from the beginning.

Questionnaire result

Mostly "Yes" answers.

What should your first 90 days look like if the records exist but don't connect?

Don't start by just trusting records you've inherited. Test them first by taking ten supplier relationships and trying to answer the following three questions about them:

Who originally checked and signed off on these suppliers?
What did we agree to?
What have we paid?

How many suppliers, and how many of the three questions you can answer without asking colleagues, is your real starting position. Even with records in place, that number is usually lower than expected.

Days 1 to 30. The ten relationship test.

Pick ten, mixed by size and by how long they've been in place (think spot-checking). For each one, trace the chain backwards. The credit check or security review done before signature, the agreed terms, each side's obligations, and what's been invoiced since. Count how many you can complete without asking anyone else.

The exercise may take around a day and will tell you more than a maturity assessment would at this point, because it produces a number you can repeat in ninety days and compare.

Days 30 to 60. Fixing the joins.

The same steps in the process usually don't join up.

A check was done and never became a clause, condition, or right to audit, so the business carries a risk it identified once and forgot about.
Obligations agreed at signature were never monitored: a certificate due every year, a quarterly review nobody owns, or the notice you were promised before a price hike.

These don't need a project to fix them. The diligence gap closes at the next renewal or variation, provided that somebody has written down which agreements have one. The obligations gap needs an owner and a date against each commitment. Capturing contract metadata for each supplier relationship fixes the diligence and obligation gaps. Dedicated time to capture the data and set owners fixes this.

Days 60 to 90. Continuous monitoring instead of periodic.

What you've inherited might have been accurate at the time, but that doesn't mean the data and information are correct now. A well-organised repository doesn't mean it remains a reliable record.

An onboarding assessment only describes a supplier that could have changed hands since then, moved a service offshore, changed its AI policies, or let a certification lapse. The next thirty days are about deciding what to recheck, how often, and what triggers a recheck outside your standard schedule.

Don't just assume the records are right.

Suppliers may have been acquired, or a business may have split off from its parent, so services and policies could have changed. Look at the transaction documents before the contract file.

What transferred?
What was retained?
What needed consent that wasn't asked for?

By day ninety, you should be able to answer a question about any supplier without assembling the answer from multiple places.

procurement concerns

Are procurement teams monitoring real-time risk?

Only 6% of 160 Senior Procurement Leaders reported that they have predictive or real-time risk monitoring tools.

Only 6% have predictive or real-time risk monitoring tools 6%
62% still rely on manual or periodic tools 62%

Source: ProcureAbility's CPO Benchmark Report

Your first 90 days in a new procurement role.

Your first 90 days in your new procurement role depend on how much you can already answer about what you've inherited.

Could you produce a list of every supplier the business pays without asking anyone to look for them?

Does each of those relationships have a named person in the business who owns it?

Do you know what the business has committed to beyond paying the invoice, such as notice periods or minimum volumes?

Could you say how much the business spent with suppliers last year?

Do you know what renews or lapses in the next 90 days?

If most answers were "Yes".

If most answers were "No".

Most of your answers were "I'd have to check".

Is poor data quality a challenge in supplier management?

Is late procurement engagement
the biggest barrier to value?

Are procurement teams monitoring real-time risk?

Top Rated Solution for Vendor and Contract Lifecycle Management

Book your Free Demo of Gatekeeper

Your first 90 days in a new procurement role.

Your first 90 days in your new procurement role depend on how much you can already answer about what you've inherited.

Could you produce a list of every supplier the business pays without asking anyone to look for them?

Does each of those relationships have a named person in the business who owns it?

Do you know what the business has committed to beyond paying the invoice, such as notice periods or minimum volumes?

Could you say how much the business spent with suppliers last year?

Do you know what renews or lapses in the next 90 days?

If most answers were "Yes".

If most answers were "No".

Most of your answers were "I'd have to check".

Is poor data quality a challenge in supplier management?

Is late procurement engagement the biggest barrier to value?

Are procurement teams monitoring real-time risk?

Is late procurement engagement
the biggest barrier to value?