Work Performance Report
- Purpose and Principles
- Blank Template Structure
- Worked Example: Website Delivery Project
- Quick Reference Rules
§1 Purpose and Principles
A Work Performance Report is the formal instrument used to communicate project status to the sponsor and steering committee. It is not merely a list of tasks completed; it is a vital project control document designed to highlight schedule slips, budget variances, and emerging risks before they become unrecoverable.
By forcing the project manager to document the root causes of variances alongside a planned corrective action, the report shifts the conversation from passive data monitoring to active problem-solving.
§2 Blank Template Structure
The standard KEVOS® Work Performance Report is structured across four distinct pages, separating narrative status from strict financial analysis.
Page 1: Core Status
Features the Executive Summary, detailing the overall health indicator (Red/Amber/Green). It explicitly lists work completed, work planned but missed, and the root causes of any immediate variances.
Page 2: Schedule & Near-Term Costs
Focuses on the immediate future. It captures Impact to Upcoming Milestones resulting from any slips identified on Page 1, alongside the funds spent during the current reporting period.
Page 3: Financial Forecasting
The Earned Value Management (EVM) hub. Details the Impact to Overall Budget, remaining contingency funds, and tracks the Estimate at Completion (EAC) against the Budget at Completion (BAC).
Page 4: Risks & Issues
A distilled view of the risk register. Highlights New Risks Identified with their probability/impact scores, escalated issues requiring sponsor attention, and general PM commentary.
§3 Worked Example: Website Delivery Project
To demonstrate the template in practice, consider the following data synthesised from a real-world scenario (Mary's Consulting — New Company Website). The report is dated 30 September 2026.
The schedule on the critical path has compressed to just 2 days of slack. The cost forecast (EAC: $154,520) exceeds the approved baseline by $11,568. However, this is fully recoverable within the existing contingency reserve. Quality metrics remain strong, with zero Severity-1 defects preventing entry into User Acceptance Testing (UAT).
1. Schedule and Work Variances
While the component library and CMS configuration were completed on schedule, two critical backend deliverables (Build Page Templates and Backend APIs) suffered slips. The root cause was an unbudgeted CRM API gap discovered mid-build, consuming five days of developer effort.
| Milestone Impact | Original Target | Revised Target | Corrective Action |
|---|---|---|---|
| M06 Build Complete | Oct 9 | Oct 12 | Absorbed by test phase buffer; reduce launch scope by deferring two templates to Phase 2. |
| Consultant Bios | 60% submitted | 44% submitted | Tiered launch plan: top 50 consultants go live first, remainder batched in Phase 2. |
2. Financial Performance (Earned Value)
The financial data reveals the exact impact of the CRM rework and an approved change request (CR-007). In September, the project consumed an Actual Cost (AC) of $24,500. By calculating the Earned Value (EV) at approximately $22,001, we observe a Cost Variance (CV) of -$2,499 and a Cost Performance Index (CPI) of 0.898 for the period.
Extrapolating this cumulatively:
- Cumulative AC to date: $93,500 (approx. 65% of the baseline budget).
- Budget at Completion (BAC): $142,952.
- Estimate at Completion (EAC): Using the typical EVM formula (BAC / cumulative CPI), a cumulative CPI of ~0.925 yields an EAC of $154,520.
- Variance at Completion (VAC): An $11,568 overrun.
Because the project holds $11,200 in remaining contingency, and a $7,500 management reserve remains entirely untouched, the project manager correctly advises that no financial change request is required at this time. The trend will be presented to the steering committee, with the management reserve acting as a backstop.
3. New Risks Escalated
The report logs Risk R-16: Reduced schedule slack limits the ability to absorb further variance (Score: 12, Medium-High). The mitigation strategy is aggressive weekly monitoring of October critical-path activities. A second risk (R-17) involving a hosting vendor maintenance window conflict (Score: 15, High) has been escalated directly to the vendor's account team.
Contents§4 Quick Reference Rules
Lead with the Critical Path
Highlight tasks that directly impact the final delivery date. A schedule slip on a non-critical activity requires far less executive attention than a one-day slip on the critical path.
Quantify with Earned Value
Always provide objective cost and schedule performance indices (CPI/SPI) rather than subjective estimates of progress. "We are 80% done" is a guess; an EAC of $154,520 is a mathematical forecast.
No Problems Without Plans
Never present a variance or a high-severity issue without an accompanying corrective or preventive action plan for the sponsor to review and approve.
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 Report 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 Report Template & Example as a decision instrument rather than an administrative form. The subject terms—work, performance, report, template, example—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 Report Template & Example?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about work would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- Benefits Realization Management: A Practice Guide — Project Management Institute. Used for linking organisational strategy, deliverables, outcomes and sustained benefits. Accessed 2026-08-13.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.