Help Center/ Assessment/ Understanding Subtest On Demand Assessments (SODAs)

Understanding Subtest On Demand Assessments (SODAs)

SODAs are short (5 to 7 minute), single-skill assessments used for frequent progress monitoring during intervention, they're assigned via the Growth Dashboard's ISIP Assess Status widget, results appear only in the Student Summary Report, and they complement (rather than replace) Benchmark and Progress Monitoring data.

5 min read · Updated 2026-08-12


A Subtest On-Demand Assessment (SODA) is a short, targeted formative assessment that measures a single reading skill in about 5 to 7 minutes. SODAs are designed for frequent progress monitoring during intervention, they're standalone, don't affect Benchmark or Progress Monitoring scores, and results appear only in the Student Summary Report.

 

What is a SODA?

A SODA is a fixed-form, adaptive assessment that targets one reading construct at a time, rather than the full assessment battery. Key characteristics:

  • Adaptive design, items adjust to the student's performance level, presenting content matched to where the student is actually reading rather than to a fixed grade level.
  • Single construct per SODA, each SODA measures one skill (e.g., phonics, fluency, comprehension).
  • Standalone and non-disruptive, SODA results don't overwrite or affect Benchmark or Progress Monitoring scores.
  • Same reporting metrics, subscores mirror the metrics used for full assessment scores, so a SODA score is generally consistent with the equivalent Benchmark subscore.

 

SODAs are supplemental tools. They're meant to complement, not replace, Benchmark and Progress Monitoring assessments, and shouldn't be used for high-stakes placement decisions or population-wide comparisons.

 

The seven SODA constructs

ConstructTasks assessedDuration
Alphabetic DecodingWord Identification, Pseudoword Identification~2 min
Letter KnowledgeLetter Names, Letter Sounds~2 min
Phonological AwarenessBlending~2 to 4 min
VocabularyOral Reading Fluency Passage, Receptive Vocabulary~1 to 2 min
SpellingSpelling~2 to 4 min
Fluency (Text Fluency / ORF)Oral Reading Fluency Passage (WCPM)~2 to 4 min
Reading ComprehensionOral Reading Fluency Passage, Comprehension Questions~2 min

 

Most SODAs target specific grade bands, but Amira makes these foundational subtests available up through 6th grade for students who still need foundational skill practice, the system adaptively delivers the highest-level content available for that student.

 

How to assign a SODA

View a step by step walkthrough for how to assign a SODA.

You'll need teacher-level access in Amira. SODAs are assigned from the Growth Dashboard, the same starting point used for full assessments:

  1. Access the Growth Dashboard and locate the ISIP Assess Status widget.
  2. Click the widget. A Student List panel opens, showing each student's current assessment status. Use the Testing Window dropdown to select the relevant period.
  3. Select the student(s) to assess, check individual students or the whole class, then click Schedule.
  4. Choose "Subtest Assessment" in the dialog box that appears (choosing "Full Assessment" instead would assign an ODA, not a SODA).
  5. Configure the setup screen, confirm the assignee(s), set the instructions language (the SODA content itself is English only).
  6. Select the target subtest or multiple subtests from the seven available constructs (Letter Knowledge, Phonological Awareness, Alphabetic Decoding, Vocabulary, Text Fluency, Reading Comprehension, or Spelling).
  7. Click Submit. The SODA will be delivered to the student's inbox on their next login and will expire at the start of the next assessment window.
  8. Confirm scheduling back on the Growth Dashboard, the ISIP Assess Status widget will show an updated status such as "SODA Scheduled."

 

Where to view SODA results

SODA results appear only in the Student Summary Report. See a walkthrough here. SODAs are excluded from district or state official reporting, they're intended purely as formative, teacher-level data.

 

When reviewing results, look for trends across multiple administrations rather than reacting to a single score. Consistent improvement over 4 to 8 weeks indicates the intervention is working; a flat or declining trend should prompt a review of instructional strategy for that skill.

 

SODAs vs. Progress Monitoring: which to use when

Benchmarks & Progress MonitoringSODAs
PurposeComprehensive progress monitoring / full assessmentTargeted, skill-specific progress monitoring
Time~20 minutes2 to 7 minutes
ContentFull assessment battery (all reading strands)Single reading skill/construct
Impacts Benchmark scores?Yes, a new Benchmark replaces the prior score in that window. Progress Monitoring Assessments do not impact Benchmark scores.No, standalone formative data only
Where results appearAll reports (Benchmark, Class Progress, Growth Dashboard, Admin)Student Summary Report only
Best used forUniversal screening, 3x/year Benchmarks, monthly progress monitoringMTSS/RTI progress checks, intervention documentation, instructional decision-making
Recommended frequencyMonthly / quarterlyWeekly / bi-weekly

 

Best practices for using SODAs

  • Match frequency to tier: Tier 2 students, weekly to bi-weekly; Tier 3 students, weekly; whole-class checks, monthly or as needed; short summer programs, once at the midpoint, bracketed by full pre/post assessments.
  • Align the construct to the intervention. Use Benchmark subscores or input from reading specialists to pick the SODA construct that matches what's actually being taught.
  • Build a consistent monitoring schedule. Regular, evenly spaced data points are far easier to interpret than sporadic ones, assign SODAs at the same point in each cycle.
  • Look for trends, not single scores. A single data point has limited meaning; track the same construct over several administrations.
  • Act on the trend. Upward trend → consider continuing (or reducing frequency of) the intervention. Flat trend → review instructional strategy. Declining trend → reassess student needs with specialists.
  • Avoid over-testing. SODAs are efficient, but they still use student time. Use the minimum frequency needed to make a confident instructional decision.
  • Reserve SODAs for targeted intervention, not universal screening. Not all students need SODAs, they're most valuable for Tier 2/3 students already receiving targeted support. Use Benchmarks or ODAs for whole-population screening.

 

Frequently asked questions

  1. How often can I use SODAs? As often as needed, they don't affect official scores. That said, use the minimum frequency necessary to avoid over-testing.
  2. Can I assign a SODA to multiple students at once? Yes, though consider whether all selected students genuinely share the same intervention need before assigning the same construct to a large group.
  3. Can SODA data be used for IEP documentation? Yes, SODA trend data can demonstrate a student's response to a targeted intervention.
  4. What happens if a SODA is interrupted? If a student logs out before finishing, they'll be prompted to complete it on their next login, resuming at the start of any incomplete task.

 

Related resources