For California K–12 districts
One export from SEIS or SIRAS shows every open assessment by practitioner and by school site, with the 60-day clock counted from each consent date.
And on every page, a plain account of what your export could not tell it.
No data entry from the team.
Request a walkthroughOr call: 951.533.4540
SEIS shows initial evaluations with case manager, consent date, and days until overdue. It is a good screen, and it stops in three places.
It calculates only if your team enters the assessment plan data, and that does not happen consistently in every district.
It reads “Webb, Marcus” and “Webb, M.” as two people, which splits one caseload in half and makes both halves look plausible.
And it will not tell you which of those is happening to your numbers right now.
01
Pull your standard report out of SEIS or SIRAS. Nothing new to install, nothing for practitioners to fill in.
02
Confirm which column is which. CANDOR suggests matches; nothing applies automatically.
03
Open assessments by practitioner and by school site, with the 60-day clock counted from each consent date.
Every figure CANDOR produces comes from one export. So every page also lists the places that export was silent, and the things CANDOR read but does not count.
How many rows had no consent date, so no clock could start. In one district’s file that was 377 of 537.
How many practitioner names matched nobody on your roster, and how many cases they carry.
Which school names matched no site in your district.
And how many evaluations finished more than 60 calendar days after consent. Those cases are closed, so they appear in no other figure on the page. Indicator 11 counts every one as late. In that same district, 18.
A number you can defend is worth more than a number that looks complete.
Never ranks
It never ranks, scores, or normalizes practitioners against each other. No leaderboards, no productivity comparisons, no FTE denominators. Counts in context.
Never stores identity
It never stores student names, dates of birth, or SSIDs. Identity columns lock at mapping and are never rendered.
Never fails quietly
It never drops a row that carries data. When a row can’t be written, CANDOR counts it and names the field that caused it. When a consent date is missing or unreadable, the row still writes and the page says how many rows have no clock rather than pretending the count is complete.
Nothing asked of staff
It requires nothing from your practitioners. No accounts, no data entry, no new workflow.
Special education directors kept describing the same problem. CANDOR is what came out of trying to solve it.
Built by a California school psychologist in his fourteenth year, and shaped by the directors and coordinators who said what their reports were missing. It comes from someone who has sat in the meetings, not from a vendor who read about them.
No. It reads an export from your existing system. It does not connect to it, write to it, or replace it. Your state system remains the system of record.
California requires an initial evaluation within 60 calendar days of parental consent. CANDOR counts calendar days from each consent date in your export. It does not exclude school breaks, so its number is elapsed calendar days rather than an adjusted statutory deadline.
No. CANDOR is sold to district administrators and read by district administrators. Practitioners have no accounts, enter nothing, and never see it. One administrator login is the entire footprint.
A student record identifier from your own export, school of attendance, plan type, case manager, and case dates. Student names, dates of birth, and SSIDs lock at mapping and cannot be imported.
One export from the system you already use, and about thirty minutes of conversation a month during the pilot. Nothing to install, nothing for practitioners to enter, and no district funds committed.
“Does this handle X in our SELPA” is a good place to start.
One California district has signed for fall 2026. One pilot spot remains.