Procurement Practice Incident Report

---
name: procurement-practice-incident-report
description: |
  Respond to, record and learn from incidents involving businesses and public bodies buying goods and services in procurement departments.
  TRIGGERS - Use when a procurement officer needs a incident reporting & response for businesses and public bodies buying goods and services in procurement departments.
category: Procurement Practice
license: MIT
version: 1.0
---
# Incident Reporting & Response — Procurement Practice

Respond to, record and learn from incidents involving businesses and public bodies buying goods and services in procurement departments. The deliverable is a factual incident report and a lessons-learned action list.
This skill is written for a procurement officer working with businesses and public bodies buying goods and services in procurement departments.

## When to use
- You are a procurement officer preparing, delivering or reviewing this part of your work in procurement departments.
- You need a defensible, repeatable approach that produces a factual incident report and a lessons-learned action list.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Tender | a formal process inviting suppliers to bid |
| Specification | the detailed requirement a supplier must meet |
| Total cost | purchase price plus all associated costs of ownership |

## Workflow
1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if supplier failure is still live
2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in purchase orders
3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in procurement departments
4. **Step 4** - Support those affected, including honest communication with businesses and public bodies buying goods and services about what happened and what happens next
5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure

## Profession-Specific Components
| Component | Details for Procurement Practice |
|-----------|-------------------------------|
| Core documentation | purchase orders; supplier evaluations; tender documents; contracts |
| Core tools & equipment | e-procurement systems; supplier databases; spend analysis tools; contract registers |
| People involved | businesses and public bodies buying goods and services; the procurement officer; colleagues and other services in procurement departments |
| Primary record | purchase orders — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in procurement departments] | **Objective:** [What this must achieve] | **Audience:** [businesses and public bodies buying goods and services and other stakeholders]

The finished output is a factual incident report and a lessons-learned action list, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in purchase orders.
2. **Short-term:** Complete the workflow steps and record outcomes against savings delivered.
3. **Medium-term:** Review results, close actions, and update local procedures in procurement departments.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| savings delivered | Agree a local target and track the trend | Measured from purchase orders and reviewed on a set cycle |
| supplier performance scores | Agree a local target and track the trend | Measured from purchase orders and reviewed on a set cycle |
| order cycle times | Agree a local target and track the trend | Measured from purchase orders and reviewed on a set cycle |
| contract compliance | Agree a local target and track the trend | Measured from purchase orders and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: supplier failure.
- Never let this happen: fraud in purchasing.
- Never let this happen: contract deadlines missed.
- Work only within the competence and authority of a procurement officer; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to procurement departments's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A procurement officer in procurement departments applies this workflow for businesses and public bodies buying goods and services: they open
purchase orders, work through the five steps using e-procurement systems, and close by recording
the outcome against savings delivered and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)