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.

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, reports — 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, 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.

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.