← Jack Quinn

Case study · D2 Labs

Students First

Software state education agencies use to roll out priorities to every district, with an agent that turns compliance data into district strategic plans.

Role
Founding engineer
Client
D2 Labs
Period
2026 – present

The problem

A state education agency sets priorities for every district it oversees, then has to see those priorities carried out and make sense of what districts report back. Students First is sold directly to state agencies to do that work. North Dakota was the first.

Before Students First, there was no real way for a state school board to track how a statewide goal was being implemented across all of its districts. Priorities were set at the top, passed down in meetings, and trusted to be carried out. Whether that happened, and whether it made any difference, was hard to see from the state, and just as hard for a district to show.

Students First makes it measurable. The state can follow every district’s progress on each priority and see the effect of the plan, and districts can show that they’re carrying it out. Both sides get confidence that the plan is being implemented and that it’s working.

From a priority to a plan

The state starts by setting its priorities for the year, like the Science of Reading or attendance, and breaking each one into the tasks, evidence and staff certifications it expects from every district. From then on, it can see where every district stands.

The Students First state console showing statewide implementation for the 2026–27 school year. Summary cards show districts enrolled, required tasks done, staff certified and strategic plans. Three state priority cards, Science of Reading, Attendance and engagement, and Career and college readiness, each show the share of districts on track. Below, a table lists districts with their task completion, staff certified and strategic plan status.
State view Each priority, the share of districts on track, and every district's progress. Screens on this page are wireframes with demo data.

Each district gets that work as a list, grouped by priority, with an owner and a due date for every item. Staff complete their certifications much like coursework in a learning management system, and the district can see what’s overdue and what’s coming up.

The district portal for Cedar Creek District showing its implementation tasks, grouped by state priority, with filters for each priority. Science of Reading and Attendance and engagement each list tasks, evidence and certifications with an owner, due date and status, from Not started and In progress to In review, Complete, Due soon and Overdue. A side panel tracks staff certifications and upcoming deadlines.
District view A district's work for the year, grouped by the state priority each task serves.
An evidence task, Adopt a high-quality K–3 literacy curriculum, in state review with changes requested. Three of four requirements are met with uploaded files; the teacher training plan is missing. A state review thread shows the reviewer asking for the training plan, beside links to state guidance.
District view A reviewer has asked for the one requirement that's still missing.

Some tasks need evidence, such as a curriculum memo, board minutes or an implementation timeline. The district uploads files against each requirement and submits the task to the state.

A task doesn’t count until a state reviewer accepts it. The reviewer can ask for changes in a thread on the task, and the district resubmits. That review is what turns each district’s work into compliance data the state can rely on.

The agent turns that data into a strategic plan. It reads the district’s completed tasks, evidence, certification records, board minutes and screening results, and drafts a plan with a goal for each state priority. Every strategy cites the records behind it. When data is missing, like a chronic absenteeism baseline, the agent leaves the measure as a placeholder and says so instead of inventing a number.

A strategic plan for Cedar Creek District, 2026–2029, drafted by the agent from 31 sources. Three goals, one per state priority, each list strategies with citations to the tasks, board minutes and certification records behind them. A side panel lists the sources used and warns that the chronic absenteeism baseline is missing, so goal 2's measures stay as placeholders. Buttons at the top regenerate the draft, request state review, or send it to the board.
District view A plan drafted from 31 of the district's records. The district can regenerate it, request state review, or send it to its board.

Each district’s plan status shows up in the state’s overview next to its tasks and certifications, so the state sees both the work and the plan it adds up to.

What I built

I was North Dakota’s sole technical advisor from discovery through go-live, and the only engineer on the platform.

Students First is a TanStack Start app running on AWS Lambda, with CloudFront in front of it and Postgres behind it. Inference for the agent runs on AWS Bedrock.

Going live statewide

North Dakota went from kickoff to statewide go-live in about a month, covering the state school board and every district in the state.

Most of that month went into the process around the software. We met with the key stakeholders at the state and planned a regimented schedule for checking in on program tasks and compliance. We designed the user roles around how that information is reported, from the districts up to the state. Then we taught users and administrators how to work within their roles in the product.

The part that nearly went wrong was explaining multi-tenancy and anonymity. Both are decided at the architecture level, and the details aren’t easy to follow if you aren’t technical, but the people deciding whether to trust the platform still needed to understand them. Getting there meant abstracting the technical details into terms that made sense to them.

Trusting agents in the public sector

Evals run in CI, and passing them is part of what makes a release ready. They test the agent’s core capabilities, including that it doesn’t hallucinate and that anonymity holds. If a change makes any of them regress, the build fails and the change doesn’t ship. The state never has to be the one to catch it.

Outcome

It’s too early for measured results: North Dakota is still in its first cycle on the platform. But hundreds of educators and state administrators already rely on it day to day to carry out the goals the public has trusted them with.