Skip to content
       

Blog

/

Vendor Management in Property Management: The Lifecycle Guide

Vendor Management in Property Management: The Lifecycle Guide

A regional manager takes over thirty properties and inherits 140 vendors with them. Some are on contract, most are not. Some have a certificate of insurance on file, and nobody knows how many of those have expired. A few have been paid on the same day for eleven years without anyone checking a rate; one has not been used since 2023 but is still active in the payment system with bank details that were changed by email last spring. Asked which vendors are insured, under contract and paid on time, the honest answer is that the information exists somewhere across four systems and two filing cabinets, and it would take a week to assemble.

That is the normal state of vendor management property management teams inherit, and it is not a people problem. It is the absence of a lifecycle: a defined sequence of stages that every vendor passes through, each stage producing a record, and one file per vendor where those records live. This guide sets out that lifecycle in eight stages, the fourteen fields a vendor file needs, when to keep a trade in-house and when to contract it, what a bad vendor actually costs (with the arithmetic), and where each stage is covered in depth across the rest of this series.

Definition

Vendor management in property management is the process by which a property manager sources, compares, contracts, onboards, dispatches, pays, reviews and exits the third-party contractors and service providers who maintain a property, and keeps one record per vendor (the vendor file) that proves each step was done. RIOO describes this as the eight-stage vendor lifecycle. It differs from procurement (one stage), accounts payable (one stage) and insurance compliance (a control inside two stages), each of which is often mistaken for the whole.

At a glance

Question Answer
What is vendor management in property management? The process of sourcing, comparing, contracting, onboarding, dispatching, paying, reviewing and exiting the third parties who maintain and service a property, and keeping one record per vendor that proves each step was done
What are the stages? Eight: source, compare, contract, onboard, dispatch, pay, review, exit
What is a vendor file? The single record per vendor holding identity, tax, insurance, licences, contract, SLA, rates, banking, system access, work history, performance and status
Which trades should be in-house? Those with daily volume, low skill barrier and high response sensitivity (make-ready, basic plumbing and electrical on larger sites); contract the rest (HVAC, elevators, roofing, fire and life safety, specialist trades)
What does a bad vendor cost? In the worked example below, one missed emergency call cost $11,120 in direct expense against a $3,500 job, and put a $100,000 renewal at risk
Where does the data belong? In the same system that issues the work orders and pays the invoices, so the vendor file is built by normal operations rather than maintained separately

What vendor management is, and what it is not

Vendor management is the set of controls that sits between a property and the people it pays to keep it running. It is not procurement (which is one stage of it), not accounts payable (another stage), and not a compliance programme for insurance certificates (a control inside two stages). Treating any one of those as the whole subject is how portfolios end up with a perfect COI binder and a plumber who has not been rate-checked since 2019.

The reason it matters in property more than in most industries is that the vendor is often the only person the resident or tenant sees. The manager writes the work order; the vendor shows up, or does not. The lease promises habitability and the tenant's business depends on the roof; the contractor's crew delivers both. The vendor management property management teams run is therefore a resident experience process and a lease compliance process at the same time, and its failures surface as complaints, abatements and non-renewals rather than as line items.

The property management vendors a portfolio depends on fall into roughly four groups, and the lifecycle treats them differently: trade contractors called per work order (plumbing, electrical, HVAC, locksmiths, glazing); contracted services on a schedule (cleaning, landscaping, snow, pest, elevator maintenance, fire and life safety inspection); project contractors engaged per bid (roofing, paving, renovation, capital works); and professional services (legal, engineering, environmental, brokers). The stages below apply to all four; the depth at each stage scales with spend and criticality.

The eight-stage vendor lifecycle

The vendor management process is easiest to run, and to audit, as a sequence. RIOO's eight-stage vendor lifecycle (source, compare, contract, onboard, dispatch, pay, review, exit) is the framework used throughout this series. Each stage has an owner, an entry condition and a record it produces. A vendor cannot move to the next stage until the record for the current one exists.

