What Is a Running Total in a Delivery Log?

Before doing any math, ask: What are the units? A delivery log might record parcels, boxes, pallets, dollars, or deliveries. The units tell you what is being counted—and help prevent a total from being mistaken for a rate.

A running total is the amount accumulated up to a particular point in a sequence or over a stated period. In a delivery log, it can show how many parcels have arrived since the start of a shift or day. It is also called a cumulative total. A warehouse running count can help staff see progress, check a target, or compare the number of arrivals at different times.

But a running total does not, by itself, tell you how fast parcels are arriving. That is a different question, with different units. This guide explains how to read, calculate, and communicate running totals clearly.

Running total: one clean definition

Here is a delivery-log question rewritten as one clean sentence: Starting at 8:00 a.m., how many parcels have arrived by each recorded time?

The words “starting at 8:00 a.m.” and “parcels” matter. They define the beginning of the count and the quantity being counted. Without them, “the total is 125” is incomplete: 125 what, counted since when?

Suppose the log records new arrivals at several times. The running total at each time is the previous running total plus the new arrivals since the previous entry. If the day begins with zero arrivals counted, then:

\[ \textrunning total at time t = \textrunning total at the previous time + \textnew arrivals in the interval \]

For example, if 18 parcels arrive between 8:00 and 9:00, and 24 more arrive between 9:00 and 10:00, the running total is 18 at 9:00 and 42 at 10:00. The number 42 means 42 parcels accumulated since 8:00 a.m. It does not mean 42 parcels arrived during the 9:00–10:00 interval.

How to read a warehouse running count

Consider this simplified log. The counts in the “New arrivals” column refer to arrivals during the interval ending at the listed time. The day’s count begins at 8:00 a.m. with zero arrivals.

Time New arrivals during interval Cumulative parcels since 8:00 a.m. 9:00 a.m. 18 parcels 18 parcels 10:00 a.m. 24 parcels 42 parcels 11:00 a.m. 15 parcels 57 parcels 12:00 p.m. 31 parcels 88 parcels

To get the 10:00 a.m. cumulative count, add the 10:00 interval’s 24 parcels to the previous total of 18 parcels. That gives 42 parcels. At 11:00, add 15 to 42 to get 57. The total increases as arrivals are added.

In a dashboard or report, label the count so its meaning is visible: “Cumulative parcels since 8:00 a.m.” is clearer than “Total.” If the day’s first recorded count is already 12 parcels, state whether those 12 were present at the start, arrived before the first timestamp, or are carried over from an earlier shift.

Totals and rates answer different questions

This distinction is worth keeping sharp: a total is not a rate. A total answers “How many have accumulated?” A rate answers “How quickly is the amount changing over time?”

Total: 42 parcels have arrived since 8:00 a.m.
Rate: 24 parcels arrived per hour between 9:00 and 10:00 a.m.

The units show the difference. A cumulative total is measured in parcels. An average arrival rate is measured in parcels per hour, or another quantity per unit of time. Calling “42 parcels” a rate would be like calling a bank balance “dollars per day”: the units do not match.

To calculate an average rate of change over an interval, divide the change in the cumulative total by the time elapsed:

\[ \textaverage rate = \frac\textending total-\textstarting total \textending time-\textstarting time \]

From 9:00 to 10:00 a.m., the cumulative count goes from 18 to 42 parcels. The change is 24 parcels over 1 hour, so the average rate is \(24\text parcels/1\text hour=24\) parcels per hour.

Over a different interval, the answer can be different. From 10:00 to 12:00, the total grows from 42 to 88 parcels. That is 46 parcels over 2 hours, or an average of 23 parcels per hour. Notice that 88 is the cumulative total at noon; 23 parcels per hour is the average rate over the two-hour interval.

Why the interval matters

A rate calculation needs two times. Saying “the average rate was 23 parcels per hour” is not fully informative unless the interval is clear. Was that from 10:00 to noon, over the whole morning, or during the busiest hour?

For a cumulative total \(C(t)\), the average rate of change from time \(t_1\) to time \(t_2\) is:

\[ \fracC(t_2)-C(t_1)t_2-t_1 \]

The numerator is a change in parcels; the denominator is a change in time. For example, the average rate from 9:00 to noon is:

\[ \frac88\text parcels-18\text parcels 3\text hours = \frac703\text parcels per hour \approx 23.3\text parcels per hour \]

That average describes the entire three-hour interval. It does not say that exactly 23.3 parcels arrived in every hour. Actual arrivals may vary from one interval to another.

