I Sat Through a Staff Meeting Where My Department Lead Claimed My Project Timeline – Part 2

Story code: ST-000146

Part 2: The Dates Started Talking

Once Eli asked that question, the room stopped moving like a meeting and started moving like people checking whether they had just heard something wrong. Gavin still stood at the front with one hand on the blue project folder, but now every date he said had somewhere to land.

He gave a short smile that didn’t last. “Version names change during development. That’s not unusual.”

Eli said, “Sure. I’m asking about order.”

Renee leaned back from the table and said, “Clarify the sequence, Gavin.”

That was the first shift. Ten minutes earlier, I had been told to save it for discussion. Now the same sequence that was supposed to wait until the end had to be explained in the middle.

Gavin clicked back to his slide with the dates. “March 12 was the first version that could actually be used as a working timeline.”

I spoke before Renee could stop me. “Then why was the March 11 version already labeled V3 on the shared draft list?”

She looked at me, but she didn’t cut me off this time.

Gavin answered without turning around. “Because earlier pieces were informal.”

I said, “Then they weren’t earlier pieces in your folder sequence. Your slide says your draft starts the project.”

A chair scraped on the far side of the table. Someone turned over a printed agenda but didn’t look at it.

Eli kept his voice flat. “Was March 12 before or after the team check-in where Maya walked us through dependencies on the screen?”

That one landed because it was simple. Not an accusation. Just a basic meeting-memory question.

I said, “Before would be impossible.”

Gavin said, “We’re getting lost in labels.”

Eli shook his head once. “No, just dates.”

Renee turned to me. “Maya, keep it factual. What are you saying specifically?”

I put my notebook on the table so it was visible and read from what I had written. “On March 11, I presented Version 3 in the Wednesday check-in. I walked through dependencies, owner columns, and rollout order on the front screen. That was before March 12. So if his March 12 draft is the first usable timeline, the numbering makes no sense and the meeting sequence makes no sense.”

Gavin opened the blue folder and pulled out a packet. “This is the working draft I’m referring to.”

Nina spoke for the first time. “Can I see the tab?”

He looked at her, then handed the packet across. Nina didn’t take the pages first. She looked at the folder itself. “No, the tab.”

She pointed at the orange Drafts divider. “That label isn’t from the first pass. We changed the tab names after the operations sync.”

The room got still again.

Renee said, “What do you mean?”

Nina kept her answer narrow. “The first pass used ‘Build’ and ‘Review.’ Later I relabeled them to match the shared draft list. Drafts, Review, Final. That happened after Maya had already circulated version names to the team.”

Gavin put his hand back on the folder. “Tabs get updated. That doesn’t change ownership.”

Nina said, “I didn’t say ownership. I said order.”

That was the second shift. People stopped listening for rank and started listening for sequence.

Renee looked from the folder to the screen. “When exactly were the tabs changed?”

Nina answered right away. “The morning after the check-in. I remember because I had to replace a crooked spine sticker too.”

I looked at the white sticker near the folder spine. Even from my seat I could see where the old label had been pulled off unevenly.

Eli said, “So the folder as it sits there now has later labeling on it.”

“Yes,” Nina said.

“And the packet Gavin is using as the starting point sits behind a tab system that didn’t exist at the start,” Eli said.

Gavin exhaled through his nose and started talking faster. “The labels are administrative. The substance came from leadership direction and refinement over several passes. We are not going to reduce this to divider colors.”

But nobody had mentioned colors like they mattered more than dates. They mattered because they placed the folder in time.

Renee folded her agenda in half. “Then let’s not reduce it. Walk me through the handoff.”

Gavin said, “What handoff?”

I turned toward Nina. “When a lead claims a draft as official, where does the folder go next?”

Nina answered with both hands on the table. “Coordinator review. Then indexing. Then it goes back for signoff to present in staff.”

I said, “Did that happen here?”

Nina looked at the folder, then at Gavin. “I indexed later materials in it. I did not log an initial coordinator handoff before the version names were already in circulation.”

Gavin cut in. “Because we moved quickly.”

Eli said, “Moved quickly around a required step?”

No one laughed. No one shuffled papers. The room had gone too quiet for that.

Renee put both palms on the table. “Hold on. If the initial handoff never happened when Gavin says his draft became official, then his sequence has a gap.”

I said, “Not a gap. A missing event.”

Gavin started answering before she finished speaking, stacking phrases on top of each other. “We had verbal alignment, iterative development, practical ownership, and evolving documentation-”

Renee lifted a hand now, not to stop me, but to stop him.

“Don’t summarize,” she said. “Show the order.”

Gavin looked down at the blue folder, and for the first time that morning, it looked less like proof and more like something that had been opened in the wrong order.

Because if the coordinator handoff never happened when he claimed it did, there was only one way that folder could have ended up in his hands at the front of the room, and Part 3 is where that missing step had to be rebuilt out loud.


Leave a Comment