WGU D172: Assessing Student Learning

What D172 Really Is (and Why It Trips People Up)

WGU D172, Assessing Student Learning, sits in the School of Education and asks a deceptively big question: once you have taught something, how do you actually know whether your students learned it? The course pushes you past the idea that assessment means "the test at the end of the unit." Instead, you learn to design assessments on purpose, read the data they produce, and change your teaching in response. It is one of those courses that feels theoretical at first and then quietly reshapes how you think about every lesson you will ever teach.

Direct answer: D172 has no proctored exam. You pass it by submitting performance tasks that show you can plan aligned formative and summative assessments, analyze student data, and reflect on your own teaching. Follow the task rubric line by line, use the WGU templates, and submit early so an evaluator's feedback becomes part of your process rather than a surprise.

Most students meet D172 while working through the teacher-preparation sequence, and it pairs naturally with the standards and instruction courses around it. Because the whole course is built on submitted work rather than a timed exam, the challenge is not memorization. It is precision: saying exactly what the rubric asks, in the order it asks, with enough evidence to back every claim. Students who treat it like an essay lose time to revisions; students who treat it like a checklist of aspects move through it far more smoothly.

What the Performance Tasks Cover

D172 is assessed entirely through performance tasks rather than an objective test. Public course descriptions and widely shared student accounts point to a consistent set of components. Expect to demonstrate that you can:

• Build an assessment plan. Using a WGU lesson-plan template, you describe formative assessments and a summative assessment tied to a specific learning objective, and explain how each one measures the intended learning.
• Differentiate and accommodate. You address how the assessments would be adjusted for distinct groups of learners, commonly gifted and talented students, English learners, and students with other exceptionalities.
• Analyze student data. Working from a provided data set or scenario, you interpret student performance, identify what the results reveal about learning, and describe the feedback you would give students.
• Recommend instructional adjustments. Based on the data, you propose specific, justified changes to future instruction rather than vague "reteach it" statements.
• Reflect on teaching practice. You evaluate a lesson or your own instruction, often using a structured reflective framework such as Gibbs's reflective cycle to move from description through evaluation to a concrete plan of action.

The connecting thread is the assessment loop: plan an assessment, collect evidence, interpret it, and let that evidence drive your next teaching decision. If you can show that loop clearly in your writing, you are demonstrating exactly what the course wants.

How Hard Is It, and How Long Should You Budget?

Many students report that D172 is moderate rather than brutal. The concepts are approachable, especially if you have any classroom or tutoring experience, and there is no exam anxiety to manage. What lengthens the course is the writing and the revision cycle. Tasks that miss a single rubric aspect come back, and each round trip through evaluation adds days.

A realistic plan is to give yourself a couple of focused weeks, faster if you can write cleanly against a rubric and slower if academic writing is not your comfort zone. The single biggest time saver is submitting your first task early. Evaluator feedback on task one usually reveals the pattern the rubric is looking for, and that pattern carries into the remaining tasks. Do not wait until you have "perfected" everything before submitting the first piece; a competent early submission teaches you more than a polished late one.

A Study and Submission Plan That Works

Because D172 is task-based, your "studying" is really preparation for writing. A few tactics fit this course particularly well:

• Reverse-engineer the rubric. Before you write, copy each rubric aspect into your document as a heading. Draft directly under each one. This is active recall applied to a PA: you are forcing yourself to produce the required content rather than hoping it appears in your prose.
• Master the vocabulary of assessment. Get crisp, confident definitions of formative versus summative assessment, validity, reliability, and differentiation. Space this out over several short sessions rather than cramming; the terms need to be second nature so you use them correctly in your tasks.
• Practice the data-analysis move. Take any small set of scores and practice writing three sentences: what the data shows, what it means for learning, and what you would change next. That is the exact shape D172 rewards, so rehearsing it on throwaway examples pays off.
• Use the course resources first. Work through the WGU learning materials and any cohort webinars or recorded task walkthroughs before reaching outside them. Instructors and course mentors know the current rubric; general internet advice may describe an older version.
• Write plainly. Evaluators are checking whether you addressed each aspect, not admiring your style. Short, direct paragraphs that name the aspect and answer it are far safer than flowing essays.

Mistakes That Send D172 Submissions Back

• Answering the topic instead of the aspect. The rubric asks for specific things in a specific order. Writing generally "about assessment" is the most common reason a task is returned.
• Vague differentiation. Saying you will "provide extra support" for English learners is not enough. Name the concrete adjustment to the assessment itself.
• Describing data without interpreting it. Restating scores is not analysis. You have to say what the numbers mean for student learning and what you will do about it.
• Recommendations with no justification. Every proposed instructional change needs a reason tied back to the evidence you just analyzed.
• Skipping the reflective structure. When a task calls for a reflective framework, use its stages explicitly instead of writing a loose reflection.
• Alignment drift. Assessments that do not clearly measure the stated objective break the whole plan. Keep objective, assessment, and evidence pointing at the same target.

Your D172 Readiness Checklist

Before you submit each task, run through these self-checks:

• Can you explain the difference between formative and summative assessment in one clear sentence each?
• Can you point to how each assessment in your plan measures the specific learning objective?
• Can you name a concrete accommodation for gifted and talented students, English learners, and students with other exceptionalities?
• Can you read a set of student results and state what they mean for learning, not just what they are?
• Can you propose an instructional adjustment and defend it with the data you analyzed?
• Can you describe the feedback you would give students so it actually guides their next steps?
• Can you walk through a reflective cycle from description to a concrete action plan?
• Have you matched every rubric aspect to a labeled section in your document?

D172 FAQ

Is D172 an objective exam or a performance assessment?

It is a performance assessment. You pass by submitting tasks that are evaluated against a rubric, not by sitting a proctored, multiple-choice exam. That means there is nothing to memorize for a test day; the work is in planning, analyzing, and writing clearly.

What is D172 actually about?

It is about the full assessment loop in teaching: designing formative and summative assessments that align to your objectives, interpreting the data students produce, giving useful feedback, and adjusting your instruction based on evidence. Reflection on your own practice is woven throughout.

How long does D172 usually take?

Many students report finishing in a few weeks, though it depends heavily on your writing speed and how many revision rounds your tasks need. Submitting the first task early to get evaluator feedback is the most reliable way to shorten the overall timeline.

How do I avoid getting my tasks sent back?

Address every rubric aspect explicitly and in order, be concrete rather than general, and always connect data to a decision. Copying each rubric aspect into your document as a heading and answering underneath it is the simplest safeguard against missed requirements.

Do I need classroom experience to pass?

No. The tasks are often built around provided scenarios and templates, so you can complete them without a current classroom. Any tutoring, coaching, or teaching experience helps you write with specifics, but it is not required.

Where should I get help if I get stuck?

Start with your course instructor, course mentor, and any official cohort sessions, since they know the current rubric. Student discussion boards are useful for morale and general difficulty consensus, but never rely on shared "task solutions"; submitting someone else's work is an academic integrity violation.

Keep Going

D172 is one of the courses that makes you a genuinely better teacher, because reading assessment data well is a skill you will use for your entire career. If you are moving through the education sequence, it sits alongside its sibling course D093 Assessing Impact on Student Learning, pairs closely with D184 Standards-Based Assessment, and the clear writing it rewards carries over from courses like D268 Introduction to Communication. You can browse everything for your program on the School of Education hub or see the full library on the all-guides index. For official course details, always confirm against WGU's teaching program pages, since requirements are updated over time.