Alabama literacy law: the Alabama Literacy Act and structured-literacy mandate

A note on Alabama’s literacy framework

The Alabama Literacy Act (2019) is the signature legislation, but Alabama’s structured-literacy framework rests on several pieces working together rather than a single statute. District leaders evaluating products or planning local implementation need to understand all of them, because they operate at different layers and address different parts of the K-3 reading problem.

• Alabama Literacy Act (2019) — The foundational statute establishing K-3 universal screening, Reading Improvement Plans, the ALSDE-approved core list, LETRS-aligned professional development, and (originally) a third-grade retention provision tied to reading proficiency. The Act is the legal anchor for everything else.
• Alabama Reading Initiative (ARI) — The ALSDE program that operationalizes the Act. ARI deploys regional literacy coaches, delivers professional development, supports districts implementing the framework, and provides technical assistance during curriculum reviews and intervention planning. ARI predates the Literacy Act and was substantially scaled up to support implementation.
• ALSDE-approved K-3 Tier 1 Core Reading Program list — The state-reviewed roster of core ELA materials. K-3 core adoptions must come from this list. The list is periodically updated as new programs are reviewed or existing programs change editions, so districts should always check the current roster rather than relying on a previously-printed version.
• LETRS professional development — The teacher training backbone. K-3 teachers and reading specialists complete the multi-volume LETRS program (or an ALSDE-approved equivalent), grounding instruction in the Science of Reading.
• Local Literacy Plans — Each district submits a Local Literacy Plan to ALSDE describing how it implements the Literacy Act framework locally, including curriculum selections, intervention structures, professional development plans, and progress monitoring.

The original retention provision tied to third-grade reading proficiency was subject to multiple legislative delays and modifications after passage. The political contestation around it — driven by concerns about equity, implementation readiness, and the consequences of high-stakes grade-level decisions — has produced a policy environment where the retention mechanism described in the 2019 statutory text is not necessarily the policy currently in operational effect. Districts should treat retention as policy-in-flux and consult current ALSDE guidance rather than the original statute.

The 2019-2026 timeline at a glance

• 2019 — Alabama Literacy Act passed. K-3 universal screening, ALSDE-approved core list requirement, LETRS training requirement, and third-grade retention provision codified. Initial implementation timelines set.
• 2020-2021 — ALSDE issues guidance on approved screeners, the Tier 1 core list begins formal review, and LETRS rollout starts in earnest. COVID-19 disruption complicates the early implementation window.
• 2022 — First wave of LETRS-trained K-3 teachers comes online. Districts submit updated Local Literacy Plans. Retention provision implementation timeline becomes a public policy debate.
• 2023-2024 — Legislative discussion of the retention provision continues. ALSDE issues operational guidance reflecting the modifications. ARI coaches deepen district-level support.
• 2025-2026 — Implementation matures. Most K-3 teachers have completed or are in active LETRS coursework. The Tier 1 core list is broadly adopted across districts, though some districts are mid-transition.

Reading Improvement Plans in practice

Reading Improvement Plans (RIPs) are the operational mechanism through which the Literacy Act reaches the individual student. The general shape is consistent across districts: a student identified through universal screening as reading below grade level receives a written RIP that documents the specific deficit areas, the intervention plan, the progress-monitoring cadence, and the criteria for exiting the plan.

In practice, the documents and the work behind them vary in quality. A well-implemented RIP names the specific phoneme-grapheme correspondences a student has not yet consolidated, ties the intervention to those specific gaps, and produces weekly or biweekly progress-monitoring data that confirms the intervention is working or signals that it needs to change. A poorly-implemented RIP names a generic “below benchmark on DIBELS” and a generic “Tier 2 intervention” without specifying either the underlying skill gap or the rate at which the gap is closing.

ARI coaches generally push districts toward the better implementation pattern, but the operational lift is real. The bookkeeping alone — keeping each RIP-eligible student’s documentation current, capturing intervention notes, recording progress-monitoring data, and producing the reports ALSDE expects — competes for teacher and coach time with the actual intervention work. Tools that reduce the documentation burden without reducing data quality are valuable here, which is why ORF and decoding data captured automatically by a digital practice tool tend to feature in RIP workflows once districts have one in place.

What this means for district adoption decisions

When evaluating literacy products for Alabama use, district curriculum offices typically check the following points before bringing a recommendation to the board:

