My Coworker Kept Rewriting My Meeting Notes—And I Thought She Was Taking Credit
The first time I noticed the meeting notes had changed, I blamed autocorrect.
The second time, I blamed myself.
By the fifth Monday, I was taking screenshots before I closed the document.
Our operations meeting started at nine every Monday in a glass conference room that somehow made eight people feel like twelve. I ran client strategy for a midsize design firm. Priya, our operations coordinator, took notes because she could type almost as fast as people argued.
At 10:03, the document would look exactly the way I remembered the meeting. By lunch, sentences had been tightened. Names had been added. Vague lines like “someone should follow up with procurement” became “Priya to contact procurement by Wednesday.”
At first, that seemed helpful.
Then I noticed something else.
An idea I had raised about adding a short client handoff call appeared later as: “Elena’s suggestion: introduce a 15-minute handoff call after proposal acceptance.”
Elena was a junior analyst. I liked Elena. That was not the point.
I remembered saying the idea out loud.
The following week, I proposed creating a checklist for new project launches. By afternoon, the notes read: “Priya to formalize launch checklist based on recurring gaps flagged by Elena and Marcus.”
My name was nowhere in the sentence.
I told myself I was being petty.
Then our managing director praised Priya in a staff meeting for “finally bringing structure to the handoff process.”
People nodded. Priya thanked him.
I felt heat climb up my neck.
The handoff call had been my idea. At least, I thought it had.
That afternoon I opened the meeting document and clicked Version History.
Priya’s name was beside nearly every change.
Some edits were harmless: punctuation, deadlines, typos. Others changed who appeared to have raised an issue, who owned the next step, and sometimes where an idea seemed to begin.
I spent forty minutes moving backward through six weeks of edits.
By the end, I had a folder of screenshots and a story in my head that felt complete.
Priya was rewriting the record.
And I was going to confront her.
I waited until Tuesday afternoon, when most of the team was out at site visits.
Priya was at her desk with two monitors full of schedules and a paper notebook open beside her keyboard.
“Can I ask you something about the Monday notes?” I said.
She looked up. “Sure.”
“Why do you change them after the meeting?”
“Because the live notes are messy.”
“I don’t mean grammar.”
She waited.
I had planned to sound casual. Instead I sounded like someone reading charges.
“You change attribution. You add people’s names to ideas. You remove other names. Sometimes you attach yourself to the action item that came out of the idea.”
Priya leaned back.
“Okay,” she said. “Show me one.”
I opened my screenshots.
I chose the handoff call because it was the example I felt strongest about.
“I suggested this,” I said. “Then the notes say it was Elena’s suggestion. And last Friday Martin congratulated you for setting up the process.”
Priya read the line.
“You did suggest it on Monday,” she said.
I almost relaxed.
Then she continued.
“Elena suggested it three times before that.”
“When?”
Priya turned to her second monitor and opened a folder.
There were copies of old project retrospectives, team chat excerpts, and previous meeting notes.
She searched Elena’s name and the phrase “handoff.”
The first result was from seven weeks earlier.
Elena had written: “Could we do a short handoff call before delivery starts? We keep losing context between sales and project teams.”
No one had responded.
The second was in a retrospective document I had skimmed.
The third was in meeting notes from a day I had been traveling.
I stared at the screen.
“I didn’t see those.”
“I know.”
Her answer irritated me more than if she had argued.
“So you rewrite the notes to decide who deserves credit?”
“No. I rewrite them so the notes stop pretending that whoever says something loudest on Monday invented it on Monday.”
“A meeting record is not neutral if it only remembers the people everyone already notices.”
I crossed my arms.
“And the checklist?”
Priya showed me that too.
For months, Marcus in production had been keeping his own handwritten launch list because projects arrived missing the same information. Elena had added two fields to a shared template. I had eventually said, “We should make a checklist.”
I had not stolen the idea.
But I had mistaken being the person who turned scattered complaints into a sentence for being the person who created the underlying knowledge.
That distinction was not flattering.
“Why didn’t you just tell me?” I asked.
Priya looked genuinely surprised.
“I thought the notes were telling you.”
I laughed once, without humor.
“They looked like you were editing me out.”
“Sometimes I am editing all of us out,” she said. “Including myself.”
She opened another document.
At the top it said “Open Loops.”
It was not secret. Anyone on the team could access it. I had simply never opened it.
Each row listed a problem, who first raised it, who was responsible for the next step, and whether the issue had been resolved.
My name appeared several times.
So did Priya’s.
Next to one client escalation, the “first raised by” column had my name. The “resolved by” column had Priya and Marcus.
Next to a scheduling problem, Priya’s name appeared under “first raised by,” but Elena’s appeared under “solution proposed by.”
It was the opposite of what I had accused her of doing.
She was separating credit.
Not collecting it.
Priya closed the document.
“Last review cycle, Elena got feedback that she needed to ‘speak up more,’” she said. “She had raised half the problems we fixed that quarter. Marcus was told he was reliable but not strategic. He had designed three of the workarounds everyone else was using.”
“So this is about performance reviews?”
“Partly. It’s about memory.”
She tapped her notebook.
“Offices have terrible memory. The person who summarizes the problem often gets remembered as the person who found it. The person assigned the task gets remembered as the person who solved it. The quiet person who noticed it six weeks earlier disappears.”
I wanted to defend myself, but I could not find the correct defense.
I had not deliberately taken credit from Elena.
That was true.
It was also not the whole truth.
I had accepted praise without asking where the idea came from. I had treated the meeting as the beginning of the story because it was the part I had witnessed.
“Martin praised you for the handoff process,” I said.
“Yes.”
“You didn’t correct him.”
Priya was quiet for a moment.
“I should have.”
That mattered to me.
Not because it proved my accusation, but because it kept her from becoming the perfect person in a lesson designed for me.
“I was tired,” she said. “I built the template. I scheduled the calls. I chased people to use it. When he thanked me, I let him.”
“So you took some credit.”
“For my part, yes. More cleanly than I should have in that moment.”
We sat with that.
Then I asked the question I should have asked first.
“What would better notes look like?”
Priya smiled a little.
“Boring.”
The next Monday, we changed the template.
Every major discussion got three fields: “Issue raised by,” “Decision,” and “Owner.”
If an idea came from an earlier document or conversation, we linked it.
If nobody knew where it started, we wrote “team discussion” instead of attaching it to the most senior person in the room.
The first meeting took ten minutes longer.
My director complained that the notes looked “overengineered.”
Then something unexpected happened.
People started correcting the record in real time.
“That was Marcus’s workaround,” someone would say.
“Elena raised that last month.”
“Priya owns the rollout, but Daniel is testing the client script.”
The corrections stopped sounding accusatory after a few weeks.
They became normal.
During the next quarterly review, Martin mentioned the handoff process again.
This time I spoke before he could move on.
“Elena first raised the gap,” I said. “Priya built the process. I tested the client side.”
It took nine seconds.
No one lost anything.
That was the part I had misunderstood most.
I had treated recognition like a single chair at a table. If Elena sat in it, I had to stand. If Priya received credit, mine disappeared.
But accurate credit was not smaller.
It was more specific.
A few months later, I found one of my own comments changed in the Monday notes.
My first reaction was still annoyance.
Then I read the edit.
I had written: “Daniel suggested revising the client kickoff deck.”
Priya had changed it to: “Client kickoff deck revision based on recurring feedback collected by Sam; Daniel to draft update.”
I remembered Sam mentioning the same complaint twice.
I had forgotten.
I left the edit alone.
Then I added a comment: “Sam—can you review the draft before we use it?”
He replied with a thumbs-up five minutes later.
I no longer take screenshots before closing the meeting notes.
I still check the version history sometimes.
Not because I am looking for proof that someone is rewriting me.
Because I learned that the cleanest version of a story is not always the fairest one.
