A counselor gets a call from a parent. Their child's grades have dropped over the last two months, they've missed six days of school in the past three weeks, and the parent wants to know what's being done about it. Reasonable question. The counselor wants to give a good answer.
Here's what happens next: the counselor opens the SIS to check the attendance record. Then they switch to the assessment platform to look at the most recent diagnostic scores. Then the discipline system to see if there have been any referrals. Then the intervention tracker to check whether the student is receiving any MTSS supports. That's four systems, four logins, four different interfaces. On a good day, pulling that information together takes 15 minutes. On a bad day — when a password has expired, or the assessment platform is running slowly, or the intervention notes are filed under a different student ID — it takes longer.
By the time the counselor has the full picture, the parent has been waiting. And the meeting hasn't even started yet.
One Student, One Screen
Starting today, Student Snapshot is available to every Arcline district. Type any student's name and see their complete profile in a single view — attendance history, assessment trends, discipline records, active interventions, demographic information, and teacher notes. All of it pulled from the district's connected systems. All of it updated in real time.
There's no export to run. No report to request from the data team. No cross-referencing between tabs. The data is already there, already reconciled, already organized around the student.
What's in a Snapshot
Student Snapshot organizes information into five sections, each drawing from the district's source systems automatically:
- Attendance. A trend line for the current school year showing daily attendance alongside the school and district averages. Students who have crossed the chronic absenteeism threshold — missing 10% or more of enrolled days — are flagged automatically. The view also surfaces patterns: is the student missing Mondays more than other days? Did absences spike after a specific date?
- Academics. Assessment scores over time, across every connected platform — whether the district uses iReady, NWEA MAP, state assessments, or all three. Grade trends from the SIS are shown alongside diagnostic results so you can see both the classroom picture and the standardized picture in one place. Proficiency status is displayed using each assessment's own benchmarks.
- Behavior. Discipline incidents, office referrals, and suspensions in chronological order. For districts tracking restorative justice participation, those records appear here too. The goal isn't surveillance — it's context. A spike in referrals after winter break tells a different story than a single isolated incident in September.
- Supports. The student's current MTSS tier, every active intervention with start dates and assigned staff, and counselor contact history. If a student was moved from Tier 1 to Tier 2 three weeks ago, that's visible. If a reading intervention was started and then discontinued, that shows up too. The record of what's been tried matters as much as what's in place now.
- Demographics. Grade level, school, enrollment date, and program participation — Title I, IEP, 504, English Language Learner, gifted, McKinney-Vento. This section is reference information, but it's often the first thing someone needs to confirm before a meeting or a phone call.
Who Sees What
Every person who interacts with student data has a different scope of responsibility, and Student Snapshot respects that. Access follows the district's existing role-based permissions. A classroom teacher sees snapshots for the students on their roster. A principal sees students in their building. A counselor sees their assigned caseload. A district administrator sees across schools.
Nobody sees more than their role requires. A teacher pulling up a student's snapshot won't see discipline records from a previous school unless the district's RBAC policy grants that access. A principal can't view students at a different building. The permissions aren't configured separately in Arcline — they inherit directly from the roles already defined in the district's SIS and identity provider.
This matters because the value of putting all student data in one place depends entirely on trusting that the right people — and only the right people — can see it. FERPA compliance isn't a feature we tacked on. It's the foundation the entire feature is built on.
What We Heard During the Pilot
We tested Student Snapshot with three districts over the fall semester. The feedback that stuck with us most came from the counselors.
"I used to spend my first 20 minutes with a family just pulling up records. Now I walk into the meeting already knowing the full picture. I can actually spend that time talking with the parent about their kid instead of typing passwords."
— Middle school counselor, pilot district
That 20 minutes matters more than it sounds. A counselor with a caseload of 400 students — which is close to the national average — might have six parent meetings in a week. If each one starts with 15 to 20 minutes of pulling records, that's nearly two hours a week spent on data retrieval that contributes nothing to the actual conversation. Over a school year, it adds up to more than 70 hours. That's time that could be spent with students.
Teachers in the pilot told us something similar. When a student is struggling, the first step is understanding what's already happening — what supports are in place, what the attendance pattern looks like, whether the assessment data shows a skill gap or something broader. Before Student Snapshot, gathering that context meant emailing the counselor, checking with the front office, and hoping someone had the intervention records up to date. Now it takes about 30 seconds.
Built on the Data Layer
Student Snapshot works because of the unified data layer underneath it. Attendance from Infinite Campus, assessment results from iReady, discipline records from the SIS, intervention tracking from the MTSS platform — all of it is already normalized into a single schema by the time it reaches the snapshot view. We don't query four systems in real time and stitch the results together on the fly. The data is already unified. The snapshot is just the interface.
This also means that when a district adds a new data source — say they adopt a new behavior tracking system mid-year — Student Snapshot picks it up automatically once the source is connected. No configuration changes, no new setup. The data flows in, gets normalized, and appears in the student's profile.
The Information Already Exists
Nothing in Student Snapshot is new data. Every attendance record, every test score, every discipline entry, every intervention plan — it all already exists somewhere in a district's systems. Registrars entered it. Teachers recorded it. Counselors documented it. The work has been done.
The problem has never been missing data. The problem is that the data is scattered across systems that don't talk to each other, accessible only to the people who know which system to check and which report to run. Student Snapshot doesn't create information. It makes the information that already exists usable by the people who need it, at the moment they need it.
Student data shouldn't require a scavenger hunt. The information is there. It should just be in one place, instantly, for the people whose job is to help that student.