Skip to content
English
More support
  • There are no suggestions because the search field is empty.

Using Milestones in Projects

Once you've created your milestones in Settings, you're ready to start using them to track progress on your projects.

Mark a Task as a Milestone

To flag a task as a milestone:

  1. Create or edit a task in your project
  2. Look for the toggle "Make this task a milestone"
  3. Toggle it on
  4. A dropdown will appear showing all your available milestones
  5. Select the milestone that this task represents (e.g., "Integration/Data Connected")
  6. Save the task

The task is now flagged as a milestone. When you complete this task, the milestone will be marked as hit.

Remove a Milestone Flag

If you accidentally flagged a task or no longer want it as a milestone:

  1. Edit the task
  2. Toggle "Make this task a milestone" to off
  3. Save

The milestone flag is removed, and the task returns to a regular task.

Change a Task's Milestone

If a task should represent a different milestone:

  1. Edit the task
  2. In the milestone dropdown, select a different milestone
  3. Save

The task will now count toward the new milestone when completed.

How Milestones Work With Task Completion

When you mark a task as complete:

  • If the task is flagged as a milestone, that milestone is marked as "hit" for the project
  • The completion date is recorded
  • Dashboard metrics update automatically

One task per milestone: You can flag multiple tasks with the same milestone. The milestone is considered "hit" once any of those tasks is completed.

Completion is permanent: Once a milestone is hit, you can't undo it. If you need to reset a milestone for a project, contact your Onboard admin.

Best Practices

Be intentional about flagging: Not every task is a milestone. Choose tasks that represent actual progress toward value, not busy work.

One important task per milestone: If possible, flag just one high-impact task per milestone. This makes your timeline clear and your data reliable.

Flag early: Mark tasks as milestones when you create them, not after. This ensures consistent tracking across all projects.

Keep milestones in order: In general, tasks flagged for earlier milestones should complete before later ones. (This isn't required, but it makes your data more meaningful.)

Example: Setting Up a Customer Project

Here's how you might set up milestones for a typical customer onboarding project:

Task

Milestone

Notes

Kickoff meeting scheduled and attended

Kickoff Completed

First real touchpoint

System configuration completed

Setup Complete

Admin work is done

Data import and integration testing passed

Integration Complete

Technical work is validated

Customer completes their first workflow

First Value Achieved

They see ROI

Handoff to CSM and adoption begins

Operational

Live and self-sufficient

FAQ

Can I flag a task as a milestone after it's already complete?
Yes. The milestone will be marked as hit immediately when you save the flag, using the task's completion date.

What if I flag two tasks with the same milestone?
The milestone is hit when the first of those tasks is completed. The second completion doesn't re-trigger the milestone.

Can a task have multiple milestones?
No. Each task can only be flagged with one milestone. If a task represents multiple stages, you'll need to choose which one is most important.

Do my team members have to know about milestones to use them?
Not necessarily. If you flag tasks at the project level, milestones will just complete automatically when those tasks are done. Your team just needs to complete tasks normally.

Next Steps