1. LandOffer
  2. Blog
  3. All articles
  4. Your Manager Changed Before Reviews: Reconstruct the Evidence Trail

Career Growth

Your Manager Changed Before Reviews: Reconstruct the Evidence Trail

A fictional manager transition shows a completed period map, source index, review narrative, and unresolved interpretations without promising a rating.

9 min readLandOffer team

When your manager changes before reviews, reconstruct the review period with dated goals, work records, and people who directly observed each part of it. Date the former and current managers' observation windows and identify evidence outside the new manager's direct view. Keep unresolved interpretations visible so a short recent period does not silently become the evidence for the whole cycle.

Confirm who is responsible for your review and how prior-manager input is handled at your employer. This LandOffer guide uses a fictional software-team handover to build a period map and a completed evidence narrative. Public employer and government guidance was checked on October 25, 2026. No manager was contacted, employee record accessed, or rating outcome tested.

Earlier and recent evidence windows remain separate across an October 1 manager-transition divider.

Establish the review boundary and the responsible reviewer

Start with the employer's actual appraisal period, submission process, and reviewer responsibility. Ask who will write the review, who can supply earlier-period input, and how that input should be recorded. A new manager may be the reviewer, but that does not mean they personally observed everything under discussion.

Organizations handle transitions differently. Tulane's published manager guidance tells a new supervisor to gather input from the previous supervisor and relevant colleagues or customers, and document time in the role. Its page also contains cycle-specific dates; those dates are not deadlines for your employer or a future review cycle.

UT Austin's HRSS guidance describes former-manager narrative input for transfers and a separate responsibility arrangement when a manager has left. These are examples of an employer addressing incomplete observation, not universal rules about who must rate you. Ask your current manager or HR contact which arrangement applies locally.

Write the relevant dates into the packet: cycle start, manager transition, evidence cutoff, and review meeting. If the cycle has not ended, label the packet as covering evidence through its cutoff. Do not describe future work as complete to make the map look like a full year.

Match claims to goal versions and observation windows

Organize the handover around dated expectations and observation coverage. For each meaningful period, show which expectations applied, which work happened, who observed it, and what record supports the claim. This lets the new manager choose which claims need source verification or prior-observer input.

Retain prior goal versions when expectations changed. Record the effective date and the decision that changed scope or priority. A discontinued goal is not automatically completed, and a replacement goal should not be applied retroactively to work performed under the earlier agreement. Where the status is ambiguous, ask for clarification rather than rewriting the historical goal to match the current story.

The OPM performance-management cycle connects planning with measurable expectations and monitoring with ongoing feedback. That is federal guidance; it does not impose a private employer's rating procedure. It does provide a useful reason to preserve the expectations against which the work was discussed at the time.

Separate direct observation, contemporaneous records, later recollection, and your own interpretation. A review comment from March can establish what someone wrote then. A colleague's November recollection may help explain it, but should not be presented as if it were a March record. Neither source automatically establishes a rating for the entire cycle.

Completed period map: a late-cycle manager change

This example is editorial fiction. Engineer Rhea has a January 1–December 31 review cycle. Former manager Sol supervised her through September 30. New manager Mina began on October 1, and Rhea prepares an evidence packet through November 20 for a November 27 discussion. December results are outside the packet.

Rhea's work concerns localization-readiness checks for an internal mobile tool. The original plan called for twelve screen checklists by June 30. A July 1 planning decision redirected work toward validation of six priority locale packs; whether it retired or deferred the two unfinished checklists remains a question for review. The fictional scope decision is retained; it is not evidence that all twelve earlier checklists were completed.

Period and goal version Completed fictional evidence Direct observer and limits Question for the reviewer
January–March, plan V1 Rhea authored the first four screen checklists; March review record notes one missing edge case Sol reviewed progress; test lead Cam reviewed the checklists, not Rhea's other duties How should the documented edge-case gap and later correction be represented?
April–June, plan V1 Six more checklists were completed, bringing the total to ten of twelve; two remained incomplete at June 30 Sol and Cam observed this work; checklist records identify Rhea's authorship and Cam's review Confirm ten completed and two incomplete, rather than describe the original goal as fully delivered
July–September, plan V2 Scope decision redirects work to six priority locale packs; three are validated by September 30 Sol observed the first three; release coordinator Ade can verify the acceptance record Confirm the effective scope change and distinguish it from cancellation of all prior responsibilities
October–November 20, plan V2 Two more packs are validated; the sixth remains in review with a recorded issue Mina observes this period; Ade reviews acceptance evidence across both periods Evaluate the recent work within its observation window and retain the earlier three-pack evidence

The counts describe stipulated work records, not measured improvements in product quality or user outcomes. Ten checklists plus five validated locale packs are different deliverables. They should not be added into a single productivity score. Likewise, the sixth pack being in review does not make it a completed validation.

The map also preserves a development issue. Cam identified a missing edge case in March; the April revision shows the correction. Rhea includes both instead of keeping only praise. The reviewer can distinguish an initially incomplete checklist from an issue that remained unresolved all year.

