Skip to content
Fito

Bloom levels and proficiency

Fito measures you on two scales that share three of their names. One is what a case aims at. The other is what you hold. Reading a score, a prerequisite badge or your Competencies page means knowing which of the two you are looking at.

This page is for anyone who has submitted a case, or is about to, and wants to know what the result records. It does not cover how a criterion is scored — that is How a case is scored.

Two scales, three shared names

Section titled “Two scales, three shared names”

A Bloom level is a target. A case declares one in its own files, and it never changes because of anything you do. There are three:

Bloom level What the case is asking for
KNOWLEDGE You can recall the thing and say what it is.
COMPREHENSION You can explain it, and say why it behaves as it does.
APPLICATION You can reach for it and use it correctly in context.

A case declares a Bloom level in four places: on each rubric criterion, on each quiz question, on each prerequisite, and on each learning objective.

A proficiency is a recorded state on your profile, for one knowledge component. It takes the same three names plus a fourth:

Proficiency What it records
NOT_ACHIEVED You were assessed, and did not meet the criterion.
KNOWLEDGE You demonstrated recall.
COMPREHENSION You demonstrated understanding.
APPLICATION You demonstrated use in context.

NOT_ACHIEVED has no Bloom counterpart, and it meets no target. A prerequisite asking for KNOWLEDGE is satisfied by a recorded KNOWLEDGE, COMPREHENSION or APPLICATION, and by nothing else.

From a case score to a recorded proficiency

Section titled “From a case score to a recorded proficiency”

Each rubric criterion names one knowledge component and the Bloom level it targets for that component. When your work is scored, the criterion takes a score from 0 to 3.

The score and the Bloom level answer different questions. The score says how well your work met the criterion. The Bloom level says how deep a met criterion certifies. Together they decide the proficiency recorded for that component, with no judgement in between:

Score Label Proficiency recorded
0 not_achieved NOT_ACHIEVED
1 partial NOT_ACHIEVED
2 achieved The criterion’s own Bloom level
3 exemplary The criterion’s own Bloom level

So an APPLICATION criterion met at score 2 records APPLICATION, and a COMPREHENSION criterion met at score 3 records COMPREHENSION. A 3 changes the feedback you read, not the depth recorded. A 1 is real work that fell short of the criterion, and it records NOT_ACHIEVED.

A quiz question records the same way, from its own Bloom level. Where a component is scored more than once in one submission — by two criteria, or by the rubric and the quiz — the highest level is what is kept, not the highest score: APPLICATION from a score of 2 beats COMPREHENSION from a score of 3.

Proficiency is recorded per knowledge component, never per competence. A competence has no stored level of its own; what you see against one is computed when you ask for it.

Nothing recorded is not the same as zero

Section titled “Nothing recorded is not the same as zero”

NOT_ACHIEVED means you were assessed and did not meet the criterion — a score of 0 or 1. The absence of a value means you have never been assessed on that component at all. Fito writes NOT_ACHIEVED rather than writing nothing, so the two stay apart.

Your Competencies page shows them apart too: a recorded NOT_ACHIEVED reads Not achieved, and an element you have never met reads Not assessed.

How a competence rolls up

Section titled “How a competence rolls up”

A competence is a standing capability, and it is made of competence elements, each defined by exactly one knowledge component. An element carries no Bloom level of its own.

To show your standing in a competence, Fito averages the recorded proficiencies over every element the competence has, including its sub-competences’. Each proficiency counts as its position on the scale — NOT_ACHIEVED 0, KNOWLEDGE 1, COMPREHENSION 2, APPLICATION 3 — and an element you have never been assessed on counts as 0 as well. That position is for averaging, not a score: APPLICATION counts as 3 whether the criterion that recorded it scored 2 or 3.

A worked example, taken from the demo learner’s Request handling fundamentals:

Element Recorded Counts as
concept:javalin.handler APPLICATION 3
concept:javalin.request-handler COMPREHENSION 2
concept:javalin.handler-chain KNOWLEDGE 1
concept:javalin.context NOT_ACHIEVED 0
concept:javalin.request-context never assessed 0

The mean is 6 ÷ 5 = 1.2, over five elements of which four are assessed.

That is why the mean is a measure of the whole competence and not of the part you have touched. An element you have never seen pulls the number down exactly as a failed one does. The assessed count beside it is what tells you which of the two is happening.

What your Competencies page shows

Section titled “What your Competencies page shows”

/competencies is behind sign-in, and it shows your own standing and nobody else’s. It lists the competences you have been assessed in — a competence with at least one element carrying a recorded value, NOT_ACHIEVED included. A competence you have never touched does not appear at all, so an empty page means no submission has been scored yet rather than a score of zero.

Each competence carries three things, and they answer different questions:

  • A pill, naming the nearest whole level to the mean, where a half rounds up. A mean of 1.2 rounds to Knowledge. A mean below 0.5 gets no Bloom pill and reads Not achieved.
  • Proficiency achievement, a whole percentage: the points you hold over the points Application on every element would give, rounded down. The example holds 6 of 15 points, so it reads Proficiency achievement: 40%, and only Application on every element reads 100%.
  • A coverage line, such as 4/5 elements assessed.

The pill and the percentage are computed from your recorded proficiencies, never stored. Each has an information icon beside it: hover over it, focus it or tap it, and it shows that competence’s own arithmetic — the sum, the division and the rounding. On one competence’s page the sum lists every element’s points in the table’s order, such as 3 + 2 + 1 + 0 + 0 = 6. The icon on the Proficiency Level column header gives the points each level adds.

Open one and you get the element-by-element breakdown: the knowledge component, its type, and your recorded proficiency on it — Knowledge, Comprehension, Application, Not achieved or Not assessed. Each component links into the Knowledge area, so you can read what it is before you go and earn it.

Sub-competences do not get their own row. They are folded into the competence they belong to, and their elements are counted in its mean.

What’s next

Section titled “What’s next”