Stage What happens Owner Record produced Covered in depth
1. Source Identify candidate vendors for a trade or project: referrals, trade associations, licensing boards, existing vendors' recommendations, the emergency roster Property or regional manager Candidate list with licence and insurance pre-check This guide
2. Compare Obtain and level bids or rate cards against a written scope; check references and capacity Manager with accounting for capital works Bid comparison sheet and award note, with losing bids retained Bid comparison template
3. Contract Agree the terms: scope, rates, service levels, insurance requirements, term, termination, payment terms Manager; legal for contracted services and projects Signed agreement and SLA Vendor SLA template
4. Onboard Collect and verify identity, tax forms, insurance, licences, banking; grant system access; safety induction; property rules Property accountant and manager Completed onboarding checklist; vendor record active Vendor onboarding checklist
5. Dispatch Issue work orders or purchase orders with scope, priority and price; vendor accepts, attends, completes, evidences Maintenance coordinator Work order with timestamps, photos and completion sign-off Vendor portal guide
6. Pay Match invoice to work order or PO, approve, pay on terms, record Accounts payable Matched invoice, approval trail, payment record, 1099 or CIS data Property management accounts payable basics
7. Review Score performance against the SLA and the scorecard; meet on a cadence; decide on renewal, probation or change Manager with the vendor Scorecard, review minutes, decisions Vendor scorecard and review cadence
8. Exit Terminate for cause, for convenience or at expiry; recover access, keys, credentials and warranties; settle the account; deactivate Manager and accounting Termination letter, off-boarding checklist, final reconciliation, vendor inactive Terminating a maintenance vendor

Two features of the sequence do most of the work. Stage 4 is the control point: a vendor with no completed onboarding record cannot receive a work order or an invoice approval, which forces the collection of tax, insurance and banking documents at the one moment the vendor is motivated to supply them. And stage 8 exists at all: most portfolios have no exit stage, which is why the payment system carries hundreds of active vendors nobody has used in years, each one an open door for a fraudulent invoice.

The vendor file: fourteen fields every record needs

The vendor file is the single record that the eight stages write to. RIOO's 14-field vendor file is the minimum record for a vendor relationship in property. Think of it the way you think of a lease abstract: a lease has parties, dates, terms, a ledger and an expiry, and so does a vendor relationship. A vendor abstract with the fields below answers the regional manager's question from the opening in one query rather than one week. (The lease equivalent, for comparison, is in our lease abstraction checklist.)

# Field What it holds Stage that writes it
1 Identity Legal name, trading name, entity type, address, principal contact, escalation contact Onboard
2 Tax status US: Form W-9 on file, TIN, 1099 reportable yes/no. UK: VAT number, CIS verification and deduction rate where the work is construction Onboard
3 Trades and coverage Trades the vendor is approved for; properties or regions covered; 24/7 availability Source, Onboard
4 Licences and certifications Licence numbers, issuing body, expiry; trade certifications (EPA 608, gas safe, electrical) Onboard, Review
5 Insurance General liability, workers' compensation, auto, umbrella limits; certificate expiry; additional insured and waiver endorsements on file Onboard, Review
6 Contract Agreement type (per-work-order, scheduled service, project), start and end dates, notice period, termination provisions, renewal date Contract
7 SLA Priority levels and the response, attendance and restoration times for each; service credit terms Contract
8 Rate card Hourly rates by trade and time band, trip charge, markup on materials, minimum charge, emergency multiplier; date last reviewed Compare, Contract, Review
9 Banking and payment terms Verified remittance details, verification date and method, payment terms, early payment discount Onboard, Pay
10 System access Portal user, mobile app, keys and fobs issued, gate and alarm codes, BMS or controller credentials Onboard, Exit
11 Work history Every work order and PO with dates, amounts, completion evidence Dispatch, Pay
12 Spend Year-to-date and trailing-twelve-month spend by property; share of trade spend Pay
13 Performance Scorecard results by period; SLA compliance; complaints; incidents; review minutes and decisions Review
14 Status Candidate, onboarding, active, probation, suspended, terminated, inactive; with the date and reason for the last change All

The last field is the one most systems lack and most audits ask for. A vendor with a status, a date and a reason is a vendor whose history can be explained; one that is simply "in the system" cannot be.

In-house vs contracted: the decision by trade

The question of whether to employ a trade or contract it is asked once at portfolio level and then re-asked at every growth step. Contractor management property teams run well depends on making that choice deliberately rather than inheriting it.

