Templates & Examples / Project Templates

Work Performance Information

A structured template and methodology for translating raw project data into actionable intelligence through variance and earned value analysis.

9 min read 4 sections Resource Template Worked Example Included

In this resource

Introduction to WPI
Variance Analysis Framework
Earned Value Analysis Framework
Worked Example: Website Project

§1Introduction to WPI

Work Performance Information (WPI) is the vital middle step in project control, converting raw observations into meaningful performance metrics.

Raw Work Performance Data is processed through Variance Analysis and Earned Value Analysis to generate WPI[cite: 6, 40]. This analysed performance information acts as the primary input for project status reporting and provides the quantitative justification required for formal change requests[cite: 5, 6, 39, 40].

Contents

§2Variance Analysis Framework

The first half of the WPI framework focuses on variance tracking. It requires project managers to juxtapose baseline expectations with actual realities, demanding a thorough investigation into root causes and planned corrective measures.

Metric	Description
Schedule Variance	Compares the planned result against the actual timeline result to isolate the schedule variance[cite: 7, 8, 11, 12].
Cost Variance	Compares the planned financial outlay against actual expenditures to determine cost variance[cite: 13, 14, 15, 16].
Quality Variance	Tracks deviations in deliverable quality against established baselines, such as defect rates or testing coverage[cite: 23, 24].
Root Cause Analysis	Identifies the fundamental drivers behind schedule or cost discrepancies[cite: 9, 17].
Planned Response	Outlines the specific corrective or preventive actions scheduled to bring performance back in line with the baseline[cite: 10, 18].

Contents

§3Earned Value Analysis Framework

The second half of the WPI template utilises Earned Value Management (EVM) to forecast future performance trends mathematically. The core baseline is defined by the Budget at Completion (BAC)[cite: 25, 68].

Forecasting Method	Formula	Application
EAC with CPI	$BAC/CPI$	Used when current cost performance is expected to continue[cite: 72, 74].
EAC with CPI × SPI	$AC+(BAC-EV)/(CPI\times SPI)$	Used when both cost and schedule variances strongly influence remaining work[cite: 72, 75].
TCPI to BAC	$(BAC-EV)/(BAC-AC)$	Calculates the required efficiency rate on remaining work to hit the original budget baseline[cite: 72, 76].

Contents

§4Worked Example: Website Project

To demonstrate the WPI framework in action, consider the following analysis for "Mary's Consulting - New Company Website" for the period ending 30 September 2026[cite: 36, 38].

Overall Status: At Risk – Cost overrun forecast is currently recoverable within contingency reserves, but the sponsor must be notified[cite: 27, 69].

1. Schedule Performance

The build phase was planned to be 75% complete by 30 September, but actual progress achieved only 71% completion[cite: 42]. This yielded a Schedule Variance (SV) of -$2,307 and an SPI of 0.974[cite: 42, 70]. The root cause involved a 5-day capacity drain due to an unbudgeted CRM API workaround and underweighted complexity in directory page templates[cite: 44, 45, 46]. The planned response is to defer two templates to Phase 2 to allow the current build to catch up[cite: 48].

2. Cost Performance

Cumulative spend reached $93,500 against a planned value of $88,807, generating a Cost Variance (CV) of -$7,000 and a CPI of 0.925[cite: 53, 70]. The overrun was driven by an approved scope expansion ($3,800) paid from contingency, and the unbudgeted labour hours required for the CRM workaround ($3,200)[cite: 55, 56]. The response requires notifying the sponsor of the projected EAC and tightening the scope of remaining activities without drawing on management reserve[cite: 59, 60, 61].

3. Quality Performance

Quality metrics indicate elevated risk. While zero Sev-1 defects are open, there are four Sev-2 defects[cite: 67]. Furthermore, the defect density sits at 0.6 per template, and test coverage is at 62%, well below the planned baseline of 80% coverage and <0.5 density[cite: 67].

4. Earned Value Forecasts

With a BAC of $142,952, the selected Estimate at Completion (EAC) is $154,520, derived using the CPI-only formula[cite: 68, 72, 74]. This formula was chosen because the cost trend is the primary concern, whereas the schedule trend is deemed recoverable[cite: 74, 75]. The To-Complete Performance Index (TCPI) indicates that to achieve the original BAC, the team must operate at approximately 107% efficiency (TCPI = 1.142) on all remaining tasks[cite: 72, 76].

Contents

EVM Table Structure

The template tracks Planned Value (PV), Earned Value (EV), Actual Cost (AC), and computes indices over current, cumulative, and past periods[cite: 28, 70].

Variance Analysis Focus

Ensure both Root Cause and Planned Responses are meticulously documented for schedule and cost deviations[cite: 9, 10, 17, 18].

Strategic Justification

Always provide a clear rationale for why a specific EAC forecasting method was selected over alternatives based on project context[cite: 31, 73, 74].

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Work Performance Information (WPI) Template & Example. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Use Work Performance Information (WPI) Template & Example as a decision instrument rather than an administrative form. The subject terms—performance, work, information, example, analysis—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.

Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.

A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.

Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.

Step-by-step operating method

Name the decision. Write the decision, approval, handover or control activity the completed template must support.
Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.

Completion and governance protocol

Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.

Information type	Minimum useful content	Review test
Outcome	Observable change and intended recipient	Not merely a deliverable or activity
Measure	Definition, baseline, target, frequency and source	Two reviewers would calculate it the same way
Ownership	One accountable role plus contributors and approver	Authority matches responsibility
Uncertainty	Assumption, risk or issue with response and trigger	Status reflects current reality
Control	Version, approval, review date and change rule	Current baseline is identifiable

Common failure modes and recovery actions

1. Watch for

Filling every box even when a field is not applicable instead of recording why.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Writing vague statements without an owner, measure, date or evidence source.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Copying a previous project without revalidating assumptions and stakeholders.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Using the document as a private worksheet when it is meant to support a shared decision.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Creating an approved baseline but failing to define who maintains it and when.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

Is the purpose and intended decision clear to a reader outside the team?
Are owners, dates, measures and sources complete and internally consistent?
Which fields are assumptions and how will they be validated?
What event, threshold or review date causes this document to change?
Are mandatory requirements distinguished from recommendations and illustrative values?
Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Work Performance Information (WPI) Template & Example?