Reporting and history

A case’s current status is only a starting point for an explanation. The submission and completion dates show the case’s timeline. The service definition, organization and assignee identify its scope. Requirement outcomes, verified documents and decision revisions explain why the work advanced, returned or stopped. Case state history retains transitions with an actor, time, source revision and reason.

The Reports screen supports the team in reviewing authorized results. Cases and Details is useful when a total needs an explanation: select the case, inspect its state history and read the related decision and operation trace. The analyst can study trends without changing operational records. Operators and reviewers can go back from an exception to the particular case they need to address.

• Case population. Group results by service and current status, then keep the underlying cases available for review.
• Decision trail. Read a decision with its reviewer, date, reason and source revision.
• Execution exceptions. Trace a failed run through its steps and attempts before counting delivery as complete.

Agree which organizations and public services belong in each operating review. Decide whether a report uses the submission date, completion date or both, and be explicit about cases still open at the review cutoff. A delivered status and a delivery reference answer different questions; the team should check both when reviewing completion. Decide who can see case-level evidence and who receives only authorized aggregates.

For a weekly review, group cases by service and status. Look at submitted cases that have stayed open, then check their pending requirements or reviewer decisions. Compare delivered cases’ submission and completion dates, and inspect a delayed example. An open follow-up with a due date should be discussed as unresolved work, even if a related case once reached a later status.

Take a case shown in a service summary and locate its number in Case Status Board. Open Case State History to read when it moved from Submitted to Verified and from Verified to Decided. Compare the decision’s source revision with the case revision. Check its requirement outcomes and supporting document verification. If the case was delivered, compare its completion date and delivery reference with its operation result.

For an exception, open Failed Runs and Execution Exceptions. The operation key and step trace help the team distinguish repeated attempts from separate work. A report should lead the operator to an assigned next action and give the reviewer enough context to decide a new revision when one is required. Keep earlier decisions available in the case history after a correction.

• Case State History — Each recorded transition with actor and revision.
• Case Status Board — A status summary that leads to the selected case’s history and detail.
• Delivered Cases — Completed cases with delivery references for follow-up review.

Review delivery and follow-up and the reports reference.