At 3:30 on Friday afternoon, I was told my job had been eliminated. I’d spent four months building the model behind a $16 million municipal transit proposal, and I was still running final checks when HR called me upstairs. I thought they needed to talk about Monday’s submission. Instead, Trudy Bell, the HR director, had a termination agreement waiting on the table.

I’m fifty-one, a senior data analyst, and I’ve been around enough meetings to know when somebody has already decided how it’s going to go.

Still, I went in carrying my yellow paper pad, with a note about a fare adjustment I wanted to check before I left. Trudy didn’t ask about the proposal. She pointed to the chair and waited until I sat down.

“We’ve decided to eliminate your position effective,” she said.

She didn’t finish the sentence. I looked at the paper in front of me. The date was Friday. The severance offer was $1,400. I read that number twice, because at first I thought I’d missed a zero. Trudy said the company was restructuring and my role was no longer needed. Her voice had the same tone people use when they tell you a meeting has been moved.

Four months earlier, Gordon Vale, the CEO, had asked me to lead the financial model for the city’s transit proposal. The firm had won the chance to bid, and the deadline was Monday morning.

I’d built the model from fare data, route costs, vehicle schedules, and a set of grant rules that changed depending on which assumptions we used. The numbers had to hold together under several different plans. It wasn’t a spreadsheet you could hand to somebody and expect them to understand by lunch.

I worked about sixty hours a week through most of that stretch. I ate dinner at my desk more than once, which I told myself was temporary. Gordon would stop by and ask if we were “still clean for Monday.” I started saying, “Clean as I can get it,” because that was true, and because I didn’t like promising more than the math could support. He seemed to like that answer.

At two that afternoon, I’d run the last round of checks. A route change made the operating costs behave differently than they had in the previous version, so I fixed it and tested it again.

I remember the little sound the office copier made when it grabbed two pages at once. I remember thinking I needed to tell Trudy about the paper jam. It was ordinary. That’s what made the call upstairs feel so wrong.

Trudy slid the agreement toward me and said the company could pay me $1,400 if I signed before leaving. She called it a standard offer. I asked whether the proposal team knew I was being let go. She said the transition had been discussed with leadership. I asked who would finish the model. She folded her hands and said the company had “coverage in place.”

That answer bothered me more than the money. Not because I thought I was irreplaceable. I’m not. But the proposal wasn’t finished just because the cells showed numbers. There were linked assumptions and tests that had to be run in a particular order. I had written the working script myself and kept the master structure in my own private repository.

The company had licensed the proposal work from me, but I had never signed away ownership of that core tool.

I didn’t say any of that. I just asked for a copy of the agreement. Trudy said I could review it after signing, which didn’t make sense, so I said I wouldn’t sign anything that day. She looked at me for a moment, then changed the subject to the computer. They wanted me to remove my personal files and wipe the work machine before I left.

A man from IT came in with Trudy. I can’t remember his name. He stood behind my chair while I logged out of my personal accounts and checked that the private repository was synced. I’d learned years ago to keep a paper daybook and separate personal work from company equipment. It wasn’t some clever plan. It was just how I kept track of things.

Then I started the wipe. The screen asked me to confirm, and I confirmed. Trudy stayed close enough to see what I was doing. I didn’t like being watched, but I understood why they wanted a clean device. I also understood the difference between wiping that workstation and handing over something I owned. Those were not the same thing.

The progress bar moved slowly. Trudy asked if it was done yet. I said no. She asked again a minute later. The whole thing took long enough that I could hear the office phone ringing out at the front desk. When the screen finally cleared, I stood up, put the unsigned agreement in my folder, and left my yellow pad on the table by mistake. I had to go back for it.

At 4:15, I walked out of the building without making a scene. I didn’t call anyone on the way home. I sat in my car for a while with the key in my hand, trying to decide whether I was angrier about the $1,400 or the fact that they had watched me wipe the one machine they thought held everything. Then I thought about the yellow pad and went back inside for it, because I didn’t want them finding my notes.

At five, I was home. At 5:15, my phone rang. Gordon’s name showed on the screen. I let it ring twice before answering. I wasn’t trying to make him sweat. I wanted one second to remind myself that I didn’t work for him anymore.

He sounded rushed. He asked if I could get into the proposal folder and help the team prepare the submission. I told him I’d been terminated and my access had been removed. He said the folder was empty. I asked what he meant by empty. He said the files the team needed weren’t there, and the shared server had only partial data.

