D699 Elementary Mathematics Curriculum, catalog number EDUC 5090, is the two-CU graduate mathematics curriculum course in the WGU Master of Arts in Teaching sequence. It covers elementary mathematics curriculum from numbers and operations through algebraic thinking, the same material as the undergraduate D691 (EDUC 2260). The graduate framing is evaluative and practical: you will teach from a programme somebody else chose, and the skill is judging its coherence and knowing what to do where it is weak.
What coherence looks like when you are judging it
Coherence in a mathematics programme is not a quality you sense; it is a set of properties you can check. Does each unit state what it assumes? Do ideas return in a form that extends them rather than repeating them? Does the treatment of an operation prepare the treatment of the next one? Are representations reused across topics so children accumulate tools, or does each unit introduce its own and abandon it?
The check that finds the most is following one idea across a year. Take equality, or place value, or the meaning of multiplication, and trace every place the programme touches it. In a coherent programme the treatments build. In an incoherent one you find the same explanation three times at the same level, separated by months, with no reference between them.
Pacing is the second practical judgment and it is where most programmes meet reality badly. Published pacing guides frequently assume more instructional days than a school year contains once assessment weeks, interruptions and absence are counted. A graduate submission that compares the guide against a realistic calendar, finds the gap, and says which units would be compressed and which protected is doing exactly the work an experienced teacher does in August.
Deciding what to protect requires a principle, and the defensible one comes from the progression. Content that later work depends on cannot be compressed without cost; content that sits at the end of a strand and feeds nothing can be shortened with less damage. Saying which is which, for your grade, is a curricular argument with real stakes.
Language is the third dimension and it is quietly consequential. Programmes vary in whether they use precise mathematical terms from the start, introduce informal language and replace it later, or leave terminology inconsistent between units. Children who meet three names for the same idea across a year carry an unnecessary load, and noticing that in an evaluation is a specific, defensible finding.
Finally, graduate work is expected to consider the teacher as well as the children. Programmes differ in how much mathematical knowledge they assume from the person teaching them. A programme whose teacher notes explain the mathematics behind each lesson supports a generalist elementary teacher in a way that a programme of scripted procedures does not, and for a career changer without a mathematics background that difference is worth naming.
Assessment design inside the programme is worth checking as its own criterion, because it reveals what the authors actually value regardless of what the introduction claims. Read the end of unit assessments before reading the lessons. If the assessments are pages of computation, the programme values procedural fluency whatever its stated philosophy, and the lessons about understanding will be the first thing teachers skip under time pressure. If the assessments ask children to explain, represent or justify, the understanding language in the front matter is load bearing. That check takes ten minutes and produces a finding that reframes everything else in the evaluation.
Turning the rubric into a curriculum evaluation
Scored aspects are held in your Course of Study rather than the public catalog. Count them before drafting, since each is judged alone against a three-point scale and each needs a 2. Evaluative aspects score on declared criteria, so a judgment offered without a stated test behind it loses even when it is correct.
Where D699 uses a performance assessment, use the rubric's nouns as headings and answer in its order. Where an aspect asks for both an evaluation and a plan, separate them so the plan visibly follows the findings.
A worked word budget. Assume four scored aspects and directions pointing at roughly 1,450 words. Reserve 100 words for context naming the grade, the programme and the standards in scope, and 70 for a close. That leaves 1,280 across four aspects, or 320 words each.
Weight toward the evaluative aspects. Coherence analysis deserves 400 and the pacing or modification aspect deserves 360. The two remaining aspects sit at 260 each, which lands the arithmetic on 1,280. In a two-CU course the sentences to cut first are the ones describing what the programme contains, because the evaluator wants the trace of one idea across the year, not a summary of the table of contents.
A shape that fits a mathematics programme evaluation
Use the directions' sections where they specify them. Where the shape is yours, this order keeps criteria before conclusions and findings before recommendations.
| Section | What it must establish | The weak version |
|---|---|---|
| Programme and grade | Exactly what is being evaluated and against what standards | A general reference to the school's mathematics materials |
| Evaluation criteria | The coherence tests you will apply, stated in advance | Criteria visible only in the conclusions |
| Idea trace | One idea followed across the year, unit by unit | Units reviewed individually with no thread followed |
| Prerequisite check | Whether units state and honour what they assume | Assumptions accepted because the sequence looks familiar |
| Pacing reality check | Guide days against a realistic calendar, with the gap named | The publisher calendar reproduced without testing |
| Language consistency | Whether terminology holds steady across units | Terminology treated as a stylistic matter |
| Modification plan | What you compress, protect, supplement, and why | General suggestions that could apply to any programme |
Do the idea trace even if the task does not ask for it by name. It is the single most productive analytical move available in this course and it usually supplies the concrete evidence every other section needs.
Evidence craft in a graduate mathematics curriculum submission
Evaluation claims need both mathematical accuracy and sourcing, and graduate readers check both.
- Cite the learning progression research that underwrites your coherence criteria rather than presenting them as preferences.
- Quote standards with codes and read them for whether they ask for understanding, procedure or application.
- Point at specific lessons or pages when you make a claim about the programme.
- Be exact with mathematical language, since imprecision in an evaluation of someone else's precision is conspicuous.
- Keep any school and any child unidentified where you describe how the programme plays out in a classroom.
- APA throughout, including full citation of the programme under evaluation.
Acknowledge what your evaluation cannot see. A programme read on paper may be taught well or badly, and distinguishing weaknesses a skilled teacher can repair from weaknesses built into the sequence makes your recommendations usable rather than merely correct. A thin explanation in the teacher notes is recoverable by anyone who understands the mathematics; a sequence that introduces an algorithm before the idea it encodes is not, because the damage happens in the order rather than in the delivery.
What separates Competent from a returned evaluation
Aspects score independently, so returns here usually name criteria that were never declared or a pacing section that reproduced the publisher's calendar.
- Criteria appear before findings and are specific enough to be argued with.
- At least one idea is traced across the year with unit references.
- Pacing is tested against a realistic number of instructional days.
- Compression decisions follow from the progression rather than from convenience.
- Every finding points at evidence someone else could check.
WGU records work as Competent or Not Competent rather than issuing letter grades, and performance assessment work can be revised and resubmitted with no grade penalty, so a return costs queue time inside a six-month flat-rate term. Since every course closed inside the term lowers your effective cost per course, declaring criteria before drafting is the cheapest protection available.
The boundaries hold: proctored objective assessments are for preparation only and never for us to sit, portal credentials are never requested, and any classroom-based component of your course remains yours to complete.
Five mistakes that weaken a D699 submission
- Reviewing unit by unit. Coherence is a property of the year, so a unit-level review cannot detect it.
- Accepting the pacing guide. Most assume more days than a real calendar provides, and testing it is a twenty-minute task.
- Compressing what later work depends on. Cutting foundational content buys time now and costs more later.
- Evaluating without criteria. An impression with adjectives is not an evaluation, however accurate.
- Being imprecise about mathematics. Loose terminology undermines an evaluation whose subject is partly terminology.
How support works on D699
Send the rubric and task directions along with the grade, the standards framework and any programme the task asks you to evaluate. The draft comes back aspect-mapped, with criteria declared first, one idea traced across the year, pacing tested against a realistic calendar, and compression decisions argued from the progression.
If your Degree Plan lists the undergraduate code, build from D691. The graduate methods counterparts, D700 and D701, teach inside the programme you evaluate here.
Three questions MAT candidates ask about D699
Is D699 the same course as EDUC 5090?
Is D699 the graduate version of D691?
What is the quickest way to test a programme's coherence?
Evaluating a mathematics programme for D699?
Send the rubric, directions and the programme in scope. You get an aspect-mapped draft with criteria declared first, one idea traced across the year and pacing tested against a real calendar.
Where D699 sits in WGU's programs
The July 2026 catalog places this code in 2 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.