Vendor management - quick start guide

You manage dozens of vendors, each with their own contracts, risk profiles, SLA commitments, and performance expectations. Right now, that information lives across spreadsheets, email threads, and someone's memory. This schema brings it all into one place.

The Vendor Management schema gives you eleven object types covering the full third-party lifecycle: vendor registration, contact management, contract tracking, risk assessment, performance reviews, SLA monitoring, spend analytics, and issue resolution. Everything links back to the vendor, so you can see a supplier's complete relationship with your organisation at a glance.

---

When to use this schema

Deploy Vendor Management if you tick two or more of these:

• You manage 10 or more active vendors and need structured oversight

• You need formal risk assessments for third parties (SOC 2, ISO 27001 requirements)

• You have multiple contracts with different renewal dates and need proactive expiry management

• You track SLA commitments from vendors and need breach detection and credit claim evidence

• You want spend analytics by vendor, category, and period to spot consolidation opportunities

tip

Pro tip: If you only need vendors as reference data for other CIs (servers, applications), use Core Schema's Vendor object type instead. This schema is for organisations that treat vendor management as a discipline, not just a lookup table.

---

Schema overview

The 11 object types

Object Type	Purpose	Key Relationships
Vendor	Central hub: the third-party organisation	Parent of all other objects
Contact	Key personnel at vendor organisations	Belongs to a Vendor
Contract	Formal agreements governing the relationship	Linked to a Vendor
Product/Service	Specific offerings provided by vendors	Provided by a Vendor
Risk Assessment	Formal risk evaluations and overall ratings	Assessed for a Vendor
Risk Factor	Individual risk items from assessments	Child of Risk Assessment
Performance Review	Periodic vendor performance evaluations	Assessed for a Vendor
SLA	Service level agreement commitments	Governed by a Contract
SLA Performance	Actual performance against SLA targets	Measured against an SLA
Spend	Vendor expenditures for budget tracking	Related to a Vendor
Issue	Problems, incidents, or disputes	Related to a Vendor

Schema architecture

Vendor (Central Hub)
                           |
       +-------------------+-------------------+
       |          |        |        |          |
    Contact   Contract  Product/ Risk       Spend
       |          |     Service Assessment    |
       |          |        |        |         |
       |         SLA       |     Risk         |
       |          |        |     Factor       |
       |     SLA Perf      |                  |
       |                   |                  |
       +-------- Issue ----+------------------+
                           |
                 Performance Review

Screenshot coming soon

Every relationship flows through or back to the Vendor, so you can always see a supplier's complete picture: who works there, what they provide, how they perform, what they cost, and where the risks sit.

Reference types

The schema defines four colour-coded reference types for visual clarity in Assets:

Reference Type	Colour	Connects
Provided By	Blue (#0052CC)	Products/services and contacts to their vendor
Assessed For	Red (#FF5630)	Risk assessments and performance reviews to their vendor
Governed By	Green (#00875A)	Contracts to their vendor; SLAs to their contract
Related To	Purple (#6554C0)	Issues, spend, risk factors, and SLA performance to parent objects

---

Prerequisites

Before deploying, confirm you have:

• Jira Service Management Premium or Enterprise licence (Assets requires Premium tier minimum)

• Object Schema Manager or Jira Admin permissions

• An understanding of your vendor landscape: who your key suppliers are, which contracts are active, and where your risk exposure sits

• Familiarity with basic Assets concepts (object types, attributes, references)

---

Documentation

This guide is split into focused sections. Start with the object types, then move to deployment.

Vendors, contacts, and contracts Complete attribute reference and implementation guidance for the four core entity types: Vendor, Contact, Contract, and Product/Service. Covers naming conventions, status workflows, strategic importance assessment, and contract lifecycle management. (~8 min read)

Risk, performance, and SLAs Attribute reference and best practices for Risk Assessment, Risk Factor, Performance Review, SLA, SLA Performance, Spend, and Issue object types. Includes risk scoring methodology, performance scorecard framework, SLA penalty structures, and issue escalation procedures. (~10 min read)

Deployment and operations Four-phase getting started plan (vendor registry, contract documentation, risk programme, ongoing operations), AQL query library, integration patterns for procurement/finance/GRC systems, common pitfalls, troubleshooting, and FAQ. (~8 min read)

---