Reading ERP Analytics

Portfolio status, budget burn and logged hours across projects.

Where the numbers come from

These metrics roll up live from your projects, budgets and timesheets β€” the status mix across the portfolio, budget burn, and hours logged. Use them to spot projects trending over budget or behind schedule before they become problems.

What to look at

  • Status mix β€” how many projects sit in each status. A growing "at risk" bucket is your earliest warning.
  • Budget burn β€” spend against budget per project. A project at 80% burn and 40% complete needs a conversation this week, not next month.
  • Logged hours β€” time booked to projects in the period, which is what ultimately drives profitability.

Drilling in

Click any project in the breakdown to open it and see its tasks, budget lines and timesheets.

If burn looks wrong

Budget burn only counts approved timesheets and posted costs. Unapproved time makes a project look cheaper than it is β€” check ERP β†’ Timesheets for a backlog of pending approvals.

Tip: Read burn alongside completion, never on its own. Burn without progress is the number that actually predicts an overrun.

Was this article helpful?