The Mouse That Scored Readworks Answer Key

Getting Readworks Answer Keys Without the Headache

I spent about three weeks dealing with Readworks answer key extraction before I found anything that actually worked reliably. The standard approach most teachers try is manually scrolling through each passage and copying answers by hand. That takes roughly forty-five minutes for a full unit. Not great when you have thirty students and five units per marking period. This is a user-script approach that automates pulling answers from Readworks assignments. The core concept is straightforward: you load a Readworks assignment page, the script runs through the DOM and extracts the correct answer values, then formats them into a readable table or CSV. It works on Chrome and Firefox with Tampermonkey or Violentmonkey installed. The actual script I use is hosted on a couple of GitHub gists and userscripts.org mirrors. I keep my own forked copy because the public versions tend to break when Readworks pushes a platform update, which happens about every six to eight weeks. My fork includes a version check that alerts you when the page structure has shifted enough to require a patch.

Here is the practical workflow. Install the browser extension first. Then open the Readworks assignment you want to pull answers from. Make sure you are logged into your teacher account. Refresh the page after installing the script. You will see a new button appear in the upper right corner of the assignment panel labeled something like "Export Answers." Click it. The script scans the page for the correct answer fields, compacts them into a spreadsheet-ready format, and offers a download. The whole process takes about two minutes for a twenty-question assignment. I have timed it. The main limitation is that the script only works on individual assignment pages, not on the Readworks resource library search results. If you are trying to pull answers for fifty different passages at once, you need to visit each one separately. It adds up. I built a simple loop script that handles this, but it requires you to have the direct URLs pre-loaded in a text file. I paste the URLs, run the loop, and it cycles through automatically with a three-second delay between requests to avoid triggering Readworks rate limits. That part usually takes about eight minutes for fifty assignments. I ran into a specific edge case last semester that took me two days to resolve. A particular Readworks passage had embedded interactive questions where the answer was stored in a data attribute rather than a standard DOM element. The script was returning null values for those questions. I opened the browser developer console, inspected the question elements, and found the answer was buried in a data-answer-key attribute inside a script tag that loaded asynchronously. I patched my forked script to wait for that attribute to populate before attempting extraction. Added a fifty-millisecond delay and a fallback check. Worked immediately after. I pushed the fix to my repository.

Another thing people miss: the script does not handle Readworks premium content that requires a district-level license key to unlock. If a passage is locked behind a paywall even for your district, the script will throw an access denied error and skip that item. It does not fail silently, which is good. You get a clear log of which assignments were skipped and why. There is also the question of academic integrity. I do not pretend this tool is appropriate for every classroom situation. Using extracted answer keys to let students bypass the reading assignments entirely is poor pedagogy. What this tool is actually useful for is time management. I use it to generate answer sheets so I can quickly grade student submissions, spot common misconceptions, and identify which questions had the lowest accuracy rates across my class. The granularity of the exported data lets me filter by question number and see distribution patterns in seconds rather than flipping through thirty printed copies. If the script approach does not fit your workflow, the alternative is using Readworks built-in analytics dashboard. It generates answer statistics automatically for every assignment, but the export function is limited to CSV format and does not include the question text alongside the answer key. That means you cannot easily cross-reference without manually matching question numbers. The script method gives you both fields in one pass. Depending on how often you grade, this difference can save you between fifteen and thirty minutes per unit.

I keep my modified script at a public GitHub repository. The original unmodified versions circulate on various educator forums, but they go stale quickly. The fork I maintain includes the async attribute fix and the URL loop functionality. Both are documented in the README. Readworks terms of service technically prohibit automated scraping, so I would suggest using this tool responsibly and only on assignments your district has already licensed for your classroom use.