Concept
Tasks are vertical. Phases are horizontal.
That one shift makes Phasi different from traditional project tools: the row describes what is being delivered, and the bars describe how execution moves through it. Because planning is centralized around the product structure, the same model can then be analyzed.
Traditional planning asks: which stage is the project in?
Phasi asks: which phases pass through each task over time?
A category system for unlimited planning models.
A phase category can represent a department, a discipline, a process family, a risk domain, or a customer-specific workflow. That makes Phasi useful far beyond one fixed industry template.
Why it matters
The phase bar is the unit of planning, responsibility, and risk.
A bar is not just a colored label. It connects a task, a phase from the company palette, dates, and optionally an owner. That makes each phase interval visible, accountable, and measurable.
Market position
Phasi sits between spreadsheets, Gantt charts, and task boards.
More structured than spreadsheets
Tasks, bars, phase categories, owners, roles, and analytics are first-class product concepts.
More flexible than fixed templates
Teams can define the phase model that fits each operational domain.
More phase-aware than task boards
The timeline shows how several functions move through the same deliverable over time.
Core belief
You cannot analyze what the planning model does not represent.
If a tool only stores a task name and a status, analytics can only guess. Phasi represents the actual product/project structure through deliverables, phase bars, owners, categories, dates, and hierarchy. That makes the real state easier to understand and more useful to evaluate.