IT vendor management is how you keep control of the companies your IT runs on. On a small team, it comes down to one register, one renewals calendar, and a named owner per vendor.
We build SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone. This guide covers the vendor management process, wherever you keep the records.
Key takeaways
Definition
IT vendor management is the ongoing work of picking IT suppliers, agreeing terms, checking delivery, controlling their risk, and ending each relationship cleanly.
U.S. bank regulators describe the same life cycle in five stages: planning, due diligence and selection, contract negotiation, ongoing monitoring, and termination.
So what is vendor management on a team of three? The same five stages, scaled down for the vendors that matter less.
Vendor procurement is one stage inside vendor management: finding, comparing, and buying. The rest of vendor management covers the years after the purchase order: renewals, account manager changes, and service that slips or holds. A vendor management system (VMS) is different: enterprise software for procuring and managing contractors and contingent staff.
IT vendors fall into five groups, and each needs slightly different fields.
| Vendor type | Examples | What usually goes wrong | Record first |
|---|---|---|---|
| Hardware and resellers | Laptops, firewalls, switches, printers | Warranty lapses, wrong part, slow replacement | Order numbers, warranty end, RMA route |
| Software licenses | Accounting, design tools, antivirus | True-up bills, unused seats, version end of life | Seat count, renewal date, license owner |
| SaaS | Email, file storage, backup, CRM | Auto-renewal, admin account tied to one person | Admin accounts, notice period, data export path |
| Internet and telecom | Office internet, phone system, mobile plans | Long terms, missed speeds, slow repair | Circuit ID, contract end, notice period, repair line |
| MSP, MSSP, and contractors | Outsourced helpdesk, security monitoring, cabling | Broad access nobody reviews, unclear scope | Their access to your systems, SLA, escalation contacts |
Vendor management matters because your vendors carry part of your security and your uptime.
| Event | Source and period | Figure |
|---|---|---|
| Breaches involving a third party | Verizon 2026 Data Breach Investigations Report, 2025 data | 48% of all breaches |
| Faulty CrowdStrike update | Microsoft estimate, July 2024 | 8.5 million Windows devices |
Source: Verizon; Microsoft.
No vendor management register stops a faulty update. It tells you which vendor sits under which service, and whom to call.
One r/sysadmin member found a domain had expired only when mail to it bounced, because it wasn't set to auto-renew.
On a team of three, vendor management lands on whoever signed up first, unless someone owns it. Our IT department structure guide shows how to give that ownership a name.
You can't manage a vendor nobody wrote down.
You don't need software or a policy binder for vendor management. You need four inputs and an afternoon for the first inventory pass. Give each field you can't fill an owner and a due date.
Write the rules on one page: who may sign a vendor contract, the spend that needs a second approver, and where contracts live. That page is your vendor management policy until you outgrow it.
The vendor management process below runs in order the first time. After that, steps 5, 7, and 8 repeat on their own schedule.
Make one row per vendor from the payments, contracts, and admin accounts you gathered. NIST's quick-start guide says to keep a record of all suppliers, prioritized by criticality.
Example: a backup service billed through your distributor still gets its own row and admin login.
Common mistake: stopping at the accounts payable list. Card-paid SaaS and free tools often don't show up there.
NIST suggests three criteria: how important the service is to the business, how sensitive the data the vendor holds is, and how much access it has to your systems. Use three tiers, and give each vendor its worst result.
Tier 1 stops the work, holds sensitive data, or has admin access. Tier 2 slows the work or holds limited data. Tier 3 is easy to replace and has neither. The tier sets how closely vendor management follows that supplier.
Example: the remote management agent on every laptop is tier 1 for its access alone. So is a cheap file-sharing tool holding client contracts.
Common mistake: ranking by spend. A $12 a month password tool can hold more risk than a $900 a month copier lease.
NIST CSF 2.0 asks for planning and due diligence before you enter a supplier relationship. Write your must-haves, tied to the service outcome you need, before the first demo. Score every candidate against them. Get quotes for the same scope, and verify one must-have through a reference call or a short service test.
Add three questions. Can the vendor meet its obligations, financially and operationally? Can it recover from its own outages? Does it rely on subcontractors that add risk?
Example: for a backup vendor: restore time, where the data sits, and how you get it back.
Common mistake: letting the demo set the criteria.
Check five clauses: term, auto-renewal, notice to cancel, service levels, and what happens to your data. Look for limits on the vendor's use and retention of your data, including its return and destruction.
Find out when the vendor must tell you about a disruption. Put security requirements in the contract, scaled to how critical the supplier is.
Renewal is your best chance to change terms. One r/ITManagers member wrote: "At renewal, I built a penalty clause into the SLA which they agreed to."
After signing, add the vendor to the vendor management register and run a short handoff. Create named admin accounts, grant only the approved access, and record who pays and your support entitlement. Then open one test case to prove the support route works.
Example: a SaaS order form renews yearly, with 30 days' notice by email to an address in the fine print.
Common mistake: clicking through a SaaS agreement without finding its notice period.
Subtract the notice period from each end date to get a working notice deadline. Confirm the contract's controlling date and whether notice counts when sent or received, then send early.
Our starting point: set an internal decision date 30 days before the notice deadline, or 60 to 90 days if a switch means a migration.
Put both dates on a shared vendor management calendar or as dated tasks with reminders, owned by the vendor's internal owner. Record how notice must be sent, and keep the confirmation.
Example: a domain set to renew by hand gets a task 30 days before expiry, assigned to the person who holds the registrar login.
Common mistake: calendaring the end date. For an auto-renewing contract, the cancellation window may already have closed.
For tier 1 and tier 2 vendors, write down response and repair commitments, the support route, your customer ID, and escalation contacts above first-line support. NIST CSF 2.0 says relevant suppliers belong in incident planning, response, and recovery. The vendor rows of your escalation matrix should point to these contacts.
Where vendors depend on each other, compare their support hours and restore commitments. When two vendors blame each other, one internal incident owner opens a case with both, records both case IDs, and coordinates until one vendor owns the fix.
Move vendor logins off personal inboxes. Give each technician a named account with MFA wherever the vendor allows it. For vendors that allow only one login, one r/ITManagers member suggests "a password manager that supports totp and a shared mailbox or distribution group." Limit that shared entry to those who need it.
Example: the telecom escalation line sits in the vendor management register next to your circuit ID, so whoever holds the outage ticket can quote both.
Common mistake: keeping the escalation contact in one technician's phone.
Check whether the vendor met its service level agreements, and compare its reports with your own records. Tickets count as evidence only with the vendor's case ID, report, first-response, and restore times, and the contract clock. For uptime, keep monitoring data for the measurement period. Add exclusions and the credit claim deadline.
Check credit eligibility after each incident and file before the contract's claim deadline; don't wait for the scheduled review.
As a starting point for vendor management reviews, score tier 1 vendors twice a year and tier 2 once a year. Watch for changes in the vendor itself: new owners, money trouble, or a leadership shuffle.
Share the vendor management scorecard with each tier 1 vendor, and agree corrective actions with an owner and a date for each.
Example: twelve tickets against the internet provider this year, three past the repair commitment.
Common mistake: reviewing only when something breaks, with no baseline.
Offboarding is the last stage of vendor management. NIST CSF 2.0 says supply chain plans should cover what happens after a service agreement ends. Plan how and when the vendor's access is removed, and when you'll confirm your data was returned or destroyed.
Run the exit in order. Confirm the termination terms and send notice as the contract requires. Export your data and check it opens. Test the replacement, then cut over.
Only then remove the vendor's accounts, agents, API keys, and VPN access, and change shared passwords it knew. Confirm deletion under the agreed retention terms. Recover your equipment, confirm what each side still owes, and settle the final invoice.
Example: the old backup vendor keeps running until a test restore from the new one succeeds.
Common mistake: cancelling before the export. Once the account closes, the export path may close with it.
A vendor management scorecard turns "they've been slow lately" into evidence for a renewal. Score five lines 1 to 3, each against its own test: 1 falls short, 2 meets it, 3 does better.
| Line | What you check | Where the evidence is | If it falls short |
|---|---|---|---|
| Service levels | Response, repair, and uptime as promised | Case IDs with report, first-response, and restore times in your tickets; monitoring data for uptime | Ask for a corrective plan; claim credits you can document |
| Escalation | Named contacts answered | Ticket notes on each escalation | Ask for new contacts or another support level |
| Billing | Invoices match the contract and the seat count | Invoices against the register's cost line | Ask for a corrected invoice |
| Security | Agreed security controls in place, issues fixed, incidents and changes reported on time | Vendor notices and security reports, your incident log | Investigate at once, whatever the other lines score |
| Fit | Still needed, at the size you pay for | Active users, licenses assigned | Cut seats or scope at renewal |
The score feeds a decision. Our starting rule: all 2s or better makes the vendor eligible for renewal. Confirm the new price, terms, budget, and any open security issue before you approve.
A security failure overrides the scores: investigate when it happens, not at the next review. A 1 on service, escalation, or billing gets a written request for correction with a date. No correction by the decision date: renegotiate or price a replacement.
Before buying or renewing, check the vendor management register for overlap: a tool or bundled service you already pay for. Then compare the proposed price with a current quote.
Don't count on service credits to cover an outage. One r/ITManagers member wrote that SLA reimbursements usually "specifically exclude any monetary impact on the business." Use the evidence to negotiate renewal terms.
On a small team, the risk side of vendor management comes down to six questions. NIST's guide says requirements should match a supplier's criticality. Our starting point: ask tier 1 vendors all six, and everyone else the first two. If either answer shows serious data or access exposure, move the vendor to tier 1.
| Risk | Question to ask | Register field |
|---|---|---|
| System access | Which admin accounts, agents, or VPN access does it hold? | Their access to us |
| Data | What of ours does it store, and how does it come back? | Our data they hold |
| One-person accounts | Whose inbox gets the login and the second factor? | Admin logins |
| Concentration | What stops if this one vendor fails? | Tier, who uses it |
| Fourth parties | Which subcontractors or hosts does it depend on? | Relies on |
| Vendor health | Has it been bought, cut staff, or changed terms? | Last review notes |
Security and access. A vendor with an admin account on your tenant is part of your attack surface. Fourth parties, your vendors' own vendors, add risk too.
Concentration. One vendor holding several critical services saves effort until it fails. After a registrar locked one member's domains, an r/sysadmin reply drew the lesson: "Good reminder though to never put your nameserver, registrar and hosting eggs in one basket." Fewer vendors also mean fewer contracts, so split only where one failure would stop everything.
Watch out
For hardware vendors, track warranty dates per device, as closely as contracts. Our warranty tracking guide covers the fields and the monthly check.
Copy one block per vendor into a spreadsheet, your documentation tool, or a plain-text file. That's where your vendor management register lives. Give each contract or subscription its own contract section, so every renewal clock shows.
Vendor management register · plain textVENDOR MANAGEMENT REGISTER: ONE BLOCK PER VENDOR
Updated: [date] · Vendor management owner: [name]
VENDOR
Name: [vendor]
Tier: [1 = stops work, sensitive data or admin access · 2 = slows work or limited data · 3 = easy to replace, neither]
Internal owner: [name] Backup owner: [name]
Who uses it: [teams, sites, clients]
Contract held by: [us / client] Signs, approves changes, cancels: [name]
ACCESS AND DATA
Their access to us: [admin accounts, agents, API keys, VPN]
Our data they hold: [what, where]
Admin logins: [named accounts with MFA; shared vault entry only if forced]
Relies on: [key subcontractors or hosting, if known]
CONTRACT (ONE SECTION PER CONTRACT OR SUBSCRIPTION)
Contract or order form: [link]
Start / end: [dates, with year] Auto-renews: [yes / no]
Notice to cancel: [days; method and address]
Notice deadline: [end date minus notice period; confirm against the contract]
Decision date: [notice deadline minus 30 days; 60 to 90 if switching means migrating]
Notice sent: [date, method, where the confirmation is saved]
Cost: [amount, billing period] Paid by: [card / invoice / client]
SERVICE
SLA: [response, repair, uptime, credits, exclusions, claim deadline]
Support route: [phone, portal, email] Customer ID: [ID]
Escalation contacts: [account manager, escalation manager]
Last review: [date, score] Next review: [date]
Last review notes: [changes in owners, finances, terms, or service]
Decision / action: [renew / correct / cut scope / renegotiate / replace] Owner: [name] Due: [date]
EXIT (IN THIS ORDER)
[ ] Termination terms confirmed, notice sent, confirmation saved
[ ] Our data exported and checked
[ ] Replacement tested, cutover done
[ ] Vendor accounts, agents, API keys, and VPN access removed; shared passwords changed
[ ] Deletion confirmed in writing under the agreed retention terms
[ ] Our equipment returned, remaining obligations confirmed, final invoice settled
[ ] Register and runbooks updated
Say you run an MSP with three technicians. The first pass of the vendor management register turns up seven vendors behind your own service. Five of them are tier 1.
| Vendor | Tier | Owner | Access and data | Notice deadline and decision date |
|---|---|---|---|---|
| Office internet provider | 1 | Owner | Access: router portal login, to verify. Data: none stored, to verify | Ends June 30, 2027; 60 days' written notice by May 1, 2027; decide by April 1, 2027 |
| Remote management tool | 1 | Senior tech | Access: agent on every client device | Renews March 15, 2027; 30 days' notice by Feb 13, 2027; decide by Dec 15, 2026 |
| Backup service | 1 | Senior tech | Data: holds client backups | Monthly via distributor; notice period still to find |
| Security monitoring provider | 1 | Owner | Access: reads client security logs | Renews Sept 1, 2027; 90 days' notice by June 3, 2027; decide by April 4, 2027 |
| Email and office suite | 1 | Owner | Data: holds company mail and files | Annual per subscription; dates per order form |
| Phone system | 2 | Second tech | Access: none known. Data: voicemail, to verify | Monthly; 30 days' notice |
| Hardware reseller | 3 | Second tech | Access: none. Data: order history only | Per order; no term |
Each gap gets an owner and a Dec 1, 2026 deadline in the vendor management register. Internet and suite details go to the owner, the backup notice period to the senior tech, voicemail to the second tech.
Example
End date June 30, 2027, notice 60 days. Count back 60 days and the working notice deadline is May 1, 2027. Swap in your own end date and notice period.
The decision date sits 30 days before that, on April 1, 2027, so a competing quote has time to arrive.
In March 2027 the owner runs the scorecard: twelve tickets against the internet provider, three repairs past the commitment. Service levels score a 1. The owner sends the account manager the three case IDs, asks for a written corrective plan, and gets one competing quote.
No plan arrives. The competing quote confirms installation before June 30, so on April 1 the owner decides to switch. Written notice goes out April 10, ahead of the May 1 deadline, and the confirmation goes in the vendor management register.
The remote management tool and security monitoring provider get 60 days, since a switch means a migration.
Client vendors need one more line in the vendor management register. When a client holds its own contract, mark it in "Contract held by" and name who signs, pays, approves changes, and cancels. If you run vendor management for internal IT, the rows barely change: client devices become staff laptops.
Check four signals each quarter against the vendor management register.
If a check slips twice, find out why before you change your vendor management routine. Missing data, an owner without authority to cancel, and too little lead time each need a different fix.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
How this works in SherpaDesk
For your own staff or the businesses you support, you get a helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
Your vendor management register stays in your spreadsheet or documentation tool. In SherpaDesk, each decision date and notice deadline goes on a To Do with a due date and reminder, assigned to an account.
Your QuickBooks Online vendors sync into SherpaDesk, and vendor payments can be pushed to QuickBooks Online as Bills. In Asset Manager, each asset tracks its service costs and total cost of ownership.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, so a team of three on Base Camp pays $90 a month ($80 billed annually). Asset Manager comes with High Camp: $55 per agent per month ($50 billed annually). Both start with 14 days free, no card.
Who this isn't for
Enterprise procurement teams running third-party risk management platforms, with security questionnaires and hundreds of suppliers. This vendor management approach is a register, a calendar, and a review habit for a small team.
Vendor management is knowing, for every company you pay for IT, what it costs, what it promised, what it can reach, and when you must give notice. See the definition.
An IT vendor manager keeps the vendor management register current, runs the reviews, owns the renewal decisions, and follows up when a vendor has to fix something. On a small team, vendor management is a part-time job, often for the IT lead or MSP owner, because renewals involve money.
IT vendors supply what your IT runs on: hardware, software licenses, SaaS, internet and telecom, and outside providers such as MSPs and contractors. The vendor types table shows what your vendor management register should hold for each.
Vendor management keeps each vendor delivering what you pay for, at a risk you chose, with an exit you can use. In practice, that means one register, a renewals calendar, scheduled reviews, and a planned exit. See the steps.
Procurement gets you to a signed order. Vendor management starts with that choice and runs until you leave, through monitoring, renewals, risk, and offboarding. On a small team the same person often does both, so one vendor management register should carry the vendor from first quote to exit.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.