Help center
Open dashboard

Project Stages

Set dated milestones on a project so your team and your clients can both see what is due, what is close, and what has slipped.

Atarim team Updated 20 Oct 2026 · 10 min read
Dashboard
An Atarim board organised by project milestone stages
Before you start

Relevant for

  • Agencies running projects to a schedule, and anyone who needs a client to see progress without asking for an update.

Required knowledge

  • A sense of how your projects are phased — the handful of dated checkpoints that matter on a typical job.

Tools & resources needed

  • A project in your workspace, a plan that includes project stages, and a role with permission to set them.

Project stages break a project into dated checkpoints — discovery, design, development, launch, or whatever phases your work actually has. Each one carries a name and a due date, and Atarim shows how close it is at a glance.

The point is not scheduling for its own sake. It is that a client looking at a project can see where it has got to without emailing to ask, and your team can see what is about to slip before it does.

Milestones For Plausible Analytics panel listing five stages with badges and due dates, from Homepage redesign sign-off (4 days ago) and Wireframes approved (Completed) to Launch, with the red arrow pointing at the in 10 days badge.
Stages are set as dated milestones on each project.
Note on wording
The menu calls these Project Stages, and the panel that opens calls them Milestones. They are the same thing, a named checkpoint with a due date. Inside Collaborate, the panel is called Project Stages and Deadlines.

Stages are not statuses

This is the distinction worth getting straight before you start, because the two are easy to confuse and do completely different jobs.

TracksSet onExample
Task statusOne piece of workEach task“Fix the header spacing” is In Progress
Project stageThe project as a wholeThe project“Design sign-off” is due in nine days

A project can have every task complete and still be mid-stage, or be approaching a deadline with plenty of tasks open. They answer different questions and neither replaces the other.

Who can set stages

Stages sit behind two gates, so check both if the option is not where you expect.

  1. They are a paid feature. On plans that do not include them, selecting the option opens an upgrade panel headed Project Stages, describing them as a way to keep your team and stakeholders aligned so no deadlines are missed.
  2. They are also permission-gated. If your role does not carry the set-stages permission, the option will not appear in the project’s menu at all.

Opening the stages panel

Stages are set per project, from the project’s own actions menu on the Projects screen.

Instructions:

  1. Go to Projects and find the project you want.
  2. Open its Project Actions menu.
  3. Select Set Project Stages. A panel opens headed Milestones for followed by the project name, with a help icon beside it.
Project Actions menu open on the Plausible Analytics card, with the red arrow pointing at Set Project Stages.
Set Project Stages sits in a project’s own actions menu, alongside Assign Team Members, Manage Project Brief, Change Project Settings, Archive, and Delete.
Milestones For Plausible Analytics panel with the Create a new Milestone form and the Active Milestones list, and the red arrow pointing at the help icon beside the title.
Each project has its own Milestones panel, with a help icon beside its title.
Tip
You can also reach the same panel from the Projects tab in Analytics, which is quicker when you are reviewing several projects and updating stages as you go.

Adding a stage

The panel opens with a Create a new Milestone form at the top. It takes two pieces of information.

FieldWhat to enter
Milestone TitleThe name of the stage. The field shows an example, eg. Sprint 1.
Due DateWhen this stage should be reached. Only future dates can be chosen.

Due dates can only be set in the future, so a stage is always something still to come rather than a record of what happened.

Instructions:

  1. Enter a Milestone Title. Name it after the outcome rather than the work — “Design sign-off” reads better to a client than “Phase 2”.
  2. Choose a Due Date. The picker only allows dates in the future, so a stage cannot be created already overdue.
  3. Select Create. The stage appears under Active Milestones with a colored badge showing how far away it is.
  4. Repeat for each stage in the project.
Create a new Milestone form with Client handover as the Milestone Title and October 31st, 2026 picked in the Due Date calendar, where earlier dates are greyed out, with the red arrow pointing at Create.
Only a title and a future date are needed, then select Create.
Recommendation
Three to five stages per project is usually right. Fewer and the client cannot see progress between them; more and you spend longer maintaining stages than delivering the work.
Active Milestones list for Plausible Analytics with five stages and their badges, 4 days ago, Completed, in 4 days, in 7 days and in 10 days, with the red arrow pointing at the in 4 days badge on Content freeze.
Several stages on one project, each with its own badge.

