Organize Your Course Catalog So Learners Can Choose the Right Level

A learner selects “Intermediate” because they completed a beginner course elsewhere. Another avoids it because they lack confidence, despite having the necessary skills. A returning learner recognizes the topics but cannot yet complete the entry tasks independently. Consider these hypothetical situations when reviewing your catalog: would its labels help each person choose, or simply leave them guessing?

If you are deciding how to organize a course catalog for different learner levels, start with the decision learners must make: “What should I take next, and what evidence supports that choice?” This guide presents SubSchool’s editorial framework for answering that question. It concerns choosing between courses, not differentiating instruction within a single course.

NWEA’s October 29, 2026 article, 4 research-backed ways to differentiate instruction, emphasizes evidence when identifying learner support needs and cautions against broad low- or high-performing labels. That is useful context for thinking about readiness, but the accessible excerpt does not establish evidence about catalog design. The workflow below is an editorial recommendation, not an NWEA-tested catalog model.

1. Define levels through observable entry skills

Before renaming courses, ask each course author to list what learners need to do before the first substantive lesson. Replace “basic knowledge required” with observable actions: write a coherent paragraph, solve a one-step equation, or create and save a spreadsheet formula.

Keep three categories separate:

• Essential prerequisites: skills the course assumes and does not substantially reteach.
• Helpful preparation: experience that may make entry smoother but is not required.
• Skills taught here: intended learning outcomes, not admission requirements.

Then describe the conditions under which an entry skill should be demonstrated. Does the learner need to work independently, use a reference sheet, or explain their reasoning? “Can calculate percentages with a calculator and explain the result” is a more precise expectation than “comfortable with mathematics.”

For this framework, treat readiness as course-specific evidence, not a permanent learner category. Keep age, intended audience, course completion, and readiness in separate fields. A previous course can be a suggested route without being the only acceptable evidence of preparation. Where your school requires a particular prerequisite course, state that requirement separately and have its academic owner confirm it.

2. Give every course the same label structure

Use the same information order across the catalog so learners can compare alternatives. A practical course card or description should include:

1. Intended learner: who the course is designed to serve.
2. Entry expectations: the essential skills, expressed as actions.
3. Intended outcomes: what learners will practice and work toward demonstrating.
4. Workload and format: estimated study time, live participation, and independent work.
5. Next step: a recommended follow-on course, review option, or teacher consultation.

Keep a familiar level word if it helps navigation, but attach it to a subject and a concrete expectation. Prefer “Writing: Developing Arguments” to “Level 2” alone. Avoid labels that describe the learner as weak, remedial, or advanced across every skill.

Hypothetical course label: Writing: Developing Arguments. For learners who can write a focused paragraph with supporting details. Practice building and revising a short argument. Estimated workload: three hours weekly, including one live workshop. Recommended next step: Writing with Sources, subject to readiness review.

The workload above is illustrative, not a benchmark. Ask the course author to check estimates against actual activities. Where two courses cover similar topics, explain whether the difference is entry skill, depth, pace, or delivery format rather than inventing another ambiguous level.

3. Build a placement pathway with an explicit review branch

Apply the same routing sequence to courses in a subject pathway. Keep it proportionate: use enough evidence to answer the entry question, without turning selection into an unnecessary examination.

1. Start with the learner’s goal. Identify the subject and intended destination before considering a level.
2. Offer a self-check. Show the essential entry skills alongside sample tasks. Let learners indicate “independent,” “with help,” or “not yet.”
3. Collect relevant evidence. Use a short diagnostic task, a recent work sample, or a teacher-reviewed record that addresses the prerequisites.
4. Compare evidence with entry criteria. Review essential skills individually rather than allowing one overall score to conceal a missing prerequisite.
5. Route the learner. Recommend the course, recommend preparation first, or send the case to the named exception reviewer.
6. Explain and revisit. State the reason, available alternatives, and when the recommendation can be reviewed.

Create a simple rule for uncertainty: unclear evidence goes to review, not automatic rejection. A learner who cannot provide a recent portfolio should have another way to demonstrate preparation. If a sample task produces an unclear result, the reviewer can request a second task or a brief discussion.

Document the recommendation in ordinary language: “Your sample demonstrates paragraph structure, but the course assumes independent use of supporting evidence. Complete the preparation activity, then request another review.” Avoid presenting a placement recommendation as a prediction of success.

4. Use a course-level and placement matrix

Maintain one internal record per course in a spreadsheet, document, or platform field set. Use these seven fields as a reusable template. Replace the illustrative entries below with your own course evidence, named reviewers, and scheduled dates; the examples are hypothetical and are not SubSchool product features.

The review date here concerns the course record, not an individual learner’s placement. Keep individual placement decisions in a separate, appropriately restricted record. Assign an actual staff member to each reviewer role before publishing the pathway.

Use the matrix to check the handoff between courses. If the next course assumes a skill that the preceding course does not teach or assess, revise the recommendation, add preparation, or explain the additional evidence required. Do not advertise progression as automatic unless that is genuinely your school’s approved arrangement.

5. Resolve uneven and borderline readiness without duplicating courses

Use exceptions to clarify decisions rather than creating a separate course for every learner profile. Consider three hypothetical cases:

• Uneven readiness: a learner produces strong ideas but has difficulty organizing paragraphs. Review the specific entry requirement and decide whether targeted preparation is sufficient before joining.
• Returning learner: a learner completed the preceding course long ago. Offer a current sample task rather than relying only on the old completion record.
• Borderline placement: a learner demonstrates a prerequisite inconsistently. Ask the exception reviewer to recommend preparation, another evidence check, or a provisional placement with a defined review point.

If provisional placement is available, explain its conditions before enrollment and check that the teacher can support the agreed review. Publish any transfer arrangements accurately. Do not imply that learners can switch courses freely unless your school actually offers that option.

Reserve separate catalog entries for meaningfully different offerings. A short preparation activity can be a bridge into an existing course; it does not necessarily need to become another numbered level.

6. Assign ownership and audit recurring mismatches

Separate responsibility for educational accuracy from responsibility for publishing changes. The course author owns prerequisite and outcome definitions. The academic manager approves pathway relationships. The catalog editor keeps labels consistent. The exception reviewer decides ambiguous placements. In a small school, one person may hold several roles, but the responsibilities should remain explicit.

Keep a restricted correction log with the original recommendation, revised recommendation, relevant skill gap, suspected cause, and responsible owner. Do not place learner names or work samples in the public catalog matrix. For wider catalog reviews, use de-identified summaries where possible.

At a scheduled review, look for repeated patterns: the same misunderstood label, the same missing prerequisite, or the same next-course recommendation being overturned. Treat these as prompts for investigation, not proof of a single cause. Check whether the problem lies in wording, diagnostic tasks, pathway logic, or changes to the course itself.

Finish each correction with an owner, a deadline, and a check of every place the label appears. Start with one subject pathway, test its labels with learners, and expand after resolving the unclear decisions.

Put the educational rules before the automation

SubSchool’s official overview describes AI-assisted course preparation with editable outputs and educator review. Use automation to support repetitive teaching work while teachers retain authorship and the final educational decision; do not assume it supplies the placement workflow proposed here.

Ready to connect clearer course information with your school’s teaching operations? Explore SubSchool for online schools, and bring your prerequisite matrix and review responsibilities to the discussion. Define the decisions first, then confirm which supporting workflows fit your setup.