Ask a programme office how a portfolio is doing and the answer usually arrives as a spreadsheet, a slide and an apology. The data exists. It is simply spread across trackers, finance reports, timesheets and inboxes, and every copy tells a slightly different story.
Most organisations do not lack project data. They lack one place where that data agrees with itself.
That sentence is the starting point for Exeo PPM, ConsultTik’s project and portfolio management solution. Before talking about software, though, it helps to be precise about where control actually slips. We group it into eight places: four that cost visibility, and four that quietly cost margin.
Four places control slips
01. Status lives in spreadsheets. Every project reports in its own file, and someone consolidates them by hand. Reporting cycles take days, and the numbers are stale before the steering meeting ends. Decisions are made on last week’s picture.
02. Capacity is a guess. Dates are committed without knowing who is available or who is already over-allocated. The plan looks feasible until the same people appear on several critical paths at once.
03. Cost and schedule sit apart. Finance tracks spend, the PMO tracks dates, and the two are reconciled by hand. A project can be on time and over budget, or on budget and quietly late, and nobody sees both at once.
04. Governance is inconsistent. Risks, changes and documents are kept somewhere different by every manager. When a change is challenged later, the decision trail has to be rebuilt from emails.
Where margin quietly leaks away
The second group is less visible, which is exactly why it matters.
05. Estimates are disconnected. The estimate that won the work lives in one file; the budget that governs delivery lives in another. Once they drift apart, nobody can say whether a project is performing against what was sold.
06. Effort goes uncaptured. Time that is never recorded never reaches cost, utilisation or billing. The project looks healthier than it is.
07. Approvals are informal. A message in a chat thread is not an approval route. Without one, changes, timesheets and spend move without a clear owner.
08. Internal work is invisible. Internal and R&D projects consume the same people as client work, but rarely appear in the same view. Capacity planning that ignores them is planning against people who are not really free.
What a single data model changes
Exeo is built on one idea: one platform, from estimation to delivered benefit. Demand, planning, resourcing, cost, governance and reporting share a single data model, so information is entered once and reflected everywhere.
In practice, that means an approved timesheet moves progress, cost and utilisation in the same pass. Hours are not re-keyed into a finance report, and utilisation is not chased at month end. Cost only moves once time is approved, so the numbers in a review are numbers someone has accepted.
The same thread runs from the first estimate. Estimates are built from role-based man-days and rate cards, with cost, price and margin calculated as you build. When an estimate is approved, it converts to the budget, so what was sold and what is governed are the same record. Risks, issues and change requests sit in registers linked to the project, with approval and audit, rather than in each manager’s personal tracker.
At portfolio level, the dashboard brings health, schedule, spend, billing and SLA consumption together, with earned value (CPI and SPI) and the ability to drill from the portfolio down to a single task.
Configured, not custom
Control does not come from imposing a new method. It comes from making the method you already use consistent. In Exeo, fields, stage gates, approval routes and reports are configuration: your methodology, not ours.
It also has to be used. A system that only the PMO opens becomes another place where data disagrees. Exeo is built for adoption, for the whole team as well as the PMO: project, non-project work and leave are captured on one timesheet grid, and resource views show utilisation by person and role, with capacity net of the working week, holidays and leave.
And it has to cover every kind of work a services organisation runs: implementation projects on fixed price or time and materials, outsourcing and staff augmentation, SLA and support contracts, and internal and R&D projects.
A practical first step
A practical way to see where your own portfolio loses control is to look at it together. Our approach has three steps:
- A requirements workshop: half a day with your PMO to map how work is estimated, approved, staffed and reported today.
- A configured demonstration: Exeo set up with a sample of your own portfolio, so the conversation is about your projects rather than a generic demo.
- An implementation plan: what to configure, what to migrate and how to bring the team with you.
Control is rarely lost in one dramatic failure. It leaks away in eight ordinary places. Closing them starts with one place where the data agrees with itself.