How We're Approaching a County-Level Education Data System Engagement
<p>When Los Angeles County needs to evaluate whether a multi-agency data system serving foster youth should be modernized or replaced, the work sits at the intersection of technology, policy, and people. That's exactly where we operate.</p> <h2> The Opportunity </h2> <p>The LA County Office of Child, Youth, and Family Well-Being is looking for a consulting team to analyze the Education Passport System (EPS), a shared data platform that connects 80+ school districts with the Department of Children and Family Services and the Probation Department. The system exists to ensure that when a foster youth moves between placements, their education records follow them.</p> <p>The question on the table: does the current system meet the needs of all stakeholders, or is it time to move to something new
When Los Angeles County needs to evaluate whether a multi-agency data system serving foster youth should be modernized or replaced, the work sits at the intersection of technology, policy, and people. That's exactly where we operate.
The Opportunity
The LA County Office of Child, Youth, and Family Well-Being is looking for a consulting team to analyze the Education Passport System (EPS), a shared data platform that connects 80+ school districts with the Department of Children and Family Services and the Probation Department. The system exists to ensure that when a foster youth moves between placements, their education records follow them.
The question on the table: does the current system meet the needs of all stakeholders, or is it time to move to something new?
What the Work Involves
This is a 12-month engagement with five major deliverables:
Needs Assessment and Gap Analysis - Working directly with LACOE, DCFS, Probation, school districts, and child welfare advocates to map what the system does today versus what every stakeholder actually needs.
Comparative Analysis - Examining what other California counties and out-of-state jurisdictions have built, what works, what failed, and whether any existing platforms could serve LA County better than what they have.
State-Level Assessment - Identifying where state policy, legislation, or system architecture is creating barriers to local implementation. CALPADS, CWS-CARES, and the patchwork of state data systems all play a role.
Recommendations - Delivering a written report and presentation with concrete options, each with cost estimates, staffing requirements, implementation timelines, and trade-offs.
Stakeholder Vetting - Presenting recommendations to county leadership, school districts, charter schools, and Board of Supervisors offices, incorporating feedback, and finalizing.
Why This Matters
There are roughly 30,000 children in the LA County foster care system at any given time. When a child moves placements, which happens frequently, their education records need to follow them immediately. Credits need to transfer. IEPs need to be accessible. Enrollment needs to happen without delay.
When the data system works, a child doesn't lose a semester. When it doesn't, they fall behind in ways that compound across their entire life.
Where We Fit
Our team brings the AI governance and systems analysis layer. We specialize in evaluating how organizations use technology, whether those systems are governed properly, and what it takes to modernize without breaking what already works.
For this engagement, we're assembling a small, focused team. We're looking for 1-2 strategic partners who bring direct experience with child welfare data systems, K-12 education data infrastructure, or multi-agency government data interoperability at the county or state level.
This is not a general call for collaboration. We're selecting operators who have been inside these systems, not just studied them.
If This Is Your World
If you've worked directly with foster youth education systems, child welfare data platforms, CALPADS, CWS-CARES, or similar infrastructure at the county or state level, we should talk. The deadline for this engagement is April 24, 2026. We're moving now.
Reach out directly:
-
Email: [email protected]
-
WhatsApp: wa.me/18184399770
-
Schedule a call: calendly.com/levelsofself/zoom
Arthur Palyan - Founder, Levels of Self - AI Governance and Systems Analysis - levelsofself.com
Canonical URL: https://www.levelsofself.com/post/how-we-re-approaching-a-county-level-education-data-system-engagement
DEV Community
https://dev.to/levelsofself/how-were-approaching-a-county-level-education-data-system-engagement-ndkSign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
platformserviceanalysis
How a 6 AM Cron Job Unlocks 2 Extra Hours of Claude Code Every Day
Schedule a single Haiku message to shift your 5-hour usage window, eliminating midday dead time without changing your workflow. The Technique — Anchoring Your Usage Window If you're on a Claude Max plan, you know the 5-hour usage window starts with your first message and resets on the clock hour. Start at 8:30 AM, hit your limit by 11 AM, and you're locked out until 1 PM—two hours of dead time. Developer Victor Smoliveira discovered a simple workaround: send a throwaway message with Claude Haiku (the cheapest model) at 6 AM. This anchors your window to 6-11 AM instead of 8 AM-1 PM. By 11 AM, you get a fresh window exactly when you'd normally be blocked. Why It Works — Understanding Claude Code's Billing Cycle Claude Code's usage window operates on a rolling 5-hour basis, but it's "floored"

