Skip to main content
In HERMES, milestones mark the decision points of a project. Each milestone is an outcome of a decision task, and each works as a quality gate: before it is reached, the responsible role decides on the outcomes and on how to proceed, and checks the project against the strategic goals of the core organization.

Milestones that structure the phases

Further milestones

Depending on the modules in the project, further decisions and milestones apply, for example:

Steering and management decisions

HERMES separates decisions by hierarchy level. The steering level, led by the project sponsor, takes the project initiation release, execution release, phase release, closure phase release and release decisions, as well as tender, contract award, launch of operation, project closure and project discontinuation. The management level, led by the project manager, takes decisions such as next steps, solution architecture, product concept, ISDP concept, preliminary acceptance, acceptance and migration acceptance. Each level keeps its own list of project decisions.

In Collabase

Model the steering decisions that release a phase as gates at the end of each phase, and the other milestones as work items of a Milestone work item type with a governed workflow.
1

Create a milestone workflow

In Admin → Workflows, create statuses such as Open, Submitted for decision, Released and Rejected. Under Settings → Transitions, allow only the paths you want, so a milestone cannot jump to Released. See Workflows.
2

Create the Milestone task type

In System Settings → Content & Organization → Work Item Types, create Milestone and make the fields for the decision required, for example the decision rationale. See Work item types.
3

Let the sponsor decide phase releases at the gate

Switch on Phases and gates in the project, add a gate to each phase and give the project sponsor a space role whose Permission Scheme grants Decide phase gate. The phase closes only with the gate decision, which is kept with its rationale. See Phases and gate approvals.
4

Record the decision

Add every decision to the Decision object type in Registry, with context, rationale, decided by and date. This is your list of project decisions.
A gate is decided by one person. If a committee decides, let the person who records the committee’s decision take the gate decision, and store the minutes with the decision.
Last modified on October 13, 2026