How should I write achievements after an internal transfer?

In the new level's terms, as scope, action, and dated result, tied to the criteria you co-wrote in week one. Calibration rooms accept sentences that can be verified against an artifact; adjectives and old-team history cannot be defended on your behalf.

What documents belong in a post-transfer review file?

The week-one criteria recap, dated delivery evidence with metrics, stakeholder statements, scope evidence at the new level, your band placement, and the closed handoff from the old team. Assemble them before the review window opens, in that order.

Should I mention my previous team's results in the review?

Briefly, as one dated line, and only where it explains continuity. The new team calibrates on the new scope, so spending your page on previous results leaves the current case thin and invites the old narrative back into the room.

What if my rating ignores the criteria we agreed on?

Respond in writing with the criteria recap, the evidence attached, and a narrow ask: a re-read, a written target list, or a dated review. Keep the tone factual, and avoid relitigating the previous role in the same message.

Post-Transfer Review Language: New Scope, New File

Transfers need new review language: the old scope does not count in the new calibration room. The self-assessment file must speak in new-scope, band terms — the language decides the cycle outcome.

The New File

90-day criteria: co-written deliverables, metrics, and stakeholder exposure become the review spine (see the 90-day guide).
Band phrasing: scope, delivery, and results written in the new level's terms; the promotion case is in the promotion generator and the self-assessment in the review generator.
Calibration record: peer statements, metrics, and the delivery trail (see the calibration guide); the PIP reset language in the transfer PIP guide.

The cycle clock, band reset, and refresher timing are in the transfer cycle guide, the comp audit in the comp audit guide, and the remote transfer rules in the remote transfer guide. Denial follow-ups live in the denial playbook.

Before you sign, get these in writing

The rule text, not a summary: the sentence in the handbook, plan document, or offer letter that states the payout, eligibility, or notice duty.
The dates: the notice date, the last day worked, the effective date of any change, and the date the decision was made.
The name and channel of the decision maker: who approved it, and the email or portal the confirmation was sent through.
Your own copy, dated: save the request you sent and the answer you received, with the timestamp. A record built after access is cut is much weaker.

The Sentence Formula Calibration Accepts

Direct answer: write each achievement as scope, action, and dated result, in the new level's vocabulary. A manager defending you in a calibration room needs a sentence they can read aloud without explanation. Four parts make that sentence.

Scope, named. "Owned the [system/team/process] at [new level], including [decisions or headcount]." Level definitions use scope words, not effort words.
Action, specific. "Rebuilt", "negotiated", "migrated", "mentored two analysts": verbs a reader can verify against a document.
Result, measured, with dates. "Cut response time from X to Y across the [period]" beats "improved responsiveness" in every room.
Attribution, stated. Name what you did versus what the team did. Overclaiming is the fastest way to lose credibility in a review you are not present for.

Build the draft with the Performance Review Self-Assessment generator, then check every line against the criteria you co-wrote in week one. Anything that cannot be tied to a criterion or a dated artifact is decoration.

The Evidence Packet, Assembled In Order

Assemble one file, in this order, before the review window opens.

The week-one recap email: the criteria, the definitions of meets and exceeds, and the checkpoint dates.
The delivery trail: shipped items with dates, the metrics you agreed to, and the artifacts (docs, dashboards, launch notes).
Stakeholder statements: short written quotes from people you now serve in the new scope, with their role and the date.
Scope evidence: decisions you own, people you mentored, on-call or process duty inherited at the new level.
Band placement: the posted range and where your base sits against the midpoint, per the salary band entry.
The old-team handoff note, dated and closed, so the room is not debating a scope you left.

If a PIP exists from the previous role, keep it out of your achievement section and handle it separately with the PIP Response Letter generator, asking that targets be re-scoped to the current duties.

Words To Delete And What To Put Instead

Adjectives lose arguments. Replace them with facts that a reader can check.

"Exceeded expectations" becomes the criterion it exceeded, with the number and the date.
"Worked closely with" becomes the decision you influenced and who owned it.
"Helped the team" becomes the specific deliverable you produced and the peer who can confirm it.
"Since joining" history from the old team becomes one short line; the new scope is the file. See the calibration room entry for how ratings get distributed.
Blame language about the transfer process becomes a factual request: missing criteria, missing band confirmation, missing checkpoints.

Then decide the outcome you want and send it in the same review: a level confirmation, a placement correction with the Promotion & Raise Request Letter generator, or, on a denial, a written target list with a checkpoint date using the Raise Denial Response Letter generator.

Weak Phrasing	Why It Fails	Replacement
Exceeded expectations	No criterion to check against	Name the criterion, the number, the date
Worked closely with X	Suggests participation, not ownership	The decision you influenced and who owned it
Improved responsiveness	Unmeasured adjective	Response time before and after, across a period
Old-team achievements	Wrong scope for this calibration	One closing line, then new-scope evidence
Complaints about the transfer	Reads as friction, not facts	Named missing artifacts with dates

For the current text behind these numbers, start with the California job exit rules page and the New York job exit rules page, along with the Internal Transfer Application generator and the workplace remote reviews guide hub. Those sources state the rule in full; this page only points at them.

Frequently Asked Questions

How should I write achievements after an internal transfer?: In the new level's terms, as scope, action, and dated result, tied to the criteria you co-wrote in week one. Calibration rooms accept sentences that can be verified against an artifact; adjectives and old-team history cannot be defended on your behalf.
What documents belong in a post-transfer review file?: The week-one criteria recap, dated delivery evidence with metrics, stakeholder statements, scope evidence at the new level, your band placement, and the closed handoff from the old team. Assemble them before the review window opens, in that order.
Should I mention my previous team's results in the review?: Briefly, as one dated line, and only where it explains continuity. The new team calibrates on the new scope, so spending your page on previous results leaves the current case thin and invites the old narrative back into the room.
What if my rating ignores the criteria we agreed on?: Respond in writing with the criteria recap, the evidence attached, and a narrow ask: a re-read, a written target list, or a dated review. Keep the tone factual, and avoid relitigating the previous role in the same message.