Thanks for joining me today, in what we’ll call a “capstone” blog.

If you've been following our recent series on Standards C1.01 and C1.02, we've covered a lot of ground. We've discussed benchmarks, trends, comparison, triangulation, contextualization, Areas Needing Improvement (ANIs), faculty and staff sufficiency, workload, capacity, and the importance of using multiple sources of evidence to reach meaningful conclusions.

But once you've completed all that work, one important question remains: How do you present your analysis so that an ARC-PA reviewer can follow your reasoning?

That's where I'd like to bring our recent discussions together.

Your Narrative Should Show Your Reasoning

One of the most important things to remember about the 6th Edition Standards is that collecting and reporting data is not enough. Your analysis should demonstrate a clear, logical connection between the evidence you reviewed, the conclusion you reached, and any action plan you developed as a result. Think of it as “showing your work.”

A reviewer should be able to read your narrative and understand which data informed your conclusion, what patterns or concerns you identified, and why those findings led you to determine that the program was either sufficient and effective or had an Area Needing Improvement.

That doesn't mean repeating every number contained in your evaluation templates. In fact, the templates can help summarize much of that information and conserve valuable space within the narrative itself. Instead, use the narrative to explain what the data mean.

Connect the Evidence to the Conclusion

Throughout our C1.01 and C1.02 discussions, we've talked extensively about comparison, trends, triangulation, and contextualization. Those analytical tools help programs move beyond individual data points and identify the larger story.

Now your narrative needs to tell that story.

• Which findings were most significant?

• Did multiple measures point toward the same conclusion?

• Did a downward trend warrant additional investigation?

• Did qualitative feedback help explain something appearing in the quantitative data?

Your job is to connect those pieces clearly enough that someone outside your program can understand how you arrived at your conclusion.

This is particularly important because the 6th Edition Standards are less formulaic in some respects than previous versions. Programs are being asked to exercise professional judgment. That makes a clear and consistent methodology especially important.

"Sufficient" Still Requires Analysis

Here's an important point that can easily be overlooked: you need to perform a rigorous analysis even when the data look good.

If your benchmarks are being met, trends are stable, faculty and staff perceptions are positive, and the evidence supports the conclusion that the program is effective or personnel are sufficient, that's excellent.

But, though it may seem strange, you still have to analyze it. "Sufficient" is a conclusion, and your narrative should demonstrate why the evidence supports that conclusion.

The purpose isn't to search for a problem where one doesn't exist. As we've discussed before, not every below-benchmark data point represents an ANI, just as meeting every benchmark doesn't eliminate the need for thoughtful evaluation. Your goal is demonstrating that you looked carefully, considered the available evidence, and reached a conclusion that logically follows from what you found.

If the Evidence Supports an ANI

What happens when the evidence does reveal a meaningful concern? This is when the analysis needs to move from conclusion to action.

We've previously discussed the importance of distinguishing isolated findings from larger program-level concerns. Triangulation can help determine whether several related data sources are identifying the same underlying issue, while trends may reveal concerns developing over time.

Once your analysis supports the determination that an Area Needing Improvement exists, however, the work isn't finished, because now your program needs a targeted response.

Building a Self-Improvement Action Plan

A strong self-improvement action plan should answer several practical questions.

Action Plan: What will the program do to address the identified concern?

Expected Outcome: What result do you anticipate, and what will success look like?

Responsible Parties: Who is accountable for implementing the plan?

Outcomes: How and when will you measure whether the intervention worked?

Those components turn an ANI from an observation into a genuine improvement process.

This is where assessment becomes especially valuable. The goal isn't simply to identify something that isn't working, but to show that you understand the concern well enough to respond thoughtfully, measure the results, and determine whether the response produced meaningful improvement.

Then, the cycle continues. Programs should continue systematically collecting and analyzing their C1.01 and C1.02 data each year, watching for changes in trends, emerging concerns, and evidence that previous interventions are—or are not—working.

Making the Analysis Defensible

Ultimately, a defensible analysis doesn't require a perfect data set or a predetermined conclusion. Instead, it simply requires a logical process.

The evidence should lead to the analysis. The analysis should support the conclusion. And when improvement is necessary, the conclusion should lead to a measurable action plan.

If an ARC-PA reviewer can follow that reasoning from beginning to end, you've accomplished something much more valuable than simply completing another section of the Self-Study Report. You've demonstrated that your program has a systematic process for evaluating itself, identifying meaningful concerns, and acting upon what it learns.

That's the real purpose of critical analysis—and one of the most important opportunities presented by the 6th Edition Standards.

Thanks for Joining Me Again!

As programs continue working with the 6th Edition Standards, all of us will continue learning. Programs are developing new approaches, sharing experiences, and discovering what works, while the Commission continues to gain insight into how these Standards are being interpreted and applied in practice.

That's part of the process. Our understanding will continue to evolve, and I expect we'll have plenty more to discuss as new guidance, experiences, and best practices emerge.

For now, I hope our C1.01 and C1.02 series have helped make this process a little clearer and given you some practical strategies you can use within your own program.

Thanks for following along. I'll see you next time!