The automation problem appeared at seven-fifteen. Two trailers had been assigned to the same dock door, and an inbound unit carrying seasonal electronics had been placed in a lane reserved for a shipment scheduled to depart before midnight. Three drivers sat idling, waiting for instructions that contradicted one another on their tablets. Cody came over with his scanner and frowned at the screen. "Didn't the upgrade fix this last month?" he asked.
"It fixed one version of it," Nolan answered. He pulled up the manifest identifiers and compared the door assignments against the actual staging lanes, careful not to override any record until he understood where the discrepancy had begun. "Software can give you an answer quickly and still give you the wrong answer," he told Cody. "Our job is to check whether the answer fits what's standing in front of us."
Cody watched him work through the approved manual correction procedure. Nolan verified the trailer numbers, confirmed where the pallets had already been scanned, and contacted the authorized dispatch desk before submitting revised assignments. Twenty minutes later the drivers had clear instructions and the lanes were available again. He documented each step, added it to the exception log, and marked the incident for review by the automation team.
"You always write it down even when it's fixed," Cody said. Nolan nodded. "Especially when it's fixed. A problem that disappears without a record gets to come back next week wearing a new name." The young man laughed, but he stayed long enough to see Nolan attach the incident to earlier reports of the same fault. Nolan suspected he would remember that lesson longer than anything printed on the training poster beside the time clock.
For months, Whitmore had celebrated its automated scheduling platform as a breakthrough. Executives spoke about higher throughput and a ninety-eight-point-six-percent on-time delivery rate, and the quarterly newsletters carried photographs of green dashboards with the phrase smarter logistics beneath them. Nolan did not dispute the delivery figures. He disputed the story the company told about how those figures had been achieved.
Nearly every week, an overnight worker corrected something the new software had missed. Some corrections were minor, a misread identifier or a late change from a carrier. Others involved incompatible door assignments, unsynchronized inventory records, or dispatch instructions that needed a certified supervisor's approval before anyone could safely act. Nolan had entered the problems faithfully, with times, names, and corrective actions, and he had sent repeated summaries to operations leadership.
Six weeks earlier, the whole night crew had signed a group complaint. It described schedule changes delivered with too little warning, staffing levels that left certified employees covering multiple responsibilities, and safety repairs that lingered because the budget prioritized equipment upgrades over maintenance. The complaint was professional, specific, and accompanied by suggested solutions. Meredith forwarded it to the proper offices and confirmed receipt, but no one came back to the crew with an answer.