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. [VERIFY: exact permission label. Likely a Manage Progression or Update Progression permission.] 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. [VERIFY: navigate to the Leadership Progression tab or section on the profile. It may be a dedicated tab in the profile's tab bar, or surfaced inside another tab.]
3. [VERIFY: locate the open milestone you want to update. Confirm the exact UI: whether milestones are listed as items to check off, shown as cards, shown in a timeline view, or otherwise.]
4. [VERIFY: open the milestone for editing and mark it complete. Confirm the control, for example a checkbox, a Mark Complete button, or a date-picker for completion date.]
5. [VERIFY: add an optional note capturing the evidence for completion.] 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. [VERIFY: save. Confirm whether save is explicit or implicit.]
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.

[VERIFY: confirm whether milestone completion can be undone, and by whom.] 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.

[VERIFY: confirm the concurrent-update behavior for progression milestones. Likely last writer wins, consistent with other OneClick 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.

[VERIFY: confirm whether a role change resets, preserves, or rescopes the progression record.] 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.

[VERIFY: confirm whether backdating a completion is supported and any constraints on it.] 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.

[VERIFY: confirm whether team members can see their own progression record. Some stores prefer transparency, others prefer leader-facing only.] 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.

---

Pre-publish checklist

13 00196a02-bd71-4320-afa6-15675bd52ca2 complete Seven sections filled.

14 dad8867c-ebfe-4a6e-88db-c3bb7a3574c1 complete Single-path How-To with decision framework.

15 de2e08b3-8d13-4bc7-b108-9ff3673f8c3a complete Manual-not-automated principle surfaced at top.

16 634f4448-b387-4e73-b856-298472a59fdf complete No em dashes.

17 59819976-42e7-4ae8-a938-add65baebdd5 complete No hedge words.

18 ceb68912-0640-4899-bf63-fc9aacf8f62b complete Permission-based role references.

19 388717c4-16de-4b3a-b699-3820a7173521 complete Voice: leader, not operator.

20 781deb51-1f44-4d54-af49-9c1367882a31 complete No real identifying data.

21 c40fb414-40d2-4285-88d6-372a806c119b complete Passport-versus-Progression distinction reinforced.

22 9e1e4085-1ae3-4b4e-9750-1d526b22aaa1 incomplete UI verified against Production (multiple VERIFY blocks inherited from Leadership Progression scaffold state).

23 57b9ddd6-e725-4625-ae62-2780bcb841ca incomplete Screenshots at decision points (profile with Progression tab, milestone list view, Mark Complete control, note field).

24 e3be37c6-b6e9-4183-882b-d030aa8df23c incomplete Reviewed by Jared and Kevin.

Why this article exists

Surfaced by the Wave 1 cross-link map Pass 3 Batch 3 audit (Turn 45, Flag 42). Both Track a Team Member's Progression and Understand Leadership Progression reference "Update a Progression Milestone" as a placeholder. The distinction between viewing progression (covered by Track) and editing it (this article) is meaningful: viewing happens frequently, updating requires deliberate leader action. Leadership Progression is a retention tool that matters for CFA specifically because the quick-service-restaurant model has limited promotion paths, and a well-maintained progression record helps leaders plan development intentionally. Approved for drafting via the Flag 42 Placeholder Decision Memo (pageId 397344811), Turn 48, as priority 4 in the drafting queue.

Source

Composed from Track a Team Member's Progression v1 (394231868) for the workflow context and Understand Leadership Progression v1 (395051010) for the manual-update principle, the passport-vs-progression distinction, and the three use cases (one-on-ones, promotion decisions, succession planning) that inform when to update. Both source articles are scaffolds with extensive VERIFY blocks; this article inherits the same density and should be resolved together during the Wave 2C Leadership Progression walkthrough (Flag 3).