MT362 Unit 7 AI Model Bias Review Example

Reviewed by Chester Goodwin, MBA Artificial Intelligence Applications for the Marketing Professional Purdue University Global Free custom sample in 24 to 48h

A churn model that never saw age still caught 61 percent of younger cancelers but only 38 percent of those 65 and over, and this MT362 Unit 7 bias review traces why. It defines the harm before measuring it, choosing detection among actual cancelers over flag rates, since older subscribers cancel less. Birth years from about 27,100 subscribers are joined back for audit only. Four stand-ins for age are tested: tenure and phone orders stay because they predict on their own merits, while paper catalog opt-in and legacy email domains go. The rerun lifts the age-band ratio from 0.62 to 0.88 at a cost of one point of overall detection. NIST Special Publication 1270, the AI Risk Management Framework, the four-fifths screen from federal hiring rules and Lambrecht and Tucker's study of ad delivery frame the work. Purdue Global MT 362 sets it in the BS in Business Administration.

CourseMT362 Artificial Intelligence Applications for the Marketing Professional
UnitUnit 7
Paper typeBias review
LengthAbout 1,160 words, 7 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramBS in Business Administration
UpdatedOctober 2026

Free sample paper for MT362 Unit 7

1

Four Stand-Ins for Age: An MT362 Unit 7 Bias Review of a Churn Model That Missed Older Cancelers

[Student Name]

Purdue University Global

MT362: Artificial Intelligence Applications for the Marketing Professional

Unit 7 Bias Review

[Instructor Name]

[Date]

The chain, model and results are composite; the frameworks, regulation and research cited are real.

What this part is doingOpening on the detection gap tells the reader the review measures missed customers, not flag counts.
2

Defining the Harm First

A bias review measures nothing until it says what unequal treatment would look like. The obvious test, comparing how often the model flags each age group, is the wrong one here. Older subscribers cancel less often than younger ones, so a model that flags them less often may simply be accurate. The harm this review cares about is different: a loyal 70-year-old subscriber who is about to leave and receives no save offer, because the model did not see the risk. The review therefore measures detection among actual cancelers, the share of subscribers who did cancel within 90 days whom the model had flagged beforehand. Schwartz et al. (2022) stress that bias must be defined in the context of a system's use, and in this context a missed canceler is the outcome the chain never intended.

Why the Audit Needs the Excluded Field

Birth year was removed from the model by design, as the Unit 4 review required. But removing it made age invisible to the model and to anyone checking the model. Fairness cannot be tested on an attribute nobody can see. The review therefore joins birth years back for audit use only, under a written restriction that keeps them out of every production system. About 27,100 subscribers, a little over a third, gave a birth year before the field was dropped in 2021, and their backtest scores form the audit sample. Because those who gave birth years may differ from those who did not, results are reported for this sample only.

Detection by Age Band

Among subscribers in the audit sample who canceled within 90 days, the model had flagged 61 percent of those under 45, 54 percent of those 45 to 64 and 38 percent of those 65 and over. The ratio between the oldest and youngest bands is 0.62.

The review borrows the four-fifths ratio as a screening threshold: a ratio below 0.8 calls for investigation. The figure comes from federal hiring rules, which use it to flag possible adverse impact in hiring (Uniform Guidelines on Employee Selection Procedures, 1978). It is employment law's rule of thumb, not a marketing rule, and the review labels it that way. At 0.62, the model fails the screen clearly.

Removing age from the model did not remove age from the model; four other fields carried it back in.

What this part is doingStating the proxy problem in one line explains why excluding a protected field is not enough.
3

Four Stand-Ins for Age

Proxies are traced one at a time, each judged on two questions: how closely does the feature track age, and does it predict cancellation for reasons other than age?

Tenure over ten years correlates with age at 0.41. It also predicts cancellation on its own merits, since long-standing subscribers have built a habit that resists small annoyances. It stays.

