# Sample discovery workflow — Purchasing approval

ILLUSTRATIVE ONLY. Fictional process, not a client engagement or approved control design.

## Problem
Purchase requests arrive through email. The requester cannot see whether a request needs clarification or is waiting for review.

## Intended users
Requester and designated reviewer. Role assignment and authorization require validation.

## Proposed flow
Draft → Submitted → Review → Approved
Review → Needs clarification → Revised → Review

## Decisions to confirm
- Required request fields and supporting evidence.
- Who may review or approve each request.
- Whether a requester may approve their own request.
- How revisions affect an earlier approval.
- Which system, if any, receives an approved request.

## First-release boundary
Create and review a request, record a decision note, and show current status. No purchase order is issued and no funds are committed in this sample.

## Candidate success measure
Ability of a representative user to identify the current status and next owner during a usability review. No measured result is claimed.