How Phasi helps teams plan structured work
A project in Phasi starts with structure. Teams can organize assemblies, buildings, software modules, features, documents, assets, supplier packages, service deliverables, training programs, audit scopes or operational work packages in the task panel.
Each item can then move through reusable phases on the timeline. These phases can represent requirements, design, review, procurement, production, testing, approval, handover, support or any custom workflow step.
Because phase bars belong to real project items, completion can be calculated from the model itself. Phasi uses category grades and completed relevant phases to create a deliverable-based Percent of Completion instead of a detached manual percentage.
Core features
Project Structure
Build a clear structure of what is being planned or delivered, from assemblies and modules to documents, packages and scopes.
Phase Timeline
Plan execution with reusable timeline phases such as requirements, design, review, procurement, production, testing or approval.
Percent of Completion
Measure progress from structured project items, category grades and completed relevant phases.
Timeline Comments
Keep questions, decisions and replies attached to the exact item, phase, owner and timing.
How Phasi calculates progress
Percent of Completion in Phasi is calculated from the planning model itself: project structure, relevant phase bars, category grades and completed work. A completion value is not stored as a separate opinion; it is derived from the phases that actually exist for each item.
Teams can define category grades for the project, such as Requirements, Engineering, Procurement, Manufacturing, Testing or Approval. The grade for each category is distributed across the relevant phases in that category, then rolled up through items, parent tasks and top-level project structure.
This keeps progress configurable while making it less arbitrary than a detached manual percentage. The more accurately a team maintains the task panel and timeline, the more accurately Phasi reflects the project's current state.
The product model
- 1 Structure
Define the project structure
Create the hierarchy of work that belongs to the project: deliverables, components, modules, buildings, zones, documents, packages, assets, scopes, lessons or service items.
- 2 Phases
Configure reusable phases
Create phase categories that describe how work moves from start to completion, such as requirements, planning, design, procurement, production, review, testing, approval or handover.
- 3 Timeline
Plan the timeline
Place phase bars on the timeline for each project item so teams can see when work is planned, where phases overlap and how the sequence develops.
- 4 Progress
Track Percent of Completion
Measure progress through relevant phase completion and project-specific category grades at item, parent and project level.
Suitable for many planning vocabularies
Phasi does not require one fixed industry structure. A project item can be a machine assembly, building zone, software feature, course module, audit scope, service package, supplier order, event area or maintenance asset. The team defines the vocabulary. Phasi provides the planning model.