How to Create a Diagnostic Test Before a Course Starts: A Practical Blueprint for Tutors

Before assigning a revision pack, setting targets, or describing likely progress, establish what learners can currently do. A course-start diagnostic gives you a baseline for instructional decisions: which skills need priority, which misconceptions are common, and what kind of support learners may need first.

The key word is evidence. A useful diagnostic does not aim to label learners as able or weak. It collects enough relevant evidence to make a small number of defensible teaching decisions. That fits the wider principle of using assessment information in an ongoing cycle of instructional improvement, rather than treating data collection as an end in itself.

This practical blueprint shows how to create a diagnostic test before a course starts, review the results with context, and turn them into an achievable first-week plan.

What a course-start diagnostic should—and should not—tell you

A diagnostic assessment is designed to identify strengths, gaps, and starting points. The Institute of Education Sciences distinguishes diagnostic assessment from formative assessment: diagnostics identify what a learner does and does not yet know, while formative assessment is used during learning to inform instructional decisions. Your first test should therefore be the beginning of a process, not its final verdict.

A well-designed diagnostic can help you:

• identify prerequisite skills that may block access to the course;
• spot patterns in errors, including common misconceptions;
• select priorities for whole-group teaching and targeted practice;
• create provisional learner groups for the first week;
• give learners a clear, non-judgmental picture of where to begin.

It should not be used on its own to predict an exam grade, determine a learner’s potential, or promise a particular amount of score growth. Test-score interpretations need evidence appropriate to their intended use; a short tutor-created diagnostic is most credible when its claims stay narrow and practical.

1. Decide what decisions the test must support

Write the decisions first. Questions come second. This prevents the common mistake of assembling interesting questions that produce scores but no useful next action.

For a new GCSE mathematics cohort, for example, you may need to decide:

1. Which prerequisite number skills need immediate reteaching?
2. Who can begin algebraic manipulation independently?
3. Which learners need support reading multi-step word problems?
4. What should each learner practise after the first session?

Keep the list to three to five decisions. If you cannot name the instructional action a result will trigger, remove the skill or postpone it to a later check.

Design rule: every item should earn its place by supplying evidence for a decision you are prepared to make.

2. Build a simple skills-to-evidence blueprint

Map the course’s essential entry skills before writing items. Start with the course specification, scheme of work, or your own learning sequence. Then choose a small sample of skills that are both foundational and teachable early in the course.

Use more than one question format where that improves the evidence. Selected-response items can efficiently reveal a specific choice or misconception. Short constructed responses can show method, vocabulary, reasoning, or the point where a process breaks down. For language courses, a brief reading or listening task may need to sit alongside a short written or spoken response.

A short diagnostic is usually more usable than a broad paper that samples every topic superficially. Set a time limit that lets you review responses promptly. If the test is too long to mark and act on before the next lesson, it is too long for its purpose.

3. Write items that expose thinking, not only answers

For each skill, ask: “What would a learner who is nearly secure do? What would a learner with a likely misconception do?” Then write an item that makes those differences visible.

For example, a mathematics item may ask learners to solve a simple equation and show each step, rather than only enter a final answer. A science item may ask learners to choose a claim and explain which evidence supports it. A language item may ask learners to revise one sentence and briefly explain the change.

Use the item-review checklist below before administering the test:

• Does the item assess one intended skill rather than several accidental barriers?
• Is the wording clear to the learners who will take it?
• Does the response provide evidence for a specific teaching decision?
• Could a correct answer be a guess? If so, is another item available to confirm the skill?
• Could an incorrect answer reveal a recognizable misconception?
• Are required vocabulary, examples, and contexts appropriate for this cohort?
• Can you explain how you will score the response before learners see it?

Fairness matters even in low-stakes tutor assessments. Review examples, names, cultural references, and unnecessary reading load. If English proficiency is not the skill you intend to assess, avoid making dense language the main obstacle to demonstrating subject knowledge.

4. Set scoring rules before you look at results

Prepare a simple scoring key and a response-review routine in advance. For selected-response items, record correct, incorrect, and omitted. For constructed responses, use a small rubric such as: secure, partly secure, not yet evident. Add a misconception code where relevant, such as “operation error,” “misread command word,” or “unsupported inference.”

Do not rely only on a total mark. A total can be useful for sorting responses quickly, but it can conceal very different learner profiles. One learner may have strong knowledge but poor time management; another may complete routine questions but struggle to select an approach. Assessment design research emphasizes that score meaning depends on the intended interpretation and the evidence collected, so combine the score with item-level patterns, written work, and a brief learner conversation where possible.

Practical score interpretation notes

• Secure across most priority skills: offer early extension, but still check unfamiliar application.
• Mixed profile: target the specific weak skill rather than assigning a generic lower-level pack.
• Several gaps in prerequisites: prioritise the few skills that unlock upcoming course content.
• Low score with incomplete work: check time, access needs, confidence, language load, or unfamiliarity with the format before drawing conclusions.
• Unexpected response pattern: ask the learner to explain one or two answers; this can distinguish a misconception from a recording mistake.

5. Turn results into flexible groups and first-week homework

Create groups around a shared next step, not a permanent label. For example: “rebuild fraction fluency,” “practise equation structure,” and “apply algebra in context.” Learners can appear in different groups for different skills, and membership should change as new evidence arrives.

Use the diagnostic to plan the first week at three levels:

Keep homework focused. A learner does not need a complete course pack because they missed two prerequisite skills. Assign a manageable task that gives fresh evidence at the next session. SubSchool can help reduce repetitive preparation by drafting differentiated homework materials, while you retain authorship and make the final instructional decision.

When your first-week priorities are clear, use SubSchool’s AI homework generator to turn teacher-selected skills, examples, and support levels into a reviewable homework draft for each group.

6. Share the baseline carefully

Tell learners and families what the result means in plain language: “This is a starting snapshot that helps us choose the right next steps.” Share strengths first, name one or two priorities, and explain when you will check progress again.

A useful baseline statement includes:

• the skills sampled;
• what the learner demonstrated;
• the immediate focus for practice;
• the next opportunity to show improvement.

Avoid language such as “you are a grade 5 learner” or “this score proves you will achieve X.” NWEA’s recent discussion of setting growth goals and tracking progress reinforces the value of establishing goals and monitoring evidence over time. A tutor’s diagnostic can support that process, provided it is treated as one starting point among several sources of information.

A reusable checklist for every new cohort

1. Name three to five decisions the diagnostic must support.
2. Select essential entry skills from the course map.
3. Build a skills-to-evidence table before writing questions.
4. Include at least one item that reveals method, reasoning, or explanation.
5. Set a realistic time limit and scoring key.
6. Review items for clarity, unintended barriers, and likely misconceptions.
7. Analyse skill patterns as well as total marks.
8. Check unusual results with learner context and follow-up questions.
9. Create provisional groups around next steps.
10. Assign one focused first-week task, then collect new evidence.

The best diagnostic is not the most comprehensive paper. It is the smallest assessment that gives you trustworthy enough evidence to make the next teaching decision well.