Why change order SLAs mislead procurement leaders
Change order SLAs mislead procurement leaders because they measure the wrong moment: they report how long supplier confirmations took last month, after the amendments they describe have already gone stale or rolled downstream as someone else's exception. The metric can sit at a respectable percentage while unconfirmed changes quietly become receiving mismatches and invoice variances that nobody traces back to the SLA report. The gap sits at supplier confirmation, the step that turns a proposed change into an agreed one. A buyer can draft and send an amendment in minutes; getting the supplier to confirm the new quantity, date, or price depends on someone else's inbox, workload, and willingness to respond, and that is the step the SLA watches without touching.
A missed SLA and an incomplete confirmation are different problems
Treat every SLA breach as the same failure and the response ends up wrong half the time. A supplier who doesn't respond at all needs a follow-up, then an escalation, then possibly a phone call. A supplier who responds but confirms only part of the amendment, agreeing to the new quantity but silent on the delivery date, needs something different: someone to notice the response is incomplete and go back for the missing piece. Buried in a shared inbox, a partial confirmation often reads as done. It isn't, and it won't surface as a problem until the delivery date arrives and nobody prepared for it.
An SLA without a follow-up loop only reports failure after it happens
A percentage-confirmed-within-48-hours metric tells a procurement leader how the team did last month. It does nothing for the amendment sitting unconfirmed right now. By the time a breach shows up in a monthly report, the PO it describes may already be sitting on a receiving dock with the wrong quantity written into a system that hasn't heard about the change. Changing that outcome takes something watching each open amendment and acting before its deadline passes, while there's still time to do anything about it.
A breached confirmation surfaces somewhere else, weeks later
An unconfirmed amendment doesn't stay procurement's problem. If the quantity change never gets confirmed, receiving logs whatever actually arrives against a PO that still says the old number, and the mismatch shows up as a receiving exception. If the price change goes unconfirmed, the eventual invoice may not match either the old price or the new one, and AP inherits a variance with no clear resolution path. If the date change is silently ignored, a plant schedules production against a delivery that was never actually reconfirmed. In every case, the breach was visible in procurement's SLA report weeks before it became someone else's exception, and by the time it did, the person handling it had no idea a change order was ever involved.
Closing an amendment means someone follows every open one until it resolves
A stricter SLA target doesn't fix any of this on its own. What fixes it is a follow-up loop that doesn't depend on a person remembering to check: track every amendment against its deadline, flag non-responses automatically, and check whether a response covers every field that changed, since suppliers commonly answer the easy parts and stay quiet on the rest. A reply that confirms the whole change is a closed amendment. A reply that confirms half of it just looks like one, until the missing half shows up as someone else's exception.
Fragment's agents track every open amendment against its deadline, follow up automatically on non-responses, and flag partial confirmations for the specific fields still outstanding, so nothing rolls downstream as a receiving or invoice exception weeks later. It's one part of the exception-heavy work Fragment resolves across source-to-pay, alongside PO amendments and change orders upstream. See the workflows Fragment covers or book a demo.