Chapter 4: After I Left
“Nine seventeen,” Ruth said again.
The number stayed on the conference room screen while I searched my phone for the ride I had requested that Tuesday. I found it, along with the message I had sent a friend from outside the building. Neither told me who had approved the report. Both helped place me somewhere else.
“I can send these to Jo,” I said.
“Please do,” Ruth said. “And tell us what you remember about leaving, separately from what the records show.”
I looked at the badge entry again. At 6:06 p.m., I had walked out carrying my lunch container and a headache. I remembered stopping under the awning because it had started to rain. I had not gone back inside.
“I left after I emailed the draft for review,” I said. “The disputed pallets were still unresolved.”
Jo wrote that down. She had kept her questions narrow all afternoon, even when I wished she would say what I was thinking: someone had put my name on work I refused to approve.
Ruth seemed to hear it anyway.
“The time matters,” she said. “But an approval timestamp alone doesn’t tell us whether the field records a click, a submission, or something carried forward from an earlier version. And being outside the building doesn’t mean an account couldn’t be used remotely.”
I knew she was trying to be precise. It still felt like being asked to stand beside my own name while strangers decided whether it belonged to me.
“What would tell us?” I asked.
“The version history. The login records. How this system assigns an approval.”
Jo’s phone rang before Ruth finished. IT had secured copies of the report history and remote-access logs. Jo put the call on speaker and asked Ruth to stay on the video connection.
The technician, whose name was Marcus, spoke carefully. He had found an after-hours remote session associated with the submitted report. The session began after my badge exit, and the vendor-report application recorded activity under my account. At 9:17, that account submitted the changed version.
I gripped the edge of my chair.
“I didn’t log in from home,” I said. “I don’t even have that application on my home computer.”
“We’re not saying you did,” Jo said.
Marcus added that he had preserved the underlying records and the earlier report versions before conducting the comparison. He could identify the account the application recorded. He could not yet identify the person at the keyboard.
“So someone used my password?” I asked.
“Possibly,” Marcus said. “I don’t want to call it that until we finish checking the access path.”
Across the screen, Ruth made a note. She asked Marcus to preserve the remote gateway records as well as the application history, including the device identifiers. Then she asked him not to draw a conclusion from the account name alone.
I thought of the final paycheck in my bag. My name was on that, too. A record could be real and still tell only part of the story.
While Marcus gathered the remaining logs, Jo asked me to send the ride receipt and my message. I forwarded them from my phone. The receipt showed where the driver had picked me up. The message said, Finally outside. Report sent. Going home.
For a moment, I was embarrassed by how relieved I felt to find those ordinary words. They did not prove I had stayed home all evening. They did not have to. I had told the truth about leaving, and there was a record from the time I had done it.
Jo looked up from her laptop.
“Before we contact anyone about the report, I want to understand who had access to the system.”
“Miranda could request changes,” I said. “The warehouse supervisors could review shipment counts. Daniel had no reason to prepare a vendor report that I know of.”
“That helps us make a list of questions,” Jo said. “It doesn’t take anyone off or put anyone on it.”
By then the office outside the conference room had grown quiet. A cleaner moved a cart past the glass wall and gave me a brief, sympathetic glance. I wondered what Daniel had told people about why I was still there after Miranda had ended my employment that morning.
Marcus called back with an answer I disliked more than a single suspicious login. The remote gateway used a shared night-review credential. Several people who handled late shipment paperwork had been given access to it. From that gateway, the report application showed activity under my account.
“How?” I asked.
“We’re investigating that,” Marcus said. “There’s a coverage procedure that allowed staff to resume a preparer’s report session. I haven’t established whether it was followed here.”
“I was never told someone could resume mine.”
Jo asked him to send the procedure and its access list through the preserved channel. When the call ended, she turned to me.
“Does the phrase ‘night review’ mean anything to you?”
“Only that people wanted reports finished before morning.”
That was how everything at Sterling & Vale became normal. Someone needed a shipment number, so someone borrowed a login. Someone needed an answer, so an unresolved pallet became a corrected count. By the time a report reached a client, the shortcuts looked like decisions.
“I don’t want my account used as an excuse to question the warehouse staff,” I said.
“We haven’t reached that conclusion,” Jo replied.
“I know. But the report might.”
Ruth had been reading the two versions while we talked. Now she asked Jo to enlarge the submitted copy.
The draft I had saved showed six disputed pallets awaiting confirmation from receiving. Beside the first two, I had noted a vendor arrival time that did not match the warehouse intake record. My note asked for the original shipment information before anyone assigned a cause for the delay.
In the submitted version, that request was gone.
The same rows said the warehouse team had corrected its counts after a late internal check. Another field described the resulting delay as a warehouse reconciliation issue. The vendor arrival time remained in the report, but the note drawing attention to it had disappeared.
“They didn’t just fill in blanks,” I said.
“No,” Ruth said. “The saved and submitted versions describe different reasons for the delay.”
She enlarged one more row. My draft had left it unresolved. The submitted report attributed the missing pallets to an inventory count correction on the warehouse side.
I knew what a client would hear in that phrase. The delivery had been fine; the people unloading and counting it had made the trouble. I pictured Nia Brooks at the warehouse, marking pallet numbers with a pen that barely worked because nobody ever reordered supplies until they ran out.
“Can you tell whether those corrections happened?” Jo asked Ruth.
“Not from these versions. We’ll need the underlying receiving and shipment records.” Ruth paused. “What we can establish here is that the submitted report shifted the explanation toward warehouse work.”
I wanted to tell her Nia would remember. Nia had worked beside me during one of the weekend audits, checking the physical counts while I reconciled the report. But remembering work and remembering a particular shipment were different things. I had spent the day asking people not to stretch evidence beyond what it said. I could not ask Nia to do it for me.
Jo closed the report.
“We need to speak with the people who handled those pallets,” she said.
“Please secure their records first,” I said.
“What are you concerned about?”
“Schedules. Assignment changes. The little things that don’t look like much unless you need the hours.”
For three years, I had watched people decide whether they could afford to challenge a mistake. I had made those calculations myself. Losing a Saturday shift could mean postponing a bill. A manager did not have to threaten anyone out loud for them to understand the risk.
Jo said she would request preservation of posted warehouse schedules and any changes to them. She would ask for private interviews, without routing invitations through local management. Ruth added that the warehouse witnesses should be asked what they saw before being shown either version of the report.
After they finished, Jo asked if I wanted to contact Nia or preferred that she do it.
“I can ask whether she’s willing to hear from you,” I said. “I won’t ask her what to say.”
Jo agreed.
I stepped into the empty hallway. Nia answered my call on the fourth ring, with warehouse noise behind her.
“Emma? I heard you were gone.”
“Miranda accepted my notice effective immediately.”
Nia was quiet for a second.
“You okay?”
I had been answering questions about money and timestamps for hours. Hers was the first question that made my throat tighten.
“I’m working on it,” I said. “There’s a question about a shipment report. Jo Ramirez from corporate HR and an outside auditor are looking at it. They’d like to talk privately with anyone who handled the inventory.”
“What kind of question?”
“I don’t want to put answers in your head. It involves the shipment with the pallets we couldn’t reconcile.”
A cart rattled past her. When the sound faded, she lowered her voice.
“I remember that shipment.”
“You don’t have to tell me anything now. And you don’t have to talk to them because I asked.”
“I’d rather talk where nobody here can hear,” she said.
I told her Jo could arrange that. Nia said Monday morning would work, before her shift. She asked whether I would be there. I told her I could come if Jo agreed, but the interview had to be hers.
Back in the conference room, Jo noted Nia’s preferred time and sent a private invitation to her phone. She also followed up on the schedule preservation request. It was nearly evening before I left the building for the second time that week, my original paycheck still tucked in my bag.
May you like
On the sidewalk, my phone lit up with a message from Nia. She had attached two screenshots of the warehouse schedule. In the first, posted earlier that day, her name appeared on four upcoming shifts. In the second, the current schedule, only one remained.
I haven’t even talked to them yet, she wrote.
