A clearer view of the school
Reports across students, attendance, fees and staff from one connected record instead of separate registers.
People, not just profilesPlans, not just periodsContext, not just records
The reason behind the platformA school is connected.
A school is connected.
Its software should be, too.
An admission becomes a student record. That student joins a class, appears in attendance and has a fee profile. When teams work in separate files, the context has to be rebuilt at every handover.
Schogle is designed around those connections—so the next task starts with the school information it needs.
The student recordSchool · Academic session · Class
AdmissionsEnquiry & profileAttendanceSchool-day contextAcademicsClasses & subjectsFeesCharges & receipts
A conceptual view of connected records—not an application screen.
The Schogle effect
Every team gets a better school day.
One connected platform means each person starts their work with the information they need.
Less repetitive work
Mark attendance on a phone, enter marks per student and see timetable changes and substitutions in one place.
Organised daily operations
Admissions, fee collection, receipts, inventory and certificates follow the same school setup and session.
Timely, consistent information
Notices, profile-change requests, leave and appointment rules handled through defined school workflows.
16connected modules
114+documented sub-modules
2workspaces: desktop & touch
1school per deployment
Dedicated modules for every department
See what each module does for you.
Choose a department, then a module, then a sub-module. See its features and the benefit your school gets.
schogle · Students & admissions
Academics / Students & admissions
Pre-Admission Enquiry
Keep family details, enquiry progress and admission review in one session-specific context before offering a seat.
Features
- Child, parent, sibling and contact details
- Session-specific enquiry register
- Keyword, stage, grade, status, date, source and mode filters
- Contact status and enquiry journey
- Lead stages and follow-ups
- Custom enquiry fields, ordering and admission-field mapping
- Public online admission form with Turnstile protection
- Intake session, schedule and eligible classes
- Admin alert recipients and channel share links
- Document checklist and eligibility rules
- Imports, registration setup and change history
- Enquiry-to-admission conversion summary
What your school gets
An enquiry ready for a documented admission review.
Supplied screens show enquiry capture and setup options. Field mapping does not create a student record by itself. Confirm notification delivery, imports, upload and fee-setting scope in a demo; no payment gateway is currently available.
Admissions teamsSchool administratorsClass teachers
View details 1Capture and admit
2Maintain the student record
3Progress or close the record
Designed around the school day
Real work. A clearer way through.
Start with the situation your team recognises. Follow the purpose, the steps and the handover.
An enquiry is only the beginning.
Keep the student’s story together.
From the first parent conversation to admission, profile changes and promotion, each next step needs the context of the last.
THE CONNECTED WORKFLOWStudents & admissions
- 01Capture and admit
- 02Maintain the student record
- 03Progress or close the record
A student record that gives the next responsible team a clearer starting point.
Workflow illustrations based on Schogle’s module overview. Confirm available screens and configuration in your demo.
For supported task assistance, explore Sahayak’s review-before-action approach and confirm its current scope in a demo.
What shapes SchogleNot just more features.
Not just more features.
More considered connections.
The value is in how people, records and responsibilities come together.
01
One shared school context
Classes and subjects are session-scoped, and a session transition carries data forward, so every module reads the same foundation.
02
A familiar desktop workspace
A Windows-style desktop with a Start menu, taskbar and multiple windows, so office staff can keep several screens open at once.
03
A touch shell for phones & tablets
A unified mobile launcher grouped by department, with mobile-friendly attendance and per-student marks entry.
04
Security by role
Staff sign in with email one-time-code verification, every action is permission-checked, and the Role Access Center shows who can do what.
05
Your school’s identity
Dedicated studios for certificates, fee receipts and report cards, plus custom forms for school-specific information.
06
An honest view of scope
Documented workflows come with their limitations. A personalised demo confirms exactly what is available for your school.
A thoughtful starting pointYour school first.
Your school first.
The software conversation second.
A meaningful demo starts with the way your school works—not a promise that every feature is the right fit.
- 1
Bring your everyday challenges
The repeated tasks, disconnected records and handovers you want to improve.
- 2
Walk through the relevant modules
Review the screens, configuration and release status with your school’s needs in mind.
- 3
Agree on the scope
Discuss records, access, implementation requirements and commercial terms before deciding.
Before you chooseThe right questions.
The right questions.
A more confident decision.
Clear expectations are part of finding the right school software.
How is Schogle different from separate school tools?
Schogle’s approach is to connect related work through one school context: shared classes, academic sessions, student profiles and staff responsibilities. The goal is a clearer handover between teams, rather than another isolated register.
Which workflows should we explore first?
Start with the work your team repeats most often: admissions, teaching schedules and substitutions, information collection or school documents. Then explore the related attendance, communication, fees and reporting workflows.
Can Schogle fit our school’s processes?
The overview describes school and session settings, role permissions, custom forms and document studios. Bring your existing processes to the demo so we can review the supported options, configuration needs and any gaps together.
Can we move our existing records?
Share your record formats, data volume and required history with our team. The module overview includes Excel student imports with validation; migration scope and implementation requirements still need a school-specific assessment.
Is our school’s information secure?
Staff sign in with email one-time-code verification, every request is checked against role permissions, and stale sign-ins can be revoked. Each school runs as its own deployment, so its records are not shared with other schools.
Does Schogle work on phones and tablets?
Yes. Alongside the desktop workspace there is a touch shell for phones and tablets, grouped by department, with mobile-friendly attendance and marks entry.
What should we confirm before making a decision?
Confirm module availability, the timetable version, import needs, access permissions, implementation scope and commercial terms. The documented product has no payment gateway or promised live bus tracking; salary processing and multi-level approvals are not established capabilities.