Keep a vendor price-change log

Why this control matters

A useful vendor price changes control starts with a stated purpose. Record the change and the approval date, then compare the record with that purpose rather than the busiest board.

What to check first

Begin with one test: compare the log with the purchase order. Keep the case that failed because a named mismatch is stronger evidence than a general complaint.

Build the routine

Put the vendor price changes review on a short weekly calendar. Open the queue, run the test, and leave one decision for each item.

Handle the exceptions

Log the exception when you see a price change applied before approval. Record why the normal rule missed it and where the fix belongs.

Review the evidence

Save the smallest useful evidence: the vendor, part, and effective date. A dated record lets the next person continue without asking you to remember.

What to change next

Finish with one controlled change. Use the evidence to require one approval for changes above a threshold, then set the next review date.

Common questions

What can an HVAC assistant prepare for vendor price changes? The assistant can gather the record, compare sources, label exceptions, and prepare a dated next action. Licensed technical decisions stay with the qualified technician.

What decision stays with the service manager? The service manager decides whether the vendor price changes evidence is sufficient and whether the job can move forward.

How should the team review vendor price changes? Sample one routine item, one exception, and one corrected item each week. Check the source, owner, next action, and close evidence.

Plan the next handoff

Choose one recurring queue with a known owner. Define its inputs, completion evidence, review point, and escalation triggers before adding volume.

A consultation can turn that first workflow into a role brief your team can inspect and improve.