Also check the time units before dividing. If timestamps are 9:00 a.m. and 9:30 a.m., the elapsed time is 30 minutes, or 0.5 hours. If 12 parcels arrived in that interval, the average rate is 12 parcels per 0.5 hours, which equals 24 parcels per hour. Writing the interval as 30 minutes while reporting a rate per hour is fine—but make the conversion explicit.

What a graph can—and cannot—show

A graph of cumulative arrivals should have labeled axes. The horizontal axis could be Time since 8:00 a.m. (hours), and the vertical axis could be Cumulative parcels (parcels). The starting time and counting rule belong in the title or a note.

When the log records counts only at specific timestamps, avoid drawing a smooth line that implies the arrivals happened continuously or evenly between those times. In many delivery records, arrivals are events that happen in jumps. A step graph is often a better choice: the cumulative count stays at one level, then jumps when new parcels are recorded.

For instance, if 18 parcels have arrived by 9:00 and the next 24 are recorded at 10:00, a step graph can show a level of 18 until the 10:00 record, then a jump to 42. If your system records the arrivals at the instant they happen, those may be smaller, more frequent jumps. The graph should match the actual recording warehouse deliveries practice rather than suggest unobserved detail.

A straight-line connection between two hourly totals can be useful when explicitly showing an average trend, but it can also suggest that the cumulative count increased smoothly between timestamps. If the data only tells you the totals at 9:00 and 10:00, it does not tell you exactly when each parcel arrived. Label an interpolated line clearly—or use steps when the events happen in jumps.

Define what is being counted

“Arrivals since start of day” sounds straightforward, but a workplace may need to define the counting rule. Does the log count each parcel when it reaches the receiving dock, when it is scanned, or when it is checked into inventory? Those events may happen at different times.

It also helps to distinguish arrivals from the number of parcels currently on hand. A running arrival total can continue to increase even when parcels are dispatched, moved, or returned. It measures accumulated arrivals—not necessarily current inventory.

Arrivals: parcels received during the stated period.
Current inventory: parcels currently in stock or on site, based on a separate accounting rule.
Net change: additions minus removals over a period.

If the log includes corrections, returned parcels, or records entered late, decide how those affect the running total. For example, a negative adjustment might lower a corrected cumulative count. In that case, a total that decreases is not automatically wrong—but the log should explain the adjustment. A count labeled “new arrivals” may need to distinguish physical arrivals from later data corrections.

A practical checklist for reading the log

Name the quantity. Are you counting parcels, boxes, pallets, or something else?
State the start time. Is the count since the start of the day, the shift, or another checkpoint?
Check the timestamp rule. Does a row represent arrivals before that time, during the interval ending at that time, or an instantaneous scan?
Separate total from rate. Keep “parcels” distinct from “parcels per hour.”
Specify the interval for a rate. Give both the start and end times and use consistent time units.
Read the axes and labels. A chart should identify what each axis measures and its units.

This checklist also helps when comparing shifts. A count of 120 parcels after two hours and a count of 160 after four hours do not show, by themselves, which shift was faster. Calculate the average rate over the relevant intervals: 120 parcels over 2 hours is 60 parcels per hour, while 160 over 4 hours is 40 parcels per hour. Confirm that both counts start from comparable baselines before drawing a conclusion.

Using MathJax and Runestone to teach the idea

MathJax can render the formulas for cumulative totals and average rates clearly in a web page, including the units in the calculation. For a lesson, showing the subtraction and division step by step can help learners see that the rate comes from a change in the total—not from the total alone.

Runestone, an interactive publishing platform, can support short practice activities around a delivery log. Learners might calculate the next cumulative count, choose the correct units for a rate, or identify which interval a rate describes. A graphing exercise can ask them to compare a step graph with a straight-line connection and explain which one better represents recorded jump events.

Keep the workplace context intact in those activities. Ask learners to say what the count means, identify its starting point, and explain the units before they calculate. That makes the math more than a procedure: it makes the result interpretable.

The takeaway

A running total in a delivery log is an accumulated count up to a stated time. To interpret a warehouse running count correctly, name the quantity, define the start time, and understand what each timestamp represents. Cumulative parcels and arrivals since start of day are totals, not rates. To find an average rate of change, compare two totals across a clearly stated interval and report units such as parcels per hour.

When the log describes events that happen in jumps, use a graph that respects those jumps. Clear labels, time intervals, and units make the running total useful—and help everyone avoid confusing how many parcels arrived with how quickly they arrived.