Factor Favours in-house Favours contracted
Volume Enough daily work to keep a technician busy (roughly 150 to 250 units per maintenance technician in multifamily is a common planning ratio) Intermittent or seasonal work
Response sensitivity Habitability items where the first hour matters (lockouts, no heat, active leaks) Items that can wait a scheduled visit
Skill and licensing General repairs, make-ready, basic plumbing and electrical within the technician's licence Licensed or certified work: HVAC refrigerant, elevators, fire and life safety, gas, high-voltage, roofing, structural
Liability Low-risk tasks High-risk tasks where the contractor's insurance and warranty carry the exposure
Equipment Hand tools and a van Specialist equipment (lifts, cranes, diagnostic gear)
Geography Properties clustered within a drive time Dispersed portfolio where travel kills technician utilisation
Cost structure Predictable salary and benefits with high utilisation Pay per job; no bench cost during quiet periods

Most portfolios land on a hybrid: in-house technicians for daily volume on larger sites, with contracted specialists for licensed trades and contracted generalists for the smaller or remote properties. The point of the table is to make the split explicit and to revisit it at each acquisition, because a portfolio that has grown from 800 units to 2,400 by acquisition is usually still running the vendor model of the 800-unit company.

Whichever side of the line a trade sits on, the vendor lifecycle still applies to the contracted side, and the same dispatch, evidence and cost tracking applies to the in-house side so that the two can be compared on cost per work order rather than on instinct.

The cost of a bad vendor: a worked example

The invoice is the smallest part of what a failed vendor costs. The example below is built from the kind of incident every portfolio manager has seen; the figures are illustrative but the arithmetic is the point.

A rooftop HVAC unit serving an 8,000 square foot retail tenant fails on a Friday in July. The tenant pays $20,000 a month. The contracted HVAC vendor's SLA requires attendance within four hours for a P1 failure; the vendor acknowledges the call and then does not attend for three days, citing a staffing problem. The lease gives the tenant a rent abatement for each day the premises are untenantable after 24 hours' notice.

Item Calculation Cost
Rent abatement 3 days at $20,000 ÷ 30 $2,000
Emergency replacement vendor Standard repair $3,500 at a 2.4× emergency and weekend rate $8,400
Management time 12 hours across the manager, coordinator and accountant at $60 $720
Direct cost of the incident   $11,120
The job as it should have cost Standard repair by the contracted vendor $3,500

The direct cost is 3.2 times the price of the job. It does not include the contracted vendor's invoice for the visit it eventually made, the tenant's claim for spoiled stock, or the complaint escalated to the owner. And when the lease comes up eighteen months later, the tenant cites the July failure in declining to renew. Three months of vacancy at $20,000 is $60,000; leasing commission and tenant improvement contribution on the replacement lease add roughly $40,000. The renewal exposure attributable to one missed call is in the region of $100,000.

Set against that, the cost of the controls that would have caught it (a rate card and SLA in the contract, a secondary vendor on the emergency roster, a scorecard that would have shown two earlier missed attendances) is a few hours of setup. The economics of vendor management are almost always this lopsided: the controls are cheap and the failures are expensive, and the failures are paid for in abatements, emergency premiums and vacancy rather than in a line called "vendor management".

