Reports & Analytics

Reading and interpreting the Queue Breakdown report

Understand what each column and row means and how to spot bottlenecks.

Jul 11, 2026

What the Queue Breakdown report shows

The Queue Breakdown report is a real-time operational snapshot designed to help clinic managers monitor patient flow. It displays each clinic queue and how many patients are in each stage of the queue process.

How the report is organized

The report is laid out as a table, with one row per queue at your clinic.

  • Queue Name — the name you gave this queue when you set it up.
  • Waiting — patients in the queue but not yet in consultation.
  • In Consultation — patients currently being seen by a doctor or nurse.
  • Completed — patients who have finished their consultation and left the queue.
  • Total — sum of all three statuses for that queue.

At the bottom, you will see a Grand Total row showing the sum across all queues.

Why this matters

Use this report to:

  • Spot bottlenecks — if "In Consultation" is very high and "Waiting" is very low, doctors may be overstaffed or delays are happening downstream (e.g., in billing).
  • Manage capacity — if "Waiting" grows large relative to available staff, you may need to open additional consultation rooms or staff more doctors.
  • Track efficiency — comparing "Completed" across queues helps you see which queues are moving faster.

Reading the numbers

Each number represents a count of patients at that exact moment. Because queues change as patients are served, the numbers will update in real time (or when you refresh the report).

  • A queue with mostly "Waiting" patients may indicate patients are arriving faster than they are being served.
  • A queue with high "Completed" indicates good patient flow.
  • A queue with mostly "In Consultation" but very few "Waiting" may mean a queue is light or there is a gap in incoming patients.

Limitations

  • The report shows a snapshot, not a history — it does not tell you how long patients waited (see Patience/Wait Time reports for that).
  • The report only includes queues that existed at the time of the report generation.

Was this helpful?

More like this