Skip to main content

The operating system for restoring student presence.

Connect attendance data, family outreach, barrier diagnosis, school action, service fulfillment, reintegration, compliance, and measurable outcomes in one accountable infrastructure.

Request a Demonstration

From first signal to sustained return.

A closed, auditable sequence; every step owned, time-bound, and evidenced.

Detect: Find risk early. Every handoff is owned, time-bound, evidenced, and auditable.

One accountable operating system. 10 connected layers.

Connect data, people, services, school action, and evidence without creating another disconnected workflow.

Layer 1

Presence Data Grid

Layer 2

Risk and Prevention

Layer 3

Family Trust and Access

Layer 4

Recovery Orchestration

Layer 5

Barrier Resolution Network

Layer 6

Managed Recovery

Layer 7

School-Side Remediation

Layer 8

Return and Reintegration

Layer 9

Compliance and Equity

Layer 10

Outcomes and Economic Value

Follow the work from district signal to accountable recovery.

The interface compositions below use fictional Northstar Unified demonstration information and reflect existing PresenceOS™ workflows.

District Command Center

See risk, ownership, and next action in one district view.

District leaders can review student recovery cases alongside assigned work and due dates. Teams can open a case, verify completed work, and keep accountable handoffs visible without relying on disconnected trackers.

Primary rolesDistrict executivesPrincipalsNavigators

Student Recovery Record

Move every recovery step forward from one student record.

Authorized teams can review the student profile, case status, contacts, barriers, tasks, recovery plans, service orders, school actions, and checkpoints together. They can assign work, document completion, update case status, and preserve a visible record of recovery activity.

Primary rolesNavigatorsPrincipalsDistrict teams

Family and Barrier Workflow

Turn family contact into an owned barrier-resolution path.

Teams can record outreach attempts, contact outcomes, family-visible summaries, and reported barriers. Families can submit help requests or explanations through their portal, while authorized staff verify barriers, assign responsibility, and track resolution.

Primary rolesFamiliesNavigatorsSchool teams

Service Fulfillment

Track support from referral through verified completion.

Teams can review provider capacity and follow service orders through matching, scheduling, delivery, evidence review, and completion. Evidence requirements and family confirmation remain attached to the order so a referral is not mistaken for fulfilled support.

Primary rolesNavigatorsService providersDistrict teams

Return and Reintegration

Coordinate return, school action, and stabilization as one plan.

Teams can document the recovery plan, return date, family-visible summary, and school-side actions required for reintegration. They can schedule and complete return-day, 3, 7, 14, 30, 60, and 90-day checkpoints while recording the next action when concern or relapse risk appears.

Primary rolesPrincipalsNavigatorsSchool teams

Outcomes and Accountability

Measure completed work and observed presence states responsibly.

Leaders can review recovered cases, stable student records, verified actions, and completed services from current operational records. PresenceOS™ distinguishes process accountability from causal proof; formal impact claims still require appropriate evaluation design and data-quality review.

Primary rolesDistrict executivesState administratorsProgram leaders

Data Connections and Integrations

Bring attendance records in through a supported, reviewable path.

PresenceOS™ currently supports vendor-neutral OneRoster attendance file imports in CSV or XLSX format. Uploaded rows enter validation, match against enrolled student numbers, and appear in import history with accepted and rejected record counts; no unverified SIS, SSO, API, or vendor connection is represented here.

Primary rolesDistrict data teamsSystem administrators