DAT 565 Week 2 Reports and Descriptive Statistics Example

Reviewed by Davina Cresswell, MBA · University of Phoenix · Updated

This DAT 565 Week 2 example builds business reports from prepared data and uses descriptive statistics to show not only averages but spread, shape and outliers that averages conceal. University of Phoenix DAT 565 builds reports and descriptive statistics in Week 2, and in DAT/565 MBA students choose measures that fit each question, summarize distributions honestly and design reports that managers will actually use. The data are the prepared order records from the composite Atlanta fulfillment warehouse in Week 1, covering 2.5 million orders for 34 clients. The paper defines the measures, presents summary statistics for accuracy, on-time shipping and order profiles, shows where averages mislead, compares clients and designs a weekly report with exceptions highlighted.

CourseDAT 565 Data Analysis and Business Analytics (DAT/565)
Week2
Paper typeGraduate reporting and descriptive statistics analysis
Lengthabout 1,160 words, 4 double-spaced pages plus title page and references
FormatAPA 7 student paper
SchoolUniversity of Phoenix
ProgramMBA
UpdatedOctober 2026

Free sample paper for DAT 565 Week 2

1

Averages That Hide the Story: Building Client Performance Reports at an Atlanta Fulfillment Warehouse

[Student Name]

University of Phoenix

DAT/565: Data Analysis and Business Analytics

Week 2 Assignment

[Instructor Name]

[Date]

Peachtree Fulfillment Partners, its clients, data and figures are composites written for a model paper.

What this part is doingThe title states the paper's main lesson about averages.
2

Week 1 prepared 12 months of order data for Peachtree, the fictional Georgia warehouse that serves 34 client brands. The table holds one row per order, about 2.5 million in all, with flags for accuracy and on-time shipping and details of each order's lines, units and products. This paper builds reports and descriptive statistics on that table.

Defining the Measures

Neely et al. (1995) reviewed research on performance measurement and argued that measures should be derived from strategy, defined precisely, including formula, frequency and data source, and designed to prompt action. Peachtree's three core measures are defined accordingly. Order accuracy is the share of shipped orders with no client-reported picking or packing error within 30 days. On-time shipping is the share of orders receiving a carrier scan by the cutoff time on the day of release, excluding the carrier outage days identified in Week 1. Time to ship is the hours from release to first carrier scan.

The Overall Picture

Across all clients and months, order accuracy was 99.4 percent and on-time shipping 96.8 percent, against typical contract targets of 99.5 and 97 percent. Mean time to ship was 4.6 hours. These averages suggest a warehouse slightly below target but broadly healthy, which is how the operations team has described itself.

Looking at Distributions

Anscombe (1973) showed with four small data sets that shared nearly identical means, variances and correlations but looked completely different when graphed, arguing that analysts should examine data visually rather than rely on summary statistics alone. Tukey (1977) made the same case for exploratory data analysis, urging analysts to look at data with simple displays before fitting models or reporting summaries. Plotting Peachtree's measures shows why.

Time to ship is strongly right-skewed. The median is 3.1 hours, below the mean of 4.6, and the 95th percentile is 11.4 hours. Most orders move quickly; a tail of orders released late in the afternoon waits for the next wave, and some miss cutoff. The mean blends these groups and describes neither.

Accuracy by client is not normally distributed either. Thirty clients cluster between 99.4 and 99.9 percent; three sit between 97.6 and 98.4 percent; one is at 99.0. The company-wide average hides the three clients who drive most complaints.

What this part is doingShowing distributions before summaries follows Anscombe's lesson directly.
3

Comparing Clients

Grouping by client reveals the pattern behind accuracy. The three low-accuracy clients sell cosmetics and personal care products in many shades and sizes that look alike, and their orders average 4.8 lines against 1.9 for other clients. Their error rate per line is only modestly higher than average; their error rate per order is much higher because each order has more chances for a mistake. That distinction matters: the problem is partly order complexity, not only picker care.

On-time shipping varies more by release time than by client. Clients whose orders arrive mostly after 2 p.m. show on-time rates near 93 percent; those whose orders arrive in the morning exceed 98 percent.

The three clients with the most complaints do not have careless pickers; they have orders with five chances to go wrong instead of two.

Per-Order and Per-Line Measures

The client comparison raises a measurement question. Contracts define accuracy per order, so a client with five-line orders is judged on whether all five lines are right. Per-line accuracy, the share of lines picked and packed correctly, is a fairer measure of picker performance across clients with different order sizes. Across all clients, per-line accuracy was 99.86 percent; for the three low-accuracy clients it was 99.62 percent. Reporting both lets managers separate two questions: how well the warehouse picks, and how much risk each client's order profile creates. The client report will continue to show contract accuracy, since that is what clients pay for, but internal reports will add per-line accuracy.

What this part is doingDistinguishing per-order and per-line measures prevents an unfair comparison among clients.
4

Release Timing in Detail

Splitting orders by the hour they were released shows a sharp pattern. Orders released before noon shipped on time 99.1 percent of the time, with a median time to ship of 2.2 hours. Orders released between noon and 2 p.m. shipped on time 97.4 percent of the time. Orders released after 2 p.m., about 22 percent of volume, shipped on time only 91.8 percent of the time, with a 95th percentile time to ship of 19 hours, meaning many waited overnight. Six clients send most of their orders in a single afternoon batch from their e-commerce platforms. A conversation about release timing with those clients may improve on-time shipping more than any change inside the warehouse.

Seasonality

