Funding · district progress snapshot

Aggregate PulsePoint data for grants, LCAP context, and leadership review—plus a district outreach & demo kit (links, script, pilot framing) for shopping PulsePoint to districts. Passcode: control-center-config.json → funding_passcode or staff_passcode (default in funding-gate.html).

PulsePoint is MIT-licensed open source (see repository LICENSE) · Created by Aris Tunson · © 2024–2026 · Terms · Privacy · Roosevelt SEIS · Oakland USD

← Dev hub Instructions System map Grants index

District outreach · MIT open source · funding narrative

PulsePoint is a special education workflow platform (IEP goals, assignments with supports, progress evidence, behavior/MTSS logging) built at Roosevelt SEIS and offered as MIT-licensed open source. Districts can pilot on an isolated demo stack, review aggregate outcomes on this page, and scale without proprietary lock-in on the core platform—implementation, hosting, and support are negotiable; the codebase remains inspectable and forkable.

MIT License Open source core District-owned MongoDB data FERPA-aware design

Why open source matters for grants

  • LCAP / ESSER narratives can cite transparent tooling and local control of student data.
  • No black-box SPED vendor dependency for the core teacher workflow.
  • Pilot → evaluate → adopt with clear exit path (data stays in district MongoDB).

10-minute demo script

  1. Dev hub — show demo stack, student roster, staff gate.
  2. Student login — tap a name → enhanced dashboard with IEP-linked panels.
  3. Teacher hub — assignments, daily planner, monitor live view.
  4. This funding page — refresh charts; toggle presentation mode.

Procurement framing

Typical SPED SaaSPulsePoint (MIT)
Closed sourceOpen source · auditable
Vendor-hosted onlyDistrict or TunsonCloud-hosted options
Per-seat licenseCore platform free; services priced separately
Dev hub Grants index Demo instructions Terms of service Privacy policy

Loading…

Program usage & student outcomes (MongoDB)

Loads full-roster aggregates from /api/funding-program-impact when you refresh.

Presentation: program-impact metrics use real app submissions only by default (rows from /api/seed-all are excluded). To include seeded demo volume for a fuller chart, open this page with ?includeSeed=1.

How to read this for OUSD: “Program use” is volume of PulsePoint progress rows and recent activity. “How students are doing” is shown through gradebook % (math / science / ELA) and mean scores on work logged in PulsePoint—proxies for engagement and mastery, not surveys of student feelings.

Class average grade % (from Mongo grades)

Roster students that have a subject score. Missing subjects are excluded from that bar’s average.

Students by mean PulsePoint assignment score

Each student’s average of numeric scores across their student_progress rows (attempt-level work).

Progress records logged by calendar month

Intensity of platform use—more logged completions mean more evidence captured for IEP and grading conversations.

How to read it: Each month shows how many student progress rows have a completion date in that calendar month (logged work/completions—not a grade average). The series includes every calendar month from the earliest to the latest dated progress row in the chart range; months with no rows show as 0. Dates use completion time when available (completedAt / date, or stored assignment due on the row); otherwise the matched assignment’s due date is used only to place the row in a month. Taller bar = more evidence captured that month; compare bars to spot busy vs quiet periods.

Student Gr Math % Sci % ELA % Progress rows Avg score Rows marked done Last progress Behavior # H / M / L

Technical system charts (optional)

Core domains (db-counts)

Assignments — active vs rest

MongoDB collections — document volume (top drivers)

MongoDB collections — full inventory (all collections)

AI assist + live engagement analytics

KPIs and charts here come from /api/ai/growth-scan-status, /api/ai/daily-digest, and sampled Mongo progress and activity rows (see dashboard note when data loads). Where Ollama is configured, we generate draft IEP goal growth notes for staff review only—nothing ships to families or students without review. Tournament and live-game counts (e.g. Connect Four) are under Program usage & outcomes above.

Source: MongoDB collections and Mongo-backed API endpoints.

Student adoption snapshot (all-time)

Retry outcomes (2+ attempts only)

Loading retry coverage…

Expanded analytics (optional)

Mongo student dataset footprint (collection counts)

Understanding after repeat attempts (% right trend)

Latest score bands after retries

Standards coverage by subject (all-time)

Weekly trend (last 8 weeks)

IEP goal progress distribution

Loading AI workflow and student engagement metrics…

District recommendations and cost scenarios (full pricing tables)

District consultant recommendations (teacher-first SPED use)

This section is written for district leaders and SPED program managers to evaluate whether PulsePoint is effective in both restricted and unrestricted instructional environments.

Recommended implementation model

  • Restricted setting: daily teacher dashboard use (IEP goals, intervention logging, assignment supports), with weekly standards review by case manager.
  • Unrestricted setting: shared access for gen ed + SPED staff to standards effectiveness and accommodation plans, with clear role-based edit rights.
  • Cross-setting success metric: movement from "needs reteach" to "working" standards families plus IEP goal progress gains.

What districts usually ask to see

  • Standards-aligned outcomes (CA Common Core, NGSS, CAASPP readiness) by subgroup and classroom setting.
  • Teacher adoption indicators (weekly active teachers, assignment completion cycles, intervention closure rates).
  • Compliance support indicators (IEP progress report timeliness, goal update cadence, evidence traceability).
  • Family communication artifacts (printable updates and conference-ready summaries).

Estimated service pricing (planning ranges)

Service component Estimated range How to interpret
Platform subscription (SPED data + workflow) $10-$100 per SPED student/year (market range) Benchmark from published SPED vendors; exact pricing depends on modules and contract term.
Implementation + training $15,000-$75,000 one-time (small-to-mid district rollout) Includes onboarding, data mapping, teacher PD, and adoption support.
Ongoing managed support $2,000-$12,000/month Depends on SLA, reporting cadence, and number of schools/teams served.

Public OUSD examples show SIS/assessment platform contracts can range from roughly ~$95k annual tools to seven-figure multi-year SIS agreements. Use district procurement records to set the target band for a PulsePoint pilot.

Public references: OUSD Legistar contract records (for example, Aeries SIS and Illuminate DnA entries) and published California SPED vendor rate cards.

OUSD comparable public spend context

Comparable category Public record example Presentation use
District SIS (multi-year) Aeries SIS agreement in OUSD public board records is in the seven-figure multi-year band. Shows district-level systems can justify larger totals when mission-critical.
Assessment platform (annual) Illuminate DnA public OUSD contract examples are around mid-five to low-six figures annually. Useful benchmark for annual instructional analytics tools.
LMS/operations tools OUSD public records include contracts around ~$100k/year range for specific school operations platforms. Positions PulsePoint pilot as comparable to existing approved software categories.

Use exact board agenda items/IDs from OUSD Legistar before presenting externally; numbers above are intended as planning context, not legal procurement advice.

Pilot and rollout budget scenarios (for board discussion)

Scenario A — Single school pilot

1 school, SPED team only, 1 semester. Typical planning envelope: $35k-$120k (setup + training + support).

Scenario B — Multi-site pilot

3-5 schools, SPED + selected gen ed collaboration. Typical planning envelope: $120k-$350k annualized.

Scenario C — District rollout

District-level governance, full support model, compliance reporting package. Typical planning envelope: $350k+ based on scale and contract structure.

Recommended procurement framing: run Scenario A first with explicit success criteria (standards growth, IEP reporting timeliness, teacher adoption), then scale only if targets are met.

Director memorandum (embedded)

Director memorandum (embedded)

Full page (print / PDF): Open memorandum in new tab · Printable class check-in sheet · Freetime word search