Where to start with a fragmented purchasing workflow

Commerce Street Procurement · Workflow guide · Updated October 5, 2026

Follow one real purchase

Select a representative purchase and trace it from request through receipt and payment. Record where information is entered, who approves it, and how the next person knows the work is ready.

Look for waiting and rework

Incomplete requests, unclear ownership, and repeated data entry can create delays. Ask staff where they spend time chasing information. Distinguish a needed control from an avoidable administrative step.

Design a small, testable improvement

Clarify required fields, assign the next action, or document an approval path. Test the change with a small group before expanding it. A clear process should inform software decisions.

Measure whether the change helps

Compare a suitable baseline with the revised process. Look at turnaround time, returned requests, and staff feedback. Make sure an improvement in speed does not remove documentation or approvals that are required.

Make approval responsibility visible

Map who requests, reviews, orders, and confirms receipt. Record which decisions need approval under your organization’s policy and who handles exceptions. This is a process-mapping exercise, not a recommendation to remove controls or impose the same approval pattern on every organization.

Preserve the reason behind a decision

Keep the request, relevant product information, approval, supplier selection rationale, and order record connected where practical. Ask the people reviewing purchases which details they need. New York’s local-government competition guide provides a jurisdiction-specific reference for procurement review; other organizations should consult their own requirements.

Choose a small set of useful measures

The Harvard Government Performance Lab guide describes using data to identify operational bottlenecks. As a practical starting point, consider time to approval, requests returned for clarification, and orders requiring follow-up. Define the start and end of each measure so comparisons remain meaningful.

Ask whether the change helped the people using it

Include staff feedback and the quality of the outcome in your review. GAO’s procurement performance research highlights end-user participation and outcome measures. A faster request process is less useful if it creates more corrections or obscures the purchasing record.

Give technology a defined role

Use automation to reduce repeated entry, organize records, and surface status where the system supports it. Keep a named owner for exceptions and follow-through. Compare the result with the baseline before expanding the change to additional departments.

General educational guidance. Consider your organization’s circumstances and applicable requirements. Source references do not imply endorsement of Commerce Street.