Reading the badges

Each stage carries a badge that changes colour as its date approaches, so a glance tells you where a project stands without reading any dates.

BadgeMeansShows
GreenThe stage is complete.Completed
PurpleMore than two days away.How far off, such as in 12 days
OrangeDue within the next two days.in 1 day, in 6 hours
RedThe date has passed and it is not complete.How long ago, such as 3 days ago
Tip
Orange is your cue to act, not red. Two days is enough warning to move a date honestly or push the work through — by the time a badge turns red the client has already seen it slip.

Updating and completing stages

Existing stages are listed under Active Milestones, each with its own controls. Changes apply to that stage only.

ControlWhat it does
Mark milestone as completeThe clock icon beside the title. Marks the stage done. Its badge turns green and reads Completed.
Mark milestone as incompleteThe green check on a finished stage. Reopens it, in case it was closed early.
Save changesApplies an edited title or date.
Cancel editingDiscards your edits without saving.
More actionsOpens a menu headed Actions with Edit Milestone and Delete Milestone.

Edits happen in place and nothing changes until you save, so you can back out of a change part-way through.

Instructions:

  1. Find the stage under Active Milestones.
  2. Open More actions and select Edit Milestone. The title and date become editable, and the controls change to Save changes and Cancel editing.
  3. Select Save changes to apply, or Cancel editing to discard.
  4. When a stage is finished, select the clock icon, Mark milestone as complete. Its badge turns green, and the project reads as having cleared that checkpoint.
  5. To remove a stage entirely, open More actions and select Delete Milestone. The stage is removed immediately — there is no confirmation step.
The Launch stage open for editing, with its title and October 30th, 2026 date in editable fields and the red arrow pointing at the green save button beside the cancel X.
Each stage is edited in place, with its own save and cancel controls.
Actions menu open from More actions on the Launch stage, with the red arrow pointing at Edit Milestone above Delete Milestone.
More actions opens Edit Milestone and Delete Milestone.
Delete has no confirmation
Selecting Delete Milestone removes the stage straight away, with nothing to confirm and no undo. If a stage is finished rather than unwanted, use Mark as complete instead — that keeps the record.
Moving a date is better than letting it go red
If a stage is going to slip, change the date and tell the client why. A red badge they discover themselves costs more goodwill than a date you moved openly.

Where stages show up

Once set, stages are not confined to the panel you created them in. They surface in five places, which is what makes them worth maintaining.

WhereWhat is shown
Project cardsThe nearest active stage, with its name and how far away it is, in its badge colour.
The Collaborate barA dedicated control on the site itself — see below.
AnalyticsA Project Stage column on the Projects tab, so every project’s stage reads in one table.
Task detailsProject Stage, with the stage’s name and the time left, in Inbox and on Boards.
Email remindersEveryone assigned to the project is emailed when a stage is created or completed, and before and after its due date. The account owner is also emailed the day after a stage’s due date passes without it being completed.
Projects screen with the red arrow pointing at the red Homepage Redesign Sign-Off - 5 Days Ago badge on the Plausible Analytics card.
A stage deadline on the project card, shown in its badge color.

Stages in Collaborate

This is the one that matters for clients. While viewing a site in Collaborate, a control in the bottom bar shows the project’s stages without anyone leaving the page they are reviewing.

Instructions:

  1. Open the project in Collaborate.
  2. Select the stages control in the bottom bar. Its tooltip reads Track project stages and deadlines.
  3. Read the panel, headed Project Stages and Deadlines. Outstanding stages appear under Active Stage with their badge and time remaining. Finished ones appear under Completed Stages with a Complete badge and their due date struck through.
Project Stages and Deadlines panel in Collaborate on the Plausible site, with four stages under Active Stage and Wireframes approved under Completed Stages with its due date struck through, and the red arrow pointing at Completed Stages.
Once a stage is marked complete, it moves to Completed Stages with its due date struck through, and the stages still ahead keep counting down.
The viewer must be signed in
The stages control shows only to people signed in to Atarim who aren’t guests or collaborators. It also needs at least one stage on the project, and it’s hidden on small screens.

Time remaining is written plainly — as remaining while a stage is still ahead, and as overdue once its date has passed — using whichever unit fits, from seconds up to days.

