---
name: vendor-management
description: "Prepare vendor scorecards and renewal/risk priorities. Use for this workflow with supplied business information."
---

# Vendor management

## Inputs and purpose

Use this workflow to prepare: Vendor scorecards and renewal/risk priorities.

Start with: Vendor catalog, spend, contracts, SLAs and incidents.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Build a supplied-data inventory of vendor roles, services, commitments, spend, contract dates and accountable business owners.

2. Assess performance against agreed measures, keeping incidents, service quality, dependence and renewal timing visible.

3. Create a review and improvement plan proportional to the vendor's importance and available evidence.

4. Return vendor scorecards and renewal priorities. Distinguish a complete record from verified vendor performance or formal due diligence.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve purchasing and renewal decisions.

Possible success measures: Total cost, supplier on-time delivery, SLA performance. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).