Work Performance Data, Information, and Reports in Process Quality, Monitoring & Closure (PMP/PMBOK 8)
Understanding Work Performance Data, Information, and Reports
One of the most frequently tested concepts on the PMP exam is the progression of raw project measurements through three distinct stages: Work Performance Data, Work Performance Information, and Work Performance Reports. Understanding this hierarchy is essential for project managers who need to monitor and control projects effectively, and it is especially important in the context of Process Quality, Monitoring, and Closure.
Why Is This Important?
Every project generates a massive volume of raw measurements and observations. Without a structured approach to processing this data, project managers would be overwhelmed and unable to make informed decisions. The three-tier structure ensures that:
• Raw measurements are captured accurately during project execution
• Data is analyzed and contextualized so it becomes meaningful
• Stakeholders receive clear, consolidated reports that support decision-making
• Quality processes are informed by factual, analyzed information rather than guesswork
• Closure activities are supported by documented performance evidence
This framework is fundamental to the Monitor and Control process group and is a critical component of quality management, ensuring that the project delivers what was promised.
What Is Work Performance Data?
Work Performance Data represents the raw observations and measurements collected during the execution of project work. Think of it as unprocessed, unanalyzed facts.
Examples include:
• Actual start and finish dates of activities
• Number of defects identified during quality inspections
• Actual costs incurred to date
• Percentage of work physically completed
• Number of change requests received
• Resource utilization hours logged
• Test results (pass/fail counts)
Key characteristics:
- It is collected during the Direct and Manage Project Work process (or its equivalent in PMBOK 8's execution domain)
- It has no context on its own — it is simply numbers and observations
- It is the input to monitoring and controlling processes
What Is Work Performance Information?
Work Performance Information is the result of analyzing and contextualizing Work Performance Data. It is data that has been compared against the project management plan, baselines, and other benchmarks to determine its significance.
Examples include:
• Schedule Variance (SV) and Schedule Performance Index (SPI) — derived from comparing actual dates to planned dates
• Cost Variance (CV) and Cost Performance Index (CPI) — derived from comparing actual costs to planned costs
• Defect density trends showing whether quality is improving or degrading
• Status of deliverables (e.g., "Deliverable X is 3 days behind schedule")
• Risk trigger status — whether identified risk conditions have been met
• Quality control measurements compared against quality metrics and thresholds
Key characteristics:
- It is generated within monitoring and controlling processes (e.g., Control Quality, Control Schedule, Control Costs)
- It provides meaningful context — telling us whether things are on track or off track
- It is the output of monitoring and controlling processes and an input to reporting
What Are Work Performance Reports?
Work Performance Reports are compiled, formatted, and distributed documents that organize Work Performance Information into a format suitable for stakeholder communication and decision-making.
Examples include:
• Status reports
• Progress reports
• Dashboard presentations
• Earned Value Management (EVM) summary charts
• Quality audit reports
• Trend analysis documents
• Forecasting reports (Estimate at Completion, Estimate to Complete)
• Variance analysis summaries
• Closure reports and lessons learned summaries
Key characteristics:
- They are generated primarily through the Monitor and Control Project Work process
- They are designed for specific audiences and tailored to stakeholder communication needs
- They support decision-making, such as approving change requests, reallocating resources, or initiating corrective actions
- They are used as inputs to many other processes, including Perform Integrated Change Control and closure activities
How the Flow Works: The Three-Stage Progression
The progression follows a logical pipeline:
1. Execution Processes → produce Work Performance Data (raw measurements)
2. Monitoring & Controlling Processes → take Work Performance Data as input, analyze it against baselines and plans, and produce Work Performance Information (analyzed, contextualized results)
3. Monitor and Control Project Work → takes Work Performance Information from various controlling processes and compiles it into Work Performance Reports (formatted communications for stakeholders)
This can be visualized as:
Data → Information → Reports
Or in terms of transformation:
Raw → Analyzed → Communicated
Connection to Quality, Monitoring, and Closure
In the context of quality management:
• Work Performance Data includes raw quality measurements, inspection results, defect counts, and test outcomes collected during execution
• Work Performance Information is generated when the Control Quality process compares these measurements to quality metrics, tolerance thresholds, and control limits — identifying whether quality standards are being met
• Work Performance Reports communicate quality status to stakeholders, highlight quality trends, and may trigger corrective or preventive actions
In the context of closure:
• Work Performance Reports serve as critical documentation for verifying that all project deliverables meet acceptance criteria
• They support the formal acceptance process by providing evidence-based summaries of performance
• Lessons learned are often derived from the analysis chain of data → information → reports
• Final project reports consolidate all performance information into a comprehensive closure document
Common Exam Scenarios
The PMP exam frequently tests your ability to distinguish between these three levels. Here are common question patterns:
Scenario 1: A question describes someone collecting actual hours worked on tasks. This is Work Performance Data — raw, unanalyzed.
Scenario 2: A question states that the project's CPI is 0.85. This is Work Performance Information — data has been analyzed against the cost baseline.
Scenario 3: A question mentions that the project manager prepared a status report for the steering committee showing schedule and cost variances. This is a Work Performance Report.
Scenario 4: A question asks what is the output of the Direct and Manage Project Work process. The answer is Work Performance Data.
Scenario 5: A question asks what is the output of the Control Quality process. One key answer is Work Performance Information (specifically quality-related).
Exam Tips: Answering Questions on Work Performance Data, Information, and Reports
1. Remember the transformation sequence: Data → Information → Reports. If you can remember this simple chain, you can answer most questions correctly. Data is raw, Information is analyzed, Reports are formatted for communication.
2. Associate each level with its process group:
- Data = Output of Executing processes
- Information = Output of Monitoring & Controlling processes (individual control processes)
- Reports = Output of Monitor and Control Project Work (the integrative M&C process)
3. Look for keywords in the question:
- Words like "actual," "raw," "collected," "measured," or "observed" point to Data
- Words like "variance," "index," "status of deliverables," "compared to baseline," or "analyzed" point to Information
- Words like "report," "memo," "dashboard," "presentation," "distributed to stakeholders," or "communicated" point to Reports
4. Don't confuse Information with Reports: This is the most common trap. Information is the analyzed result (e.g., SV = -$10,000). A Report is the document that packages that information for stakeholder consumption. If the question focuses on the analysis result itself, it's Information. If it focuses on a document being shared, it's a Report.
5. Context matters for quality questions: If a quality inspection yields a defect count, that is Data. If that defect count is compared to an acceptable threshold and a determination is made (e.g., "defect rate exceeds tolerance"), that is Information. If a quality status report is prepared and sent to the sponsor, that is a Report.
6. Use the "so what?" test: If the item by itself doesn't tell you whether the project is healthy or not, it's Data. If it tells you something meaningful about project status, it's Information. If it's packaged for a specific audience, it's a Report.
7. For PMBOK 8 and adaptive/agile contexts: The same concepts apply even in agile environments. A burndown chart showing remaining work plotted daily contains Work Performance Information (story points remaining vs. planned). A sprint review presentation to stakeholders is a Work Performance Report. The raw count of story points completed in a sprint is Work Performance Data.
8. Watch for "input to" and "output of" questions: The exam loves to test whether you know that Work Performance Data is an input to controlling processes, and Work Performance Information is an output of those same controlling processes. Similarly, Work Performance Information is an input to Monitor and Control Project Work, and Work Performance Reports are an output of that process.
9. For closure-related questions: Remember that Work Performance Reports feed into project closure activities. Final performance reports summarize cumulative Work Performance Information and are essential for formal project acceptance and lessons learned documentation.
10. Practice with elimination: On the exam, if two answer choices seem similar, ask yourself: "Is this describing a raw number, an analyzed metric, or a formatted document?" This distinction will usually eliminate at least one or two wrong answers.
Summary Table
Work Performance Data
- Nature: Raw observations and measurements
- Source: Executing processes
- Example: 150 actual hours logged, 12 defects found
- Purpose: Serves as input for analysis
Work Performance Information
- Nature: Analyzed and contextualized data
- Source: Individual Monitoring & Controlling processes
- Example: CPI = 0.92, SPI = 1.05, defect rate above threshold
- Purpose: Determines project health and status
Work Performance Reports
- Nature: Compiled, formatted documents
- Source: Monitor and Control Project Work
- Example: Monthly status report, quality dashboard, closure report
- Purpose: Communicates status to stakeholders and supports decisions
Mastering the distinction between these three levels is one of the highest-value study investments you can make for the PMP exam. It appears directly in many questions and indirectly in questions about inputs, outputs, and the flow of information across process groups.
