Evidence selection
Whether students choose text evidence because it supports the claim, not because it feels related.
WhyDive™ Reading
Students can cite the text and still overclaim what it proves.
WhyDive Reading is the developing reading branch of the WhyDive assessment system, built to help districts see whether students can keep claims inside the evidence.
WhyDive Reading At A Glance
A developing diagnostic branch for textual evidence and inference discipline.
Many students can cite a text and still claim more than the text proves. WhyDive Reading is being developed to help districts see whether student claims stay inside the evidence.
Request a Reading Conversation- Who This Is For
- District leaders thinking beyond reading scores
- Curriculum and literacy teams reviewing evidence use
- Assessment teams interested in the next WhyDive diagnostic branch
- The Problem
- Reading performance can hide whether students selected evidence because it truly supports a claim or because it merely sounds related.
- Cost Of Inaction
- If districts cannot see the reasoning boundary, they may treat inference errors as generic comprehension problems and miss the specific move students need to repair.
- The Insight
- Reading and chart interpretation share a deeper reasoning question: what does the evidence authorize, and where does the student go beyond it?
- The Solution
- WhyDive Reading applies the same bounded-reasoning framework to textual evidence, inference boundaries, claim discipline, and repairable reasoning patterns.
How It Works
- 1Identify the claim students are being asked to make from a text.
- 2Check whether selected evidence actually authorizes that claim.
- 3Locate where inference becomes unsupported interpretation.
- 4Report the reasoning move that would make the response stronger.
Proof
- The WhyDive framework already defines the shared reasoning engine.
- WhyDive Charts demonstrates how a domain branch can make hidden reasoning visible.
- Reading uses the same authorization, boundary, and repair logic in a textual domain.
Reframed Decision
The question is not only whether students comprehend a passage. It is whether they can keep their claims inside what the text supports.
The Reading Problem Beneath The Score
Reading performance can hide whether students know what the text actually supports.
Students may locate relevant words, select plausible evidence, or write fluent responses while still making claims the text does not authorize. WhyDive Reading will focus on that reasoning layer.
Inference boundaries
Where students move from reasonable inference into unsupported interpretation.
Claim discipline
Whether students can keep a response aligned to what the text authorizes.
Repair needs
Which reasoning moves should be strengthened after the diagnostic evidence is visible.
Same Engine
The domain changes. The reasoning question remains.
Charts asks what the data can support. Reading asks what the text can support. In both cases, WhyDive looks for authorization, boundary discipline, and repairable reasoning patterns.
Input
What is the student being asked to interpret?
Authorization
What evidence gives the student permission to make a claim?
Boundary
Where does the evidence stop supporting the claim?
Repair
What reasoning move would make the response stronger?
District Decision
WhyDive Reading will become a branch of the same assessment system, not a separate product story.
Districts should be able to understand WhyDive the way they understand mature assessment systems: one system, multiple domains, shared reporting logic, and domain-specific diagnostics.