The timeline covers eighteen months. We are going to walk through it in compressed form, because the compression is part of the point: credit absorption happens so slowly that no single incident would survive a complaint, and the cumulative effect is only visible when you lay the incidents end to end and see the arc.
A program coordinator, let us call her Lucia, designs a community health navigation system for a mid-sized nonprofit. She builds it from scratch over three months: the referral pathways, the data tracking infrastructure, the community partner agreements, the training materials for the navigators. Her supervisor, David, is supportive throughout the build. He provides resources when she asks. He praises the work in their one-on-ones. He is, by any reasonable assessment, a good manager.
Month Four: David presents the navigation system to the organization's leadership team. Lucia is not in the room. David's presentation slides reference "the team's work on the health navigation initiative" and include two of Lucia's flowcharts, reformatted with the department's header. When Lucia asks why she was not invited to present, David says the leadership team meeting has a limited roster and he thought it would be more efficient for him to represent the department. The explanation is plausible. Lucia accepts it.
Month Seven: The organization's annual report includes a section on the navigation system. The section credits "the department's innovative approach to community health referrals." Lucia's name does not appear. David's name appears as department lead. Lucia notices but does not raise it because the annual report is already published and raising it now feels like asking to be praised retroactively, which triggers a shame response she has been carrying since her first professional job, where she was told by a senior colleague that "wanting recognition is a sign you're doing the work for the wrong reasons."
Month Ten: David is promoted. The promotion announcement cites, among other accomplishments, "the development of the community health navigation system." The system is now officially part of David's professional record. Lucia reads the announcement on the organization's intranet and feels something collapse quietly in her chest.
Month Twelve: Lucia begins keeping a Receipts Ledger, not because she has read about the concept, but because she has started to suspect that what is happening is a pattern and she wants to know whether her suspicion is accurate or whether she is, as she fears, being petty. She opens a spreadsheet. Five columns: Date, Deliverable, Audience, Attribution, Evidence. She goes back through her email and fills in entries for the past year.
The ledger takes two hours to build from the archived emails. When she finishes, the pattern is unmistakable. Twelve deliverables. Her name appears in the upstream communication for two of them. David's framing appears in all twelve. The two where her name survived were both situations where she had sent the deliverable directly to a board member with her own cover email, bypassing the normal chain of custody.
Month Fourteen: Lucia schedules a one-on-one with David. She brings the ledger, not the spreadsheet itself but a printed summary of three representative examples. She uses language close to the Private Boundary script: "I've been tracking how our department's work is presented upstream, and I've noticed that my specific contributions haven't been individually attributed in the last year. I want to make sure future communications reflect who designed and built what. Can we talk about how to handle attribution going forward?"
David's response is illuminating. He does not get defensive. He does not deny it. He says: "I think of the work as the department's. I don't think of it as mine or yours. We're a team." He is sincere. The sincerity is the problem.
David has absorbed Lucia's work into a departmental identity that he, as department head, represents. In his experience, he is being inclusive by saying "we." In the organizational effect of his language, "we" means "me," because he is the one in the room when "we" is discussed at the leadership level. The absorption is structural, built into the relationship between a department head and a program coordinator, and David's sincerity makes it harder to address than intentional credit theft, because the person absorbing the credit genuinely does not see himself as stealing.
Month Sixteen: Lucia starts practicing evidence-forward communication. Every deliverable she completes goes to David with a sentence that establishes authorship: "Attached is the navigator training module I designed this week, incorporating the feedback from the pilot sites." She copies herself on every email. She begins sending quarterly summaries directly to the leadership team, framed as department updates, with her name as the contact for each initiative.
The shift is gradual. Leadership starts emailing her directly about the navigation system. David notices. In a one-on-one, he says: "I've noticed you're communicating more directly with the leadership team. I just want to make sure we're coordinating on messaging." The sentence is a gentle reassertion of the gatekeeping function that produced the absorption in the first place.
Lucia responds: "I think it's important that the people who do the work are visible to leadership. I'll keep you in the loop on anything that affects department strategy." She is calm. She is specific. She does not ask permission.
Month Eighteen: Lucia applies for a director-level position at a different organization. In her application materials, she includes the Receipts Ledger, reformatted as a portfolio of accomplishments with dates, outcomes, and evidence links. She gets the position. At her exit interview, when asked what would improve retention at her current organization, she says: "Attribution. When people's work is visible, they stay. When it's absorbed, they leave."
The organizational cost of Lucia's departure is significant. The navigation system she built requires six months to transition to a new coordinator, and during the transition, referral rates drop by 40%. The community partners she cultivated call the organization asking what happened to Lucia. David presents the transition plan to the leadership team, and for the first time, the leadership team asks a question that reveals the gap: "Wait, Lucia designed the whole system? I thought this was a departmental initiative."
It was a departmental initiative. It was also one person's design, one person's execution, one person's relationships. The department was the frame. Lucia was the content. When the content left, the frame held nothing.
I do not know whether David learned anything from Lucia's departure. I do know that the ledger she kept, which started as a private tool for clarifying her own perception, became the evidence that secured her next role. The documentation did not save her position at the original organization. It saved her career trajectory. The receipts did not change the system that produced the erasure. They gave her the records she needed to build something outside the system, on terms where her authorship was a matter of documented fact rather than organizational interpretation.