Your manager leaves on Friday. On Monday, a new person asks what you are working on and why a particular deadline matters. The project did not become new over the weekend, but the explanation suddenly did. Without a handoff, employees can end up reconstructing decisions while still being expected to deliver the work those decisions created.
The first meeting with a new manager does not need to settle your entire career. It does need to establish which commitments remain active, who can make decisions, and what happens when the new priorities conflict with the old ones. A pleasant introduction helps. A working agreement helps when two departments both expect their request first.
Bring the current work, not your whole history
Prepare a short picture of the work already in motion. Include the outcome, deadline, people depending on it, and any decision that is holding it up. Existing documents should do most of the work; you do not need to write a personal archive of every project. The purpose is to make current obligations understandable to someone who did not hear the original discussion.
Distinguish commitments from suggestions. A promised delivery date is different from an idea raised in a meeting. An approved purchase is different from a request waiting for approval. If those categories are mixed together, the new manager may treat unfinished proposals as established instructions or reopen something another team is already relying on. Label the status and link to the relevant record.
You can also note work that is less visible: maintaining a shared file, handling recurring requests, or answering questions from another department. Do not inflate every small favor into a formal responsibility. But if the organization depends on a task being done regularly, it belongs in the picture. Otherwise a new set of priorities may be added on top of an unseen workload rather than replacing anything.
Find out who holds the decisions now
A new reporting line does not explain every approval path. Your manager may be able to change internal priorities but not a customer commitment, staffing level, or budget. Ask where those decisions now sit and what should happen while a request is waiting. Employees cannot resolve an authority gap by guessing which person sounds most confident.
In a hypothetical situation, an outgoing manager approved two days for a testing task before a delivery. The new manager wants to use those days for a separate request. The relevant discussion is not whether you seem flexible. It is which result is now expected, whether the original delivery changes, and who tells the people affected. A reassignment needs an updated plan, not simply a second deadline.
If the answer is that both tasks must happen, ask what resource or scope change makes that possible. More work can be a real business decision, but it should be described honestly. A transition is not a reason for deadlines to stop adding up. You can make the conflict visible without claiming the authority to decide which obligation the organization should drop.
Separate a preference from a changed condition
A manager may prefer a weekly written update instead of a standing meeting. That is different from changing your schedule, responsibilities, or an established working arrangement. Put these in separate conversations. A discussion about communication should not quietly become an agreement to be available at different hours or to take over a different role.
For any existing arrangement, identify what is recorded and where. This might be a team schedule, an HR confirmation, or a specific project agreement. Do not rely only on the fact that the previous manager knew about it. At the same time, do not assume that every new preference overrides formal terms or applicable policy. If there is disagreement, involve the responsible channel rather than treating the first conversation as the final ruling.
The goal is clarity, not immediate confrontation. You might explain that a particular schedule was agreed through a certain process and ask whether the manager has received that information. That gives them a way to check the existing arrangement. If a change is proposed, ask for the actual proposal, its timing, and the process for resolving it. This article does not establish legal rights for your particular employment situation.
Agree on updates that lead to decisions
Ask what the manager needs to know to do their part of the work. A useful update could cover progress, changes to the plan, and a decision needed by a specific date. If every update is a long list of activities, the important request can disappear. A short message that names the blocked decision may be more useful than a polished report with no clear next step.
For example, an invented update might say: The draft is complete. Legal review is still pending. We need a decision by Wednesday on whether to move the launch or reduce the first release. This does not replace the underlying documents. It tells the manager what requires attention and why. Agree on a reasonable place and rhythm for such updates so neither person has to search several channels.
Urgent issues need a different route from routine reports. Clarify how to flag a problem that cannot wait until the next scheduled meeting, and who covers when the manager is unavailable. This does not mean every message should be answered immediately. It means the team should have an understood way to distinguish a developing problem from ordinary background information.
Do not let the transition bury a serious concern
Some issues need action before the new manager has learned everyone's job. If a concern affects workplace safety, use the appropriate reporting process rather than saving it for a general introductory meeting. OSHA's management leadership guidance describes establishing responsibilities and encouraging communication about safety and health as management functions. That guidance is about safety programs, not a rule for every performance conversation.
For an ordinary project concern, be specific about what is known and what remains uncertain. A missing approval, a delayed supplier response, or two incompatible deadlines gives the manager something to investigate. A general warning that the department is chaotic may express a real frustration but offers less guidance about the next decision. You do not need to hide the pattern; connect it to a current example.
Avoid making yourself the sole keeper of that history. If an issue belongs to the team or another responsible role, the record should be accessible through the proper work system. A manager transition can reveal that key information lived only in one person's memory. The organization needs a way to preserve it that does not depend on that person being permanently available.
Close the first meeting with a usable record
A short follow-up can capture the decisions, unresolved questions, and next review date. Write it as a record of what was agreed, not a transcript or an attempt to secure approval for things never discussed. If you understood a priority differently, the written note gives both people a chance to correct it while the conversation is still recent.
Separate immediate agreements from longer-term goals. You might confirm this week's delivery and approval path now, while scheduling a later conversation about development or the team's future structure. Putting everything into the first meeting can leave urgent work less clear rather than more. A new manager needs time to learn, and employees still need timely decisions while that learning happens.
A few weeks later, revisit the arrangement against actual work. Are decisions reaching the right person? Are updates useful? Did an old responsibility continue after a new one was added? The transition is working when those questions have clear answers. You should not have to start your job from scratch merely because the person overseeing it has changed.
