| Course | BUS 352 Business Statistics |
|---|---|
| Topic | Topic 1 |
| Paper type | Descriptive statistics memo |
| Length | About 790 words, 1 pages |
| Format | Memo with APA 7 references |
| School | Grand Canyon University (GCU) |
| Program | BS in Business Management |
| Updated | September 2026 |
Free sample paper for BUS 352 Topic 1
Memorandum
To: Carla Nguyen, Store Manager, Elm Street
From: [Author Name], operations analyst
Date: [Date]
Re: What the last 30 trading days show about daily transactions
The Variables
You asked what a typical day looks like at the store. The data cover the last 30 trading days, Monday through Saturday, with the store closed Sundays. Three variables are involved, and they are summarized differently. Daily transaction count is quantitative, a number that can be averaged, so it is described with numbers: a center and a spread. Weekday and payment method are categorical, labels rather than amounts, so they are described with counts and percentages (Levine et al., 2020). All figures here are illustrative.
Checking the Data First
Before summarizing, the daily counts from the point-of-sale system were checked against the bank deposit records for the same days. They matched on 29 days. On one Wednesday the system showed a gap of about forty minutes during a network outage, when the store took card payments on a backup terminal; those transactions were added from the terminal's own report, so the count for that day is complete. No day was missing, and no count looked implausible, so all 30 days are used.
Daily Transactions Overall
Across the 30 days, the store averaged 240.7 transactions a day, with a standard deviation of 46.3. The median, the middle day when all 30 are sorted, was 225, and the middle half of days fell between 211 and 251.5, an interquartile range of 40.5. A handful of very busy days drags the mean up past the median. For describing a typical day, the median of about 225 is the better guide; the mean is still useful for planning total stock and cash handling over a month, since total transactions equal the mean times the number of days.
By Weekday
Splitting the count by weekday shows where the spread comes from.
Table 1
Daily Transactions by Weekday
| Day | Days observed | Mean | Median | Lowest | Highest |
|---|---|---|---|---|---|
| Monday | 5 | 207.8 | 200 | 197 | 229 |
| Tuesday | 5 | 211.4 | 214 | 196 | 223 |
| Wednesday | 5 | 216.4 | 225 | 203 | 226 |
| Thursday | 5 | 223.6 | 212 | 211 | 244 |
| Friday | 5 | 250.6 | 253 | 244 | 255 |
| Saturday | 5 | 334.4 | 328 | 325 | 357 |
Why Report Both Center Measures
Reporting the median and interquartile range beside the mean and standard deviation is not duplication. The mean and standard deviation use every value and are sensitive to the busiest days; the median and interquartile range describe the middle of the data and are barely affected by them. When the two centers differ, as they do here by about 16 transactions, the difference itself is information: it tells the reader that the data are not spread evenly around a single typical value. Here the reason is the Saturday cluster, which the next section shows directly.
What the Dot Plot Shows
A table of averages hides the shape of the data, so the counts were also drawn as a dot plot, one dot per day, with weekdays along the bottom (Tukey, 1977). The plot shows something the overall summary cannot: Saturdays form a separate cluster. All five Saturdays fall between 325 and 357, while no other day exceeds 255. Monday through Thursday overlap heavily, between about 196 and 244, and Friday sits a little above them, between 244 and 255. The overall standard deviation of 46 is large mainly because it mixes the Saturday cluster with the rest; within Monday to Friday, the standard deviation is about 19, and within Saturdays about 14.
How Customers Pay
Payment method was recorded for each of the 7,221 transactions.
Table 2
Transactions by Payment Method
| Payment method | Transactions | Share |
|---|---|---|
| Card | 4,622 | 64.0% |
| Mobile wallet | 1,733 | 24.0% |
| Cash | 866 | 12.0% |
| Total | 7,221 | 100% |
What the Thirty Days Show
Three things. A typical weekday brings about 210 to 250 transactions, with little difference between Monday and Thursday. Saturday is a different kind of day, about half again as busy as a typical weekday, and it behaves consistently. And about 88 percent of transactions are cashless, card or mobile wallet, with cash at 12 percent. For staffing, this suggests treating Saturday as its own schedule rather than a busier version of a weekday (Anderson et al., 2020).
What They Do Not Show
Thirty days is one short period. These figures describe what happened; they do not predict next month, which could differ because of the season, a promotion or road works. They also do not show time of day, which matters for staffing shifts within a day. If you would like a forecast or an hourly view, the same records can support both, and I can prepare them next.
It would also be worth repeating this summary each quarter, since a change in the Saturday cluster or in the cash share would be an early sign that customer habits are shifting.
References
Anderson, D. R., Sweeney, D. J., Williams, T. A., Camm, J. D., Cochran, J. J., Fry, M. J., & Ohlmann, J. W. (2020). Statistics for business and economics (14th ed.). Cengage Learning.
Levine, D. M., Szabat, K. A., & Stephan, D. F. (2020). Business statistics: A first course (8th ed.). Pearson.
Tukey, J. W. (1977). Exploratory data analysis. Addison-Wesley.
Reading the GCU BUS 352 Topic 1 instructions
BUS-352 opens with Topic 1, where students summarize business data with descriptive statistics. Many papers report a mean for everything. The assignment rewards memos that identify each variable's type before summarizing it, describe quantitative variables with both center and spread and categorical variables with counts and percentages. Students should report the median and interquartile range beside the mean and standard deviation, split the data by a relevant category, use a plot to reveal what a table hides, check the data before use and state clearly what the summary does and does not show.
How the BUS-352 Topic 1 example is put together
The finished memo is brief, prose around two exhibits, addressed to the store manager who asked the question. It begins by naming the variables and their types: daily transaction count is quantitative, weekday and main payment method are categorical, so the memo summarizes the first with numbers and the other two with counts and percentages. The count is then described overall and split by weekday, with the median and interquartile range reported beside the mean and standard deviation. A dot plot by weekday shows what the table cannot, that Saturdays sit in a separate cluster. The memo states what the thirty days show, labels all figures as illustrative, and stops short of predicting next month. Its recommendation is framed as a scheduling trial to be checked against later counts.
Reading the BUS 352 Topic 1 rubric
Faculty grading the descriptive memo reward summaries matched to variable types. Excellent memos explain why the mean sits above the median and which one better describes a typical day. Credit goes to a dot plot that exposes the Saturday cluster the overall standard deviation hides. The rubric values reporting spread within groups as well as overall. The highest level checks the data against another record before summarizing and declines to predict from thirty days. Memos that average categorical variables or report a mean alone usually lose marks with graders.
BUS 352 Topic 1 help before you submit
Errors in this topic are often plainly wrong rather than merely weak. A mean computed for payment method, or a standard deviation reported for a categorical variable coded as numbers, is marked as incorrect however tidy the table looks. Percentages that do not sum to one hundred, or that were calculated on the wrong base, cost the same way. Reporting only the overall mean hides the weekday pattern that answers the manager's question, so a correct figure ends up supporting the wrong schedule. Papers also slip from description into prediction, writing that Saturdays will need extra staff next month when thirty observed days only describe themselves. Unlabeled exhibits, charts without axis titles and a memo that never says what the manager should do lose marks that many rubrics assign to communication.
Get a BUS-352 Topic 1 example written to your instructions
Send the BUS-352 Topic 1 instructions and the rubric from your classroom, along with the data file or business scenario your section provided. We write a custom example to those criteria, with every variable classified, the right summaries computed and the description tied to the decision, back in 24 to 48 hours. The first one is free.
More BUS 352 papers and BS in Business Management samples
- BUS 352 Topic 2: Distribution Shape Analysis
- BUS 352 Topic 3: Sampling Variability Exercise
- BUS 352 Topic 4: Interval Estimate Memo
- BUS 352 Topic 5: P Value Dq Response
- BUS 352 Topic 6: Two Sample Test Report
- BUS 352 Topic 7: Simple Regression Interpretation
- BUS 352 Topic 8: Management Findings Report
- BUS 340 Topic 1: Legal Exposure Map
- BUS 332 Topic 1: Retention Economics Comparison
- BUS 317 Topic 1: Financial Statement Limits Paper
BUS 352 Topic 1 questions, answered
Why does a business memo need the variable types spelled out?
Because the type decides which summaries are legitimate, and a manager cannot check that from the numbers alone. Transaction counts can be averaged; payment methods can only be counted and compared as shares. Writing the classification down takes one sentence and prevents the most checkable error in the topic, a mean or standard deviation reported for something that was never measured on a numeric scale.
Can the memo recommend a schedule from thirty days of data?
It can recommend trying one. Thirty observed days describe those days, including any holiday, promotion or weather that shaped them, and they do not establish what future days will look like. Framing the suggestion as a trial with a count to watch keeps the memo inside what description supports, and it gives the manager a way to find out whether the pattern holds.
Should I use Excel output directly in the memo?
Use the values, not the raw output block. A manager reading the memo needs a clean table with labeled rows and sensible rounding, and a pasted summary panel full of kurtosis and standard error figures buries the few numbers that matter. Many sections want the software output attached or shown separately so the work can be checked, and the memo itself carries only what the decision uses.
Where can I find a free BUS 352 Topic 1 sample paper?
The whole memo is above: the variables, checking the data, daily transactions overall, why report both centers, by weekday, what the dot plot shows, how customers pay, what the thirty days show and what they do not. Share your store data for a free worked memo.
What does the dot plot reveal in BUS 352 Topic 1?
Saturdays form a separate cluster between 325 and 357 transactions, while no other day exceeds 255, which the overall summary hides.