1. ALSDE Tier 1 Core Reading Program list inclusion (for cores) — Is the product on the state-reviewed list, or applying to be? K-3 core ELA adoptions must come from this list. A product that is not on the list cannot serve as the primary core, regardless of how strong its pedagogical case is.
2. Science of Reading / structured-literacy methodology — Does instruction use explicit, systematic, cumulative phonics consistent with LETRS-trained teachers’ practice? Programs that rely on three-cueing scaffolding, predictable text driven by picture cues, or balanced-literacy methodology will struggle in an Alabama review even where there is no formal statutory ban.
3. LETRS compatibility — Does the product’s scope and sequence align with how LETRS-trained K-3 teachers will deliver instruction? LETRS is not a curriculum; it is a teacher knowledge program. But teachers trained in it have specific expectations about phoneme-grapheme correspondence ordering, orthographic mapping, and decoding-first methodology that a product needs to match.
4. Universal screening and progress monitoring fit — Does the product produce data usable for Reading Improvement Plan progress monitoring under the Act? ORF (oral reading fluency) data, nonsense-word fluency, and grade-level decoding measures are the data types ARI coaches expect to see in RIP documentation.
5. ESSA evidence tier — For federally-funded supplemental purchases, what tier of evidence does the product carry? ESSA tier remains the federal-funding gate independent of state policy.

For supplemental and intervention purchases, ESSA evidence tier is the key federal-funding gate. Storytime’s ESSA Tier 4 evidence rationale supports federal-fund procurement of supplemental practice tools.

A district-by-district checklist

Before scheduling a vendor demo, curriculum leaders in Alabama districts can save significant time by answering the following internally:

• Which core ELA program from the ALSDE Tier 1 list has the district adopted, and what scope-and-sequence does it follow?
• How far through LETRS coursework are the K-3 teachers in each building? Are there still teachers who need to start or finish?
• What universal screener is in use, and how is its data being routed into Reading Improvement Plan documentation?
• How are RIPs currently being progress-monitored, and is the data informing instructional change inside classrooms?
• Are there federally-funded line items (Title I, IDEA) that require ESSA evidence tier documentation for supplemental purchases?

Answering these questions internally before vendor conversations begin allows the procurement committee to evaluate products against the actual local implementation state rather than a generalized “Alabama” frame, which is rarely the right level of abstraction for an operational decision.

Common procurement misconceptions

A few patterns recur in conversations with district leaders that are worth flagging directly:

• “Alabama banned three-cueing by statute.” Not in the same explicit language some other states have used. The gate is the approved Tier 1 core list and the LETRS training requirement, which together produce a similar functional effect but through curriculum review rather than statutory prohibition.
• “Third-grade retention is automatic for students below benchmark.” The retention provision has been modified and delayed; current operational policy is set by ALSDE rather than by the original 2019 text. Districts should not assume a fixed retention rule without checking current guidance.
• “Any structured-literacy core counts.” K-3 core adoptions must come from the ALSDE Tier 1 list specifically. A program that is structured-literacy-aligned but not on the list does not satisfy the core requirement, although it may still be procurable as a supplement.
• “LETRS is optional if our teachers already have a reading credential.” Alabama requires LETRS or an ALSDE-approved equivalent. Existing reading endorsements do not automatically substitute. Districts should confirm equivalency status with ALSDE rather than assume a prior credential covers the requirement.

Being clear on these four points up front tends to make vendor conversations more productive, because the committee and the vendor are operating from the same description of the policy environment rather than past one another.

A note on assessment-driven decisions

Universal screening data is meant to inform Reading Improvement Plan decisions, but the path from screener output to instructional change is not automatic. Many Alabama districts have invested heavily in the screening side of the Literacy Act framework without an equivalent investment in the intervention and progress-monitoring side, which produces a familiar pattern: a building has clean fall, winter, and spring screening data but unclear documentation of what changed between screening windows for the students flagged as below benchmark.

The corrective is not more screening — it is sharper alignment between the screening signal and the instructional response. A student flagged as below benchmark on a phonemic awareness composite needs a different intervention than a student flagged on a fluency composite, and that distinction has to live somewhere in the RIP documentation and in the actual instructional minutes a teacher spends with the student. Products that produce screening-compatible diagnostic detail — not just a level or a benchmark category — give teachers a clearer line from screening to instruction than a generic “below benchmark” flag does.

