PART 3: The Name Ryan Put Forward 035
Part 3 – The Numbers That Changed
“I’ll explain tomorrow,” Emma had said.
That night, the promise kept me awake longer than the work itself.
I opened the project brief again and read the line beside Emma’s name, though it hadn’t changed.
Historical project records.
The words seemed simple enough, but the tightness in Emma’s voice had made them feel like a door she had spent years keeping shut.
I tried to imagine what the earlier project had been, and why she had never mentioned it during our two years of friendship.
Every possibility I came up with felt less likely than the last.
By morning, I had settled on one decision.
I would ask Emma before I asked Ryan.
The next day began with a quiet meeting in one of the smaller conference rooms.
Ryan sat at the far end of the table, his sleeves buttoned and his attention fixed on the project brief.
In daylight, the easy warmth I had glimpsed in the hotel hallway seemed to have folded itself away.
He was my boss again, composed and deliberate, and I was grateful for the reminder.
“Before we begin,” he said, “I want to be clear about the scope.”
The finance team had assembled around the table, along with two senior executives whose names I recognized from the previous day’s presentation.
“We’re reviewing the forecast for the next phase,” Ryan continued. “We’re not reopening old questions unless the current analysis gives us a reason to.”
His gaze moved briefly to me, then to the documents in front of him.
“Keep the work focused, and keep the working files within this group.”
One of the executives, Martin Hale, nodded.
“Agreed. There’s no value in stirring up historical confusion when we have a current plan to finish.”
The remark sounded practical, but I noticed Ryan’s jaw tighten.
Only for a moment.
Then he turned a page.
“Lauren will lead the model review,” he said. “Nina Patel will coordinate the finance team’s data requests. Emma will advise on the archived records.”
The name beside me in the brief had felt like an administrative detail.
Hearing it spoken aloud made it sound like a decision everyone had already accepted.
Emma had not yet arrived.
“Is Emma familiar with all of the historical files?” I asked.
The question seemed harmless enough, but Martin looked at me as though I had asked something more pointed.
“She worked on the earlier forecast,” he said. “Before my time on this division.”
Ryan’s attention settled on him.
“Emma can tell us which records are relevant.”
Martin gave a restrained shrug.
“If she can remember them.”
The words were not openly unkind, but something in them made the room feel colder.
Ryan closed the folder in front of him.
“We’ll let her decide what she remembers.”
The conversation moved on to reporting dates and access permissions.
I took notes, though I found myself thinking less about the schedule than about the small exchange I had just witnessed.
Ryan’s defense had been immediate.
It might have meant nothing more than basic professionalism.
Still, Emma had mentioned that he supported her at the time she led the earlier work, and I could not stop wondering what had happened after that.
When the meeting ended, Ryan asked me to stay for a moment.
The others gathered their papers and left, their voices fading into the corridor.
“You asked about Emma’s familiarity with the records,” he said.
“I did.”
“Was there a reason?”
“I saw her name in the brief last night and realized I knew nothing about the old project.”
“That’s fair.”
His answer was measured, but his expression had grown more guarded.
“Is there something I should know before I start reviewing the files?”
Ryan glanced at the closed door.
“I don’t want to create expectations about an investigation we haven’t begun.”
“I’m not asking you to.”
“I know.”
He rested one hand on the table.
“The earlier forecast was complicated. It was handled at the time, and this assignment is about the current plan.”
The wording was careful enough that it sounded rehearsed.
“Handled how?”
“Through the normal process.”
“Was there an error?”
His eyes held mine for a beat.
“There were discrepancies.”
The room seemed to narrow around that word.
“Were they corrected?”
“Yes.”
“Then why do the old records matter?”
“Because the forecast informs the current model,” he said. “We need to understand how the assumptions were built, not revisit every decision that was made around them.”
I thought of the line in the brief and of Emma’s silence the night before.
“Did she leave the team because of what happened?”
Ryan’s expression changed, though only slightly.
“That’s a question for Emma.”
“I wasn’t asking for details about her private life.”
“I understand.”
“Then why won’t you answer?”
For the first time since I had joined the company, I saw him seem genuinely uncertain.
“I don’t want to tell her story for her,” he said at last.
The answer was fair.
It was also not an answer.
I nodded and gathered my notes.
“Understood.”
“Lauren.”
I stopped.
“You have the authority to review the records relevant to the forecast,” he said. “If you find something that affects the current analysis, document it and bring it to me.”
“Privately?”
“Through the project channel.”
His gaze stayed on mine.
“Please don’t assume that discretion means concealment.”
I wanted to believe him.
“I’ll follow the process.”
“Good.”
As I left the room, his last sentence followed me into the corridor.
It sounded like reassurance.
It also sounded like a warning he had not meant to give.
Emma came to my office later that morning with two paper cups of coffee.
She set one beside my keyboard and stood near the doorway, her eyes moving over the folders on my desk.
“You’ve started,” she said.
“I’ve started making a list of what I need.”
“Smart.”
I waited for her to say more.
She lowered herself into the chair across from me.
“About last night,” she began.
“You don’t have to explain anything you don’t want to.”
“I know. But if you’re going to work with the old records, you should at least understand why I’m on the list.”
I turned away from my screen.
“Okay.”
“Several years ago, the division was preparing a long-term forecast for a project that was meant to become a major part of the company’s future.”
“Was it the same project we’re assessing now?”
“Not exactly. The current work builds on some of the same assumptions.”
She wrapped both hands around her coffee cup.
“I was a junior analyst then. Not as junior as you were when you started, but junior enough that people assumed I’d do the calculations and leave the decisions to someone else.”
“Were you leading the analysis?”
“I was part of a small team. I worked on the supporting model, checked the source files, and prepared a summary for the executive review.”
Her eyes had fixed on the cup.
“What happened?”
“There was a serious discrepancy in one of the forecasts. The figures presented to leadership didn’t match the numbers in the source model.”
“What kind of discrepancy?”
“Large enough to change how the project looked.”
My stomach tightened.
“Did someone make a mistake?”
“That was the conclusion.”
“Your mistake?”
Emma looked up.
“They said I had used an outdated version of the file.”
“Had you?”
“I thought I hadn’t.”
Her quiet answer made the room feel suddenly smaller.
“You weren’t sure?”
“I was sure of what I remembered. I wasn’t sure I could prove it.”
She took a sip of coffee and set the cup down again.
“The review moved quickly. The project was under pressure, and the people making decisions were more senior than I was. I had sent my notes to my manager, but they couldn’t find the version I’d been working from.”
“And they blamed you.”
“They said my handoff had created confusion. No one called me dishonest. They didn’t have to. My name became the explanation everyone settled on.”
I leaned forward.
“What did Ryan say?”
Emma’s gaze moved away from me.
“Ryan wasn’t running the division yet. He was newly responsible for the team that inherited the project.”
“Did he believe you?”
“He believed there was more to the story.”
“That isn’t the same thing.”
“No,” she said. “It isn’t.”
The words were gentle, but they carried a hurt that had not gone away.
“Did he support you?”
“He asked questions. He tried to find the original files.”
“And?”
“By then, the documents had been reorganized. The person who had overseen the review said we had already corrected the forecast, and there was no reason to keep digging.”
“Who was that?”
Emma paused.
“I’m not ready to tell you that.”
I nodded, though the answer left me with a fresh list of questions.
“Ryan couldn’t prove I was right,” she continued. “I was offered a transfer to a different team, and I took it.”
“Because you wanted to leave?”
“Because I didn’t want to spend every day proving I hadn’t done something I couldn’t prove I hadn’t done.”
I felt the impulse to reach across the desk, but I wasn’t sure whether she wanted comfort or room.
“So you stayed at the company.”
“I did. I just stopped working on that division.”
“And you never told me.”
“I didn’t want the story to become the first thing you knew about me.”
“It wouldn’t have.”
“I know that now.”
Her expression softened, but only a little.
“Back then, I didn’t know you well enough to trust that.”
The honesty hurt more than if she had accused me of anything.
“I wish you’d felt you could tell me.”
“So do I.”
For a moment, we sat with that between us.
Then I opened the folder beside my keyboard.
“Do you remember anything about the files themselves?”
“A few names. One of the working spreadsheets had a note in the header saying it had been copied from the original model. I wrote down the file name in a notebook at the time.”
“Do you still have it?”
“I think so. I kept the notebook in a box at home.”
“Would you be comfortable bringing it in?”
Emma looked down at her hands.
“I can find it tonight.”
“You don’t have to do that for me.”
“I know. I want to.”
She rose, then rested one hand on the back of the chair.
“There’s something else.”
“What?”
“Be careful about assuming Ryan’s support means he can tell you what happened.”
“I didn’t assume that.”
“You asked him about my leaving.”
“I asked if it was connected to the discrepancy.”
“And he told you it was a question for me.”
“He did.”
She studied my face.
“Then maybe he’s learned not to speak for other people.”
I thought of the way he had closed the folder after Martin’s remark.
“Maybe.”
Emma gave me a tired smile.
“Don’t let me turn this into something it isn’t. You have a project to lead.”
“I’m not letting you.”
“Good.”
After she left, I opened the archive request form and began searching the approved records.
The files were old enough to have been transferred several times, and the first results were little more than dated folders with vague labels.
I found meeting notes, two versions of a forecast, and a summary report that described the discrepancy as a temporary data-entry error.
The report was less than a page long.
It did not name Emma directly, but one line noted that the issue had been traced to an analyst’s use of an outdated source file.
The language sounded official.
It also left out every detail that might have established what actually happened.
I opened the earliest forecast and compared its assumptions with the later version.
The numbers had shifted, but not in a way that looked like an ordinary correction.
Some values were lower.
Others had been raised.
The changes did not follow one consistent pattern, and I could not determine whether they reflected revised data or a different set of assumptions.
The file history was incomplete.
One document referred to an attachment that was no longer available.
Another cited a review meeting whose notes were missing.
I began a list of questions.
At the bottom, I wrote: Locate original model and version history.
Then I stared at the phrase for a long moment.
By late afternoon, the conference room had emptied, leaving me alone with the archived files and the quiet hum of the building.
I sent a message to Ryan asking whether the original model had been transferred to the current archive.
His reply came a few minutes later.
The source folder may be under the pre-reorganization archive. I’ll check the access list.
I read the message twice.
The word may unsettled me.
If he knew the file might be there, why had he not mentioned it?
I told myself the simplest answer was probably the right one: he had been managing too many old files and too many current deadlines.
Still, I remembered the careful way he had said the discrepancy was handled.
A notification appeared on my screen.
Ryan was requesting access to a restricted folder.
I clicked the folder name.
An old project directory opened, its contents arranged by year and department.
Several files were marked read-only.
One folder was labeled Historical Forecast Working Copies.
I opened it, and the first spreadsheet appeared.
The date matched the period Emma had described.
The file name began with the words Initial Forecast, followed by a version number and a timestamp.
I downloaded the file and placed it beside the later forecast.
The spreadsheets looked nearly identical at first.
Then I found a line where the underlying revenue figure had been changed.
It had not been recalculated.
It had been overwritten.
I checked the formula, then the cell history.
The history was sparse, but one entry showed that the number had been manually changed on the same evening as the executive review.
The user identification field had been partially corrupted.
I could make out a department code and the first letter of a surname.
Not enough to draw a conclusion.
Enough to make me stop breathing for a moment.
A second file sat in the same folder, one I had missed because its title was abbreviated.
I opened it.
It was an exported copy of the model, saved only minutes after the first file had been altered.
The edited figure was still there.
But a comment had been added to the adjacent cell.
The comment read: “Confirm against original before circulation.”
It was signed with the initials E.M.
Emma’s initials.
I sat back from the screen.
The note did not prove she had made the change.
It did not prove she had seen it before the file went out.
But it proved she had noticed something that the official summary never mentioned.
I saved both files in the project directory and wrote down the file paths.
Then, remembering Ryan’s instruction, I checked the project channel before sharing anything.
He had not yet replied about the archive.
I started drafting a message that described the mismatch without drawing conclusions.
Before I could send it, a new email arrived from the records system.
Your access request has been approved.
The sender was Ryan.
I looked back at the folder.
The access had appeared just as I found the archived files.
Maybe he had opened the folder himself and sent the approval through.
Maybe he had been reviewing the same evidence.
I wondered whether to call him.
Instead, I went to the conference room where I knew he sometimes worked after hours.
The room was dark.
His office door stood open, and I could see a narrow band of light across the corridor floor.
I knocked once on the frame.
“Come in,” he called.
He was standing beside his desk, reading something on his tablet.
When he saw the printed copies in my hand, his expression grew still.
“Did you find the source folder?” he asked.
“I did.”
He set the tablet down.
“What did you find?”
“An earlier version of the forecast, a later copy, and a note about confirming the figures against the original.”
His eyes moved to the top page.
“Does the note have a name?”
“Initials.”
He waited.
“E.M.”
Ryan’s face changed in a way I could not quite read.
For a moment, it seemed as though I had surprised him.
Then the surprise was replaced by something older and heavier.
“Have you shown this to Emma?”
“Not yet. I wanted to follow the project process.”
“Good.”
The word came out too quickly.
I placed the documents on the edge of his desk.
“Do you recognize the files?”
He looked down at them but did not touch them.
“I recognize the project.”
“That isn’t what I asked.”
“I know.”
His gaze met mine, and there was a trace of fatigue in it.
“Ryan, if there’s something I should know before I keep going, I need you to tell me.”
He drew a breath, then seemed to reconsider what he was going to say.
“This is exactly why I wanted the review kept focused.”
“Because the numbers were changed?”
“I didn’t say that.”
“But you recognized the file.”
“Yes.”
“Was Emma blamed for something she didn’t do?”
His silence was answer enough to make my pulse quicken.
Then he spoke.
“The official review concluded that she used the wrong version.”
“Did it establish that?”
“It established what the company was prepared to accept at the time.”
The distinction sat between us, small and devastating.
“Why didn’t you tell me there was a question about the review?”
“Because I don’t know the complete answer.”
“You know more than you’re saying.”
“I know some of what happened.”
“Then tell me.”
He looked at the files again.
“Not tonight.”
I felt my hand tighten around the edge of the chair.
“Is that because it’s confidential, or because you don’t want me to find out?”
“Both could be true.”
“Which one is it?”
His expression held no anger, but the restraint in it made me feel shut out.
“I don’t want you to make a conclusion from a fragment,” he said. “And I don’t want to put Emma in the position of having her history discussed without her.”
“Then we should bring her into the conversation.”
“We should.”
“Have you already spoken with her about this?”
He hesitated.
That pause told me more than the answer might have.
“Not recently,” he said.
“Did you speak with her before assigning her to the project?”
“I told her she could decline.”
“She didn’t mention that.”
“She may not have thought it mattered.”
“You’re both making decisions on my behalf and calling it discretion.”
A flicker of regret crossed his face.
“That isn’t what I intend.”
“But it’s what it feels like.”
“I understand.”
I searched his expression for the confidence I had seen in the investor meeting, the quiet belief he had shown when he put me forward for the project.
Instead, I found a man trying to hold back a story that might have been too large for either of us to carry alone.
“Was your support for me about the current work?” I asked.
“Yes.”
“Only the current work?”
His gaze held mine.
“Your analysis earned this opportunity.”
The answer sounded clear.
It should have been enough.
But after what I had found, I could not stop wondering whether there was something he had left out.
“I’ll document the files,” I said. “Then I’ll speak with Emma before I make any recommendation.”
“That’s the right approach.”
“Please don’t tell me what the right approach is and then keep the facts from me.”
Ryan lowered his eyes.
“You’re right.”
The admission softened nothing, though I appreciated its honesty.
“I should have told you the old review was incomplete,” he said. “I was trying not to influence your work.”
“Did you think keeping me uninformed would make me more objective?”
“No.”
“Then why?”
He looked toward the windows, where the city lights were beginning to appear against the dusk.
“Because there are people who can be hurt by the wrong conclusion,” he said. “And because the company is still dealing with the consequences of decisions made back then.”
I thought of the investors, the revised plan, the hundreds of employees whose jobs depended on the company’s stability.
Then I thought of Emma, carrying a story she had believed she left behind.
“Those reasons don’t make the old records less important.”
“No,” he said quietly. “They don’t.”
I took the papers back from his desk.
“Tomorrow, I’ll ask Emma to review the files with me.”
“Let her decide what she wants to see.”
“I will.”
I turned toward the door.
“Lauren.”
I stopped, but did not face him.
“There’s one thing I want you to remember,” he said. “A discrepancy is not proof of who caused it.”
“I know.”
“And an old record can look different without the context around it.”
“I know that too.”
When I finally looked back, his expression had softened.
“I’m not asking you to ignore what you found,” he said. “I’m asking you not to decide what it means before you have the rest.”
The request was reasonable.
It was also the kind of request a person might make when the rest of the story could change everything.
Back in my office, I sent Emma a message asking if she could meet me in the morning.
She replied almost at once.
Of course. I found the notebook.
I looked at the two archived files on my screen and at the comment bearing her initials.
For the first time, I understood why she had kept the old story locked away.
She had not forgotten the work.
She had been waiting for a way to prove what she had seen.
And if the note in the spreadsheet meant what I thought it might, the person who changed the forecast had not been the only one who knew the numbers were wrong.
**–END OF PART 3–CLICK “NEXT” AT THE BOTTOM OF THE PAGE TO CONTINUE READING**
* * *
[PREVIOUS: PART 2](https://puretales.idolsgift.com/blog/part-2-the-name-ryan-put-forward-035) | [NEXT: PART 4](https://puretales.idolsgift.com/blog/part-4-the-name-ryan-put-forward-035)
✓ Lynn R. Adams
Part 3 – The Numbers That Changed “I’ll explain tomorrow,” Emma had said. That night, the promise kept me awake longer than the work itself. I opened the project brief again and read the line besid…