Seven project types. One data foundation.
A construction project runs to a different beat than a sprint, a public-sector programme to a different one than a series of experiments. WORKSPACE.PM models each project type in its own language - and rolls them all up into a portfolio that reports consistently.
Seven project types, each in its own language
Every card leads to its detail page - with the terminology, the project journey and the objections specific to that project type.
What all seven project types share
However different the undertakings are, the same core sits underneath. That is precisely what makes them comparable in the portfolio.
Structure from building blocks
Phases, work packages, milestones and quality gates, with features enabled per level. Recurring sections are saved as building blocks for the next undertaking.
Project structureSchedule with critical path
Whether cutover weekend, migration or handover: fixed dates anchor the plan, the critical path calculates itself, the baseline comparison evidences every delta.
Schedule & baselineRisks and decisions
Risks assessed gross and net, countermeasures on the board, decisions with status and whereabouts - the same mechanics in every project type.
Risk managementOne reporting position for every undertaking
Released status reports freeze their values and roll up through portfolio hierarchies - whether a construction site or an experiment series sits underneath.
Portfolio reportingAround this core the remaining modules engage as the project type requires: meeting series with memory, approval processes with deadlines, Kanban boards, time tracking on work packages, OKR and wiki. What gets enabled is what the project type needs - not what a form prescribes.
Which methodology suits which project type
WORKSPACE.PM does not prescribe a methodology. It models how your project type is actually run - iteratively, as a programme with guardrails, or strictly scheduled.
Run iteratively
The plan changes faster than it can be printed. Sprints and boards carry the work, quality gates secure commitment to the outside.
Project typesMatching methodsProgramme with guardrails
Binding goals and reports, but freedom in how teams work within them. Measures move visibly across boards, impact is measured.
Project typesMatching methodsScheduled and evidence-bound
Fixed phases, hard dates, evidence. The critical path leads - what stays flexible is the coordination in between.
Project typesMatching methodsFrequently asked questions about project types
What prospects ask before settling on a project type.
Nothing in the platform, quite a lot in the configuration. All project types run on the same freely definable project structure. What differs is which features are enabled per level, the saved building blocks, the report templates and the metrics. That is exactly why undertakings of different types can later be compared within the same portfolio.
Yes. Portfolio hierarchies consolidate dates, costs and status regardless of project type. A construction project, a system rollout and a sustainability programme sit side by side under the same traffic light, because released status reports freeze their values and carry the same fields.
The seven pages are entry points, not separate product variants - there is no licence per industry. The project structure is freely definable, and recurring sections are saved as your own building blocks. If your project type does not appear here, that does not mean it cannot be modelled; raise it with us during the discovery call.
Yes - and even within a single project. In the container concept each level carries its own way of working: a rollout strand runs classically with phases and fixed dates, while development underneath is organised as a board. Structure, budget and reports remain one unit.
From a PDF - award documents, a council paper, an application - the project profile is generated, and from it a container structure with milestones. Added to that are suggestions for risks including countermeasures, and recommendations on project quality. These functions work identically in every project type, and they suggest: your team reviews and accepts, nothing becomes binding automatically.
Find your project type - or build your own
Start free and structure your first undertaking in minutes. Building blocks, fixed dates and reports are there from the first minute.