Start with a question and a consistent set of numbers
A summary number is useful only if it helps answer a specific question. A freelancer might ask, “What size are my invoices?” A small team might ask, “How long do our projects usually take?” Those questions call for different data. Before calculating anything, decide what each number represents and which records belong in the set.
For example, suppose six completed projects produced invoices of $100, $120, $140, $160, $180 and $500. These amounts can help describe invoice size, but they do not show profit. If the $500 project required far more work or expenses than the others, its larger invoice may not mean it was the best project. Keep the unit and time period consistent, and note any exclusions, such as cancelled work or invoices that have not yet been issued.
Use the average to describe the overall level
The arithmetic average, also called the mean, is the total divided by the number of values. The six invoices add up to $1,200. Dividing by six gives an average invoice of $200. This answers a useful question: if the total invoiced amount were distributed evenly across these projects, how much would each account for?
The average uses every value, which makes it helpful when the total matters. It can also be pulled upward or downward by an unusually large or small value. In this example, five of the six invoices are below $200. Reporting only the average could give someone the impression that a $200 invoice is more typical than it is. When a few projects differ sharply from the rest, compare the average with another measure before drawing conclusions.
Use the median to find the middle
The median is the middle value after the numbers are sorted from smallest to largest. With an even number of values, take the two middle values and find their average. For the six invoices, those values are $140 and $160, so the median is $150. Half the invoices are at or below that middle point, and half are at or above it.
Because the median depends on position rather than the size of every value, the $500 invoice does not pull it upward as strongly as it pulls the average. The median may therefore be a clearer description of a typical invoice in this set. It does not replace the average, though: the $500 still contributes substantially to the total. Looking at both figures reveals something neither says alone—the larger project raises the average well above the middle of the list.
Use the range to check how much values vary
The range shows the distance between the smallest and largest values. Here, the invoices run from $100 to $500, a spread of $400. Stating both endpoints is often clearer than giving the spread alone: “$100 to $500” immediately shows the scale of the work. A wide range is a prompt to look more closely, not proof that anything is wrong.
The range is especially useful when consistency matters. If project completion times vary widely, a team might check whether certain types of work need more preparation or clearer scopes. But the range uses only two observations. One unusually large project can make the spread look dramatic even if most projects are similar. If you have enough records, review the individual values or group similar projects before treating the endpoints as representative.
Put the three measures to work together
A compact summary of the invoice example might read: “Six completed projects; average invoice $200; median invoice $150; invoices ranged from $100 to $500.” That description gives a reader the overall level, the middle and the spread. It also makes the difference between the average and median visible, inviting a closer look at the $500 invoice rather than hiding it inside one figure.
The same approach can help with project hours, customer order sizes or time between an inquiry and a reply. First check that the records are comparable and that missing values have not been treated as zero by mistake. Then calculate the three measures and ask what practical follow-up they suggest. A high average alongside a lower median might call for examining a few large cases; a broad range might suggest separating routine work from complex work. These summaries are starting points for better questions, not forecasts or guarantees.
