Admissions pipeline

Lead tracking, notes, status pipeline, and conversion into live student records.

School OS includes an admissions CRM with lead statuses, parent contact details, notes, source tracking, and lead-to-student conversion.

Run admissions as the front door of the same system that will later manage records, family access, finance, and school operations.

CRM Pipeline
Lead Notes
Source Tracking
Lead-to-Student Conversion
Operational layer
Admissions & CRM

The current CRM module already supports inquiry tracking, pipeline stages, lead notes, and conversion from accepted lead into a live student record.

01
Pipeline visibility

Leads move through inquiry, tours, applications, acceptance, enrollment, and loss inside a single admissions workflow.

02
Source and contact context

Admissions teams hold family details, student interest, grade interest, notes, and lead source together.

03
Conversion into live records

Accepted leads can become real student records with generated student numbers and grade-level matching.

04
No dead handoff

Admissions does not end in an export because the learner enters the same operational system after conversion.

Why it matters
Run admissions as the front door of the same system that will later manage records, family access, finance, and school operations.
A cleaner admissions-to-enrollment handoff with less duplicate entry.
Better institutional memory because inquiry context stays attached to the eventual student journey.
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.

Admissions team

Pipeline workspace

Track every inquiry, note, follow-up stage, and parent detail inside a CRM built for school admissions rather than generic sales motion.

Operations

Clean conversion to enrollment

When a lead is ready, School OS turns that family from prospect into active student record without rebuilding the data elsewhere.

Leadership

Top-of-funnel to operating system

The enrollment journey starts in the same system that will later manage classes, billing, portals, and academic records.

01

Pipeline visibility

Leads move through inquiry, tours, applications, acceptance, enrollment, and loss inside a single admissions workflow.

02

Source and contact context

Admissions teams hold family details, student interest, grade interest, notes, and lead source together.

03

Conversion into live records

Accepted leads can become real student records with generated student numbers and grade-level matching.

04

No dead handoff

Admissions does not end in an export because the learner enters the same operational system after conversion.

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

Lead capture

Store student interest, parent contact details, source, grade interest, and free-form notes for each lead.

Capability 02

Pipeline statuses

Move leads through inquiry, tour scheduled, tour done, application, accepted, enrolled, and lost.

Capability 03

Admissions notes

Add team notes to each lead record for follow-up and internal tracking.

Capability 04

Lead conversion

Convert a lead into a student record with generated student number and optional grade-level matching.

Capability 05

Operational handoff

Once converted, the lead becomes a live student record inside the wider School OS system.

Operating Sequence

How the workflow runs in practice.

1

From inquiry to enrolment

Track the family through the admissions pipeline and convert the lead once the school is ready to enrol.

2

Shared context

Keep admissions data connected to the same system that will later run student records, portals, finance, and reporting.

Strategic Outcome

Why this matters at system level.

A cleaner admissions-to-enrollment handoff with less duplicate entry.

Better institutional memory because inquiry context stays attached to the eventual student journey.

A stronger growth story because admissions is treated as part of school operations, not a disconnected funnel.

With TeachSignal Intelligence

With TeachSignal Intelligence added, enrollment growth and staffing conditions can be understood together instead of as separate leadership conversations.

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
CRM Pipeline
Connected app
Lead Notes
Connected app
Source Tracking
Connected app
Lead-to-Student Conversion
One system, two modules

See how Admissions & CRM 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.