This is one of the structural reasons Storytime emphasizes detailed decoding and ORF data over a single composite score: the diagnostic specificity is what an LETRS-trained teacher needs to design the actual intervention, and what an ARI coach needs to evaluate whether the intervention is working.

Common implementation challenges

Three issues come up repeatedly as Alabama districts implement the Literacy Act framework. None of them are insurmountable, but each requires a deliberate operational answer rather than an assumption that the core curriculum alone will resolve it.

1. Phonics scope-and-sequence alignment for decodable text. ALSDE-approved Tier 1 cores have specific lesson orders, and the orders differ from program to program. Most decodable book libraries are level-tagged (Decodable Level B, Level 2) but not lesson-tagged to a specific core scope and sequence.

The result is that teachers spend significant time hunting for books that match the specific lesson a student is on. A Level B book that fits one program’s phonics order may be misaligned with the order another program is teaching, even though both are on the ALSDE Tier 1 list.

When a teacher cannot find lesson-aligned decodable text quickly, the default fallback is often a generic leveled reader — which can quietly reintroduce the picture-cue and predictable-text patterns the structured-literacy framework is designed to move away from. Storytime’s decodable library + on-demand generation addresses this directly by cross-tagging books to multiple scope-and-sequence maps and generating lesson-specific text when the existing library does not cover a particular phoneme-grapheme correspondence at the right point in the order.

2. ORF data for Reading Improvement Plans. RIPs require ongoing progress monitoring. ORF (oral reading fluency) data is the standard measure, but capturing it at scale in a classroom is operationally hard. A teacher pulling individual students aside for one-on-one timed readings is a meaningful drain on small-group instructional time, particularly in classrooms where multiple students are on RIPs.

The other operational issue is that hand-captured ORF data tends to be inconsistent across teachers — different counting conventions, different prosody judgments, different passage choices — which makes the RIP documentation harder for ARI coaches to interpret across a building or district.

Storytime’s ORF assessment lets every student record reading passages weekly with automatic WCPM and prosody scoring. The data is consistent across teachers because it is produced by the same scoring pipeline, and it sits in the same student record alongside the rest of the literacy data — which is the kind of running record evidence ARI coaches expect to see in RIP documentation and that audit reviews ask for.

3. Differentiation without leaving the published scope. LETRS-trained teachers anchor every classroom to a published scope and sequence, which is the point of the training. But student variation within a classroom is large, and RIP-eligible students by definition need a different trajectory than the whole-group lesson is providing.

The tension is that a teacher who deviates from the published scope to meet an individual student’s needs may end up off-pace with the rest of the class, which has its own consequences. A teacher who stays on-pace may miss the individual student’s need entirely. Neither outcome serves the student well.

Storytime’s customizable phonics curriculum layer gives teachers per-student journey overrides without breaking the class baseline. The class can stay on the published scope; the individual student can practice the prerequisite or advanced skill independently through the digital practice layer; and the RIP documentation captures the differentiation without requiring the teacher to manually reconstruct it from instructional logs.

How the components fit together

For a district leader reading this page, the cleanest way to organize the Alabama framework is by what each component does.

The Literacy Act is the legal anchor — it establishes what is required. The ALSDE Tier 1 core list is the curriculum gate — it determines what cores can satisfy the requirement. LETRS is the teacher knowledge layer — it ensures the educators delivering instruction understand the underlying science. ARI is the implementation support — it provides the coaching and technical assistance districts need to put the framework into practice. Local Literacy Plans are the accountability mechanism — they document how each district is meeting the requirements.

This stack works only when all five components are operationally aligned. A district with a Tier 1 core but no LETRS-trained teachers will struggle to implement the curriculum as designed. A district with LETRS-trained teachers but no current Local Literacy Plan will have alignment gaps in how the framework is documented. A district with strong ARI coaching but no clear data on RIP progress will have a hard time demonstrating impact.

For procurement decisions, the implication is that a literacy product should be able to articulate how it supports each of these components — or should be clear about which it does not support. A practice and assessment layer like Storytime does not replace the core curriculum or the LETRS training, but it does directly support universal screening, Reading Improvement Plan progress monitoring, and the differentiation that LETRS-trained teachers need to apply across diverse classrooms.

There is also a budgeting consequence worth naming. Districts that approach the Literacy Act framework as five separate purchases — a core, a screener, a LETRS subscription, a coaching contract, and a documentation system — often end up with components that do not talk to each other. The screener data sits in one system; the RIP documentation lives in another; the intervention minutes are logged in a third; the LETRS coursework completion is tracked in a fourth.

