Published November 4, 2026
A protocol for measuring how long a refund exception waits for evidence, owner review, and customer communication, with separate clocks for each stage. The notes below keep the customer request, the approved source, and the next owner in one reviewable place. They are written for a support team that may hand the case to another shift. Use the routine to review one ordinary case and one exception before changing the workflow.
Question and scope
This study asks how long a refund exception takes from the first recorded request to a documented decision and customer update. It separates evidence gathering, owner review, and communication. It does not measure the financial outcome or the customer's satisfaction. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Set the scope to one support queue and a fixed period. Record the refund policy, the approval thresholds, and the owner roles in force. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Population and unit
The unit is one refund exception tied to one order or payment. An exception that is reopened after a correction remains one unit with a linked event. Record the order key, the reason, the owner, and the request time. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Include exceptions still open at the cutoff and exceptions declined by the owner. Exclude routine refunds that followed the normal path without an exception. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Definitions and measures
Measure the time to evidence complete, the time to owner decision, and the time to customer update. A single total hides which stage is responsible for the delay. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Separate a missing customer document from a missing internal approval and from a customer who did not respond. These are different delays with different remedies. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Evidence standard
Collect the case record, the payment reference, the return evidence, the approval log, and the customer message. Mask payment details in the analysis table. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
If a decision was made by phone, record the time and the person. A verbal approval should be documented before the payment moves. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Sampling and collection
Sample exceptions rather than orders, then review every stage within the selected case. Stratify by reason and amount band. Use a random or systematic start. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Include an exception that crossed a month-end close and one that required a backup owner. Those cases test the real handoff. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Analysis and reporting
Report the number of exceptions, the median time to evidence complete, the median time to decision, and the median time to customer update. Show the open and declined counts. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Inspect the slowest cases. Was the evidence missing, the owner unavailable, or the customer message delayed? The pattern should lead to one process change. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Limitations
The record may not capture a phone call or a conversation at the desk. State the unobserved evidence and avoid treating a missing note as a failure. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
The study describes one queue during one window. It is not a financial audit or a customer-satisfaction benchmark. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Review and next action
Choose one change: a required evidence field, a decision-owner backup, a customer-update template, or a weekly aging review. Assign the owner and the next sample date. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
Repeat the study after the change and compare the same clocks. Close when the owner accepts the result. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.
