A capital-improvement tracking system should track the approved mandate, current phase, scope, funding source, baseline cost and schedule, commitments, actual costs, forecast at completion, milestones, changes, risks, decisions, owners and expected operational benefit.

Project teams need delivery detail. Portfolio leaders need consistent definitions that allow projects to be compared without manually rebuilt monthly presentations.

The core requirement is traceability. A red portfolio indicator should lead to the relevant project, control account, change, decision or dependency.

Many organisations already have a project list and dashboard. The weakness appears underneath: dates are copied from schedules, costs arrive from finance on a different cycle, risks sit in separate registers and narrative status is rewritten for each governance meeting.

This process is expensive but late. Project managers reconcile slides instead of resolving the underlying constraint. Portfolio leaders receive a clean summary with little evidence about what changed or who owns the next action.

Tracking software should reduce that translation work, highlight exceptions and carry decision history between reviews.

1. Portfolio, programme, project and control-account hierarchy with stable identifiers.
2. Stage gates with entry criteria, evidence, decisions and approvers.
3. Budget, commitments, actuals, changes, estimate to complete and forecast at completion.
4. Baseline and current milestones, dependencies and forecast dates.
5. Proposed, approved and rejected changes with quantified effects.
6. Risks and issues linked to affected work, responses, dates and owners.
7. Decision questions, options, evidence, owners and downstream impact.
8. Expected benefits and accountable owners after handover.
9. Exception-led reporting with access to underlying evidence.
10. Version history, permissions, source identifiers and approved status.

A portfolio tracker should not become the unofficial owner of every source record. The ERP should remain authoritative for actual costs, procurement systems for commitments and specialist scheduling tools for approved logic.

The tracking layer needs a governed mapping between those systems and the portfolio structure. It should retain source identifiers, update timestamps and reconciliation exceptions. Manual overrides should be visible, attributed and time-bound.

The US GAO cost and schedule guides emphasize a common work breakdown structure because it connects scope, schedule, cost, responsibility and performance.

Build a test pack from three real projects: one healthy, one changing rapidly and one with incomplete data. Ask each vendor to reproduce the current portfolio view from the same evidence.

Then introduce a controlled change. Move a milestone, add a pending contract variation or alter a funding constraint. The product should show which records, forecasts, decisions and reports are affected while preserving the prior approved state.

Score configuration effort, data lineage, exception handling, role-based contribution, auditability and the time required to answer a governance question.

Some organisations need a portfolio-management suite. Others already have adequate finance, scheduling and reporting tools but lack a shared operational layer between them.

Optimality is designed for that coordination gap. It connects work, decisions, deliverables, commitments, dependencies and governed changes without claiming to replace the ERP or specialist schedule.

Start with one portfolio review cycle. Identify every number and narrative copied manually, map each to its authoritative source and select the exceptions consuming the most management time.

Sources: US GAO Schedule Assessment Guide; US GAO Cost Estimating and Assessment Guide; US DOE Project Management Lexicon; DOE Order 413.3C.

What is capital-improvement project tracking software?
It monitors scope, funding, cost, schedule, changes, risks, decisions and expected outcomes across a capital portfolio.

What is the difference between project tracking and portfolio reporting?
Tracking maintains the underlying owned records and changes. Reporting summarizes them for governance.

Should project tracking software replace an ERP?
No. The ERP should remain authoritative for accounting transactions while tracking software connects them with forecasts, milestones and delivery context.

What is the most important evaluation requirement?
Traceability. Every portfolio indicator should lead to its source, owner, approved baseline and relevant change or decision.