Quick Answer:
Primavera P6 is built to calculate core earned value metrics like PV, EV, AC, CPI, and SPI. When the schedule is properly cost- or resource-loaded, running P6 is sufficient. However, having a separate Earned Value Management (EVM) software becomes useful when actual costs, commitments, burdened rates, forecasts, and portfolio reporting are managed outside P6. Best practices suggest running P6 as the scheduling source while the EVM software handles the broader cost and performance picture.
If you already use Primavera P6, you may not need another tool just to calculate earned value. Many organizations are already getting real value from the earned value fields in P6. The question is whether P6 gives you the full picture you need to manage project performance, or whether you need another software for EVM.
Earned value brings together three numbers: planned value from the baseline, earned value from measured progress, and actual cost from wherever project spending is recorded, often the ERP. When those numbers are spread across different systems, P6’s calculations are only as reliable as the information fed into it.
This article takes a closer look at what P6 handles well, where the EVM process can start to break down, and what dedicated EVM software adds.
What Primavera P6 Already Does for Earned Value
Primavera P6 handles a meaningful part of the EVM process. With a sound WBS, a resource-loaded schedule, an approved baseline, and actual costs applied to assignments, it calculates planned value, earned value, actual cost, cost and schedule variances, CPI, and SPI.
With P6, controls teams can choose an earned value technique at the WBS level. They can choose from activity percent complete, 0/100, 50/50, weighted WBS milestones, custom percent complete, or activity steps. Progress itself can be recorded as duration, units, or physical percent complete, depending on how the work is tracked. P6 can also calculate an Estimate to Complete from the budgeted work still to be earned (BAC minus EV), using a performance factor such as 1, 1/CPI, or 1/(CPI × SPI), with results rolling up through the WBS and the EPS.
All of this sits on top of what P6 is best known for: schedule logic, critical path analysis, resource leveling, and schedule baselines.
Ten Six Consulting, a firm that specializes in P6 and earned value, says P6 Professional and EPPM have “basic Earned Value capabilities.” It calls them a good starting point for companies moving toward more advanced project management. The same firm is clear about the ceiling: a certified government EVMS built on P6 alone is unlikely without considerable customization.
Oracle’s own approach points the same way. The Earned Value Manager module in Primavera Unifier imports activities and rates from P6, then runs the earned value analysis in Unifier against the WBS or a cost breakdown structure. . Even within Oracle’s product family, the answer for cost-side EVM is a separate product.
What Information is Beyond the P6 Schedule
In reality, P6 can provide a strong view of the schedule. The issues start to appear when project decisions and financial factors sit outside it.
1. Variance gets explained instead of anticipated
If you need to get costs into P6, they typically have to be imported and mapped to the appropriate activities, often as part of a month-end process. That can already create a lag between when costs are recorded and when they appear in the schedule.
2. Budgets only partly loaded into the schedule
Engineering and EPC firms often resource-load labor hours but leave subcontracts, materials, and expenses out. Earned value then describes a slice of the project rather than the whole thing.
3. Commitments that never reach the schedule
A $350,000 subcontract signed last week is already a financial commitment, even if the project has not yet been invoiced. If that commitment is tracked in the ERP or procurement system rather than P6, the schedule may still show no actual cost against it. By the time the invoice posts and the cost is imported into P6, the project team may already have been managing against a number that didn’t include the full commitment.
4. Forecasts, changes, and risk drifting apart
P6’s ETC is calculated from a performance factor. The forecast a project manager uses for leadership reporting may be built separately, often in a spreadsheet, with pending changes and risks factored in along the way. That can leave the team comparing two different views of the project’s expected final cost.
5. Formal reporting that needs more than the fields
Contracts that require a formal EVMS expect standard performance reports, documented variance analysis, and a controlled baseline history. Producing those from schedule data alone can require significant configuration or manual work.
This is why many organizations still have the familiar routine of exporting from P6, pulling actual data from ERP, and reconciling in a workbook. After they build the report, the CPI that reaches leadership already comes from that workbook rather than P6.
At that point, the workbook has effectively become the real EVM system, with no clear audit trail and often one person who knows how it works. It’s the same pattern we described in 7 Signs Your Project Management Software Isn’t Built for Complex Projects.
So, Is P6 Alone Enough?
Schedule-led teams with simple cost structures can safely rely on P6 alone. Think of a contractor with fully cost-loaded schedules, timely actuals, and a need for project-level CPI and SPI. If there’s no formal EVMS requirement, improving how P6 is configured and maintained may be the better first step.
Dedicated earned value management software makes more sense when the project’s cost side is more complex. Here’s a table to help you visualize the difference:
Need | Primavera P6 Alone | P6 + EVM Platform |
Schedule logic, critical path, baselines | Core strength | P6 stays the schedule source |
PV, EV, AC, CPI, SPI | Available when the schedule is cost- or resource-loaded | Calculated across the full budget, not only loaded resources |
Actual costs from the ERP | Import and mapping, often monthly | Integrated and mapped to control accounts |
Commitments and purchase orders | Not held | Tracked against budget |
Forecasting | Formula-based ETC | Bottom-up and index-based forecasts, with approvals |
Change and risk | Separate logs | Pending changes and quantified risk feed the forecast |
Portfolio reporting | Depends on configuration and reporting tools | Recalculated across programs and portfolios |
Formal EVMS reporting | Heavy configuration or manual work | Depends on the platform; confirm before you buy |
In the connected setup, dates and progress come from P6 while the actuals and commitments come from the ERP. The platform puts them side by side and shows where they disagree. Every number should trace back to its source record, and every baseline and forecast change should be kept, so a controls lead can defend a CPI without rebuilding it.
Questions to Ask Before You Decide
Some organizations genuinely don’t need more than P6. These questions should give you a good sense of which side you’re on.
1. What share of the total budget is actually loaded into the schedule?
If it’s mostly labor, P6’s earned value only covers part of the project.
2. Where does the CPI in leadership reports come from?
If the answer is a spreadsheet, that spreadsheet is effectively your EVM system.
3. How many days pass between a cost posting in the ERP and that cost appearing in earned value?
4. Does the ETC your project managers report match what P6 calculates?
5. When a change order is approved, how many systems does someone have to update by hand?
6. Can you roll earned value up to a program or portfolio without a separate consolidation exercise?
If your answers are “nearly all of it, straight from P6, a day or two, yes, one, and yes,” you may be well served already. If they look more like the workbook routine above, the gap is on the cost side, and that’s where EVM software can earn its place. For the wider evaluation, our guide to choosing project controls software covers the capabilities worth testing.
What to Look for in an Earned Value Management Software
After answering the questions above, you also need to know what to test with vendors. Most earned value management software can produce a CPI, but their differences are much more obvious in everything around it.
Always take note of the following:
- P6 Integration – Activities, progress, and baselines should come in from P6 on a regular cycle, not through a manual export. Each piece of data should have one clear owning system, or someone ends up correcting dates in two places.
- ERP actuals and commitments – Actual costs should land against control accounts, with the cost-code mapping kept in the platform rather than rebuilt in a workbook each month. Purchase orders and subcontracts need the same treatment, because a signed commitment is exposure from the day it’s signed.
- Forecasting – Test out this ability by asking the vendor the following:
Can project managers build a bottom-up EAC alongside the index-based one?
Do pending changes and quantified risk feed the forecast?
Is every forecast revision kept, with who approved it and when?
- Roll-up and reporting – Earned value should consolidate to programs and portfolios without a separate consolidation step. If any of your contracts carry EVMS clauses, ask to see the reports those contracts require.
How PACE Works With Primavera P6
PACE is a project delivery execution platform designed to work alongside P6 by adding the cost and performance data needed to build a more complete EVM picture. P6 or Microsoft Project can remain the scheduling system, while the ERP remains the financial system of record. PACE connects them with progress, commitments, forecasts, risk, and change, so controls teams can see how those pieces come together across the project.
PACE was built by people with long careers in enterprise project delivery and the software behind it. They saw firsthand where fragmented systems and spreadsheet reconciliation were failing project teams. The platform was designed to address that and not just add another reporting layer on top of it.
Through that, teams can track progress at the activity level, including through Microsoft Teams, and use that information to calculate earned value at the task, WBS, and project levels. The results can then roll up to programs and portfolios, as covered in how PACE measures progress with earned value.
PACE AI can flag deteriorating trends and help explain what’s driving a variance, while the project team remains in control of the decision. The team behind PACE has built and deployed project environments at AECOM supporting more than 25,000 users and 50,000 active projects. PACE itself is used in 70+ countries today, with 26,000+ active users and 98% user satisfaction.
Wondering whether P6 alone gives your team the EVM visibility it needs? Bring one of your own P6 schedules to a PACE demo. We’ll show you what changes when the cost side is connected.
Frequently Asked Questions (FAQs)
1. Is P6 enough for earned value management?
For schedule-driven EVM on cost-loaded projects, P6 is often enough. However, it gets complicated when you need ERP actuals, commitments, burdened rates, portfolio reporting, or formal EVMS reports.
2. What’s the difference between P6 and earned value management software?
P6 is a scheduling platform with built-in earned value features. EVM software focuses more on the cost side: actuals, commitments, rates, forecasts, governance, and reporting across projects. In many setups, the two work together, with P6 providing the schedule.
3. How does earned value management software get actual costs from the ERP?
EVM software gets costs from ERP through integrations that map ERP cost codes to control accounts or WBS elements. Stronger setups keep that mapping inside the platform, bring actuals in more often than month-end, and track commitments alongside invoiced costs. In this way, forecast reflects both what has been signed and what has been paid.