Email addresses at legacy internet-provider domains correlate with age at 0.37 and add almost nothing to prediction once tenure is included. They go.

Paper catalog opt-in correlates with age at 0.44, the strongest of the four, and also adds almost nothing once tenure is included. It goes.

Phone orders correlate with age at 0.33 and predict cancellation in their own right, because phone orderers are more exposed to delivery problems that the app would have flagged. They stay, with a note to retest.

Lambrecht and Tucker (2019) showed that an ad-delivery algorithm produced unequal outcomes by gender without any intent to discriminate, through the economics of the system itself, and this model's problem has the same character: no one chose to miss older cancelers.

Two Features Out, One Point Lost

The backtest was rerun without the catalog flag and the email-domain feature, with the flagging threshold reset so that the model flags the same total number of subscribers. Detection among cancelers 65 and over rose to 51 percent, while detection among those under 45 fell to 58 percent, a ratio of 0.88. The middle band moved from 54 to 55 percent. Overall detection fell from 55 to 54 percent. The fix costs one point of overall detection, which at roughly 4,200 cancellations a month means about 42 fewer subscribers flagged correctly, against a model that no longer systematically misses its oldest customers.

Fixes Considered and Rejected

Two other fixes were considered before the proxies were removed, and the review explains why each was set aside. The first was a separate flagging threshold for older subscribers, lowering the score needed to flag anyone 65 or over until detection matched. That would close the gap on paper, but it would require using birth year in production, which the Unit 4 review ruled out, and it would apply only to the third of subscribers whose birth year is known. The second was retraining the model with older cancelers weighted more heavily. That might work, but it would depend on the vendor's willingness to change its training process, and the chain cannot inspect that process directly. Removing two features the chain can see, and measuring the effect with a test it can repeat, was the fix within the chain's own control.

What the Fix Does Not Settle

The review does not claim the model is now fair in every sense. Detection still differs by seven points between the youngest and oldest bands, and the ratio of 0.88 passes a screen borrowed from another field rather than a standard written for retention marketing. Flag rates also still differ, because older subscribers cancel less, and the review accepts that difference as accurate. What the fix does settle is the specific harm the review defined: loyal older subscribers who were about to leave are now much less likely to go unnoticed.

Frameworks, With Dates

The review follows two federal frameworks, named with their dates so readers can check them: NIST Special Publication 1270, published in March 2022, on identifying and managing bias in artificial intelligence (Schwartz et al., 2022), and the AI Risk Management Framework 1.0, published in January 2023 (Tabassi, 2023). The framework's emphasis on measuring and monitoring risks over time is the reason the audit repeats.

A Test That Repeats

The review asks for the same audit each quarter and whenever the vendor retrains the model, owned by the analytics lead. A ratio below 0.8 in any audit pauses model-chosen offers until the cause is found. The age-band ratio also becomes a guardrail in the Unit 8 pilot.

Limits

The audit sample is the third of subscribers who gave a birth year before 2021, and they may not represent the rest. The correlations measure association, not cause. And the review addresses only age; other attributes, such as disability, cannot be tested with the data the chain holds.

What this part is doingNaming what the audit cannot test keeps the review honest about the limits of its evidence.
4

References

Lambrecht, A., & Tucker, C. (2019). Algorithmic bias? An empirical study of apparent gender-based discrimination in the display of STEM career ads. Management Science, 65(7), 2966-2981. https://doi.org/10.1287/mnsc.2018.3093

Schwartz, R., Vassilev, A., Greene, K., Perine, L., Burt, A., & Hall, P. (2022). Towards a standard for identifying and managing bias in artificial intelligence (NIST Special Publication 1270). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.1270

Tabassi, E. (2023). Artificial intelligence risk management framework (AI RMF 1.0) (NIST AI 100-1). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.AI.100-1

Uniform Guidelines on Employee Selection Procedures, 29 C.F.R. pt. 1607 (1978).

What the MT362 Unit 7 assignment asks for

