The Skills Map

Amal does not measure Arabic reading as a single number. It measures it as a structured map of 79 individual skills, organized into areas of reading development. Every child’s assessment produces a picture of where they stand across this map, not a single summary figure.

Why a map instead of a score

Arabic reading development does not unfold in a single dimension. A child might decode words accurately but struggle to understand what they read. Another child might understand spoken stories well but have difficulty with morphological endings in written text. A single composite number would hide these distinctions and make it impossible to match support to what the child actually needs.

The skills map keeps these distinctions visible. Teachers, support specialists, and school leaders can see which areas are strong, which need attention, and which have not yet been assessed.

Areas of reading covered in the current phase

The platform currently measures skills in seven active areas:

Listening comprehension is part of the map and is tracked in the platform’s data model, but it is not yet active as an assessed area in the current phase. Writing and spelling are designed and planned for a future phase.

79 individual skills

Within the seven active areas, 79 individual skills are mapped. Each skill has:

• An Arabic name and an English reference name
• A base weight reflecting how much it contributes to reading development
• A developmental stage range (for example, a skill expected to develop in Stages 2 through 3)
• A grade applicability range (some skills begin from Grade 1; others begin from Grade 2)

Not all 79 skills are assessed in every session. A diagnostic session covers the subset of skills relevant to the child’s grade and the current assessment window.

Gateway skills

Some skills in the map are classified as “gateway” skills. A gateway skill is one where a persistent weakness does not just affect performance on that single skill; it affects the interpretation of a whole area of reading development.

When the platform detects a persistent weakness in a gateway skill, it treats that differently from a weakness in an isolated, non-gateway skill. Rather than treating it as a small, contained problem, it flags a concern at the area level. The teacher sees that the gateway skill weakness may be affecting the child’s reading in a broader way.

Gateway skills have a priority ranking. If a child has weaknesses in multiple gateway skills at the same time, the ranking guides the teacher and the platform toward which one to address first. Spreading support across too many gateway skills simultaneously is less effective than concentrating on the highest-priority one.

What makes a skill a gateway

The gateway classification reflects the pedagogical relationship between skills. In Arabic, some skills are load-bearing for later development. A child who has not yet consolidated a gateway skill will find it harder to progress on the skills that depend on it, even with additional practice on those downstream skills. Identifying and addressing gateway weaknesses early is one of the core purposes of Amal’s measurement approach.

The Arabic-accuracy carve-out

Certain Arabic-specific orthographic features are tracked separately from the main skills map. These include:

• Shadda (the gemination marker)
• Tanween (nunation markers)
• Madd (long vowel length marks)
• Short-vowel markings (diacritics)

These features are classified as “Arabic-accuracy indicators” rather than gateway skills. When a child shows a pattern of errors on these features, the platform notes it as a gentle monitoring signal, not as an area-level escalation.

The reason for this distinction is pedagogical. Errors on these features can reflect:

• Normal acquisition pace (these features are among the later-consolidated aspects of written Arabic)
• Dialectal exposure (some features are more prominent in formal written Arabic than in the Arabic varieties children speak at home)
• Genuine orthographic difficulty

Because these causes produce the same surface pattern, the platform treats Arabic-accuracy indicator errors cautiously. It records the pattern, surfaces it to the teacher as a monitoring note, and adds a modifier to the child’s profile, but it does not use accuracy-indicator errors alone to trigger a support recommendation or an intervention.

An important constraint: accuracy indicator errors can only be detected from written and visual assessment items. Oral reading fluency probes, which measure reading speed and accuracy from text read aloud, do not provide reliable evidence about these specific features. The platform enforces this constraint automatically; Arabic-accuracy signals are never derived from fluency data.

Skill weight types

The platform assigns each skill a weight type that reflects its role in reading development:

Arabic-accuracy indicator skills are always classified as Supporting, regardless of their base weight, because they require gentler handling rather than escalation.

Grade applicability

The skills map applies grade-appropriate subsets of skills to each child. A few specifics:

• Some skills are applicable starting from Grade 1; others begin from Grade 2
• Pseudo-word reading items (which test decoding ability with invented words that follow Arabic phonological rules) are used only from Grade 2 onward; they require phonological awareness that is still developing in Grade 1
• The platform reads the child’s grade from their own profile, not from a class-level label, to handle multi-grade or cross-grade enrollment correctly

Assessment windows

The 79-skill map is assessed across three windows each year: beginning of year, middle of year, and end of year. Each window focuses assessment effort on the skills most relevant to that point in the year. Comparing a child’s status across the three windows shows growth over time on each skill individually, not as a combined number.