A student can have a strong IEP, a well-run evaluation, and a dedicated team behind them, and still show up wrong in Wisconsin’s state data. When a record is missing, submitted from the wrong system, or flagged with an error, the district’s compliance picture changes, even if the work in the classroom was done right.
For special education directors and data coordinators, WISEdata reporting is where daily practice becomes official record. It shapes Indicator 11 compliance results, school and district report cards, and the counts that inform funding. Getting it right means knowing which records DPI expects, which system sends each one, and where submissions most often break down.
This guide walks through each piece, from the WISEid to the three special education records, so your team can submit clean data with fewer surprises.
Why Wisconsin DPI Collects Special Education Data
The Wisconsin Department of Public Instruction (DPI) collects individual student and aggregated data to meet school, district, state, and federal reporting mandates. That data informs educational research, supports funding allocations, and feeds the school and district report cards required by state law.
DPI also provides dashboards and reporting tools so teachers, administrators, families, and researchers can use the data to improve outcomes for Wisconsin students. At the local level, districts can use the same data for future planning.
💡 Takeaway for school districts:
WISEdata is DPI’s statewide data collection system. Districts send student records to WISEdata through their student information system (SIS) and approved vendor software, and DPI uses those records for state and federal reporting.
The WISEid: Where Every Record Starts
Every student reported to DPI needs a WISEid, a unique, permanent 10-digit state student identifier. For special education, the rule is broader than many teams expect: every referred child needs a WISEid, whether or not they are evaluated and whether or not they qualify for services.
This matters most for children who are not enrolled in the evaluating district. The education organization that conducts the evaluation assigns the WISEid, and DPI is clear that districts should not delete a WISEid when a student is found not eligible.
The Three Special Education Records in WISEdata
Wisconsin’s special education reporting runs on three connected records. Each one has a distinct job, and each one depends on the record before it.
The Wisconsin DPI will assign each student a WISEid. The WISEid is also referred to as the State Student ID. This is a unique, permanent, and unduplicated way to identify a student. This 10-digit numeric field is required for all reported students and for educators.
GoIDEA is certified by the Wisconsin DPI to transfer Special Education and Initial Evaluation related data to WISEdata on a nightly basis. The record types submitted to DPI are called sSEPA and sSEPEA records.
- sSEPA = student Special Education Program Association (Special Education Record)
- sSEPEA = student Special Education Program Eligibility Association (Initial Evaluation Record)
SEORA: The Responsibility Record
Some children being evaluated are not enrolled in the school conducting the evaluation. Common examples include children below compulsory school age, students parentally placed in private schools, and children receiving home-based education. Because enrollment records can only be created for students ages 3 to 21, these children need a different record to anchor their data.
That record is the Student Education Organization Responsibility Association, or SEORA. According to DPI’s guidance on the SEORA and Indicator 11 reporting, the SEORA must be submitted from the primary SIS, and it must be in place before any evaluation data can be sent. Once the child enrolls, the enrollment record replaces the SEORA.
A SEORA includes:
• Begin Date (typically the Consent to Evaluate Received Date)
• Education Organization ID (the School ID)
• Student Unique ID (the WISEid)
• Responsibility Descriptor (“SPED Initial Evaluation”)
• End Date
sSEPEA: The Initial Evaluation Record
The Student Special Education Program Eligibility Association (sSEPEA) holds most of the data for Indicator 11, Wisconsin’s measure of timely initial evaluations. Every initial evaluation where parental consent was received must be reported, including students found not eligible and those whose parents declined services.
Without an sSEPEA, a student will not appear in DPI’s Indicator 11 reporting. The record stays in WISEdata under “SPED Initial Evaluation Details” whether or not the student is ever enrolled or served.
Key sSEPEA data elements include:
• Consent Received Date
• Evaluation Type
• Determination Date
• Evaluation Completed Status
• Evaluation Delay Reason or Evaluation Late Reason
• IDEA Indicator
sSEPA: The Special Education Services Record
When a student is found IDEA-eligible, DPI expects a Student Special Education Program Association (sSEPA) record. An IDEA-eligible student must meet all of the following:
• Be age 3 to 21 and not yet graduated with a regular high school diploma
• Have an impairment that requires special education and related servicesRelated Services Support services (such as speech therapy, occupational therapy, or transportation) that are required to assist a child with a disability in benefiting from their educational program., as determined by a current evaluation and a current IEP (or a services plan for parentally placed private school students)
• Be attending and receiving all services specified in the IEP or services plan
• Be receiving a free appropriate public education (FAPE), or be a parentally placed private school student receiving services under a services plan (34 CFR 300.452–300.462)
DPI’s current special education program association record also captures residential care center (RCC) placement and shortened school day details, alongside long-standing fields such as IEP begin and end dates, October 1 Child Count inclusion, educational environment, disability, FAPE-responsible school and district, last evaluation date, and exit reason.
💡 Takeaway for school districts:
Think of the three records as a sequence: SEORA anchors unenrolled children, sSEPEA documents the evaluation, and sSEPA documents services. A gap early in the chain blocks everything after it, so most “missing data” problems start with a missing WISEid or responsibility record.
Indicator 11 and the 60-Day Evaluation Timeline
Wisconsin must report the percentage of children evaluated within 60 days of receiving parental consent for an initial evaluation. Evaluations that miss the timeline count as noncompliance unless an allowable exception applies.
When an evaluation is delayed or late, the sSEPEA must explain why using one of two fields, and only one can be submitted:
• Evaluation Delay Reason: a coded value explaining why the evaluation did not take place or was not completed
• Evaluation Late Reason: free text describing the specific situation
Indicator 11 data is collected as part of Year-End data in DPI’s December Student Snapshot. That gives districts a window to correct errors, but only if someone is reviewing the data well before the snapshot closes.
Who Submits What: SIS vs. Special Education Software
One of the most common sources of WISEdata errors is confusion over which system sends which record. Here’s how each record reaches WISEdata:
| Record | Purpose | Submitted from |
|---|---|---|
| sSA (enrollment) | Student enrollment | Primary SIS |
| SEORA | Responsibility for unenrolled children being evaluated | Primary SIS |
| sSEPEA | Initial evaluation (Indicator 11) | Special education vendor, if the district uses one |
| sSEPA | Special education services | Primary SIS, or a DPI-certified special education vendor such as GoIDEA |
The order matters. If your district uses dedicated IEP software for special education records, that system cannot send Indicator 11 data until the SIS has submitted either an enrollment record or a SEORA. When data entered in one system isn’t reaching DPI, districts need to work with that system’s vendor support team to resolve the flow.
A District Checklist for Clean WISEdata Submissions
DPI’s special education data reporting FAQ covers many edge cases. These are the checks that prevent the most common errors:
1. Assign a WISEid at referral. Include children referred from Birth to 3 programs, and never delete a WISEid if the child doesn’t qualify.
2. Submit the SEORA or enrollment record first. Evaluation data cannot post without one.
3. Report every consented initial evaluation. Include students found not eligible and those whose parents declined services.
4. Document delays with one reason field. Use either the Evaluation Delay Reason or the Evaluation Late Reason, not both.
5. Complete FAPE fields on every sSEPA. Paying tuition or holding a cooperative agreement does not transfer FAPE accountability; the resident district keeps it.
6. Set sSEPA dates carefully. Begin the sSEPA on the first day of services under the current IEP or the first day of school, whichever is more recent, and don’t end it on June 30. An sSEPA that begins after October 1 will leave the student out of the October 1 Child Count, Wisconsin’s annual federal count of students receiving special education services.
7. Hold summer IEPs until enrollment exists. Submitting a new sSEPA before the upcoming year’s enrollment is created can trigger errors.
8. Review before the December snapshot. Year-End data, including Indicator 11, is locked in with that collection.
GoIDEA Process
Each weeknight, a process runs in GoIDEA to check for changes in Special Education or Initial Evaluation data. If a change is found, a new record is added or modified in WISEdata. For example, if a student is exited from special education, the exit date and reason are updated on the sSEPA record in WISEdata.
The district’s Student Information System vendor is still responsible for uploading the sSA enrollment record and data related to the Third Friday Count. Additionally, SIS vendors can download sSEPA information from WISEdata that GoIDEA has uploaded. Skyward, PowerSchool, and Infinite Campus currently have this functionality. Downloading sSEPA information from WISEdata eliminates the need for double entry into a district’s Student Information System.
GoIDEA meets with DPI on the fourth Tuesday of each month to cover WISEdata topics and Wisconsin DPI special education updates. DPI hosts these meetings and posts the meeting notes.
This service is an add-on module with an open enrollment period of July 1 to August 15 for the upcoming school year. The first step is to sign an agreement with GoIDEA. Next, the district will need to give GoIDEA permission to sync with WISEdata. Then, the GoIDEA Development Team will set up the networking. Training will be set up with the district to explain how to enter data into GoIDEA and how to correct WISEdata errors within the software. Reach out to our sales team to receive a quote for this service.
Looking for a simpler way to manage IEPs?
GoIDEA helps your staff save time with user-friendly tools, built-in compliance checks, and seamless integration with Medicaid billing — so you can write accurate IEPs faster and avoid duplicate data entry.
Latest Posts
