Career Growth
Your Company Reorganized: Confirm What Changed About Your Role and Priorities
A fictional engineer confirms a new reporting line, continuing operational duties, and a resolved priority conflict while keeping rotation, HR, access, and future handoff questions open.
After a company reorganization, confirm the change to your own work before acting on assumptions. Identify the authoritative announcement, effective date, reporting line, continuing responsibilities, changed priorities, and decisions still awaiting an owner. Bring a short before-and-after record to your new manager, resolve conflicting commitments with the relevant people, and write back what was actually confirmed. An organization chart does not settle every delivery, access, or employment question.
This LandOffer.ai guide provides a completed employee clarification packet and a written manager summary with unresolved items preserved. The company, people, work, and dates are fictional. No HR record, system permission, employer communication, or work assignment was changed. Primary guidance was checked October 27, 2026. The process supports role clarity; it does not predict layoffs, guarantee job security, determine employment terms, or assume that you should start looking for another job.

Establish what was announced, and what was not
Start with the announcement and authorized follow-up that apply to your role. Record who issued it and when the change takes effect. Separate a confirmed reporting move from a proposed team name, a rumored headcount reduction, or somebody’s interpretation of a slide. If the source is missing, ask where the decision is recorded; keep the rumor out of your factual summary.
A reorganization can change reporting, responsibilities, decision rights, resources, or interfaces with other teams. These do not necessarily change together. Moving under a platform organization does not by itself authorize you to approve production releases, take another team’s on-call rotation, or stop a recurring operational task. Ask which responsibilities continue during the transition and who can approve an exception.
15Five’s practitioner article addresses role clarity specifically after a reduction in force. It recommends managers and employees revisit expectations, responsibilities, and objectives rather than assume the previous distribution still fits. Its post-layoff context does not establish that layoffs occurred in your reorganization. The useful question here is what your current organization has actually changed, not whether every disruption resembles the source’s example.
Make a short list of sources you can rely on: the announced reporting structure, your current role description, existing commitments, and the approved planning record. If two records conflict, preserve the conflict and ask the responsible owner to resolve it. Do not silently choose the more convenient version or rewrite a prior commitment as though it never existed.
Map responsibilities before rewriting all your goals
A before-and-after table helps you find gaps that an organization chart misses. For each important responsibility, record the previous owner, current instruction, effective date, and remaining decision. Include recurring work and operational coverage, not only visible new projects. A task that disappears from a planning slide may still need an explicit handoff.
The University of Minnesota’s change-conversation guidance encourages clarification, questions, and checking assumptions about how employees experience a change. For the employee, that suggests bringing concrete uncertainties to a conversation rather than trying to decode leadership’s intentions alone. You can acknowledge concern and still ask a practical question: “Who sets my priority when the old and new teams both request work?”
Ask separately about the person who assigns work, the technical decision owner, and the manager responsible for ongoing feedback. A manager can clarify your priorities without having authority over a shared service’s release process. If a new role needs access or training, distinguish approval to perform the work from readiness to do it safely. Do not request excessive permissions simply because a new team name appears next to yours.
MIT’s HR guidance recommends clarity around changing expectations and priorities and aligning individual responsibilities with organizational needs. That supports an explicit conversation about the work. Formal goal revision can follow once responsibilities and effective dates are understood; replacing your annual goals is not the first answer to every unresolved reporting question.
Completed before-and-after record: a reporting move with continuing work
Sana is an engineer at fictional Morrow Data. An October 26, 2026, announcement says her monitoring group will join Developer Platform on November 2 and that Vik will become her manager. Erin is her previous manager. The announcement does not describe a layoff, a new job title, compensation, or a complete redistribution of work. Sana does not turn that silence into a promise about future employment terms.
Before meeting Vik, Sana creates the following record. “Pending” means a question still needs an answer; it is not a new instruction she has decided to apply:
| Area | Before the announced change | Known information and question for the transition |
|---|---|---|
| Reporting | Erin is the manager | Announcement names Vik from November 2; confirm who handles feedback and priority conflicts from that date |
| Certificate-expiration alerts | Sana reviews the existing alert queue and follows the current escalation procedure | No handoff announced; ask whether this continues and whether any coverage changes are approved |
| Configuration-audit draft | Not in Sana’s current work block | Vik has proposed a first draft for November 6; scope, priority, and capacity need agreement |
| Monthly internal CSV report | Sana owes Erin a report planned for November 4 | Ask Erin and Vik whether this is still required, paused, or transferred; no receiving owner has accepted it |
| On-call rotation | Sana follows the current published rotation | A colleague says Platform might combine rotations; no authorized new schedule exists |
| Systems and role terms | Existing approved permissions and recorded role | No formal access, title, level, or compensation change is stated; route questions to the authorized owners |
This record distinguishes a confirmed managerial change from an unconfirmed operating model. Sana still has work to do, but she cannot honestly claim that the old report disappeared or that someone else now owns the alert queue. She also does not treat a colleague’s suggestion about combined rotations as a scheduling instruction.
Her capacity note is equally concrete. In the next work block she has 18 focus hours after other scheduled obligations. The proposed audit draft needs an estimated 12 hours, existing alert work is estimated at four hours, and the old CSV report needs six hours. That is 22 estimated hours before any handoff work. The numbers are fictional planning assumptions, not measured execution times or a legal workload standard.
The table and estimate let Vik decide the immediate work conflict. Sana’s request is not “please explain everything about the reorganization.” It is “please confirm the operating instructions I should follow from November 2, and help resolve the six-hour report conflict with Erin before I promise both deliveries.”
Use the clarification meeting to obtain decisions and owners
Sana requests a 25-minute meeting on October 28. She proposes five minutes for the announced facts and effective date, eight for responsibilities, eight for priorities and capacity, and four to read back decisions. The time allocation is an original example, not a mandatory organization process. She sends the table in advance and asks Vik to add any missing instruction.
Her meeting questions are specific enough to answer:
From November 2, do you own my priority order and ongoing feedback, including requests from the previous group? Until an explicit handoff is accepted, should I continue the certificate-alert responsibility and the published on-call rotation? What is the scope of the November 6 audit draft, and who owns its eventual technical approval? Can we resolve the November 4 CSV commitment with Erin rather than assuming it is cancelled? Who should answer the title, role-record, and access questions that the announcement did not address?
Vik confirms that he will set Sana’s priorities and provide ongoing feedback from November 2. He confirms that the alert responsibility and existing escalation procedure continue during this initial transition. The audit deliverable is a written draft identifying configuration inconsistencies and questions; it is not permission to change production settings. The shared service owner retains technical approval authority.
Vik cannot resolve the old CSV commitment alone because Erin owns that internal report’s use and timing. He agrees to ask Erin for a decision by October 29. He also agrees to ask Noor, the rotation owner, whether a combined on-call schedule has been approved. Until there is an authorized change, the existing published rotation remains the instruction. Neither Sana nor Vik assigns Noor a response date she has not accepted.
The meeting therefore produces some confirmed instructions and two outbound questions. Sana writes those distinctions down rather than compressing the conversation into “Vik approved the transition.” That phrase would hide the unresolved report, rotation, and administrative questions.
Completed summary: resolve one conflict and retain the open items
In the fictional case, Erin replies on October 29 that the November 4 internal CSV report can be paused for this work block and will remain her responsibility to reschedule. She does not claim that it has been transferred to another employee. Sana and Vik then allocate two hours to documenting the current alert process for future handoff discussion. The revised estimate is 12 hours for the audit draft, four for alerts, and two for that documentation: 18 hours.
This resolves the immediate capacity conflict without claiming that every old duty permanently ended. There is still no accepted receiving owner for the alert process. Writing handoff documentation is preparation, not an actual transfer of operational responsibility.
Sana sends Vik the following completed summary on October 30 within the fictional scenario, and Vik confirms that it matches their agreement:
Operating instructions from November 2: You will set my priority order and provide ongoing feedback. I will continue reviewing the existing certificate-alert queue under the current escalation procedure. No production approval rights are added by the reporting change.
Current work block: I will prepare the configuration-audit draft for November 6 within the agreed draft scope, continue alert work, and document the existing alert process. Our planning estimates are 12, four, and two hours respectively against 18 focus hours. If new work or estimates change, I will ask for a priority decision before accepting an additional delivery date.
Previous commitment: Erin confirmed October 29 that the November 4 CSV report is paused for this work block. She retains responsibility for deciding its later schedule. This is not a permanent cancellation or a transfer to an unnamed colleague.
Rotation: The current published on-call rotation remains in force. You have asked Noor about a possible combined rotation; no authorized replacement is available. I will not use the rumor to alter my coverage.
Open administrative questions: I have asked the HR partner where the current role record and any formal changes are documented. The announcement did not settle title, level, or compensation questions. Access needs will follow the existing approval route, based on the actual work required.
Recheck: We will review the audit draft’s status, the rotation question, and any administrative responses on November 6. That date is a check-in, not evidence that the work or outside decisions are complete.
The clarification is complete; the transition and outside decisions remain unfinished. It names the confirmed manager, continuing work, a resolved scheduling conflict, and specific unresolved questions. Vik’s confirmation supports those operating instructions within the fictional case; it does not constitute an actual employer approval or change anyone’s contract.
Sana keeps the original table and the dated summary in the approved workspace. When an answer arrives, she can update the relevant row with its source and effective date. She preserves the earlier uncertainty and the actual decision date.

Handle new requests while responsibilities are still settling
When an old stakeholder asks for work, explain the current arrangement without implying that their need no longer matters. Sana could say, “Vik now sets my priorities. The CSV report is paused for this block under Erin’s October 29 decision. Please route a changed requirement through them so we can agree what moves.” This names the decision rather than using the reorganization as a blanket refusal.
If instructions conflict again, bring the exact requests and deadlines to the decision owner promptly. For urgent operational matters, use the established escalation route instead of waiting for the next transition meeting. Keep continuing responsibilities visible until an authorized decision and, where required, an accepted handoff change them. A new manager does not eliminate the need for safe coverage.
For changes affecting pay, location, hours, benefits, or other employment terms, ask the appropriate HR or specialist contact for the actual documentation and process. Do not use this operational summary to make personal legal or tax conclusions. Equally, an unanswered question is not proof that a negative change will occur. Separate what you need to know now from a prediction about the company’s future.
Adapt the role table and manager summary, confirm your next work instructions, and recheck open questions on the agreed date. LandOffer.ai publishes this workplace guide; it does not determine your reporting line or administer your employer’s reorganization.


