Understanding Milestone Versions
Milestone versions let members complete the same milestone more than once — each time as a separate, named version with its own progress and answers. Useful for programs where members repeat a process for different clients, projects, or time periods.
By default, a milestone is a one-time experience — a member works through its steps, completes it, and moves on. But some programs need members to go through the same milestone multiple times. That's what milestone versions are for.
When to use versions
Versions are useful when a milestone represents a repeatable process that members apply to different situations. For example:
- A coaching program where members run the same planning exercise for each new client.
- A monthly review milestone that members complete once per month with different data.
- A framework application milestone where members apply your methodology to multiple projects.
In each case, the steps and questions are the same — but the member needs to go through them multiple times with different context and answers.
How versions work for members
When versions are enabled on a milestone, members can create a new version by giving it a name (like "Client A" or "January Planning"). Each version:
- Has its own set of answers and progress — independent from other versions.
- Can be completed separately — one version can be finished while another is still in progress.
- Is listed in a version selector so members can switch between them.
- Shows its status as either "In Progress" or "Completed."
Members can also delete a version if they no longer need it.
Context milestones
When creating a new version, members may be asked to select versions from other milestones in the same journey. This connects the new version to relevant context — so the AI knows which version of related work to reference. For example, if a member creates a "Client A" version of the implementation milestone, they might link it to the "Client A" version of the planning milestone.
How versions affect the journey
The "what's next" guidance in the journey takes milestone versions into account. If a member has multiple in-progress versions, the journey correctly points them to the next available step across all their active versions.
Frequently asked questions
- Can a member have unlimited versions?
- There's no hard limit on the number of versions a member can create per milestone.
- What happens to existing versions if I disable versioning?
- Existing versions are preserved. Disabling versioning prevents members from creating new versions, but doesn't delete the ones they've already started or completed.
- Can members see each other's versions?
- No. Versions are private to each member. Each person manages their own versions independently.
- Does the AI know which version a member is working in?
- Yes. The AI considers the active version's context when guiding the member, including any linked versions from other milestones.