Chapter 6: The Empty Folder
Ruth kept her hand on the mouse but didn’t click anything else.
“Can you tell me whether this folder was moved?” she asked the records employee on the phone.
I could hear the faint rattle of a keyboard through the speaker.
“I sent you the location we use,” he said. “I don’t know of a new one.”
“All right. Please don’t try to restore it yourself.”
After she hung up, Ruth took a screenshot of the empty window. She recorded the folder path, the time, and the name of the employee who had given it to her. Then she called Jo.
“The usual location is empty,” Ruth said. “That tells us what’s there now, not what happened to the files.”
Jo asked IT to preserve the server backups, access history, and any file-system records for that location. She also asked the records employee to hold off on searching through old drives. He had wanted to help. Ruth explained that an ordinary attempt to put the files back could make it harder to understand when they had disappeared.
I watched her write shared copy absent in her notes. Not deleted. Not hidden.
I was grateful for her care, and impatient with it. Somewhere in those files might be the answer to whether the warehouse had ever corrected the six pallets.
“Who else recorded the truck coming in?” Ruth asked.
I thought about the second weekend audit. Nia and I had spent most of it at a folding table beside the receiving area, comparing pallet labels to the numbers we had been given. When we went looking for the delayed truck, a gate attendant had told us it was still outside.
“The gate staff,” I said. “They had their own screen. I asked whether the truck had checked in, and he read me a time.”
“Was that screen part of the inventory system?”
“I don’t think so. We couldn’t see it from our accounts.”
Ruth wrote that down too.
“I remember standing there because I felt ridiculous,” I added. “I’d been asked to explain a receiving delay for a truck the warehouse hadn’t received.”
“That’s worth checking,” she said. “But I need the record, not just the memory.”
“I know.”
It stung less than it would have three years earlier. Back then, I had learned to treat every request to check my work as a warning. Ruth wasn’t asking me to be quiet. She was asking for something that could speak when I wasn’t in the room.
Jo joined us an hour later, carrying a folder of schedule printouts. She closed the conference-room door before setting them on the table.
“We have the selection record for Nia’s shifts,” she said.
The scheduling coordinator’s explanation had been a weekly labor-hours adjustment. That part was true: the department’s schedule had been revised. But the revision history showed who had chosen the shifts to remove. Cal Mercer had sent the coordinator a list that included three of Nia’s four upcoming shifts. The coordinator had entered the changes under the adjustment code.
“Did he say why he chose hers?” I asked.
“He wrote that those shifts could be covered by the remaining team. I’m asking him to explain the selection and who, if anyone, directed it.”
I looked at the first printout. The changes had been entered before Cal approached Nia with the statement he wanted her to sign. That didn’t make the missing hours harmless. It also didn’t tell us what he had been thinking when he chose them.
“Nia saw four shifts posted on Friday,” I said. “Then she saw one. She didn’t know anyone was going to take the other three.”
“I’m going to speak with her about the practical effect,” Jo said. “In the meantime, decisions about her upcoming schedule will go through a staffing manager outside Cal’s reporting chain.”
“Will she get the shifts back?”
“I’ve requested that her original hours be made available while we review this. I won’t tell her it’s done until staffing confirms it.”
I nodded. Nia needed hours she could count on, not a reassuring sentence from me.
Jo had also obtained the original of the unsigned statement Cal had handed her. The page matched Nia’s photograph. Its file history showed that Cal had created the document that morning, but Jo was still checking the earlier notes from which he said he had drafted it. I thought of Nia standing outside in the wind, afraid she would regret refusing to sign.
“Has someone told Cal not to approach her about it again?” I asked.
“Yes,” Jo said. “And Nia has a direct number to call if he does.”
It was not the same as making her safe. Jo didn’t pretend it was.
By late afternoon, IT had located a backup containing the shipment-log folder. Ruth went down to their office to watch them make a separate copy for review. I stayed in the conference room with my phone faceup, waiting for a message from Nia about her shifts.
She sent one just before five.
Jo called. Staffing says I’m back on the three I lost. A different manager has to approve changes for now.
I read it twice.
Are those the hours you wanted? I wrote.
Yes. I just wish I hadn’t had to ask for them.
I didn’t have a useful reply. I sent back, I know.
Ruth returned carrying a printed timeline.
“The backup shows the folder and its files were there Sunday night,” she said. “That was after the inquiry started. The shared folder was empty when I opened it today. IT also found a file-system event at 10:14 this morning that removed the files from that location.”
“Removed how?”
“That’s what they’re working on. The event doesn’t yet tell us whether a person moved them, an automated process did, or where the shared copy went. They’re preserving the relevant logs.”
“Can you read the backup?”
“They’ve made a review copy. I’m not relying on any entries until we compare it with the other records and establish which version we have.”
The folder had existed. Its absence wasn’t my faulty memory, or Ruth typing the wrong path. But the word removed brought a cold feeling I couldn’t reason away.
Ruth slid another page toward me. Gate operations had supplied records from a separate system.
The truck carrying the disputed shipment had checked in at 7:04 on the morning named in the vendor report. The gate recorded it waiting outside, then receiving clearance to enter at 9:12. A receiving sheet showed warehouse custody beginning at 9:38.
I read the times again. The submitted vendor report attributed the delay beginning shortly after eight to warehouse count corrections.
“At eight, it was still at the gate,” I said.
“Yes.”
“Nia and I weren’t making corrections to it.”
“The gate record supports that the truck hadn’t entered warehouse custody at the time the submitted report assigns the delay to warehouse work,” Ruth said. “It doesn’t tell us everything that happened later to those pallets.”
She was right. Nia and I had counted six unresolved pallets. The gate record did not prove no one corrected them after we left. But it gave us a firm place in the morning’s sequence. The truck had waited before our team could touch it. Calling that wait a warehouse count correction changed more than a line on a report.
“Would Miranda have seen these times?” I asked.
“I don’t know.”
That answer held more weight than a guess would have.
Jo came back in while we were comparing the records. Ruth showed her the times, then the backup timeline. Jo asked for copies to be preserved with the report versions and Nia’s interview. She did not call it proof that someone had set out to blame the warehouse. She wanted to know who had supplied the explanation in the submitted report and whether a later receiving entry supported it.
I thought about how easy the altered sentence had been to read. Warehouse count corrections caused the delay. It sounded like the kind of problem people were paid to fix. It took two other systems, a worker willing to speak, and an empty folder to make anyone ask when the truck had arrived.
The next morning, Ruth invited me to review the description of the work Nia and I had done. She didn’t show me other workers’ pay records. Jo had arranged for affected employees to be contacted privately, and I wanted it kept that way. My check was already evidence. Their names didn’t have to become a story told to me.
June called while Ruth and I were checking the dates. She had found the accounting crosswalk for the payroll exception code on my check. Ruth put her on speaker after warning her I was present.
“It labels the charge as an employee recovery,” June said. “That’s an accounting description. I still don’t have support showing what the employee was supposed to be repaying.”
“Does it say where the entry was posted?” Ruth asked.
“Yes. I’ve sent the ledger line and the cost-center directory.”
Ruth opened the files side by side. One contained the exception from my final paycheck, the one that had left me with $37.44. The other identified the internal department account against which it had been recorded.
May you like
She leaned closer to the screen, checked the code a second time, and turned the monitor so I could see.
The alleged employee recovery was posted to Miranda Vale’s operating cost center.
