Funktionen Preise Dokumentation Kontakt Anmelden Jetzt starten
Sprache

Skip logic and scoring

Showing a question only when it applies, scoring a response, and comparing a pre test with a post test.

Two features turn a flat list of questions into something that behaves. Skip logic decides which questions a person is asked at all; scoring turns the answers they give into a number.

Showing a question only when it applies

Skip logic belongs to the question you want to hide. Open that question in the builder and give it one or more conditions. The question then appears only when those conditions are met, and stays out of the way when they are not.

A condition always looks back. It tests the answer to a question that comes earlier in the form, so a question can never depend on one the person has not reached yet. There is no separate logic screen: you set the logic where you set everything else about the question.

The conditions you can write

Each condition names an earlier question, an operator and, for most operators, a value to compare against. These are the operators:

  • equals
  • does not equal
  • contains
  • is empty
  • is not empty
  • greater than
  • greater than or equal to
  • less than
  • less than or equal to

Add more than one condition and you choose how they combine. With and, which is what you get unless you change it, every condition must be true before the question appears. With or, any one of them is enough.

Two details worth knowing. Text comparisons ignore letter case, so Yes and yes match each other. The four numeric comparisons fail closed: if the stored answer is not a number, the condition simply does not match, and the question stays hidden rather than appearing by accident.

Scoring a form

A form uses one scoring method, chosen on the form itself:

  • No Scoring, which leaves the answers as answers.
  • Knowledge Test, where you supply an answer key and the platform marks each response against it.
  • Rating Average, for a satisfaction survey where the useful figure is the mean of a scale such as 1 to 5.
  • Rating Sum, where the useful figure is the total across the scored questions.

The form also carries the maximum of its rating scale, which is 5 unless you change it, and a pass threshold, which is 70 percent unless you change it.

Each question is then set up in the builder. Mark it as scored, set the correct answer, and set the points it is worth, which is 1 unless you say otherwise. For satisfaction scoring you also mark which answer counts as a positive one, and whether the question is counted in the score at all.

You do not calculate anything yourself. When a response becomes complete the platform works out the score, the maximum that was available and the percentage, and stores all three against that response.

Comparing a pre test with a post test

Two forms can be paired: one marked as the pre test, the other as the post test. Ask the same people the same questions before and after your activity, and the platform does the comparison for you.

When a post test response is completed, the platform looks for that same person's most recent completed pre test and works out three figures:

  • The simple gain, which is the post test score minus the pre test score.
  • The normalised gain, which is the share of the ground still left to gain that the person actually gained.
  • The relative gain, which is the increase expressed as a percentage of the pre test score.

Two of the three have limits worth knowing. The normalised gain has no value when the pre test was already 100 percent, because there was nothing left to gain, and the relative gain has none when the pre test score was zero, because an increase cannot be expressed as a share of nothing. All of them appear on the response detail page for the post test response.