Project delivery
For portfolios that build as well as let. Milestones and budgets, risks and issues on a register, change control that requires approval, and lessons captured while they are still remembered.
What it does
Milestones and work packages
Delivery broken into packages with dates and owners.
Project budgets
Budget lines per package, tracked against committed and actual spend from procurement.
Risks and issues
A register with owners and status, rather than a slide that ages.
Change control
Changes are requested, costed and approved before they alter the baseline.
Decisions and lessons
Decisions recorded with who made them; lessons captured and approved for reuse.
Subcontractors
Subcontract packages tracked against the project and its budget.
How it works
The sequence an operator actually follows, not a feature list rearranged into steps.
- 1
The project is broken into work packages with budgets.
- 2
Spend flows in from procurement against those packages.
- 3
Risks and issues are registered and owned.
- 4
Changes are approved before the baseline moves; lessons are captured at close.
What the database guarantees
These hold whether or not the interface remembers to check.
- A change cannot silently alter a baseline — approval is recorded.
- Project spend is the same spend the ledger sees, not a parallel figure.
What it does not do yet
You will ask this in an evaluation, so here it is without being asked.
- No Gantt or critical-path scheduling.
- No integration with construction-specific tooling.
Works with
These share the same database, so nothing is re-keyed between them.