The Last Month of June

When Linh accepted the position of data analyst at Calder & Vale, the work sounded almost elegant: dashboards, reporting, cleaner pipelines, process improvements. It was the kind of job that suggested order could be coaxed out of chaos with enough logic and patience.

That illusion lasted three weeks.

The first warning sign was a soft-spoken finance veteran named Graham, who was retiring at the end of June. Everyone described him as “the person who keeps the place running.” That phrase should have meant something was wrong, but at first it sounded like praise.

Then Linh sat in on the handoff meetings.

Graham owned the Sales Register, COGS, deferred revenue, SAP extracts, Spreadsheet Server files, journal entries, mapping tables, tie-outs, and the grim little rituals that turned a warehouse of messy data into financial reporting the leadership could trust. None of it was clean. All of it was stitched together by memory.

In conversation, Graham called everything “straightforward.”

Linh began recording and transcribing his explanations, then building a runbook from the audio. Ten pages in, the document still felt incomplete. Every answer opened three new questions. Every file depended on another file. Every exception had an exception. There were formulas buried in spreadsheets older than Linh’s employment, and rules that existed only because Graham remembered why a particular customer had once been misclassified six years ago.

Linh was a data analyst. She could document a process, trace data flows, build dashboards, write scripts, compare outputs, and surface anomalies. She could not, in a matter of weeks, become the accounting brain of a public-company reporting system.

Leadership did not seem to care about the difference.

Her new top priority became the Graham transition. At the same time, she was pulled into anything that “touched data”: SAP changes, master data cleanup, dashboard requests, ERP migration prep, reporting infrastructure. It was as if every unowned task in the building had found its way to her desk and decided to stay.

When she told Graham she thought it would take three to six months to take over properly, he went still.

“Well,” he said after a long pause, “that’s not happening.”

That was the first moment Linh understood she was not being trained. She was being drafted.

A week later, she discovered it was worse.

A second employee, who owned another critical reporting deliverable, was also leaving on June thirtieth. Two exits. Two bodies of knowledge. One person—her—caught in the middle as if she were a bridge the company had forgotten to inspect.

She opened one of the inherited files and stared at the screen for a long time. Thousands of formulas stretched across a dozen tabs. The instructions were five cryptic lines written by someone who clearly lived inside the process rather than explained it. It looked less like a workbook than a machine assembled by habit.

Still, Linh did what she could. She built a dashboard the right way: validated metrics, cleaner visuals, useful filters, something the business could actually use. It was the sort of work she had been hired to do, and for a brief moment she allowed herself to believe that if she produced enough proof of value, someone would see the line between analysis and accounting.

Leadership’s response was swift.

Dashboard work needed to pause.
The transition was the priority.

Of course it was.

She pointed out that she had already built extensive documentation for Graham’s process and would continue to do so. The reply came back with the quiet force of a demand dressed up as guidance: documentation was good, but she also had to be able to re-perform the work. The result, they said, was a transition.

The phrase hung in the air like a verdict.

Not “preserve knowledge.”
Not “reduce risk.”
Not even “support the handoff.”

Learn it. Own it. Do it.

Linh read her offer letter again that night. The job description was ordinary and reasonable: dashboards, business intelligence, ERP data, automation, governance, KPIs. A normal analyst role in a modern company. Nothing about becoming the final authority on multiple departing employees’ undocumented financial processes.

The gap between paper and reality was enormous.

She began to see the shape of the trap. The better she documented the work, the more capable she appeared. The more capable she appeared, the more the company treated the handoff as solved. Meanwhile, the people leaving were still the only ones who truly understood the system, and the unresolved risk was being quietly transferred to her by proximity.

Worse, they seemed to want the impossible because it was cheaper than hiring the right person.

A controller, a senior accountant, a contractor with the correct background—any of those would have made sense. Instead they had chosen a data analyst and a calendar.

The company had mistaken extraction for transition.

Then life outside work got involved too.

Linh had been handling medical paperwork after a car accident, including a work-from-home accommodation request. She had back surgery in her recent history, and the ergonomics of her home setup were already better than the office’s. Even that process, which should have been straightforward, sat half-finished in the background while leadership piled more critical handoffs onto her desk.

She was documenting a system built on memory while also proving she could keep working through pain.

That was the week she stopped imagining this role as something salvageable.

Not because she wanted to quit in a blaze of anger. She did not. She wanted to leave quietly, with her dignity intact and her rent still paid.

But she could see the future too clearly now.

The company would praise the transition if it went smoothly.
If it failed, they would blame the person nearest the smoke.
And if Linh stayed long enough to become “the one who knows,” she would inherit a liability disguised as trust.

So she changed her strategy.

She stopped saying she could not do it.
She started saying, in writing, what the work actually was.

Minimum transition target.
Independent re-performance.
Review and signoff boundaries.
Unresolved ownership.
Paused tasks.

No heroics. No implied promises. No pretending that a documented procedure was the same thing as years of judgment.

She flagged the risk to the VP she trusted and then to the chief accounting officer, carefully and calmly, as a company problem rather than a personal complaint. She recommended they bring in someone qualified now, while the departing employee could still train them. She made sure the message was polite, factual, and impossible to confuse with enthusiasm.

Then she began job hunting in earnest.

Not dramatically. Not with slammed doors or dramatic speeches. Just with the steady, private determination of someone who had already learned the shape of the trap and refused to stand in it forever.

On her desk, the dashboard remained open: bright, clean, and unfinished. Behind it waited the spreadsheets, the mappings, the tie-outs, the hidden logic, the ancient dependencies, the work of four people being pressed into one pair of hands.

Linh closed the file.

For the first time since joining Calder & Vale, she felt the difference between being useful and being used.