My Coworker Kept Booking Meetings Under My Name—And I Finally Asked Why
The first meeting appeared on my calendar on a Tuesday afternoon.
Vendor Escalation — Organizer: Claire Morgan.
I was Claire Morgan.
I had not organized it.
I assumed I had forgotten.
My weeks were full of customer calls, planning sessions, and the kind of internal meetings that produced more meetings. Forgetting one was possible.
Then a second invitation appeared.
Then a third.
Each listed me as organizer.
Each involved Daniel, a project coordinator on my team.
By the fourth, I knew I had a problem.
I opened the calendar details and saw that Daniel had created the event from our shared project calendar, then changed the organizer display to my name.
Technically, anyone with editor access could do it.
I had never imagined anyone would.
My first thought was petty and immediate.
He was borrowing my title.
I was a senior program manager. Daniel was twenty-eight, smart, ambitious, and one level below management. He had asked twice that year about promotion requirements.
Now vendors were receiving invitations that looked as if they came from me.
I felt used.
I started collecting examples.
A supplier dispute.
A budget clarification.
A call with our legal team.
In every case, Daniel attended.
In most cases, I did not.
At lunch, I mentioned it to another manager.
“Maybe he thinks people respond faster if your name is on it,” she said.
That was exactly what I feared.
“That is not okay.”
“No.”
Her immediate agreement made me feel more certain.
By Friday I had drafted a formal message to Daniel about misrepresentation.
I did not send it.
Something about putting accusation into email made me hesitate.
Instead, I asked him to come to my office.
He arrived carrying a notebook.
“What’s up?”
“Why are meetings being scheduled under my name?”
He stopped opening the notebook.
“Which meetings?”
“Daniel.”
He looked embarrassed.
“Okay.”
“How many?”
“I don’t know. Maybe seven?”
“Seven?”
“Maybe eight.”
I felt my voice sharpen.
“Why?”
He took a breath.
“Because people don’t come when I schedule them.”
I had expected ambition.
I had not expected that.
“What do you mean?”
He showed me his calendar.
Two months earlier, he had scheduled a meeting with Finance about delayed purchase orders. Three people declined. One ignored it. The issue remained unresolved for nine days.
The following week, he scheduled another meeting about the same problem and listed me as organizer.
Everyone accepted within an hour.
“So you decided to keep doing it?”
“I know how it looks.”
“It looks like you are using my identity to get people to show up.”
“Yes.”
I appreciated that he did not argue.
Then he said, “But the reason it works is a problem too.”
I crossed my arms.
“Explain.”
Daniel opened his notebook.
He had tracked response times.
Not officially. Just for himself.
Requests he sent as coordinator were often ignored for days.
The same requests forwarded by me, or by another manager, were answered within hours.
It was not every department.
It was especially bad with Finance and two outside vendors.
“Why didn’t you tell me?” I asked.
“I did.”
“When?”
He searched his email and found a message from six weeks earlier.
The subject line was: Escalation process question.
I remembered skimming it.
I had replied: Use judgment and escalate when necessary.
At the time, I thought I was empowering him.
He interpreted “escalate” as using the one signal people consistently respected: a manager’s name.
I leaned back in my chair.
“You still cannot put my name on meetings without asking.”
“I know.”
“But I should have understood what you were telling me.”
He nodded.
A broken process often survives because junior employees quietly invent workarounds that senior employees never have to see.
We reviewed all eight meetings.
None had been personal.
None had benefited Daniel individually.
Every one involved a stalled project issue.
That did not make his solution acceptable.
It did make the problem larger than his judgment.
I asked him to stop using my name immediately.
Then I did something uncomfortable.
I tested his claim.
On Monday morning, Daniel sent a routine request to one of our vendors asking for updated delivery dates.
No response.
Tuesday afternoon, still nothing.
I forwarded the exact same message with one sentence: Please prioritize Daniel’s request below.
The vendor replied in eleven minutes.
I stared at the timestamp.
The issue was not imaginary.
That week, I pulled response-time data from our shared mailbox and compared requests by role.
The pattern was messy but clear enough. Coordinators waited longer. Managers got answers faster even when the content was identical.
I presented the examples at our leadership meeting.
One manager said, “That’s just how escalation works.”
I disagreed.
“Escalation is for urgency. We are using hierarchy as a substitute for basic responsiveness.”
Another manager asked whether Daniel had violated policy.
“Yes,” I said. “And I addressed that with him.”
Then I added, “But if we only discipline the workaround and ignore the reason it worked, we will teach people to hide the next workaround better.”
We changed two things.
First, meeting organizers had to remain the person actually scheduling the meeting. No borrowed names.
Second, cross-functional requests received a defined response window regardless of job title. If an answer could not be provided, the recipient still had to acknowledge the request.
It was not revolutionary.
It was a rule that should have existed already.
Daniel apologized to the people who had received invitations under my name.
I documented the incident in his coaching notes because pretending it had not happened would have been dishonest.
But I also documented the process problem he exposed.
Three months later, he applied for promotion.
During the review, another manager asked whether the calendar issue should count against him.
“It should count as a judgment mistake,” I said.
“So yes?”
“Yes. And his response after being corrected should count too.”
Daniel had not defended the workaround. He helped replace it.
That mattered.
He received the promotion.
On his first day as an associate manager, he sent me a calendar invitation.
The organizer line said: Daniel Ruiz.
The title was: Process review—no borrowed authority required.
I accepted.
Then I walked down the hall and told him the joke was terrible.
He said that was the price of management.
He was probably right.
Want another story you can finish on a short break? Browse our 5 minute short stories for adults.
