> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mesolab.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Subjects and year groups

> What MESO covers, and why your profile decides what you can plan.

MESO plans against the NCCA specifications for **Junior Cycle** and **Leaving
Certificate**. Senior Cycle coverage in particular expanded substantially during
2026 and continues to grow.

## Your profile decides what you see

The subject and year-group pickers are not a catalogue of everything MESO
supports — they are filtered to **what you told MESO you teach** during
[profile setup](https://docs.mesolab.ai/teachers/setup.md).

> [!TIP]
>
> If a subject you teach is missing from the picker, that is almost always the
> profile, not the coverage. Add it under **Settings → Account → Profile** and it
> appears.

If it is still missing after that, the specification is not loaded yet. Tell us
at [contact@mesolab.ai](mailto:contact@mesolab.ai) — subject coverage is
prioritised by what schools actually ask for.

## Checking what is available

The picker in the create-unit flow is the authoritative list for your account,
and it is always current. This page deliberately does not reproduce a list of
subjects, because a copy in documentation goes stale the moment a specification
is added.

## Junior Cycle and Senior Cycle are separate

A subject can exist at both cycles and they are **distinct** in MESO, with
different specifications, different learning outcomes and different assessment
methods. History at Junior Cycle and History at Senior Cycle are not the same
subject and will not plan the same way.

Choosing the year group first, as the create-unit stepper does, is what settles
which of the two you are working in.

## Levels

> [!NOTE]
>
> Where a specification distinguishes levels, that distinction lives in the
> specification content MESO plans against rather than in a separate picker. Check
> the outcomes selected on a unit's **Overview** if you need to confirm what a plan
> was built from.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.