Milestones mark key dates in a project — a launch, a client review, a release — and status updates give the rest of the team a plain-English summary of how things are going without anyone opening the project.
Add a milestone
Open the project and go to the Milestones tab.
Click New milestone.
Name it — for example, Beta launch — and set a target date.
Optionally, attach tasks that need to finish before the milestone is reached.
Milestones appear as diamond markers on the Timeline view at their target date, and the project header shows how many days remain until the next one.
Post a status update
Status updates live on the project's Overview tab and are visible to anyone with access to the project, including guests.
Open the project's Overview tab.
Click Post update.
Set a health: On track, At risk, or Off track.
Write a short summary — what shipped, what's blocked, what's next.
Click Post.
Note: Posting a status update notifies every project member. There's no way to post silently, so use it when there's something worth a notification.
Update history
Every status update is kept on the Overview tab in order, newest first, so a new teammate or a returning client can scroll back and read how the project's health has changed over time. Updates can't be edited after posting — if the health changed, post a new update.
Milestones and status updates on Timeline
On the Timeline view, each milestone shows as a diamond and each status update's health color appears as a small badge on the project header. This makes it possible to tell, at a glance and without opening the Overview tab, whether a project heading into a milestone is on track to make it.
If a milestone's target date slips, update the date directly rather than deleting and recreating it — any tasks attached to the milestone stay linked, and the change shows up automatically on Timeline for everyone with access to the project.
Who can post updates
Any teammate with editor access to the project can post a status update or add a milestone — it isn't limited to the project's lead. Guests with editor access can post updates too, which is useful when a client-side contractor is closer to day-to-day progress than anyone internal.
Tip: A project lead who posts a weekly update, even a one-line "On track, nothing new," keeps stakeholders from pinging the team to ask.
