He had expected disappointment, perhaps.
Not consequences.
“I’m glad we can be professional about this,” he said.
I stood.
“So am I.”
Then I returned to my desk, opened the bottom drawer, and pulled out a folder I had been building for eight months.
I had not started it because I was planning revenge.
I had started it because sometime the previous spring, after my third consecutive “temporary” responsibility became permanent, I realized memory was a terrible career strategy.
My father had been an accountant for thirty-seven years.
Growing up, he wrote everything down.
Mileage.
House repairs.
Utility bills.
Even Christmas gifts.
When I was sixteen, I once asked him why he kept receipts for purchases nobody would ever question.
He said, “Because facts get simpler when they have dates.”
I used to think that was the least exciting sentence any human being had ever spoken.
At thirty-four, I understood exactly what he meant.
The first section of my folder contained my original job description.
I had highlighted every responsibility I was hired to perform.
Project scheduling.
Client communication.
Meeting coordination.
Status reporting.
Documentation support.
Then came my current workload.
Resource forecasting.
Vendor escalation.
Client recovery planning.
Quarterly operational reporting.
Team onboarding.
Internal process training.
Contract deliverable tracking.
Quality review.
Launch risk assessment.
Cross-functional issue resolution.
I had not invented those responsibilities to make myself look important.
I had email chains assigning every one of them.
Marcus had written most of the emails.
Erin, can you own this for now?
Erin, please step in until we find someone permanent.
Erin, you know the account best.
Erin, I need someone reliable on this.
Temporary had become the unofficial architecture of my career.
The second section contained project results.
The Bellmore account was first.
Bellmore Retail Group had signed a major implementation agreement with Westbridge eighteen months earlier. The rollout covered inventory software across more than a hundred stores.
Four months before launch, the implementation manager resigned.
The replacement lasted six weeks.
A key vendor missed two delivery dates.
Then Bellmore’s vice president sent an email saying they were considering reducing the scope of the contract.
Marcus called me into a conference room.
“I need you to stabilize this.”
“I’m not the implementation manager.”
“I know.”
“I have three other projects.”
“I know.”
“When are we hiring a replacement?”
“We’re working on it.”
That phrase lasted eleven weeks.
During those eleven weeks, I ran daily calls at eight in the morning, updated the project plan after dinner, worked two Saturdays, reorganized the vendor schedule, and convinced Bellmore to accept a phased launch rather than abandon the rollout.
The project went live three weeks later than originally planned.
But it went live.
More importantly, Bellmore renewed.
Their vice president sent Marcus an email.
I was copied.
Erin is the reason we stayed confident enough to finish this.
I printed it.
Not because I expected to wave it dramatically across a conference table someday.
Because facts get simpler when they have dates.
The next section contained another client.
Harrington Home Supply.
A software update created reporting errors two days before their quarterly inventory close.
The engineering team was already overloaded.
The account manager panicked.
Marcus was traveling.
I spent fourteen hours coordinating between the client, our technical team, and finance.
We had the reporting issue corrected before Harrington’s internal deadline.
Their director emailed me afterward.
You made a bad situation manageable. Please make sure your leadership knows that.
I forwarded it to Marcus.
He replied with three words.
Nice work, Erin.
I printed that too.
Then there were training records.
When two new coordinators joined, I built their onboarding guide because the official one referenced systems we had stopped using eighteen months earlier.
Nobody asked me.
I simply got tired of watching new employees spend their first month learning by mistake.
The guide eventually became the department standard.
Marcus presented it during an operations meeting.
He called it “our new onboarding framework.”
Our.
I sat in the third row and said nothing.
At the time, I told myself recognition didn’t matter if the work helped people.
That was partly true.
The problem was I kept using noble explanations to excuse a practical imbalance.
Recognition matters when recognition determines title.
Title matters when title determines salary.
Salary matters when the mortgage, retirement contribution, emergency fund, and cost of groceries do not accept personal fulfillment as currency.
The folder also contained a compensation analysis.
I had started researching salaries the previous summer after a recruiter contacted me about a role I wasn’t ready to pursue.