Projects & Programmes organises planned efforts into templates, paths, milestones, work and achievement records.
A project here is a carried effort with a shape: it starts from a template your operation trusts, runs paths and milestones, and makes progress visible — down to the trophies that mark the achievements. This manual covers the instance, its structure, and its visible achievement.
What you record
The project instance
| Field group | What it holds |
|---|---|
| Origin | The template it started from (and the template type) |
| Ownership | The owner (employee), the department, the manager |
| Lifecycle | Status, registered, started, completed — and the honest states: paused, abandoned, with their dates |
| Progress | The totals: paths and paths completed, milestones and milestones completed, works — committed, completed |
| Achievement | The trophies earned; the milestone and path progress breakdowns |
| Activity | The last activity time — the container knows it is alive or not |
The structure inside
Paths — the route the effort travels: the phases or tracks your template defines. Each path instance carries its own progress.
Milestones — the markers on the path: what "reached" means, when it was reached, and the bottleneck signals when it was not.
Works — the work entries the project contains: the tasks and deliverables that roll up into the milestones.
Trophies and boards — the achievement layer: trophies earned at the milestones, and the achievement boards your operation composes — where progress becomes visible and celebrated. Decide explicitly whether an activity involves competition, how participation works and who can see individual or team achievements.
The templates
New projects start from templates — your operation's proven shapes: the onboarding sequence, the quarterly programme, the development track. The template carries the paths and milestones; the instance carries the reality.
What you can do
- List, search, filter — your projects by status, owner, department, template; bulk actions
- Start from a template — the shape arrives configured; adapt from there
- Run the paths — milestones reached, works committed and completed
- Watch the progress roll up — paths, milestones, works: the totals compute from the structure
- Earn and display trophies — the achievement layer, per your operation's configuration
What it connects to
| Target | Examples |
|---|---|
| Employees & units | The owner, the department, the participants |
| Works | The work entries inside |
| Calendar events | The milestones and reviews on the timeline |
| Templates | The shape it started from |
| Trophies/boards | The achievement records |
Where it feeds
The project container is what the achievement campaigns and development programmes run on: People & Culture development programmes are project instances here, and the progress data — reached milestones, completed paths, earned trophies — is what makes development visible. The campaigns story is the buyer page; this manual is the container surface.
The pattern note: same four-part structure — record, do, connect, feed. The projects manual is where the achievement pattern shows: progress that rolls up from real work, made visible through milestones and trophies, under the participation and visibility rules chosen for the activity.
Implementers load your operation's proven shapes as templates at adoption; consultants help design the programmes whose achievement layer matches your culture — which milestones deserve trophies, what the boards celebrate.
No record is an island
Every project relates to its owner, its works, its timeline, its achievements. The container is the carried effort made visible — and the visibility is what turns effort into development.
Review the record and its context before deciding what to do next.
Processes → · Works → · All manuals → · The Projects platform page →
Check your work
Choose a template that fits the effort, confirm ownership and participants, and check how milestone completion is recorded. Open campaigns and assigned development programmes have different participation arrangements. Set recognition and board visibility deliberately; trophies record defined achievements and do not prove wider personal or cultural improvement.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.