Chapter 14 - The Vendor’s Visit
Northline Systems sent a representative to the facility on Wednesday morning. He arrived in a dark gray sedan and wore a tailored coat that looked better suited to a downtown law office than a loading dock.
His name was Graham Pritchard. The business card he handed me identified him as Northline’s senior account director.
“I’m here to help restore confidence,” he said.
“You can start by explaining why the system erased the original exception logs.”
His smile was smooth enough to make the question seem rude. “The platform doesn’t erase anything. It consolidates events into a normalized operational record.”
Grace joined us at the dispatch desk. “Then you can show us where the original events are stored.”
“Of course,” Graham said. “Our technical team can schedule a demonstration.”
“Today would be helpful.”
“Today won’t be possible. The engineers are supporting a national rollout.”
Grace opened her laptop. “The board’s preservation request covers the source records and the performance calculations. Your company has received a copy.”
He glanced at me. “I understand there was a difficult Thanksgiving shift. People were upset. That can lead to exaggerated conclusions.”
Marcus, standing behind me, let out a low breath. Maria’s eyes narrowed.
“Thousands of records are not an exaggeration,” Grace said.
Graham spread his hands. “I’m sure everyone acted in good faith.”
That phrase seemed to make the air colder.
He asked to see the control panel. I led him to the platform, but I didn’t give him access to the terminals. The system was disconnected from the network while the audit team preserved its data.
Graham examined the screen. “This is an outdated deployment. Our latest version would avoid these issues.”
“Is that the version Whitmore paid for?” Grace asked.
“We’ll have to check the contract.”
“We have the contract,” she said. “It lists a release number that your company’s public documentation says was discontinued two years ago.”
For the first time, Graham’s smile faltered.
He recovered quickly. “That may refer to the user interface. The underlying engine is updated continuously.”
“Then provide the update records,” Grace replied.
Graham’s gaze turned to me. “Mr. Avery, I’m sure you don’t want the company’s relationship with Northline to be damaged by a misunderstanding.”
“I want accurate records.”
“Accuracy matters. So does context.” He slipped his card onto the dispatch counter. “My office is available if you’d like to discuss the operational transition.”
After he left, Grace photographed the business card and added it to her log.
“Did you know he was coming?” I asked.
“No. Victor’s office scheduled the visit.”
That afternoon, I received a call from Victor asking me to attend an executive briefing. The room was crowded with managers who had spent the past few days trying to look busy while avoiding the audit.
Victor stood beside a presentation showing the system’s “recovery rate.” The chart displayed a clean upward line. It made the rollout appear successful.
“By using consolidated event reporting, we avoided presenting every corrected scan as a crisis,” he said.
Grace raised her hand. “Who approved that definition?”
Victor blinked. “It was standard practice.”
“Standard according to whom?”
He looked toward the department managers. None of them answered.
I took out the binder. “The board approved a success measure that counted a correction as a successful dispatch even when the original route was unsafe. That should have been disclosed.”
Victor’s voice sharpened. “This meeting is about moving forward.”
“Moving forward without understanding what happened means repeating it.”
The meeting ended ten minutes later. A few managers thanked me in the hallway. One of them, a supervisor named Kevin, stopped me near the elevators.
“I wanted to report the same issue months ago,” he whispered. “My access was changed the next day.”
“Changed by who?”
He shook his head. “I’m not sure. I just know my password stopped working after I asked about the reports.”
I gave him Grace’s contact information and asked him to document exactly what he remembered.
On my way back to the warehouse, I saw a new email on my phone from an address I didn’t recognize.
Don’t trust the dashboard. Ask who approved the bonuses.
The message had no name, no signature, and no attached file.
I showed Grace as soon as I reached the dispatch cage. She read it and looked at me.
“Someone inside is trying to help.”
“Or someone is trying to point us toward a trap.”
May you like
“Either way, we preserve it.”
The operations board behind her listed the next day’s loads in neat rows. I had once believed clean numbers meant a clean operation. Now I knew a polished chart could hide anything—and that the person willing to ask who had drawn it might be the next one told to keep quiet.