I Built a Complete E-commerce REST API with Laravel 12 — Here's What's Inside
Building an e-commerce backend from scratch takes months. Authentication, payments, inventory, shipping, admin panel, tests… the list never ends. I decided to build it once, properly, and package it for other developers. The result is LaraCommerce API — a complete, production-ready e-commerce backend built with Laravel 12. WHAT I BUILT A fully-featured REST API covering every e-commerce use case, with an admin panel, full Stripe integration, and 100% test coverage. THE NUMBERS API Endpoints: 325+ across 25+ modules Database: 88 Eloquent models, 72 migrations Admin Panel: Filament v3 with 46 screens Tests: 2,452 tests / 100% coverage Docker: 12 services, one-command setup Languages: 3 (EN, FR, AR) Currencies: 7 (USD, EUR, GBP, MAD, CAD, CHF, AED) TECH STACK Framework: Laravel 12 (PHP 8.5+)

I Built 25 Cloudflare Workers APIs — Here's What I Learned
Over the past few months, I built and deployed 25 APIs on Cloudflare Workers . All running on the free tier. Total monthly hosting cost: $0 . Here's what I learned about building, deploying, and monetizing utility APIs at scale. The Stack Every API follows the same pattern: worker-api/ ├── src/ │ └── index.js # Single entry point ├── wrangler.toml # Cloudflare config └── package.json No frameworks. No bundlers. Just vanilla JavaScript on Cloudflare Workers. The 25 APIs Here's a sampling of what I built: API Purpose Complexity Readability Score Text analysis (Flesch-Kincaid, SMOG, ARI) Medium QR Code Generator Generate QR codes from text/URL Low Password Generator Cryptographically secure passwords Low Markdown to HTML CommonMark-compliant conversion Medium Color Converter HEX/RGB/HSL conve
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products
Do Not Stick Out: The Dynamics of the ECH Rollout
When you re trying to hide, the last thing you want is to draw attention to yourself. That was the philosophy behind the design of Encrypted Client Hello (ECH), a new technology that helps close a 20-year-old privacy leak in the Internet’s design [1]. ECH encrypts the name of the website you’re visiting, making connections to [ ] The post Do Not Stick Out: The Dynamics of the ECH Rollout appeared first on Center for Democracy and Technology .

490+ Calculator Tools with Zero Hosting Cost — Architecture Deep Dive
I built a site with 490+ free calculator tools — BMI, loan payments, unit conversions, tax calculators — all statically generated with Next.js. Monthly hosting cost: $0 . Here's the architecture behind keisan-tools . The Problem Japanese users search for specific calculators constantly. "BMI計算" (BMI calculator), "住宅ローン計算" (mortgage calculator), "年齢計算" (age calculator). Each query has moderate search volume with surprisingly low competition. Instead of building each tool by hand, I built a system that generates tools from configuration . Architecture Overview keisan-tools/ ├── data/ │ └── tools.json # 490+ tool definitions ├── app/ │ └── [category]/ │ └── [slug]/ │ └── page.tsx # Dynamic route template ├── lib/ │ ├── calculator.ts # Calculation engine │ └── tools.ts # Tool loader + search └

I Built a Complete E-commerce REST API with Laravel 12 — Here's What's Inside
Building an e-commerce backend from scratch takes months. Authentication, payments, inventory, shipping, admin panel, tests… the list never ends. I decided to build it once, properly, and package it for other developers. The result is LaraCommerce API — a complete, production-ready e-commerce backend built with Laravel 12. WHAT I BUILT A fully-featured REST API covering every e-commerce use case, with an admin panel, full Stripe integration, and 100% test coverage. THE NUMBERS API Endpoints: 325+ across 25+ modules Database: 88 Eloquent models, 72 migrations Admin Panel: Filament v3 with 46 screens Tests: 2,452 tests / 100% coverage Docker: 12 services, one-command setup Languages: 3 (EN, FR, AR) Currencies: 7 (USD, EUR, GBP, MAD, CAD, CHF, AED) TECH STACK Framework: Laravel 12 (PHP 8.5+)


Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!