That night Nadine stayed in her regional office after the cleaning crew finished. On her screen were the nineteen disputed claims, twelve summaries carrying Tessa's receiving identifier, and a note from the human resources director asking why an employee with seventeen years of service had been dismissed without a proper incident review. Nadine had told herself for years that a good regional director could manage by watching trends rather than individual transactions. Now she was looking at the individual transactions and seeing how a trend might be produced by the person measured against it.
She opened the appeal-routing policy she had signed the previous winter. The purpose had been to shorten resolution times by allowing local managers to close disputes involving store-level inspections. She had praised the change at a leadership meeting because the average days-open number fell almost immediately. It had never occurred to her to ask how many growers received answers they considered meaningful.
At eleven-forty, Nadine sent headquarters a second preservation request, this one covering the original receiving events, edits to supplier-fault status, related emails, and all pending or closed appeals involving Graham's store. She copied the legal and compliance teams and asked that no single person with a direct interest in the claims be allowed to approve their closure. Then she wrote a sentence in a private notebook she rarely used.
"A resolved complaint is not always a resolved problem."
It was not an apology. Nadine knew that. It was the beginning of an admission she would have to make to people who had trusted her to look more closely than she had.
The headquarters event history arrived in the regional office at eight-twenty the following morning. It was not elegant. The report ran through dozens of columns of account numbers, access tokens, and machine-generated time stamps, the sort of document that makes an ordinary person feel as though the information has been hidden by being made difficult to read. Nadine asked a systems analyst named Oliver Chen to sit beside her and explain what each column actually meant.
Oliver had worked on Bridgeville's receiving platform for eight years. He knew that the store-facing summaries showed one final status per load because the design team believed customers wanted simple answers and employees should not have to navigate a history of edits. The full event log existed to satisfy audit requirements, but ordinary purchasing staff rarely asked for it. When Nadine told him a store manager might have used the difference to shift costs onto farms, Oliver looked at the screen with an expression that suggested he had just discovered an unintended use for something he had helped build.
They began with the earliest disputed shipment for which Tessa's records were complete. Lot 309 had arrived on Thursday, August sixth, at 3:42 in the afternoon. Tessa Green had entered the receiving information and accepted the load, noting that the fruit temperature was within the documented range and that no visible issue justified refusing it at the dock. Her time record showed that she clocked out at 4:30.
At 7:16 that evening, Graham Vol had used his manager authorization to replace the accepted status with supplier fault. The system contained no subsequent inspection record, no photographs, no sample count, and no explanatory report identifying a new problem discovered after Tessa left. The final summary retained Tessa's employee number in its intake field, and the ordinary printout placed that number close enough to the rejection code that it could easily be mistaken for her approval.