Career Growth
Reset Performance Goals When Your Project or Priorities Change
Close obsolete targets without erasing prior contributions, agree on the replacement assessment basis, and distinguish goal dates from approved allocation weights.
When a project is canceled or your priorities change, reset the performance goal with the person authorized to approve it. Record what happens to the old goal, what work remains relevant, when the replacement starts, and how the revised work will be assessed. Agreeing on today’s tasks does not by itself explain how the original and replacement goals will appear in your year-end review.
This guide from LandOffer.ai shows how to prepare that agreement using public performance-management guidance and a fictional engineering case. The example preserves unfinished work and separates goal dates from rating weights. It is a planning method, not a rule that lets you rewrite an employer’s expectations unilaterally or guarantees a favorable review.

Identify which expectation stopped matching the work
Start with the last agreed goal, including its measure, deadline, dependencies, and owner. Then name the change that made it unrealistic or irrelevant. “Priorities changed” is too broad to explain whether the goal should end, shrink, move, or continue with different support.
A canceled product can remove the opportunity to meet an adoption target. A staffing reduction can change feasible scope. A delayed dependency can leave the business objective relevant while making its original date unworkable. Those are different situations. If the objective still matters, discuss a revised deliverable or date before treating it as closed.
Yale’s mid-year review guidance describes a structured conversation about progress, roadblocks, feedback, and realigning priorities for the rest of the year. That supports raising a mismatch while adjustments are still possible. Its suggested January timing reflects Yale’s process; your employer’s cycle and approval requirements may differ.
Separate the business decision from your performance up to that point. A sponsor’s cancellation does not prove that every earlier milestone was met. Equally, a goal that became impossible after cancellation needs a different explanation from a goal you simply stopped pursuing. Bring the dated decision and the actual work record into the same conversation.
Propose a change that the right person can approve
Ask your manager which changes they can approve and whether HR, a reviewing manager, or the goal system requires another step. Describe your document as a proposal until the necessary agreement is recorded. Editing your own draft or hearing “focus on the new project” does not necessarily update the formal performance plan.
The Teachers College announcement on evaluating and revising goals, dated February 21, 2025, asks employees to consider changing responsibilities and team objectives with their managers. It is a specific employer’s check-in guidance, not a current deadline for other workplaces. The useful principle is to discuss relevance and progress together rather than changing only the wording of a target.
Bring a proposal for both the old goal and its replacement. For the old goal, propose whether it is completed, reduced, deferred, or closed because the work was discontinued. For the replacement, propose the deliverable, success evidence, effective date, and checkpoint. Name the old work that will stop or shrink, such as further pilot recruitment, so the replacement has capacity behind it.
If approval is delayed, ask what you should work on meanwhile and which expectations remain active. Keep the provisional direction separate from an approved goal revision so you can see what still needs confirmation. An unanswered proposal leaves the evaluation basis unresolved. A short written clarification can prevent two different interpretations from surviving until review season.
Completed change record: a canceled adoption goal
The following is a fictional teaching case. Elena Solis is a software engineer in a January–December review cycle. All people, projects, documents, dates, and approvals are invented. No employer performance system was accessed or changed.
Elena’s original goal was to launch an internal planning dashboard and reach 60 percent monthly adoption among the defined pilot group by September 30. The project had six planned pilot teams. On June 24, the sponsor canceled the dashboard after a budget decision and asked the engineering group to prioritize accessibility work in an existing employee portal.
By June 30, Elena had completed onboarding for four pilot teams; two had not started. The adoption measurement had not begun. Her first draft says, “Dashboard goal completed; switching to accessibility.” That would erase the unfinished pilots and confuse cancellation with achievement. The completed change record below is more accurate.
| Decision field | Completed fictional agreement |
|---|---|
| Change and authority | June 24 sponsor decision cancels the dashboard; manager approves this performance-goal revision June 30 |
| Old goal disposition | Close the dashboard adoption target effective June 30 because the launch is discontinued; do not record 60 percent adoption as achieved |
| Prior work retained | Four of six pilot teams onboarded; two not started; adoption unmeasured. Evaluate the completed onboarding and documented handover within their agreed scope |
| Closeout work | Archive the approved design and handover notes in the internal project space by July 10; no further pilot recruitment |
| Replacement and start | From July 1, implement and document accessibility corrections for four specified employee-portal flows by October 15, with release review planned for October 22 |
| Support and checkpoints | Accessibility specialist reviews the test approach; product owner confirms the four-flow boundary. Check scope and dependencies July 15 and progress August 15 |
| Assessment evidence | Approved issue list, change reviews, agreed test records, unresolved defects, and release decision. No claim of whole-product accessibility certification |
The closeout task extends ten days past the old goal’s effective closure. That is intentional: the adoption target ends June 30, while a small, explicitly retained handover obligation remains due July 10. Record that distinction rather than using one date to imply every responsibility vanished.
The replacement also has a bounded result. Elena is accountable for specified corrections, evidence, and raising blockers. A release review is a decision point, not a promise that reviewers will approve everything. If specialist availability or the four-flow scope changes, the record identifies what needs another discussion.
Write the replacement measure before counting progress
A useful replacement goal explains what evidence would support assessment. “Improve accessibility” leaves too much unresolved: which flows, what changes, who reviews them, and what happens to unresolved issues? In the fictional agreement, the issue list and agreed test records make those questions discussable before work is evaluated.
The U.S. Office of Personnel Management’s performance-management cycle guidance describes measurable, understandable, verifiable, equitable, achievable standards and plans that can adjust to changing work requirements. This is federal performance-management guidance; it does not determine a private employer’s approval authority or rating formula. The planning lesson here is to state both the expected work and how it will be checked.
Define what the employee controls and what depends on others. Elena can implement reviewed changes and provide test evidence. She cannot independently approve the release, schedule every specialist, or guarantee that no accessibility issue exists elsewhere. Include dependencies and escalation points so a later assessment does not silently expand the original commitment.
Use a checkpoint to discover a bad measure early. If the product owner cannot agree which four flows are included, the goal is not ready to be treated as a stable target. Resolve that boundary first. Adding a precise date to an ambiguous deliverable does not make the underlying expectation clear.
Completed weight example: dates do not calculate the rating
Some employers use weighted goals; others assess work without a numeric weighting system. If your plan uses weights, ask how the revised allocation is approved and represented. Do not invent a formula because the year has reached its halfway point. Time worked on a project and its importance in a performance assessment are different quantities.
Continue Elena’s fictional case. Her initial plan assigned 40 percent of the annual goal allocation to the dashboard, 35 percent to service-quality responsibilities, and 25 percent to team documentation. For this invented example only, the employer’s process permits this revision and the manager has authority to approve the allocation. It is not a recommended universal weighting scheme.
| Assessment component | Applicable work window | Agreed annual allocation after revision |
|---|---|---|
| Dashboard contribution and closeout | January–June work plus the defined July 10 handover obligation | 10 percent; assess the completed contribution and handover, not the canceled adoption result |
| Four-flow accessibility work | Replacement effective July 1; delivery and release-review dates recorded separately | 30 percent; assess the new goal using the defined evidence and scope |
| Service-quality responsibilities | January–December, unchanged | 35 percent |
| Team documentation | January–December, unchanged | 25 percent |
The total remains 10 + 30 + 35 + 25 = 100 percent. The former 40 percent slot has been divided into 10 percent for prior contribution and closeout and 30 percent for the replacement. These numbers are stipulated managerial agreement in this teaching case. Six months on each project did not automatically produce a 20/20 split.
This is also not a calculation of Elena’s eventual rating. A 30 percent allocation does not mean she has earned 30 rating points, and four completed flows would not automatically determine a score without the employer’s standards. The example records what will be considered and how it is allocated; it supplies no actual appraisal outcome.