Recommendation
This is the strongest argument for keeping stages current. A client reviewing a page can see the schedule in the same window, which answers “when is this due?” before they think to ask.

Analytics and workflows are covered separately. Explore Analytics And Metrics, or Learn More About Workflow Automation.

Recommendation
Stages chase themselves. Assignees are emailed in the run-up to each due date and again if it passes, so a slipping stage surfaces without anyone remembering to look.

Known limitations

Where stages stop:

  1. Stages are per project. There is no shared template to apply the same set across several projects at once.
  2. Due dates must be in the future when created, so past milestones cannot be backfilled.
  3. Stages are a paid feature and permission-gated on top of that.
  4. Stages do not change task statuses. Completing a stage does not close its tasks, and closing tasks does not complete a stage.
  5. There is no dependency between stages. Each stands alone; completing one does not affect another.
  6. The reminder schedule is fixed. Assignees are emailed 14, 7, 3 and 1 days before the due date and 1, 3 and 7 days after — the intervals cannot be changed or switched off.
  7. Tasks cannot be attached to a stage. Stages track the schedule, not the work items.
  8. Deleting a stage is immediate and has no confirmation step.

FAQs

What is the difference between a stage and a milestone?

Nothing. The menu says Project Stages and the panel says Milestones, but they are the same feature.

How is a stage different from a task status?

A status tracks one task; a stage tracks the whole project. A project can be mid-stage with every task complete, or approaching a deadline with plenty open.

Can I set the same stages across all my projects at once?

No. Stages are set per project, so a standard set has to be recreated on each one.

Can I add a stage with a date in the past?

No. The date picker only allows future dates.

Do clients see project stages?

Yes, if they are signed in. A logged-in client reviewing the site in Collaborate can open the stages control in the bottom bar and see active and completed stages with their dates. Anonymous visitors do not see it.

Do milestones send automatic reminders?

Yes. Assignees are emailed 14, 7, 3 and 1 days before a stage is due, and again 1, 3 and 7 days after it passes. The account owner is also emailed the day after a stage’s due date passes without it being completed. The schedule is fixed.

Can I delete a stage?

Yes — open More actions on the stage and select Delete Milestone. It is removed immediately with no confirmation, so use Mark as complete if you simply want to close it off.

Can I attach tasks to a stage?

No. Stages track the project’s schedule; they are not containers for tasks, and completing one has no effect on any task.

Does completing a stage close its tasks?

No. Stages and tasks are tracked separately — completing one has no effect on the other.

Can a workflow react to a stage?

No. There is no milestone or stage trigger in the workflow catalogue, so an automation cannot react to a stage being created, completed or missed. The built-in email reminders cover the deadline case.

Common issues

  • Set Project Stages is missing from the menu. Your role does not include it. It isn't set in Settings → Workspace Permissions, so ask an administrator about your role.
  • Selecting it opens an upgrade panel. Stages are not included on your plan. The panel names the minimum plan required.
  • You cannot choose a past date. Expected — the picker only allows future dates. Create the stage with a future date, or leave it out.
  • A badge is red. The due date has passed and the stage is not complete. Either mark it complete or move the date.
  • A stage badge is not on the project card. Only active stages appear there. A completed stage will not show.
  • A client cannot see the stages in Collaborate. The control needs a signed-in account that isn’t a guest or collaborator, and at least one stage on the project. It’s also hidden on small screens.
  • Your edit did not stick. Editing needs Save changes to apply. Navigating away or selecting Cancel editing discards it.

Conclusion

Stages work best kept few and honest. Three to five dated checkpoints per project, moved openly when they need moving, tell a client more than any status report — and the colour on the badge means nobody has to ask how it is going.

Stages sit alongside the rest of a project’s configuration, which is covered separately.

Learn More About Setting Up And Customizing Projects

Tips & best practices

  • Name stages after outcomes, not phases. “Design sign-off” means something to a client; “Phase 2” does not.
  • Act on orange, not red. Two days is enough warning to move a date honestly or push the work through.
  • Keep it to three to five stages. More than that and maintaining them costs more than they are worth.
  • Move a date openly rather than letting it slip. A moved date reads as management; a red badge reads as neglect.
  • Check the Projects tab in Analytics to read every project’s stage in one place.

Related articles