Key facts

  • Vendor management in property management has eight stages: source, compare, contract, onboard, dispatch, pay, review and exit (RIOO's eight-stage vendor lifecycle).
  • A property vendor file needs fourteen fields, of which the status field (candidate, active, probation, suspended, terminated, with date and reason) is the one most often missing.
  • Onboarding is the control point: a vendor with no completed onboarding record should not be able to receive a work order or an invoice approval.
  • A common planning ratio for in-house multifamily maintenance is one technician per 150 to 250 units; licensed and high-liability trades (HVAC, elevators, fire and life safety, roofing) are usually contracted.
  • In RIOO's worked example, one missed emergency HVAC call cost $11,120 in direct expense against a $3,500 job (3.2×) and put roughly $100,000 of renewal value at risk.
  • Property vendors fall into four groups: per-work-order trade contractors, scheduled service providers, per-bid project contractors and professional services.
  • US vendors need a Form W-9 on file and a 1099 reportable flag; UK construction vendors need CIS verification and a deduction rate.

Where each stage is covered in depth

This guide is the map. Each stage has its own post with the templates and worked examples.

The vendor bid comparison template covers stage 2: how to level three bids for scope, exclusions, allowances and warranty so the low bid and the low cost are the same number. The vendor SLA template covers stage 3: the three clocks (acknowledge, attend, restore), the priority matrix and the clauses. The vendor onboarding checklist covers stage 4, including insurance minimums by trade, bank-detail verification and the emergency vendor roster. The vendor portal guide covers stage 5 from the vendor's side: what vendors expect from a portal and why adoption fails. Stage 6 is covered by property management accounts payable basics. Stage 7 splits into what to measure, in the vendor scorecard, and when to meet and what each meeting may decide, in the review cadence. Stage 8 is terminating a maintenance vendor.

Three controls run across every stage. Insurance is covered in COI tracking (what a certificate proves and which endorsements matter) and vendor compliance (why document collection is not a programme). Dependency is covered in the vendor you cannot replace.

Running it in one system

The lifecycle above can be run on a spreadsheet and a shared drive for a handful of properties. It stops working at the point where the person who knows which vendor is on probation is not the person approving the invoice, which in practice is around the second office or the fiftieth vendor. From there the vendor file has to live where the work orders and the invoices live, so that the record is written by normal operations: a closed work order becomes work history, an approved invoice becomes spend, an expired certificate blocks the next dispatch.

In RIOO on NetSuite, the vendor management and accounts payable module holds each vendor's profile with its contacts, bank details, payment terms, purchase history, past payments and credit memos, runs purchase requests through approval to a purchase order, matches invoices to the PO and receipt with duplicate flagging, and schedules payments on terms, with spend reports by vendor, category and date. Work orders are created, prioritised, assigned to technicians or vendors and monitored to completion in service request and task management, which also centralises vendor communication, documentation and task assignment and supports comparing proposals, monitoring performance and managing contracts. How the vendor side is set up inside NetSuite specifically is in our NetSuite vendor management guide for real estate.

Put the lifecycle to work. Start with stage 4: the vendor onboarding checklist has the full field list, the insurance minimums by trade and the emergency roster template. If you would rather see how vendor records, work orders and invoices sit in one system, book a walkthrough of RIOO's vendor management and AP module.

Frequently asked questions

Q1. What is vendor management in property management?
The vendor management property management teams run is the process by which a property manager sources, compares, contracts, onboards, dispatches, pays, reviews and exits the third parties who maintain and service the property, and the record kept for each vendor proving that each step was done. It covers trade contractors, scheduled service providers, project contractors and professional services.

Q2. What should a vendor file contain?
Fourteen fields: identity, tax status, trades and coverage, licences, insurance, contract, SLA, rate card, banking and payment terms, system access, work history, spend, performance and status. The status field (candidate, active, probation, suspended, terminated) with a date and reason is the one most often missing and most often asked for at audit.

Q3. Should maintenance be in-house or contracted?
It depends on the trade and the portfolio. In-house suits daily-volume, response-sensitive, low-licence work on larger or clustered sites (a common planning ratio is one technician per 150 to 250 multifamily units). Contracted suits licensed and high-liability trades (HVAC, elevators, fire and life safety, roofing), intermittent work and dispersed portfolios. Most portfolios run a hybrid and should revisit the split at each acquisition.

Q4. How much does a bad vendor cost?
Far more than the invoice. In the worked example above, one missed emergency HVAC call cost $11,120 in abatement, emergency premium and management time against a $3,500 job, and contributed to a non-renewal with roughly $100,000 of vacancy and re-letting cost. The controls that prevent it (an SLA, a secondary vendor, a scorecard) cost hours to set up.

Q5. Do I need separate vendor management software?
Not necessarily. The vendor file is built by the same events that already happen in a property system: work orders, invoices, payments, certificate expiries. What matters is that those records are in one place and that a vendor's status controls whether it can be dispatched and paid. Separate tools help with insurance monitoring and bidding at scale, but they should feed the operating system rather than hold a second copy of the vendor list.

Related reading