Student data foundation

Student handling, records, and guardian-linked profiles.

School OS includes student roster management, profile editing, class and grade assignment, guardian linking, transcript views, and CSV roster import.

Build one live student record that follows the learner from enrolment to family access, reporting, and historical context.

Students
Guardians
Parent Portal
Report Cards
Transcript View
Operational layer
Student Records

This page reflects the implemented student and guardian workflows in the product today: student CRUD, roster import, guardian records, invite-based parent access, and linked academic history.

01
One live profile

Identity, class placement, guardians, medical context, and academic history sit on a single record.

02
Family-linked access

Guardian relationships and invite-based onboarding connect the family directly to the student record.

03
Import-ready onboarding

CSV roster import speeds migration while protecting against duplicate student numbers.

04
History preserved

Published report cards roll forward into transcript views for cumulative context.

Why it matters
Build one live student record that follows the learner from enrolment to family access, reporting, and historical context.
Fewer duplicate records across admissions, academics, and family communication.
Cleaner handoff from enrollment into live school operations.
Product Narrative

Built for the actual operators behind this workflow.

These are not abstract product claims. The experiences below map to workflows already represented in the platform today, translated into the operating model a school leader or investor would expect to see from a serious system product.

Registrar

Student profile workspace

Manage enrollment, placement, student numbers, nationality, medical notes, and linked family details without leaving the core record.

Families

Guardian connection layer

Invite guardians into the system, maintain relationship context, and tie communication and portal access directly to the child record.

Leadership

Longitudinal student context

Use transcript and report-card history as a cumulative source of truth rather than rebuilding a student picture from separate systems.

01

One live profile

Identity, class placement, guardians, medical context, and academic history sit on a single record.

02

Family-linked access

Guardian relationships and invite-based onboarding connect the family directly to the student record.

03

Import-ready onboarding

CSV roster import speeds migration while protecting against duplicate student numbers.

04

History preserved

Published report cards roll forward into transcript views for cumulative context.

Actual Functionality

What this module already supports in the product.

The list below is grounded in the implemented controllers, views, and workflows already present in School OS. This is the part investors and buyers both care about: not just a category story, but a real operating surface.

Capability 01

Roster management

Create, edit, delete, and browse student records with student numbers, enrollment status, admission date, and class placement.

Capability 02

Profile details

Store date of birth, gender, nationality, grade level, current class, and medical notes on each student profile.

Capability 03

Guardian linking

Link guardians to students, store relationship and preferred contact method, and view linked families on student and guardian pages.

Capability 04

Transcript history

Generate cumulative transcript views from published report cards grouped by academic year.

Capability 05

Roster import

Import students from CSV with duplicate student-number checks per tenant.

Operating Sequence

How the workflow runs in practice.

1

Student setup

Create or import a student, assign grade and class, then connect guardians and start academic activity.

2

Guardian access

Send guardian invites by email so families can activate their parent portal account.

3

Student history

Use the student profile and transcript views to see enrollments, recent behaviour, and published report-card history.

Strategic Outcome

Why this matters at system level.

Fewer duplicate records across admissions, academics, and family communication.

Cleaner handoff from enrollment into live school operations.

A stronger parent experience because access starts from the actual student record.

With TeachSignal Intelligence

When School OS and TeachSignal Intelligence run together, student movement, family context, and academic history create stronger operational context around where school pressure is emerging.

View TeachSignal Intelligence
Connected Modules

This module is stronger because it is not alone.

School OS is built as one operating system. Each module below contributes more value because it is already connected to the same school context, user roles, and live data model.

Connected app
Students
Connected app
Guardians
Connected app
Parent Portal
Connected app
Report Cards
Connected app
Transcript View
One system, two modules

See how Student Records works inside the wider School OS platform.

Buy this module on its own or run it as part of the full School OS stack. The strongest version combines School OS operations with TeachSignal Intelligence on top.