If 20 Parcels Became 50 Parcels in 3 Hours, What Is the Rate?
What are the units? The quantity is measured in parcels, and the elapsed time is measured in hours. That gives us a rate in parcels per hour.
Here is the question rewritten as one clean sentence: A parcel count increased from 20 to 50 over a 3-hour interval; what was its average rate of increase?
The count went up by 30 parcels, not 50. So the average rate of increase was:
\[ \frac50\text parcels-20\text parcels3\text hours =\frac30\text parcels3\text hours =10\text parcels per hour. \]
So the answer is 10 parcels per hour. This is an average arrival rate only if the count represents parcels arriving, with no other changes—such as departures, transfers, or corrections—affecting the total. That distinction matters: the arithmetic is simple, but interpreting what the numbers represent is part of getting the answer right.
Totals and rates answer different questions
A total tells you how much is recorded at a particular time. A rate tells you how quickly a quantity changes over an interval. These are related, but they are not interchangeable.
- Total: “There are 50 parcels recorded at the end of the interval.”
- Change in total: “The recorded count increased by 30 parcels.”
- Average rate: “The recorded count increased by an average of 10 parcels per hour.”
In the example, 20 parcels is the starting count and 50 parcels is the ending count. The difference is the change in count:
\[ \Delta Q=Q_\textend-Q_\textstart=50-20=30\text parcels. \]
Then divide that change by the elapsed time:
\[ \textAverage rate of change =\frac\Delta Q\Delta t =\frac30\text parcels3\text hours =10\text parcels per hour. \]
A common mistake is to divide the ending total, 50 parcels, by 3 hours and report about 16.7 parcels per hour. That calculation answers a different question: it treats the count as though it started at zero. But the stated starting count is 20. If you want the rate at which the count increased, subtract the starting count first.
Another mistake is to give “30 parcels” as the rate. That is the change, not the rate. A rate needs a time unit as well as a quantity unit. Saying “30 parcels in 3 hours” gives the change and interval; saying “10 parcels per hour” gives the average rate.
Define what is being counted—and when counting starts
Before calculating a rate from a work dashboard, identify exactly what the displayed quantity records. Is it the number of parcels that have arrived since a shift began? The number currently in a sorting area? The number processed during a time window? Those quantities can change for different reasons, so they do not all support the same interpretation.
For example, suppose a staging-area count rises from 20 parcels to 50. If the display is an inventory snapshot, the increase of 30 means there are 30 more parcels in the area than before. It does not necessarily mean exactly 30 parcels arrived. Parcels could have arrived while others departed. In that situation, 10 parcels per hour is the average rate of net inventory increase, not necessarily the average arrival rate.
To call the result an average arrival rate, make the assumptions clear. The recorded quantity should represent cumulative arrivals over the interval, or other activity that changes the count must be ruled out or accounted for. A useful description might be: “The cumulative arrival counter increased from 20 to 50 parcels between 9:00 a.m. and noon, with no resets or corrections.” Now the calculation has a meaningful interpretation.
The start time matters for the same reason. “In 3 hours” tells us the interval length, but an operational report should usually state the endpoints too. A count recorded at 9:00 a.m. and another at noon define the interval. If the first number was recorded at 8:45 and the second at noon, the interval is 3 hours and 15 minutes—not 3 hours.
Why the interval matters for an average rate of change
An average rate is calculated over a specified interval. It summarizes the total change across that interval; it does not tell us exactly how the change happened at every moment.
For a quantity \(Q\) recorded at times \(t_1\) and \(t_2\), the average rate of change is:
\[ \fracQ(t_2)-Q(t_1)t_2-t_1. \]
Here, \(Q(t_1)=20\) parcels, \(Q(t_2)=50\) parcels, and \(t_2-t_1=3\) hours. The result is 10 parcels per hour. It is an average over the entire interval from the first reading to the second.
That average does not prove that 10 parcels arrived every hour. Perhaps 30 parcels arrived in the first hour and none arrived in the next two. Perhaps the arrivals were spread out unevenly. The two endpoint readings alone cannot tell us which pattern occurred.
This is the difference between an average rate and an instantaneous rate. An average rate uses a change across an interval. An instantaneous rate describes how fast something is changing at a particular moment, which requires more detailed data or a model. For everyday operations, a well-defined average rate is often useful—but it should not be presented as a moment-by-moment description.
Use the units to check the calculation
Units are not decoration. They tell you what the answer means and help catch errors. In this example:
- The change is measured in parcels.
- The elapsed time is measured in hours.
- Dividing parcels by hours gives parcels per hour.
\[ \frac\textparcels\texthours=\textparcels per hour. \]
If the elapsed time were given in minutes, convert it or keep the result in parcels per minute. For example, 3 hours is 180 minutes, so the same average increase can be written as:
\[ \frac30\text parcels180\text minutes =\frac16\text parcel per minute. \]
That is equivalent to 10 parcels per hour because \(10\text parcels/hour\times 60\text minutes/hour=600\) parcels per 60 hours? Let’s check the conversion carefully: \(10\) parcels per hour divided by \(60\) minutes per hour is \(1/6\) parcel per minute. Multiplying \(1/6\) parcel per minute by 60 minutes gives 10 parcels per hour. The units cancel as they should.
Be especially careful when a dashboard mixes hours and minutes. A period of 3 hours 15 minutes is 3.25 hours, not 3.15 hours. The average rate for a change of 30 parcels over 3.25 hours would be approximately \(9.23\) parcels per hour. Writing the interval clearly prevents a small-looking time-format mistake from changing the result.
When a step graph is better than a straight line
Parcels often arrive in batches. If a system records a count at specific timestamps, the count may stay the same between updates and then jump when a new batch is scanned. That pattern is naturally shown with a step graph.
Suppose the count is 20 at 9:00 a.m. and 50 at noon, but no intermediate readings are available. A graph with labeled axes could show time on the horizontal axis and parcel count on the vertical axis. It should make clear that 20 and 50 are recorded values at those times. If the count changes in jumps, a step graph can represent that kind of event without suggesting that parcels arrived smoothly between observations.
A straight line connecting the two points may be useful as a visual summary of the average change. But it can also imply that the quantity increased continuously and uniformly, which may not match the recorded events. Do not treat the line as evidence of what happened between timestamps unless the data or model supports that interpretation.
Always label both axes with units. For this example, use “Time (hours)” and “Parcel count (parcels).” An unlabeled graph can make it difficult to distinguish a total from a rate, or hours from minutes.
A practical rate calculation example
When you need to calculate an average rate from a pair of readings, use this sequence:
- Name the recorded quantity. Is it arrivals, processed parcels, or current inventory?
- Identify the start and end readings. Record the timestamps and the units for each value.
- Find the change. Subtract the starting quantity from the ending quantity.
- Find the elapsed time. Make sure both timestamps use consistent units.
- Divide change by elapsed time. State the result with units and describe what it represents.
Tools for exploring rates
For a written explanation, MathJax can render the formulas clearly in a web page or lesson. For example, the average-rate formula \(\fracQ(t_2)-Q(t_1)t_2-t_1\) makes the subtraction and division visible, while the units show what the result measures. MathJax activecalculus.org is a rendering tool, though; it does not decide whether a count represents arrivals or inventory. That interpretation still comes from the data definition.
Runestone is an interactive publishing platform that can be used to present instructional material with activities and questions. A lesson could ask learners to identify the starting value, calculate the change, select the correct time interval, and choose units for the answer. Interactive practice is most helpful when it asks not only for a number but also what that number means.
The takeaway
If a parcel count rises from 20 to 50 in 3 hours, its change is \(50-20=30\) parcels. Divide by the 3-hour interval to get an average rate of increase of 10 parcels per hour. Call it an average arrival rate only if the recorded quantity and operating conditions justify that description.
In short: totals describe how many; rates describe how quickly a quantity changes. Define what was recorded, state the start and end times, use a consistent interval, and include units. Those habits turn a quick calculation into a result people can interpret correctly.