The Work Stopped Coming.
Nobody called a meeting about it. There was no announcement, no formal change in your job description, no conversation with HR about your role.
The work just stopped arriving.
The projects that used to come to you started going to someone else. The meetings where decisions got made stopped including you. The emails that used to be addressed to you started arriving as FYIs, if they arrived at all. The access that defined your standing in the organization began to narrow, quietly and without explanation.
By the time you could name what was happening, months had passed. And months of reduced scope, undocumented and unchallenged, had created a record of an employee operating in a diminished capacity.
WHAT SCOPE WITHDRAWAL IS AND WHAT IT IS NOT
Scope withdrawal is the gradual, undeclared removal of the work, access, and opportunity that define an employee’s role and standing. It is not a restructuring. Restructurings are announced, documented, and applied to positions rather than individuals. Scope withdrawal happens to a specific person, without a formal process, and without the documentation that would make it challengeable as a demotion or an adverse action.
That is the point. A formal demotion is an adverse employment action that can support a legal claim. A quiet withdrawal of scope that leaves the title and the compensation intact while removing the substance of the role is harder to characterize as an adverse action. The employee still holds the position. The position has simply been emptied out.
This is the strategy. The employer does not eliminate the role. The employer eliminates the relevance of the person in it. Then they wait. The employee’s reduced activity level gets documented in check-ins, performance reviews, and management observations as a pattern of decreasing contribution. The decreasing contribution becomes the file that justifies the outcome the employer had already decided on.
HOW THE WITHDRAWAL HAPPENS
Scope withdrawal follows a recognizable sequence. It begins with access. The employee stops being included in meetings where decisions are made. The projects that require strategic input stop arriving. The relationships with senior leadership that used to be direct become mediated or disappear.
Then the work volume changes. Not dramatically. Gradually. Tasks that were previously assigned to the employee start going to other team members. New initiatives that would previously have involved the employee are launched without them. The employee’s contribution to the team’s output begins to shrink without any formal reassignment.
Then the visibility changes. The employee’s work stops being referenced in team meetings. Their contributions stop being cited in leadership communications. The organizational presence that their work used to create disappears as the work disappears.
By the time the employee recognizes the pattern, the employer has months of documentation showing an employee with a diminished footprint. That documentation was not created through any single formal action. It was accumulated through the absence of action. The employer stopped giving work and documented the gap that created.
They did not eliminate your role. They eliminated your relevance.Then they documented the gapbetween who you wereand what the record now showed.
WHAT THE RECORD SHOWS WHILE THE WITHDRAWAL IS HAPPENING
While the scope is being withdrawn, the employer’s documentation of the period is being built around the employee’s reduced activity. Performance reviews note decreasing contribution. Management observations reference a lack of initiative or engagement. Check-in meetings document that the employee has not been taking on new projects.
None of this documentation notes that the work was not given. The documentation of the reduced activity looks exactly like the documentation of a performance decline. And a performance decline, documented over a sufficient period, justifies whatever adverse action follows.
The employee who does not document the withdrawal has only the employer’s record of the period. That record shows a pattern of declining contribution with no reference to the structural cause of the decline. The employer has built a file that explains the outcome without explaining the strategy that produced it.
WHAT TO DOCUMENT RIGHT NOW
If the work has stopped coming, the documentation window is open and the withdrawal is already in progress.
Document what your scope looked like before the withdrawal began. The projects, the meetings, the access, the relationships. The baseline exists in your email history, your calendar, your prior performance reviews. Pull it and record it.
Document the withdrawal itself. When specific projects stopped arriving. When specific meetings stopped including you. When specific access changed. The dates, the context, and whether any explanation was offered.
Request work in writing. An email to your manager noting that you have capacity and asking what you should be prioritizing creates a documented record that you were not inactive by choice. It also creates a record that the reduced scope was structural rather than self-directed.
The work stopped coming. That is not a natural evolution of your role. It is a deliberate withdrawal, and it is being documented against you while it happens. Your documentation of the withdrawal is the counter-record.
If the work stopped arriving without a conversation, the withdrawal has already started.
