Work Performance Data vs Information vs Reports: What’s the Difference?
The three terms look like jargon for the same thing and they describe three stages of a chain that runs from what happened on site to what somebody decides about it. Projects that report badly are almost always missing one of the stages, and the missing stage is usually the middle one, which is the only one that requires thought.
Section 4 of the PMBOK® Guide Eighth Edition deals with what projects produce and consume, and this chain is one of its more practically useful distinctions, because each stage has a different owner and a different failure.
Three stages, one chain
Data is what was observed. Hours booked, units installed, the date an activity actually started, costs incurred, defects raised, tickets closed. It carries no judgement and it is produced continuously by the people doing the work. Data is either accurate or it is not, and its quality problems are practical ones: timesheets filled in on Friday from memory, a start date recorded when somebody remembered to update the tool.
Information is data compared with an expectation. The activity took nine days against a planned five. Spend is at forty-one per cent with the work at thirty per cent. Defect arrivals have risen for three cycles running. This is where analysis happens, and it is the stage that requires somebody to think: a variance is only meaningful against a baseline, and a trend only exists across time. Nothing can be decided from data alone, because a number without a comparison has no direction.
A report is information arranged for a particular audience and decision, at their cadence. The board needs a different package from the team, and both are built from one set of information, drawn from one extract of the data. The value added at this stage is selection and clarity, and a good report is characterised by how much has been left out.
Where projects skip a stage
Data presented as though it were a report. The schedule is exported, the cost ledger is attached, and forty pages go to a governance group who are then expected to perform the analysis themselves during the meeting. This is not reporting; it is forwarding, and it transfers the hardest part of the work to the people with the least time and the least context.
Information presented without the decision. The analysis has been done properly and the package arrives with no statement of what it means or what is being asked. The group discusses whatever catches their eye, which is usually the item with the brightest colour on it, and the thing that genuinely needed a decision goes unaddressed because nobody said so.
Forty pages and one unanswered question
A university was building a new research facility, a three-year programme with a capital budget in the tens of millions. The monthly report to the project board ran to about forty pages: a full milestone listing, the cost ledger by code, a risk register extract, a contractor's programme in landscape, and a two-page narrative at the front.
Everything in it was accurate. Compiling it took the project office about four days a month. At one board meeting, a member asked a simple question, which was whether the laboratory fit-out was still going to complete before the first researchers arrived in September. Nobody could answer from the report. The information needed was present across three of the sections and had never been brought together, because no page in the pack had been built around that question.
The redesign started from the decisions the board actually took. There were four: release the next tranche of funding, approve or decline changes above a threshold, decide whether to hold the September occupation date, and escalate anything requiring the university executive. The new report ran to five pages. A forecast against the occupation date with the three things that could still move it. Spend against forecast with a variance explanation for anything beyond a stated percentage. The four changes awaiting decision. Two escalations. The forty pages still existed and became an appendix that nobody opened, which was the honest position it had always occupied.
Preparation time went from four days to about a day and a half, and most of that day and a half was analysis, which is where the effort belongs. The September question was answered at every meeting thereafter, because there was a page whose whole job was to answer it.
Designing a report backwards
Start from the decision. What does this audience decide, and when? A report to a group that decides nothing is a status update and can be shorter than anybody thinks. A report to a group that releases funding needs whatever supports that release, and very little else.
Fix the audience and the cadence together. Weekly for the team, monthly for the board, immediately for anything that crosses a threshold. The exception matters: a report that only arrives on the calendar cycle will always deliver bad news later than it could.
Keep the chain traceable. Every figure in a report should be traceable back through the information to the data it came from, and that chain should survive somebody asking. Where two reports disagree, the cause is nearly always two different extracts of the underlying data taken at different times, and the fix is one source rather than better proofreading.
For a PMP® candidate, what helps is seeing that each stage adds something specific, so a scenario about a governance group that cannot act on what it receives is describing a missing stage rather than a communication problem. A response that circulates more detail has moved further from the decision. A structured PMP exam preparation course treats situations where the data is accurate and nobody can make a decision from it as worth a long look.
One test is enough here. Take your last report to a governance group and write down the decisions they took at that meeting. Then check how many pages contributed to those decisions. The ratio is usually startling, and correcting it gives you back the preparation time to spend on the analysis nobody is currently doing.
Interested in going further?
Reporting consumes more project management time than almost anything else and is rarely designed around what the reader has to decide. Omega's PMP® Exam Preparation works through performance information as the basis for decisions rather than as a monthly obligation.
The chain from project data through to reporting is described in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A167: Project Charter Explained: Purpose, Content and Common Misunderstandings
A168: Business Case vs Project Charter: What’s the Difference?
A169: Assumption Log vs Risk Register
A170: Decision Log: The Forgotten Project Control
A171: Change Log vs Issue Log
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