If your system allows only one entry for the original goal, ask how to preserve the prior period and replacement in its permitted fields or attachments. Do not quietly overwrite the old text and leave a year-end reviewer unable to reconstruct the change. If numeric weights cannot change, request the applicable assessment explanation instead of maintaining a competing private formula.
Confirm the agreement in the actual record
After the discussion, send or enter the revision through the process your employer uses. The agreed destination might be the performance platform, an approved attachment, or a manager-confirmed document. Keep the required version and access permissions intact. This guide does not authorize taking internal plans, customer details, or private feedback into a personal account.
A concise fictional confirmation for Elena would read: “Please confirm that the dashboard adoption target closes June 30, with the July 10 handover retained; the four-flow accessibility goal begins July 1; and the revised 10/30/35/25 allocation is the basis for this year’s goal assessment. The approved scope and checkpoint dates are in revision 2.” It identifies the decisions without implying that an email alone satisfies every approval step.
Check the record after approval. Does the visible goal show the correct effective date, owner, scope, and measure? Are old targets preserved with an explicit disposition? If the platform still shows the original adoption target as active, ask whether another action is needed. A saved draft and an approved revision are different states.
If you and your manager cannot agree, keep the proposed change and unresolved question identifiable. Ask which existing expectations apply and who can clarify the process. Do not label your preferred version “approved” or stop required work solely because you have documented an objection. A written record improves clarity; it does not remove organizational disagreement.
Revisit the goal when the next dependency moves
At the first checkpoint, compare actual conditions with the agreement. If the accessibility specialist is unavailable, identify the blocked review, the work Elena can continue, and the decision needed. If the flow list expands, discuss which existing work is displaced. Treat another scope change as another explicit revision rather than quietly absorbing it into the same measure.
At year end, summarize performance against the versions that actually applied. Preserve the canceled adoption target’s disposition, the contribution before cancellation, the closeout obligation, and the replacement’s observed result. Do not retroactively present the replacement as the goal that existed in January.
Start now with the obsolete expectation: write its current wording, the dated change that affects it, and your proposed disposition. Ask the authorized approver to decide whether that goal continues, changes, or closes; then record the replacement’s start date and evidence requirements. LandOffer.ai publishes this career guidance; approval and assessment stay with your employer’s process.


