Who this is for: New Jersey district test coordinators, data managers, and the people who maintain whatever spreadsheet or system consumes state assessment results each year.
When a district buys anything built to order, the first question is what it will actually receive. Not the approach, not the methodology — the list of things that get handed over. A statewide assessment is the most standardized purchase in public education, so the deliverables ought to be the easiest part to pin down. New Jersey did pin them down. Its own bid solicitation names them, one by one.
What that document does not do is say what shape they arrive in. And it is the shape, not the list, that every district workflow is built on.
The deliverables are specified, and the list is public
New Jersey procured its new assessment program through Request for Quotes #25-004, issued by NJDOE on October 15, 2024. Its contract terms define a deliverable plainly: "Goods, products, Services and Work Product that Contractor is required to deliver to the State under the Contract." Approving all of them falls to one named role, the State Contract Manager, or SCM.
Reporting is split into two cycles. For the first, the RFQ says:
"In the first phase, individual student reports for each assessment, student rosters, school and district roster summaries, and school and district summary reports along with a downloadable student level data file shall be released to school districts by a date approved by the SCM each year for the spring administration."
The second cycle adds aggregate score reports including federally required subgroups, summary reports by reporting category, an item analysis report, a State Summary Report, and a score interpretation manual — which "shall be made available on the Contractor's assessment website." There is a separate state summary downloadable data file, required to carry "at a minimum, the number and percent of General Education, Multilingual Learner (current and former), Special Education students, demographic categories, and other State and federally required student reporting categories."
So a district can already answer the first question. It gets individual student reports, rosters, roster summaries, school and district summaries, aggregate reports, an interpretation manual, and a downloadable student-level data file. That last one is the one that matters most and gets talked about least — the file behind every multi-year comparison, every subgroup breakdown, every "which schools moved" conversation in September. We have written before about how much sits in it and how rarely it gets opened.
What the contract does not specify is the format
Read the same document for the shape of those files and the specificity disappears. The section covering results data files — the ones delivered to the state — tells the contractor to "determine the format of these files, in conjunction with the SCM," and to "send the record layout to the SCM prior to the test administration."
Two things follow from those two lines.
First, the format was not fixed in advance. It is something the vendor and the state settle between them after award. A bidder reading the RFQ was not told to match an existing layout, and nothing in the document requires continuity with what districts received before.
Second, a record layout does exist, or will. Someone writes it, and it is due before the test is even administered. But every mention of a record layout in the RFQ points the same way: to the SCM. The phrase appears three times, and all three are deliveries to the state — the results data files, the pupil score CDs, the school and district summary. The district-facing downloadable student-level data file is named as a deliverable and given a release timeline, and then no layout, data dictionary, or field list is required for it anywhere in the document.
That is the actual gap. It is not that nobody wrote down what the file looks like. It is that the description was contracted to travel to Trenton, and nothing obliges anyone to forward it to the people who have to open the file.
The RFQ's own reference samples belong to the outgoing vendor
Where the RFQ needed to show a bidder what New Jersey's reports look like, it linked to the incumbent's materials: report samples on the previous vendor's educator support site, and the Spring 2022 NJSLA Score Interpretation Guide. That was reasonable — those were the reports in existence when the document was written in 2024.
It is worth being careful about what that does and does not mean. Pointing a bidder at existing samples set a reference standard for the quote. It is not a published commitment that the deliverables a district opens in 2027 will resemble them. Those are different things, and only the first one happened.
What has been published to districts since the award
NJDOE has published what the reports will contain. The NJSLA-Adaptive FAQ says student score reports will provide "information about an individual student's performance, including overall achievement levels, scale scores, reporting category performance, growth (when available), and comparisons to school, district, and state averages," and that aggregate reports will summarize results by group.
That is a description of content. It is not a description of delivery.
Timing is documented better than format. NJDOE's July 2026 standard-setting presentation says Fall 2026 NJGPA-Adaptive results are "anticipated to be returned to districts before winter break," and Spring 2027 NJSLA-Adaptive results are "anticipated to be provided to districts by June 30, 2027 — this represents results being delivered almost two months earlier than prior years." It also notes that results follow a student across district transfers and that districts can roster students over the summer.
So a district knows what it is owed and roughly when it arrives. What it does not know is what shape the thing arriving will be in.
Checked on 2026-08-20, across the three public pages a district would actually look at — the assessment homepage, the NJSLA-Adaptive landing page and the FAQ — none of the following appears anywhere: data file, CSV, file layout, student data file, download, or score interpretation guide. The score interpretation manual the contract requires is not yet posted where a district would find it.
The state has already answered this exact question once
It answered it for the other direction. When the vendor change was announced in August 2025, districts wanted to know whether their existing file plumbing would survive it. NJDOE answered directly, in a State Assessment Vendor Update on the NJSLEDS site:
"At this time, the shift to a new vendor does not affect the structure of State Assessment Registration (SAR) submissions in NJSLEDS. All districts should continue to use the existing SAR submission templates and guidance. No changes have been made to the file layout, required data elements, or validation rules."
Notice how specific that is. It names the file layout, the required data elements, and the validation rules, because someone on the state side understood exactly which details a district has to have pinned down before it can plan. That is the standard. It exists, it has been met once, and the deliverables coming back have no equivalent.
Why this matters this year rather than any year
None of this means the file is changing. It may well arrive looking much as it always has. The point is narrower: a district cannot currently tell, and the season for finding out is short.
Three things make the uncertainty concrete rather than theoretical.
The vendor changed. File formats are vendor artifacts. A new vendor's reporting platform exports what that platform exports, and continuity is a decision someone has to make and publish, not a default. The RFQ left that decision to be made after award, which means it was made somewhere and simply has not been announced.
The scale changed. The performance levels are being newly set, and NJSLA-Adaptive reports five levels for ELA and mathematics while NJGPA-Adaptive reports two — Graduation Ready and Not Yet Graduation Ready. Any file that carries a level column now carries a different set of values than the file that carried it before, whatever the column is named.
Column names already drift between years even without a vendor change. That is not speculation; it is the problem we have already written up, where a field holding performance level in one year's export is labeled differently in another. A vendor transition is exactly the kind of event that makes it more likely, not less.
What to do about it now
Write down what you currently consume. Not "we get the NJSLA file" — the actual list: which columns feed which report, which ones a formula or a script depends on by name, which ones a person retypes by hand every year. Most districts have never written this down, and the year a format changes is the worst possible time to reconstruct it from memory.
Separate reading from processing. The fixed reports and the raw file fail differently. A report that looks different is an inconvenience for the person reading it. A file whose columns moved is a broken workflow, and it breaks silently — a lookup that returns blanks looks like missing students rather than a renamed header.
Ask for named deliverables, in writing, before results season. This is the part the contract makes easier, because the things to ask for have names in it. Will the downloadable student-level data file released to districts keep the same layout and field names as prior years? Will the record layout be published to districts, and not only submitted to the State Contract Manager? When will the score interpretation manual be posted, given that the contract requires it on the contractor's website? Those are requests for documents the state has already required someone to produce.
Plan for a mapping step regardless. Assume you will need to align this year's columns to last year's at least once. Budget an afternoon for it in September rather than discovering it in the middle of a board-report deadline.
New Jersey did the hard part. It specified the deliverables, named them individually, and required a record layout to be written before students ever sit down to test. The remaining step is small by comparison: publish that layout to the districts that have to open the file. Districts do not need a promise that nothing changed. They need to know which it is, early enough to do something about it.