Recent chats
ASKGEEZ Q&A GUIDECareer & work

How do I prepare for a transfer to another team inside my organization?

Quick answer

Start by confirming the transfer date and who needs to approve or coordinate it. Then list your active commitments, deadlines, dependencies, and handoff needs; discuss those with your current manager. Ask the receiving team about priorities, responsibilities, and what to prepare before you join. Write down agreed owners, dates, and open questions so both teams share the same transition plan.

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

I’m moving to another team internally, but the timing and responsibilities are still a little fuzzy. What should I do first?

Geez

Treat the move as a coordinated handoff, not just a change of team name. First, confirm the proposed transfer date, who is coordinating the move, and which decisions still need agreement. You do not need every detail settled before starting a plan; mark uncertain items as open questions rather than guessing.

Make a short planning sheet with four sections: timing, current commitments, receiving-team expectations, and decisions to confirm. Share the draft with your current manager and the receiving manager or designated contact. Ask them to correct assumptions and agree on owners and dates. If a decision is not yours to make, record who will make it and when you will check back.

Follow-up question

How do I decide what to include about my current work without writing a huge inventory?

Geez

Capture the work that could affect another person, deadline, or decision while you change teams. For each active commitment, note the outcome, next milestone and date, current status, key dependency, and proposed next owner or handoff. Include recurring responsibilities if someone will need to cover them. Leave out background detail that a new owner can find easily; point to the relevant internal document or system by its name, if appropriate.

For example, assuming you have a report due soon, a concise entry could be: “Monthly report — draft due [date]; figures are being checked by [role/person]; next step is review; proposed owner after transfer: [name or role]; open question: who handles final approval?” This makes the work visible without pretending the next owner or approval arrangement is already agreed.

Follow-up question

What should I ask the receiving team so I can prepare rather than arrive and discover everything on day one?

Geez

Ask questions that turn a general welcome into a workable first plan. For example: “What are the top priorities for my first few weeks?” “Which responsibilities will I own, and which will I support?” “What should I read or prepare beforehand?” “Who should I go to for decisions, context, or routine questions?” and “Are there important meetings or deadlines I should know about?”

Also ask what can wait until after you join. That helps avoid treating every request as urgent before you know the team’s priorities. Record answers as expectations to confirm, especially if they affect your current workload or transfer date. If the two teams describe your responsibilities differently, flag the difference and ask the relevant managers to resolve it together.

Follow-up question

Can you show me a compact plan I can take into a conversation with both managers?

Geez

Use a shared draft like this, replacing bracketed text and leaving uncertain items marked “to confirm.”

Internal transfer planning sheet

  • Proposed transfer date: [date] — status: [proposed/agreed/to confirm]
  • People coordinating: [current manager], [receiving manager], [other contact if relevant]
  • Current commitments: [work item] | [next milestone/date] | [status or dependency] | [handoff or proposed owner]
  • Coverage before transfer: [responsibility] | [covering person/role, to confirm if unknown] | [start/end dates]
  • Receiving-team priorities: [first work or outcome] | [expected timing] | [support or context needed]
  • Decisions to agree: [decision] | [person responsible] | [date to confirm]
  • Open questions: [question] | [who will answer] | [follow-up date]
  • Next check-in: [date or “to schedule”]

In the meeting, review the timing first, then current-work coverage, then the receiving team’s initial expectations. Finish by reading back decisions: who owns each next step, by when, and what is still unresolved. Send the updated sheet to the people involved, following your organization’s normal practices for sharing work information. Revisit it if the date or priorities change.

A practical checklist

  • Confirm the proposed transfer date, decision-makers, and any approval still needed.

  • List active commitments, next milestones, dependencies, and recurring duties that need coverage.

  • Mark proposed handoff owners clearly as unconfirmed until the relevant people agree.

  • Ask the receiving team about initial priorities, responsibilities, preparation, and key contacts.

  • Record each open decision with an owner and a date to follow up.

  • Share the updated plan with the relevant people and revisit it if timing changes.

A few more useful answers

What if my transfer date is confirmed but my replacement is not?

Document the work that needs coverage and ask your current manager to decide who will own or temporarily cover it. Keep the proposed owner marked as unconfirmed until that decision is made.

Should I finish every current project before transferring?

Do not assume that every project must be finished or handed off. List the commitments and ask the relevant managers to agree which work you will complete, transfer, or pause.

What if the two teams give me conflicting expectations?

Write down the specific conflict, such as a date or ownership difference, and ask the managers coordinating the transfer to agree on one plan. Avoid silently committing to both versions.

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work