September 7, 2026 · 6 min read
TL;DR: Reporting questions test whether you know what a report can and cannot do. In this bank, status reporting appears in 6 keyed answers and 16 distractors, and forecasting language splits 8 to 16 the same way. The trap is nearly always the same: an option that records a problem in a report while leaving the problem itself untouched.
Reporting looks like an administrative topic and gets studied as one. It is actually a judgment topic, and the judgment is about what a report is for. Across the 114 questions in this bank that involve status reports, dashboards, information radiators or forecasts, the keyed answers cluster around a small number of principles that are easy to state and easy to forget under time pressure.
A status report is not a mechanism for making a problem go away, and it is not a channel the team's own working sessions exist to feed.
The cleanest statement of this in the bank is a question asking which of four things is NOT a reason agile teams hold daily stand-ups. Three options describe real purposes: micro-committing to one another, surfacing and clearing blockers, and keeping work flowing through the team. The keyed answer, the thing a stand-up is not for, is delivering a status report to the executive team. The stand-up belongs to the team. Reporting upward is a separate activity with a separate audience.
The more subtle version involves a transport authority's real-time passenger-information project. The team raised fourteen impediments in two months, nine are still open with no recorded update, and in the last three coordination meetings nobody has raised anything even though work at the roadside cabinets is visibly stuck. One option is to add an impediments column to the weekly status report so blockers are captured in writing even when nobody raises one. It is wrong, and the reason is worth memorizing: the team has learned that raising something leads nowhere, so the reporting route is itself the impediment. A column on the status report collects the same silence in writing. The keyed answer is to work through the nine open impediments with the team, close or hand on each, and report back before asking for more.
Common trap: choosing the option that documents a problem when another option resolves it. In this bank, adding to or producing a status report is offered as a wrong answer 16 times against 6 keyed ones, and the losing version is almost always the one where the report changes but nothing else does. Ask what would be different a week later. If the answer is "the report is longer," it is a distractor.
A dashboard fits when everyone needs the same information and just needs to see it. It fails when different audiences need different information.
An environmental initiative spans engineering, environmental science and project management, and the project manager must ensure clear communication across all three. Setting up a centralized project information dashboard for real-time updates and transparency is offered, and it is wrong. So are interdisciplinary workshops and assigning a communication liaison per discipline. The keyed answer is to develop a communications management plan whose content is tailored to the specific informational needs and preferences of each discipline.
The bank's reasoning is precise about why. The difficulty is not a shortage of communication but a mismatch: engineers, environmental scientists and project staff need different information, at different depths, in different formats, and each group reads past what is pitched at another. A single dashboard serves the same view to all of them, which is the problem restated rather than solved.
| The scenario describes | Reporting answer | Why the alternative fails |
|---|---|---|
| Different audiences needing different depth | Tailored communications management plan | One dashboard serves one view to everyone |
| Blockers raised and never closed | Close the open ones, then report back | A new report column collects the same silence |
| Two delivery cadences under one governance ask | Map both to the shared end state | Forcing one format destroys real information |
| A team's own working session | Not a reporting channel | The stand-up belongs to the team |
| A sponsor asking whether it will finish on time | Rate plus remaining quantity | A board or backlog shows state, not a forecast |
Keep each half's native measure and translate both into progress against a shared end state, because the two cadences are measuring genuinely different things.
A regional ambulance service's dispatch modernization runs a phase-gated radio and network replacement alongside incrementally delivered dispatcher software, and governance now wants a single monthly status report. The phase-gated half reports percent-complete against its plan at each gate. The software half reports completed increments against a backlog. Three of the four options are lossy: report only the phase-gated percentage because it is easier to read, force the software half to switch to percent-complete, or print both native figures side by side with no attempt to relate them.
The keyed answer builds a report that keeps each half's native measure and maps both to progress against the shared end state, so governance can read one picture built from two cadences. Percent-complete against a plan is meaningful for phase-gated work with fixed scope. Completed increments against a backlog is meaningful for work still being refined. Neither number is wrong, and neither converts cleanly into the other, so the translation happens at the level of the outcome both halves already agreed to.
A forecast needs a demonstrated rate and a remaining quantity. Anything that shows only current state is the wrong tool, however informative it looks.
Midway through an agile project a sponsor is anxious the project may not finish on time. The options include looking over the board and the current work in progress, scanning the backlog for outstanding features, and running a team meeting to log everyone's status. The keyed answer is to review the team's velocity, the product burndown chart and other performance indicators. The sponsor's question is a forecast question, and answering it needs a rate and a remaining quantity. A board shows where work sits right now. A backlog shows what is left but not how fast it is being consumed.
Forecasting also drives sequencing when two objectives are in trouble at once. On a project forecasting a 15% budget overrun and a three-week delay, where the charter names cost as the binding constraint and the date as more flexible, the keyed answer is to apply cost-reduction measures first and only then work on compressing the schedule. The order is set by which objective the project was constrained on, not by preference and not by splitting the difference, because crashing a schedule buys time with money and would deepen the overrun you were supposed to be fixing.
Reporting questions reward the same habit throughout: identify the audience, identify what decision they are trying to make, and pick the artifact that answers it. Seeing that play out across a run of scenarios where every wrong answer is explained, not just marked wrong, is what makes the habit automatic.
Is a daily stand-up a status report? No, and one bank question keys exactly that point. Stand-ups exist so the team can commit to one another, surface blockers and keep work flowing. Delivering a status report to the executive team is the keyed answer to what a stand-up is not for.
Why is adding something to the status report usually a wrong answer? Because it records a problem rather than resolving it. In this bank, status reporting appears in 16 distractors against 6 keyed answers. The distractor version usually adds a column or a line item to a report while the underlying blockage stays exactly where it was.
How should I report on a hybrid project with two delivery cadences? Keep each half's native measure and map both to progress against the shared end state. The bank rejects both forcing one half to adopt the other's format and printing two unrelated figures side by side, because each destroys information the measure was carrying.
When is a dashboard the right answer? When the need is visibility of information people already agree on. A dashboard is not a fix for stakeholders who need different information at different depths, where the keyed answer is a tailored communications management plan.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong, so the difference between reporting a problem and fixing one becomes visible across a run of scenarios. Start the free 20-question sample — no card, no signup required to try it.
Is a daily stand-up a status report?
No, and one bank question keys exactly that point. Stand-ups exist so the team can commit to one another, surface blockers and keep work flowing. Delivering a status report to the executive team is the keyed answer to what a stand-up is not for.
Why is adding something to the status report usually a wrong answer?
Because it records a problem rather than resolving it. In this bank, status reporting appears in 16 distractors against 6 keyed answers. The distractor version usually adds a column or a line item to a report while the underlying blockage stays exactly where it was.
How should I report on a hybrid project with two delivery cadences?
Keep each half's native measure and map both to progress against the shared end state. The bank rejects both forcing one half to adopt the other's format and printing two unrelated figures side by side, because each destroys information the measure was carrying.
When is a dashboard the right answer?
When the need is visibility of information people already agree on. A dashboard is not a fix for stakeholders who need different information at different depths, where the keyed answer is a tailored communications management plan.