Your Daily Backlog Figures Are Right. Why Is the Weekly Total Wrong?
Daily backlog is a snapshot of open work. Adding daily snapshots can count the same cases repeatedly; choose a weekly view that matches your question.

Monday ends with twenty open cases. Tuesday ends with twenty-five. By Friday, the report adds every daily balance into a weekly total and presents a much larger number.
The daily figures may all be correct. The weekly label can still be misleading. A backlog describes work open at a particular point, and the same unfinished case can appear in several daily snapshots.
Decide which weekly question you mean
In this fictional service team, the coordinator wants to know what remains at the end of Friday. The relevant view is the closing snapshot for that agreed boundary, not the sum of Monday through Friday.
Another reader may want to understand a typical daily load. An average daily snapshot could support that discussion if the dates, missing days and weighting are defined. It answers a different question from the number of distinct cases open during the week.
Name the view so the reader can recognise the question. “Friday closing backlog” explains more than a generic “weekly backlog” title.
Distinguish snapshots from movements
Incoming cases and completions describe events within a period. Daily backlog describes a state at a boundary. Treating both kinds of number identically can make a plausible-looking report tell the wrong story.
Write down what one source row represents. If the data contain one daily record per channel, record that clearly. A person should not assume each row represents one individual customer case.
Keep a small example where a case remains open across several days. It makes repeated appearances easy to explain without needing a technical discussion first.
Check the boundary and missing dates
Agree when a day closes and which dates belong in the report. A weekend, a missing export or a changed reporting time can affect comparisons. Do not quietly treat an absent snapshot as proof that no work remained.
For a weekly closing view, check that the selected final date has the intended data. For a typical-day view, state which observed days contribute. If the source cannot support the requested comparison, make that limitation visible.
Reconcile a few daily balances independently before reviewing the weekly visual. This separates a source problem from a summarisation choice.
Explain the report to the person assigning work
Ask a colleague to read the figure and describe what it means. If they think it represents unique customers when it represents daily workload snapshots, improve the label or the presentation.
The purpose is to support the next operational decision: which open work needs attention and whether capacity needs discussion. A bigger total is not automatically a fuller explanation.
When the source records describe snapshots, let the report preserve that meaning. Correct daily data cannot rescue an ambiguous weekly question.
Continue with a related question
Explore Keep Queue Reports Connected to the Work They Describe, or read Which Date Does Your Service Report Mean?.
For a written practice option, see Power BI with Matze: contents and requirements.
Review the provider’s course details. Affiliate link: Superstore may earn a commission if you buy.




Discussion 0
What did this article make you think about?