A short recent observation can be accurate without being representative of the earlier period. Mina has directly seen two completed packs and one open issue. Sol's records cover earlier expectations and progress. The packet makes both windows available without asking Mina to pretend she witnessed the first nine months.

Assemble a small handover packet with usable provenance

A handover folder separates source records, observation notes, and unresolved questions before a reviewer’s lens.

Rhea's completed evidence index contains five items. E1 is the January plan V1 with the twelve-checklist expectation. E2 is the June status record showing ten completed and two incomplete. E3 is the July scope decision establishing plan V2. E4 is the September acceptance record for the first three locale packs. E5 is the November 20 status record showing five validated in total and one still in review.

The packet also links the March edge-case comment and April correction under the relevant checklist, rather than treating them as separate accomplishments. Each item has a date, an internal source reference, a short explanation, and its access location. These references are fictional identifiers, not invented live employer links. A real packet should use material the reviewer is authorized to access.

For attribution, E2 identifies Rhea as the checklist author and Cam as reviewer. E4 identifies Rhea's preparation work and Ade's acceptance role. Rhea does not claim sole ownership of the team's release or credit herself with everyone else's review decisions. A shared result needs a clear account of the employee's contribution and collaborators' contributions.

Keep the source request narrow. If the employer permits former-manager input, ask through the agreed route for Sol to confirm the period supervised, expectations discussed, specific work observed, and any unresolved feedback. Do not ask Sol to endorse a predetermined rating, contact someone through an unauthorized channel, or supply information they are no longer allowed to share.

If Sol is unavailable, the packet still has dated plans, work records, and qualified witnesses. Tell Mina that Cam can verify checklist review and Ade can verify locale acceptance. Neither should be asked to reconstruct every aspect of management feedback they did not observe.

Completed review narrative and the questions it leaves open

Here is Rhea's concise fictional handover narrative, written for Mina rather than as an argument for a rating:

This packet covers January 1 through November 20. Sol supervised my work through September 30; your direct observation begins October 1. Plan V1 called for twelve screen checklists by June 30. E2 records ten completed and two incomplete. The March edge-case comment and April revision show an issue that was identified and corrected during that work.

The July 1 decision in E3 redirected the expansion work to six priority locale packs under plan V2. E4 records three validated by September 30. E5 records five validated in total by November 20, with the sixth still in review. I prepared the checklists and validation material; Cam reviewed checklist content and Ade recorded locale acceptance. I am not claiming an unmeasured reduction in defects or sole ownership of the release.

Please use the earlier records and permitted prior-manager input alongside your recent observations. The packet does not cover December results, and I have not treated the sixth pack as complete. I would like to confirm how the two incomplete V1 checklists and the changed scope will be described, and what further evidence you need before the review.

The narrative preserves both progress and limits. It names the changed goal, retains unfinished work, and specifies whose evidence belongs to which period. The source index carries the supporting detail, allowing the narrative to stay short without relying on unsupported summary language.

Mina's completed follow-up record in this fictional discussion contains three questions. First, does E3 clearly retire the remaining checklist expansion, or only defer it? Second, does E5's acceptance definition match E4's, so the five-pack total is comparable? Third, is any relevant feedback missing from the first half of the cycle? Those are evidence questions, not implied criticism or guaranteed grounds for a particular rating.

Rhea answers the second question by pointing to the same acceptance checklist attached to both records. The first remains pending clarification of the scope note. For the third, Cam confirms only the checklist feedback he personally provided; broader former-manager feedback remains unavailable until the employer's permitted process is followed. The packet records those limits; missing former-manager input is not evidence of a positive or negative assessment.

Handle gaps without filling them with confident interpretation

When two accounts differ, write the disagreement precisely. A manager may remember a goal as still active while a planning note appears to defer it. Preserve both references and ask the responsible reviewer to resolve the interpretation through the employer's process. Avoid changing an original record or editing a quote to make the conflict disappear.

A witness's absence is also a limit. If a former manager has left, do not invent their likely assessment or describe a colleague as their substitute for all purposes. Identify the work that can be verified, what remains self-reported, and what needs an authorized management or HR decision. Label the coverage gap so the reviewer can decide what additional input is needed.

Recent feedback belongs in the review, including difficult feedback. The goal is to place it in its actual time and scope, not exclude it because the new manager's window is short. If Mina observes an open issue in November, record it alongside the earlier work rather than either allowing it to erase everything or dismissing it as irrelevant.

Before the meeting, verify dates, access, goal versions, contributor roles, and completion states. Remove duplicate examples and retain the strongest source for each claim. Ask which unresolved question needs another record and which requires the reviewer to exercise judgment. More documents do not automatically produce a more accurate assessment.

Finish with a confirmed review owner, a period map, a brief narrative, and an explicit list of open interpretations. LandOffer's career guides cover related workplace development tasks; the useful result here is a review discussion that can distinguish observed work, supported history, and remaining uncertainty. No evidence packet guarantees a rating, promotion, pay change, or employment outcome.

Sources and Further Reading