← Documentation

Guided steps

Updated on August 5, 2026

Step-by-step problems break the solution into stages. Instead of just knowing whether the final result is correct, you can see exactly where in the reasoning the student goes wrong.

What they are for

When a problem has several intermediate steps — setting up equations, substituting values, simplifying, interpreting — the step-by-step type makes each one visible. The student answers each stage separately and receives specific feedback for each.

It is especially useful when the process matters as much as the result: in mathematics, physics, chemistry, or any subject where following the steps correctly is part of the learning.

How to define steps

In the editor, select the Step by step type in the How is it answered? section, then go to the Steps section. Press Add step to add a stage. Each step has two fields:

  • Step instruction — what you ask the student to do at this stage. Write it as a direct instruction, for example: "Draw the free-body diagram" or "Calculate the net acceleration".
  • What is expected in this step — an internal note read only by the AI. Describe what should appear in a good answer: which formulas, which conclusions, which common errors to detect.

You can add as many steps as you need. To remove one, press the delete button on its card.

You need at least one step to save the problem.

How it is graded

On submission, the AI receives the full statement, the instruction for each step, the expectation notes and the student's answers for each stage. It evaluates the whole and returns:

  • A score from 0 to 100.
  • A written feedback that explains what went well and what failed along the way.

As with free text, the score determines whether the result is Passed, Partial or Failed based on fixed thresholds in the system.

Tips for good steps

  • Order steps the way the reasoning flows. The student sees them in the order you define, so follow the logical sequence of the problem.
  • One task per step. A step that asks three things at once makes it hard to identify where the student fails.
  • Use the expectation field. The instruction is what the student sees; the expectation is what guides the AI. Include there the expected intermediate results or typical errors to detect.
  • Do not repeat the statement in every step. The student can always see the full statement; in the instruction it is enough to say what to do at this stage.

Steps do not render formulas in the instruction or expectation fields inside the editor. Formulas do work in the main problem statement.

Frequently asked questions

Can the student see all steps at once? Yes. The solving screen shows all steps at the same time and the student can answer them in any order before submitting.

Can I add a rubric alongside the steps? No. For the step-by-step type, the AI uses the expectation notes of each step as its guide. There is no separate rubric section for this type.

Can I mix a numeric step with a free-text step? Yes. Every step is a free-text field, but you can ask the student for a number in one and an explanation in another. The AI evaluates the whole.

Next step