Gates stage the project
Each gate carries a code, a name, an optional description, its position in the order, and the number of tasks sitting in it. The project tracks which gate it has reached.
Milestones
& Gates
Structure work can be held to.
Gates stage a project. Milestones group the work that has to land together. Sections organise what sits beneath them. When a milestone is ready to close, you see exactly what that will change before it changes.
Stages with a real order Preview before completion Owner confirmation
See the structureMILESTONES / GATES / SECTIONS / TASKS
Structure the work can be held to.
Step through how a project is staged and how a milestone closes.
WAREHOUSE SYSTEMS UPGRADEEXAMPLE STRUCTURE
The project tracks the gate it has reachedSimplified illustration · Sample data
Stage the project, not just the task list.
Gates give a project its stages. Each has a code, a name, a position in the order, and the number of tasks sitting in it. Reorder them as the plan changes, and make one inactive when it no longer applies.
Group the work that has to land together.
Tasks reach a milestone either by explicit assignment or by their position beneath it. Sections organise the work underneath, so the structure reads Milestones, Gates, Sections, Tasks.
See what completing it will do — first.
Completing a milestone cascades Completed onto the tasks beneath it, so HelixSync previews the whole effect before anything changes. Blocked tasks are listed with the reason, and only the project owner can confirm.
STRUCTURE THAT HOLDS UP UNDER PRESSURE
Key Capabilities
What the milestone and gate model does for a project in flight.
Reorder gates as the plan changes
Plans move. Drag a gate into a new position rather than rebuilding the structure around it.
Retire a gate without deleting history
Make a gate inactive when it no longer applies. The work that passed through it keeps its record.
Milestones, Gates, Sections, Tasks
Sections organise the work beneath a milestone, so a long task list reads as structure instead of a flat backlog.
Assigned and inherited tasks both count
A task reaches a milestone either by an explicit assignment or by sitting beneath it in position. Completion accounts for both.
A preview before the cascade
Completing a milestone completes the tasks under it. HelixSync shows which tasks that will affect, which are blocked and why, and how many are already finished — before anything changes.
Only the project owner can confirm
The preview tells anyone else that they cannot complete it and why, rather than failing after the fact.
Blocked tasks name their reason
On hold, stalled, awaiting approval, a dependency not met, assigned to a different milestone, or holding a blocked subtask. The reason is on the task, not in a generic error.
A cascade is a decision, so it is shown as one.
Completing a milestone can complete a great deal of work at once. That is why it is previewed rather than performed: the tasks it would finish, the tasks it cannot touch with the reason for each, and the count already complete. The project owner confirms, or does not.
Ready to get started?
Answer five questions and we will recommend a workspace built around your initiative.