Approaching the framework as an integrated stack, where the practice and assessment layer ties the components together at the student-record level, reduces the operational friction and the documentation overhead. It also tends to surface compliance gaps earlier than a separated-systems approach does, because the data is visible in a single place rather than scattered across vendor portals that have to be reconciled by hand.

Storytime in an Alabama district stack

Storytime is positioned as the digital practice + assessment layer on top of whichever ALSDE-approved Tier 1 core an Alabama district has adopted.

The product is not a core replacement and does not seek inclusion on the Tier 1 list. Instead, it cross-tags 2,000+ decodable books and ORF passages to the scope-and-sequence of multiple cores simultaneously, supports the WCPM and prosody measurement that Reading Improvement Plan progress monitoring requires, and exposes per-student differentiation capability that LETRS-trained teachers can use without breaking the class baseline.

For Alabama districts navigating the Literacy Act framework, the practical benefit is that the same Storytime deployment supports whichever Tier 1 core the district has chosen — and continues to work if the district moves to a different Tier 1 core in a future adoption cycle. The cross-tagging is the architectural decision that makes this possible: the practice layer is not locked to a single scope and sequence, so the district’s core decision and the district’s practice-and-assessment decision can be evaluated independently rather than as a single bundled choice.

That separation matters in a state where the Tier 1 list is periodically updated and individual programs sometimes leave or join the roster. A district that locked its practice library to a single core would be exposed if that core were ever removed from the list or significantly revised; cross-tagged tooling reduces that risk.

What to ask your vendor

Whether an Alabama district is in the early stages of Literacy Act implementation or several years into it, the same set of vendor questions tends to surface the right information quickly:

• “Which ALSDE-approved Tier 1 cores does your scope-and-sequence cross-tag to?” If the answer is a single core, the district is locked to that program. If the answer is several, the district has flexibility across future adoption cycles.
• “What ORF measure do you produce, and is it compatible with our existing universal screener?” WCPM is the most portable answer. A proprietary metric that does not translate to WCPM creates documentation friction inside RIPs.
• “How does your product support the LETRS-trained teacher’s instructional model?” The honest answer should reference phoneme-grapheme correspondence ordering, orthographic mapping, and decoding-first text — the same vocabulary the LETRS-trained teacher uses.
• “What ESSA evidence tier do you carry, and what does the rationale document look like?” Tier claims should be backed by published evidence rationale, not just a marketing badge.
• “How does the product document differentiation inside an RIP without breaking the class baseline?” The answer should describe per-student journey or pathway capability with audit-ready logging.

A vendor who can answer these five questions cleanly is operating in the same policy frame as the district. A vendor who deflects on any of them is worth a closer look before procurement.

Where to go next

If you are a district leader evaluating literacy products in Alabama, the most useful next steps are typically: pull the current ALSDE Tier 1 Core Reading Program list, confirm the LETRS status of K-3 teachers building by building, audit the current RIP documentation against ALSDE expectations, and identify the practice and assessment layer gaps that the chosen core does not cover on its own. Storytime is built to fit into that final step regardless of which Tier 1 core the earlier steps point to.

For districts in the middle of an adoption cycle, sequencing matters. The Tier 1 core decision is the anchor and should be settled before the practice and assessment layer is finalized, because the practice layer needs to fit alongside the core rather than dictate to it. The screener decision and the LETRS rollout can run in parallel with the core adoption, but the RIP documentation system should not be finalized until the screening and progress-monitoring data the district will actually use is clear. Out-of-sequence procurement is the most common source of integration regret in Literacy Act implementation, and the cost of redoing the integration after the fact is usually larger than the cost of waiting for the prior decisions to land.

District leaders should also keep an eye on what could change at the state level. The retention provision has moved more than once since 2019, and future legislative sessions could revisit either retention rules or the broader framework. Procurement decisions made today should be resilient to those changes — which is part of why a cross-tagged practice and assessment layer, independent of any single core, is a sturdier bet than a deeply-coupled core-plus-practice bundle that would have to be unwound if the underlying core decision were revisited.

The other change worth watching is the LETRS equivalency landscape. As more teachers complete LETRS and as alternative pathways for Science of Reading credentialing mature, ALSDE may broaden the set of acceptable equivalents. A district that has standardized on LETRS as the only acceptable training is well-positioned today, but should be open to recognizing equivalent credentials if ALSDE guidance evolves that way.