Projects & milestones

A project in PMOlikePRO is the container for one engagement: its tasks, its people, its client, its budget and its timeline. Milestones sit on top as the delivery skeleton.

Three views on every collection

Projects, tasks, clients, contacts and team can all be viewed as:

• List — grouped sections with expandable rows, count-chip filters and per-view remembered grouping.
• Kanban — drag between status, priority, type or client lanes; derived lanes (month, budget, progress) are read-only.
• Gantt (projects) — a full project timeline with baseline vs actual bars, per-project schedule verdicts, and grouped swimlanes.

All three views share the same grouping, filtering and sorting controls, and each remembers its own preferences.

The Gantt timeline

The Gantt shows each project as two bars: the baseline (the plan at a point in time) and the actual (what really happened). Each project carries a verdict — on track, behind or ahead — computed from schedule progress against elapsed time. Milestones appear on the timeline as markers, and a 300-pixel info card on each row shows status, assignees, hours and the verdict at a glance.

Swimlane grouping matches the list’s grouping options, zoom is persisted per person, and an Active/Archived scope toggle lets you include completed engagements when you need the long view.

Milestones: gates and checkpoints

Milestones come in two flavors, and the distinction is deliberate:

• Gates — decision points. A gate is where you formally pass from one phase to the next: scope approved, design signed off, go-live authorized.
• Checkpoints — progress markers. A checkpoint tracks that work is where it should be, without implying a formal approval.

Each milestone carries a status and a date, and every surface in the app — lists, cards, calendar, Gantt, Home dashboard — renders them from the same source, so a milestone never tells two different stories on two different screens.

The lifecycle

Projects and tasks move through a lifecycle with clean terminal states: active work can be paused (with a reason — client hold, internal, other), and it ends as finished or cancelled. Terminal states follow one rule everywhere:

Keep the past, cut the future.

Finishing or cancelling a project keeps every hour that was logged and every schedule entry that already happened — history stays truthful for reporting — while planned future allocations are released so your team’s calendar reflects reality again.

Progress you can defend

Task progress and delivery progress are tracked separately from hours spent, because “we burned 80% of the hours” and “we delivered 80% of the scope” are very different statements. Project cards show delivery — tasks done and milestones passed — and the financial view shows effort and cost. You see both, and neither pretends to be the other.

Quick View

Click any project name anywhere in the app — in a widget, a list, a report row — and a detail overlay appears without leaving the page. The same works for tasks, people and clients.

Archive: done means tidy

Completed engagements move to the archive: out of the daily working set, still fully reportable. Archiving keeps the active workspace fast for the team while preserving the full record — and reports can include archived work on demand when you need the long view. You can also let the system archive finished work automatically after a quiet period.

Where to go next

Tasks & recurring work covers the working layer beneath milestones. The Gantt FAQ answers the most common question.