Unit 7 asks students to review an AI model for unfair treatment of a group and to propose and test a fix. The review should define the harm in the context of the model's use before choosing a measure. Instructors expect students to explain how they can test an attribute the model excludes, and to trace proxies that may carry it back in. Each proxy should be judged on how closely it tracks the attribute and whether it predicts the outcome for other reasons. Thresholds borrowed from other fields should be labeled as borrowed. A rerun showing the effect of the fix, including its cost, is usually required, along with a plan for repeating the audit.

How this MT362 Unit 7 example is built

Opening on the harm, the sample explains why flag rates would mislead and why missed cancelers are the outcome that matters, citing Schwartz and colleagues. A method section joins birth years back under restriction. Detection by age band is reported, with the four-fifths screen labeled as employment law's figure. A highlighted line states that age returned through other fields. Four proxies are traced one at a time with their correlations, and Lambrecht and Tucker show how unequal outcomes arise without intent. The rerun results and their cost follow. Rejected fixes, what the fix does not settle, dated frameworks, a quarterly audit and limits close the review, so a reader sees both what changed and what still needs watching.

MT362 Unit 7 rubric: what earns full points

Bias reviews tend to earn marks for a clear harm definition, a sound audit method, careful proxy analysis and an honest account of the fix and its cost. Choosing a measure that matches the harm, and explaining why the obvious one would mislead, shows understanding. Rubrics reward explaining how an excluded attribute can be tested responsibly. Judging each proxy on two questions demonstrates rigor. Labeling borrowed thresholds as borrowed shows care. Reporting the cost of the fix, not only its benefit, earns credibility. A repeating audit with an owner and a trigger shows the student understands bias as ongoing. NIST's two documents carry their dates in the APA 7 list, and the borrowed hiring threshold stays clearly labeled.

MT362 Unit 7 help from the desk

A common error in bias reviews is comparing flag rates between groups without asking whether the groups differ in the outcome itself. That can make an accurate model look unfair, or hide a real harm. Another is assuming that removing a protected attribute removes the problem, when other fields can stand in for it. Some reviews drop every correlated feature, including ones that predict for legitimate reasons, and lose accuracy needlessly. Fixes are often proposed without being tested, so no one knows what they cost in accuracy. Before writing, state in one sentence who is harmed and how. Then choose the measure that would show that harm, and let that choice organize the review.

Get an MT362 Unit 7 example written to your instructions

Share the Unit 7 model or decision, the attribute it leaves out and any figures broken down by group. Include the prompt and rubric too. A first bias review, free and back in 24-48h, defines the harm before measuring it and tests each proxy on whether it earns its place. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More MT362 papers and BS in Business Administration samples

MT362 Unit 7 questions, answered

How can I test for bias if the case has no demographic data?

Say what data the audit would need and how the business could obtain it lawfully, such as a voluntary survey or an existing field held for another purpose. Some sections accept a designed audit rather than a performed one. Aggregate comparisons, such as offer rates by ZIP code against census income figures, can also serve as a first screen.

Which fairness measure should I use?

The one that matches the harm in your case. Where missing someone is the harm, compare detection among people who actually had the outcome; where exposure to an offer or a price is the issue, compare rates directly. State why you chose the measure, since graders tend to reward the reasoning over any particular formula.

Is using ZIP code in a model always biased?

Not always, but it deserves testing, because location often tracks income, race and age closely. Ask whether it predicts the outcome for a reason the business can defend, such as delivery cost, and compare results across areas with different demographics. Keeping it with a tested justification reads better than either dropping it reflexively or ignoring the question.

Where can I find a free MT362 Unit 7 sample paper?

The full MT362 Unit 7 bias review is on this page, tracing four stand-ins for age in a churn model and testing a fix.

Why does the MT362 Unit 7 sample measure detection among cancelers rather than flag rates?

Older subscribers cancel less, so flagging them less could be accurate; the harm is a loyal older customer who leaves without a save offer, which detection among cancelers measures.