This manual is for MHA-FPX5040 Assessment 3, start to submission. The third deliverable is about proof and survival: whether the change was adopted, how you know, who audited it, and what happens on the day the project team stops attending. Your scoring guide decides whether it lands as an evaluation plan, a report to a sponsor or a presentation with speaker notes, and every version is graded on the same distinction, which is that adoption and outcome are two different measurements and only one of them moves fast enough to steer by. Below is the method our tutors use, a criterion-keyed structure, and an annotated sample excerpt. Rather have it built? A premium original sample comes back inside 24 to 48 hours, revised at no cost until the last criterion clears. Your courseroom may print this as MHA FPX 5040 Assessment 3 or MHA5040 Assessment 3; it is the same deliverable, and MHA-FPX5040 Assessment 3 is what this manual walks through.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How MHA-FPX5040 Assessment 3 is scored
The four levels apply criterion by criterion, and on an evaluation and sustainment deliverable they read like this:
| Level | What it means on an evaluation and sustainment deliverable |
|---|---|
| Distinguished | Adoption is charted over time against the prior median, the audit method and auditor are disclosed, handover is dated to a named department, and a threshold is written that triggers a second look. |
| Proficient | Measures are defined and a monitoring plan exists. Before and after figures do the work, and the ownership question is answered in general terms. |
| Basic | An outcome measure and a promise to monitor progress. No adoption data, no audit method, and sustainment described as continued leadership support. |
| Non-performance | Nothing after go-live at all. A plan that ends at launch has left the evaluation criteria empty rather than weak. |
This deliverable is where change work stops being persuasion and becomes measurement, and it is the part most likely to be thin. The evaluators know that, which is why the sustainment criterion is usually the one with the widest gap between a Proficient answer and a top-column one.
The MHA-FPX5040 Assessment 3 method, step by step
-
Separate the implementation measures from the service measures
Adoption, fidelity and reach describe whether the change happened. Length of stay, cost per case or satisfaction describe whether it helped. Keep them in separate tables with separate cadences, because collapsing them is how a rollout that never launched gets recorded as an idea that did not work.
-
Define adoption as a fraction with both parts named
Numerator, denominator, window. Eligible cases in the denominator, cases handled as designed in the numerator, and a stated period. Write the definition once, precisely, and use it everywhere, since a measure that shifts definition between sections cannot be trended.
-
Say who audits it and how
Pull from a system log where one exists, sample the chart where it does not, and put the audit in the hands of someone outside the project team. A compliance figure collected by asking people whether they complied is measuring courtesy, and an evaluator who has worked in quality will read it that way.
-
Chart weekly against the prior median
Two data points cannot separate an improvement from ordinary variation. Plot the weekly values, draw the pre-change median across them, and read a run of consecutive points on one side of it as the signal. Say how many points you will need before you act on the trend, and say it before the data arrives.
-
Write the handover as a dated transaction
The receiving department, the date, the standing report the measure joins afterwards, and the person whose name is against it. Sustainment is an ownership change, not a sentiment, and the criterion is looking for the date more than for the enthusiasm.
-
Name the erosion risk and the trigger
The step most likely to disappear first is usually the one that takes longest and helps the fewest people. Name it, set the threshold at which somebody must look again, and self-score every criterion before submitting early in the week.
A structure that maps to the criteria
Word ranges our tutors plan against for an evaluation deliverable; move them to match your own guide's weighting.
| Section | What it must do | Guide |
|---|---|---|
| What was implemented | The change in two or three sentences, the launch date, and the scope actually delivered. | ~150 words |
| Implementation measures | Adoption, fidelity and reach, each defined as a fraction with a window and a target. | ~300 words |
| Audit method | Data source, sample, frequency, auditor, and why that auditor is independent enough. | ~250 words |
| Results and interpretation | The weekly series read against the prior median, plus what the data cannot yet support. | ~300 words |
| Service outcomes | The outcome measure, its lag, its confounders, and the honest statement of attribution limits. | ~250 words |
| Sustainment and references | Owner, handover date, standing report, erosion risk, review threshold, current APA both ways. | as needed |
Annotated sample excerpt
Original model work from our team, showing what a measurement paragraph looks like when it has been written by somebody who expects to be audited.
Adoption is measured on the transfer requests rather than on the outcome: of 1,462 inbound requests during the eight week audit window, 1,043 were routed through the placement centre as designed, which is 71 percent against a pre-launch baseline median of 12 percent.1 Nine consecutive weekly points above that median is a signal rather than a good stretch, and the count is drawn from the telephony and bed management logs by a quality analyst who does not report to the project, because a team counting its own compliance will find it.2 Ownership moves from the project team to patient flow operations on 14 January, the measure joins the operations council report from that date, and any month below 60 percent triggers a formal review rather than an email.3
- 1Adoption stated as a fraction against a baseline median, so the reader can see both the level and the movement without a chart.
- 2Discloses the data source and puts the audit outside the project team, which is the credibility move the measurement criterion pays for.
- 3Handover carries a department, a date, a standing report and a numeric trigger. Sustainment written as an ownership change rather than a promise.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Outcome only. The service result tracked while adoption goes unmeasured, so a rollout nobody used is reported as a change that did not work.
- Two data points. A before figure and an after figure presented as evidence, when neither can be distinguished from normal week-to-week movement.
- Self-audited compliance. The project team counting its own adherence, which produces a number no experienced reader will accept.
- Sustainment as sentiment. Continued support and ongoing monitoring promised, with no department, no date and no report named.
- No trigger. Monitoring described without the threshold that would make somebody act, which means the monitoring will not survive the first busy quarter.
Pre-submission checklist
- Implementation and service measures reported in separate tables
- Adoption defined once as numerator, denominator and window, used consistently throughout
- Audit source, sample and auditor named, with independence explained
- Weekly points plotted against the pre-change median, with the signal rule stated in advance
- Handover carrying a receiving department, a date and a standing report
- Erosion risk and numeric review threshold written down, self-scored D, submitted early in the week
Evaluation section due and the data is thin?
Send the guide, the change you implemented and whatever counts you have. A team of eight returns a premium original sample in 24 to 48 hours with adoption defined properly, the audit method disclosed, and the handover written as a dated transaction.