I knew what he meant, but I wanted him to say it plainly. He said the team couldn’t compile the model or validate the transit variables. The company had opened the proposal folder to prepare for Monday, and the master script wasn’t there. The server logs showed encrypted nodes they couldn’t unlock. It wasn’t a mystery. They had the outputs from earlier work, but not the working engine that produced them.

Gordon said someone must have deleted the files during the wipe. I told him the workstation had been cleared under Trudy’s supervision, but my private repository wasn’t on the company computer. He went quiet for a beat, then said the firm owned everything created for the proposal. I asked him to send me the signed agreement that said so.

He didn’t have one. I knew because I’d reviewed every document I signed when I joined. The company had rights to use my work for the bid. That was different from owning my underlying model. I’d kept version history, dated backups, and cryptographic signatures in my personal cloud account. None of that was on the computer they watched me erase.

Gordon tried to make it sound like we were having a normal work call. He said the deadline was Monday, and the city was expecting a complete proposal. He said the company had people who could take over. I told him those people could use the files they had, but they couldn’t rebuild my script from a blank folder over the weekend.

I asked why I’d been fired hours before the deadline. He said it had been a board decision and there wasn’t time to revisit it. I asked if the board knew the team had no working model. He didn’t answer. Then he said, “We were going to remove your name from the proposal metadata and submit under the VP.”

I stopped writing on my yellow pad. Gordon went on, more quietly now. The plan was to have the favored VP take credit for the proposal, while the executives shared the bonuses if the city awarded the contract. He said they thought the model was standard spreadsheet work and that the team could copy what it needed after I was gone. They hadn’t expected the core script to depend on my private key and my own structure.

I didn’t raise my voice. I’m not proud of how long it took me to understand what I was hearing. I had already suspected they wanted me out before the proposal went in. Hearing him say it was different. I’d trusted the “coverage in place” line for about five minutes, because I wanted it to mean what it sounded like.

Gordon said the company could make the termination right. I told him I wasn’t coming back as an employee, and I wasn’t sending my code over in exchange for a promise. He said I was making a bad situation worse. I said the bad situation was already there, and he had just explained how it happened.

I gave him three terms. The company would sign a binding independent contractor agreement naming me lead architect. It would pay the full value of my project work, plus damages for the attempt to take my work and remove my name. And it would put in writing that I owned the underlying model and could use it in my own business. The firm could receive the finished proposal materials it had paid for. It would not receive my private code or the right to claim it.

He said the board wouldn’t agree to that. I told him then they could submit without the model. It wasn’t a threat. It was the plain fact of their deadline. Gordon asked if I’d help with a smaller fee while the lawyers worked out the details. I said no. I’d already been offered $1,400 to leave quietly. I wasn’t going to spend my weekend rebuilding their proposal for another vague promise.

We hung up. He called again at 5:42, then sent an email asking me to hold the repository while the company reviewed its rights. I didn’t send anything. I replied that I would preserve my records and would consider work only under a signed agreement. That was all. I didn’t want to type something angry and give them a new issue to talk about.

The weekend was not quiet for Gordon. I heard later that the executive team spent it trying to work around the missing script. Their internal credibility took a hit when the board learned the city’s proposal couldn’t be validated and that they had fired the person who built the model. Trudy didn’t contact me. I can’t say I felt sorry for her. I also know she was carrying out someone else’s decision, which doesn’t make what she did harmless.

By Saturday night, my attorney had reviewed the draft terms. On Sunday morning, the signed amendment arrived. It named me as lead architect and independent contractor. It set payment for the full value of my project contribution, added damages, and stated that the underlying intellectual property remained mine. The letter acknowledging my sole ownership had Gordon’s signature and the company seal.

I checked every page before signing. I checked the payment date, the ownership language, and the line about my name on the proposal. It wasn’t a warm apology. It was a binding agreement, which was more useful. I sent back the completed signature pages and a list of the files I would deliver. The private repository stayed private.

On Sunday, I rebuilt the final deliverables from my verified version. I ran the scenarios again, checked the transit variables, and gave the firm the proposal package the contract covered. I did not hand over the code. The company submitted Monday morning. My name appeared as lead architect, and the city received a model that had been checked by the person who built it.

I didn’t go back to the office. A few months later, I opened my own small consultancy and used the municipal proposal as my first major portfolio project. I still have the unsigned termination agreement with the $1,400 figure on it. I keep it in a file drawer, not because I need to look at it, but because I want to remember how sure they were that I’d leave with nothing.

The last Sunday after I sent the proposal files, I sat in a coffee shop and closed my laptop. My phone stayed quiet on the table. A small cloud notice confirmed the private backup had synced. I took one last look at the yellow pad beside my cup, then put it away.