Count the work the office can act on
A dispatch board shows four visits completed. The office asks why only two reports are ready for review. Both numbers may be correct if they count different events. Relabeling completed visits as reports ready for review creates a claim the records cannot support.
This fictional exercise defines an office queue and checks every record behind it.
Start with a known workload
The reviewer prepares four visits:
| Visit | Field state | Report state | Office action |
|---|---|---|---|
| V-41 | Completed | Submitted with required information | Review report |
| V-42 | Completed | Draft only on device | Await submission |
| V-43 | Completed | Submitted, required attachment missing | Request correction |
| V-44 | Completed | Submitted with required information | Review report |
The dashboard currently counts completed visits and labels the total “Ready for office review.” That label is not supported by the records. V-42 has not supplied a report, and V-43 needs a correction before the agreed review.
The team does not change the field completion events to make the total smaller. Those events still describe what the field team recorded.
Define the queue’s eligibility
The office owner approves a rule for this particular queue: a report must be submitted and contain the required information before it is ready for review. The completed-visit total remains available under its own label.
The corrected view shows two reports ready for review, one awaiting submission and one needing correction. Each queue links to the records the viewer is authorized to open.
An administrator’s ability to see everything is not the intended acceptance role. The ordinary office reviewer must be able to inspect V-41 and V-44 and understand why the other two are elsewhere.
Move one record through the right boundary
The field colleague submits V-42’s draft. The receiving system confirms the report, and the office checks that its required information is present. V-42 now joins the review queue.
V-43 remains in the correction queue. Submitting another report should not clear its missing attachment or change all visits belonging to the same customer.
The revised totals are three ready, zero awaiting submission and one needing correction. The completed-visit count is still four.
Test an unavailable source separately
The review also simulates the report source being unavailable to the dashboard. The view shows that it cannot confirm the current queue, with the last known information identified according to the agreed design. It does not display zero as though there were no work.
That distinction lets the office decide whether to investigate the connection or use its approved fallback. A technical absence of data should not become an operational conclusion.
Record the meaning beside the measure
The handover names the source fields, eligibility rule, ordinary review role and four fixture records. It explains that report readiness is not billing readiness, customer delivery or a staff-performance score.
The result is a dashboard the office can challenge by opening its records. Operational dashboard development begins with that relationship between a count and a decision.
