Project Stages settings — stages, notifications, analytics

One tab covering what the stages are, who hears about them, and how they actually go — with the sub-tab and even the stage id in the URL.

What it is

Three views of one subject: Stages (names, checkpoints, durations), Notifications (the rules that bind to those stages), and Analytics (how stages actually run and how the plan has changed). Deep links carry the sub-tab as a third hash segment and an optional stage id as a fourth.

Also called: build stages setup · stage automations · stage settings

See it
Project Stages settings — stages, notifications, analytics
Won
44%
Avg cycle
22d
Pipeline
$396k
JanSep
The Project Stages tab with the three sub-tabs and a stage row expanded, address bar showing the four-segment hash. Sample data — no customer information appears here.
How it works
  1. 1The hash is #/settings/stages/<sub>/<stageId>, so Email Studio can hand off to the editor for the exact stage someone was just looking at.
  2. 2The retired Stage Automations tab id lands on the Notifications sub-tab.
Why we built it

The shell comment records the problem: these were 'two unrelated top-level settings tabs (Project Stages and Stage Automations) with no indication they described the same thing… splitting them meant editing a stage in one screen and its notifications in another that never mentioned it.'

The problem
  • Stage definitions and stage notifications were configured in unconnected tabs.
  • There was no way to link someone to one stage's settings.
Sound familiar?
What you get
A stage and its notification rules are edited side by side.
A single stage's settings are linkable.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →