Update a Progression Milestone

At a glance

Updating a Progression Milestone marks a step complete on a team member's internal development track, with an optional note explaining the evidence. Progression is manual by design: you update the record when you have observed the team member demonstrate readiness. There is no auto-advancement based on other OneClick activity, so the accuracy of a team member's record depends entirely on leaders keeping it current. Plan updates around one-on-ones, reviews, and specific events so the record reflects reality.

Before you start

1. You need a role with permission to update Leadership Progression milestones. Manager-level access or higher is required to update progression milestones. Typically this is limited to leaders who own development for the team member.
2. Have the evidence in hand before you update. A milestone should be marked complete when you have observed the team member demonstrate the specific competency or completed work the milestone requires. Updating from hearsay creates a record that will not hold up in a promotion conversation.
3. Know which milestone you are updating. If the team member has multiple milestones open, be specific about which one and why.
4. If you are updating after a coaching conversation, consider adding a note on the milestone that captures the evidence. Notes are visible on future views of the progression record and make the record useful in subsequent conversations.
5. Estimated time: under two minutes per milestone.

Steps

1. Open Team from the left navigation menu and open the team member's profile.
2. Open the team member's profile and select the Progression tab.
3. Milestones are listed within each stage as individual items with a completion indicator. Incomplete milestones show an open circle or checkbox; completed milestones show a filled indicator with the completion date.
4. Click the milestone to open its detail view. Use the Mark Complete control (checkbox or button) to record the completion. A date field captures when the milestone was achieved.
5. An optional note field is available in the milestone detail view. Use it to record the evidence or context for the completion, such as a passport the team member finished or a specific observation. Note content is visible on future views of the record, so write it for the next reader: the team member themselves, another leader, or you six months from now during a promotion review.
6. Save the milestone update. Changes require an explicit Save action; closing the view without saving discards unsaved changes.
7. Verify. The milestone should now display as complete, with the completion date and your name as the updater. If the team member's current stage advances based on the completion, that also reflects in the progression view.

Video

Video coming soon.

Common gotchas

I marked a milestone complete by mistake.

Milestone completion can be reversed by a leader with Manager access or higher. Open the completed milestone and use the revert or undo control to return it to an incomplete state. If it can be undone, follow the same workflow in reverse on the milestone. If not, contact support with the team member's name, the milestone, and the approximate time of the update so support can restore prior state.

The team member did the work but I did not see it personally.

Two choices. First, gather the evidence from whoever did see it (another leader, a rater's notes, a completed passport). If the evidence is solid, update the milestone with a note attributing the observation to the other leader. Second, if you cannot confirm it yourself, do not update from hearsay. Use the coaching conversation to reset expectations; the team member can demonstrate the milestone when you are present to observe.

Two leaders tried to update the same milestone at different times.

Concurrent updates to the same milestone follow last-writer-wins behavior, consistent with other OneClick record surfaces. If you discover that a milestone update was overwritten by another leader, review together and align on the canonical record during a one-on-one.

A team member has stamped the relevant Passports but a progression milestone tied to those Passports does not auto-complete.

Working as designed. Leadership Progression is manual. Stamping a Passport is evidence that a related progression milestone may now be appropriate to update, but nothing advances the milestone without a leader action. Update the milestone when you have decided the team member is ready, not when Passport state suggests they might be.

A team member's role changed and their progression record looks inconsistent.

A role change does not reset or rescope the progression record. All completed milestones and notes are preserved. If the record does not match what you expect after a role change, pause before updating further; contact support to confirm the expected behavior.

I cannot find the Update or Mark Complete action.

The action requires the progression update permission. If you have view access but not update access, you will see the milestones but cannot change them. See Request a Permission Change if your role should carry the update permission and does not.

I want to update a milestone with a past completion date.

Backdating a milestone completion is supported. Enter the actual completion date in the date field when marking a milestone complete. If backdating is supported, use it sparingly: the record is most useful when the completion date reflects when the evidence was observed. If backdating is not supported, use the completion note to explain when the actual demonstration happened.

A team member wants to know their own progression status.

Whether team members can view their own progression record depends on store configuration. Contact your operator to confirm the visibility setting at your store. If self-view is supported and your store allows it, the team member can see the same record you see. If not, share relevant context during one-on-ones based on what you see in the record.

Related articles

1. Track a Team Member's Progression (How-To Guides) for viewing a progression record.
2. Understand Leadership Progression (Reference) for the module's conceptual model, including why progression is manual.
3. Understand the Passport Lifecycle (Reference) for the related but distinct position-certification model.
4. Understand Permission Levels (Reference) for the role-to-permission model that gates update access.
5. Request a Permission Change (How-To Guides) if the update permission is missing.

Still stuck

If a milestone will not save, the Update action is missing, or the progression record shows inconsistent state after an update, submit a support ticket with:

1. Your store number.
2. The team member's name.
3. The milestone being updated.
4. What you tried to do and what happened versus what you expected.
5. A screenshot of the progression view.

Support typically responds within one business day.