Monthly figures show that accuracy dipped in November and December, falling to 99.1 percent overall, when temporary associates make up about 40 percent of pickers. On-time shipping also fell in peak weeks, though less than expected given volumes more than double the normal level. These seasonal patterns mean that annual averages understate peak risk and that comparisons between months must account for staffing mix.

Variability and Outliers

Standard deviations by day show that on-time shipping is most variable on Mondays, when weekend orders pile up, and during promotions. Outlier days, more than three standard deviations below the mean on-time rate, were traced to the carrier outage, two severe storms and one system upgrade. Identifying causes keeps outliers from being either ignored or treated as normal.

The Current Report

The current weekly report is a 14-page spreadsheet listing every client's volume and measures for the week. Managers say they look only at the company totals. It shows no targets, no trends and no exceptions.

A Redesigned Report

The redesigned report has one page. A table lists each client's accuracy and on-time rate for the week and the trailing eight weeks, each compared with its contract target and colored only when below target. A second table shows the median and 95th percentile time to ship by release window. A short exceptions section lists clients below target two weeks in a row with a one-line explanation. Details move to a linked appendix.

What this part is doingA one-page report with exceptions turns statistics into prompts for action.
5

Who Receives the Report

The one-page report goes to the operations director, the three shift managers and the account management team every Monday morning. Account managers use it to prepare for client calls, so a client below target hears about the problem and the plan from Peachtree before raising it. The appendix stays available for anyone who needs to investigate a specific client or day.

What the Statistics Suggest for Week 3

The descriptive work points to questions for visualization and deeper analysis: how order complexity relates to errors across all clients, how release timing affects on-time shipping and whether staffing patterns explain Monday variability.

Conclusion

Company-wide averages made Peachtree look nearly on target. Descriptive statistics chosen for each measure's shape, medians and percentiles for time, distributions and group comparisons for accuracy, revealed that a few clients with complex orders and late releases drive most problems. A one-page report built around targets, trends and exceptions gives managers what they need each week.

6

References

Anscombe, F. J. (1973). Graphs in statistical analysis. American Statistician, 27(1), 17-21. https://doi.org/10.1080/00031305.1973.10478966

Neely, A., Gregory, M., & Platts, K. (1995). Performance measurement system design: A literature review and research agenda. International Journal of Operations & Production Management, 15(4), 80-116. https://doi.org/10.1108/01443579510083622

Tukey, J. W. (1977). Exploratory data analysis. Addison-Wesley.

What the DAT 565 Week 2 instructions ask

In Week 2 of DAT 565, graduate students produce business reports and compute descriptive statistics from prepared data. Prompts may ask students to compute measures of central tendency, such as mean, median and mode, and of variability, such as range, standard deviation and percentiles, summarize data by groups, identify outliers and present results in tables or reports suited to managers. Some versions supply a data set and ask for Excel output. Use a prepared data set tied to a business question, explain why each statistic was chosen and what it shows and cite statistics and performance measurement sources in APA. Design a report a manager would use weekly, and say which figures belong on it and which do not.

How this DAT 565 Week 2 example is built

Our sample paper defines three measures: order accuracy, on-time shipping and time from release to ship. Across all clients, accuracy averaged 99.4 percent and on-time shipping 96.8 percent, figures that look healthy. But the distribution tells a different story: three clients fall below 98.5 percent accuracy, and time to ship is strongly skewed, with a median of 3.1 hours and a 95th percentile of 11.4 hours, driven by orders released late in the day. Comparing medians and percentiles by client shows that accuracy problems cluster among clients with many lines per order and look-alike items. The paper redesigns the weekly report to show each client against its contract target, with exceptions flagged and trends over eight weeks.

DAT 565 Week 2 grading rubric: where the points go

Graduate graders reward descriptive analysis that informs decisions. Strong papers define measures precisely, choose statistics that fit each variable's distribution, summarize by meaningful groups and identify outliers and their causes. Credit goes to explaining when the mean misleads and the median or percentiles serve better, to comparing groups fairly and to report designs that highlight exceptions and trends rather than listing every number. Graders also value research on performance measurement and on looking at data before summarizing it. Graders also look for a report design a busy manager would read each week. Clear tables, accurate statistics and APA citations complete a strong paper.

DAT 565 Week 2 help: mistakes to avoid

Descriptive statistics papers often report means for everything. Skewed measures, such as time to ship, are better summarized with medians and percentiles. Check each distribution first. Another frequent gap is reporting company-wide averages that hide problems in subgroups; summarize by client, shift or product. Students also list statistics without interpretation; say what each means for the business. Some reports include so many figures that managers ignore them. Show what needs attention. Finally, connect measures to contract targets or goals so readers know whether a number is good or bad. A tutor can help you choose statistics that fit your data's shape and decide which belong in the report.

Related DAT 565 sample papers

Other DAT 565 week samples

More MBA sample papers

DAT 565 Week 2 questions, answered

What does DAT 565 Week 2 usually cover?

It usually covers building business reports and calculating descriptive statistics, such as means, medians, standard deviations and percentiles, summarized by groups.

Where can I find a free DAT 565 Week 2 sample paper?

The Week 2 paper above builds client performance reports for a fulfillment warehouse, and the complete analysis is open on this page.

When should you use the median instead of the mean?

When data are skewed or contain outliers, such as times or incomes, because the median is less affected by extreme values.

What are percentiles useful for in business reporting?

Percentiles show the spread of a measure, such as the time within which 95 percent of orders ship, which reveals service problems averages hide.

What makes a management report useful?

Measures tied to goals, comparisons with targets, trends over time and clear highlighting of exceptions that need action.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.