Skip to Education content

SCHOOL WORKFLOWS

One school. Connected people and records.

From the first student record to the classroom, school office and family, each person gets a workspace shaped around their responsibilities.

CONNECTED SCHOOL WORKFLOW

School leadership

A shared view of school activity, with decisions kept in the hands of authorized leaders.

  • Review enrollment, attendance, academic activity and financial summaries.
  • Assign staff responsibilities and maintain class and subject access.
  • Review official reports and grade changes before publication.

An overview leads back to the school records and approvals behind it.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

Student records & imports

Move existing school records into a reviewed, school-specific structure.

  • Upload supported spreadsheets or CSV records and review field mappings before saving.
  • Keep external student references alongside generated SchoolCRM student IDs.
  • Review student, fee, tuition, payment, expense and historical grade imports separately.

Matching requires explicit identifiers; a shared name does not merge two students. Uploaded historical grades are not automatically published results.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

Teacher workspace

Bring the daily work of teaching together around assigned classes and subjects.

  • Record class attendance and follow up on absence information.
  • Prepare lesson notes, learning files and assignments.
  • Use gradebooks and teacher feedback within assigned teaching responsibilities.

Teachers work from their assignments, while school leadership governs official academic publication.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

Learning & FreedomExam

Connect learning materials, assessment preparation and student work.

  • Author questions and assessments, and review student attempts.
  • Support autosave and submission receipts for exam work.
  • Combine objective scoring with teacher-reviewed marking and feedback.

Review marks remain separate from approved reports. An automated score does not replace the school’s academic decisions.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

Student & guardian access

Give students and verified families an appropriate view of school life.

  • Students use their school-provided access details for their own records.
  • Guardians use verified child links rather than searching other students.
  • Share approved learning information, reports and school-fee records according to role.

The school manages account provisioning, identity checks and recovery. Public inquiries never provide access to student records.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

School finance

Follow tuition, collections and spending without mixing currencies or approval duties.

  • Maintain separate USD and LRD invoices, receipts and ledgers.
  • Review payment evidence, reconciliation, spending requests and corrections.
  • Work with authorized finance exports, budgets and payroll records.

Submitted payment proof needs school review; it is not an automatic payment confirmation. A school’s collections are separate from its FreedomOS subscription.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

School communications

Keep school announcements, inquiries and follow-up connected to the right audience.

  • Publish targeted school announcements and calendar information.
  • Review website inquiries, reply history and private call notes.
  • Coordinate student-record transfer requests through the authorized school workflow.

Messaging and record requests follow school permissions. Email and other external delivery channels depend on their configured services.

Discuss this workflow →
CONNECTED SCHOOL WORKFLOW

Your school website

Maintain a school-branded public presence alongside the school workspace.

  • Edit school information, programs, news and admission pages.
  • Review galleries and media permissions before publication.
  • Preview drafts and publish through the school’s authorized review process.

Public website content is separate from private student and learning records. An admission inquiry does not automatically enroll a student.

Discuss this workflow →

A practical path from existing records to a school workspace

  1. Prepare. Gather your class lists, student identifiers, fee structure and authorized staff roles.
  2. Review. Confirm field mappings, totals, currencies and student matches before importing.
  3. Authorize. Set class responsibilities and verify student and guardian access.
  4. Start carefully. Review the school’s workflows and approvals before moving everyday operations into the workspace.

School activation remains subject to release controls and the school’s onboarding review. A public demo inquiry does not activate billing or certify a school for live use.