Provide the revised duties and knowledge requirements for assessment before relying on the previous transfer plan. Describe whether the change is confirmed or only anticipated.
Align the evidence with the actual version of the work
Update relevant project descriptions and explain new learning or changed responsibilities accurately. Have any implications for a pending or approved matter assessed individually; an internal rollout date does not determine immigration permission. Work with the receiving team to document the upgrade's actual scope, distinguishing what specifically changes in the employee's responsibilities from what remains constant throughout the transition, and note the specific date the current description was last confirmed.
Flag any period where duties are genuinely undefined as an open gap to resolve, rather than describing a transitional role in vague terms that could describe almost any assignment. Confirm whether the upgrade affects the underlying knowledge itself or only the tools used to apply it, since the two require different explanations in the supporting account. Ask the project lead to identify specific milestones within the upgrade and where the employee's role changes at each one, instead of treating the whole transition as a single undifferentiated period that reads the same from beginning to end.
Revisit the description again once the upgrade is further along, since an account written early in a multi-stage transition may already be outdated by the time it is relied upon.