Inquiry And Admission Management
Capture prospective student enquiries, schedule follow-ups, review admission details and create a student only after final confirmation.
Plan and manage the complete student journey in one configurable ERP for schools, tuition institutes and coaching classes, with institute-wise modules, role-based access and future-ready web and mobile experiences.
The product roadmap covers the operational and academic modules schools and tuition institutes need, while allowing SwiftMaze SuperAdmin to enable only the modules included for each institute.
Capture prospective student enquiries, schedule follow-ups, review admission details and create a student only after final confirmation.
Maintain student and guardian profiles with school classes and sections or tuition batches, while preserving academic-year enrollment history.
Configure class or batch fee plans, instalments, partial payments, discounts, late fees, payment modes and downloadable receipt records.
Manage student attendance, teachers, timetables, homework, offline exams, marks and progress reports from connected academic records.
Plan role-specific Flutter app experiences for parents, students and teachers using the same secure backend and institute data rules.
Enable modules institute-wise, restrict access by role and expose only the reports connected to modules available for that institute.
Share your student strength, current registers, fee process, academic structure, staff roles and parent communication needs. We will help map the appropriate core and optional ERP modules for your school or tuition institute.
SwiftMaze School ERP is planned as a connected system instead of separate registers. Each enabled module contributes to one reliable student, academic and financial record.
Record prospective students, contact details, source, interested class or batch, follow-up date, notes and inquiry status.
Review admission information, preserve inquiry history and create the final student profile through a controlled confirmation step.
Support academic years, school classes and sections, or tuition batches and courses with structured student assignments.
Create class or batch fee plans, assign categories, define schedules, collect full or partial payments and track outstanding amounts.
Generate versioned receipt records for print, download and parent access, with optional WhatsApp sharing when the integration is enabled.
Maintain teacher and employee information, record student attendance and provide role-appropriate attendance visibility.
Manage offline exams and tests, subject-wise marks, grades and progress reports, with planned Excel upload and PDF templates.
Share class or batch timetables, simple homework assignments and institute notices through the relevant user experience.
Move eligible students to a new academic year, class or batch without overwriting earlier fees, attendance and result history.
Review student, attendance, fee, pending-payment, exam, class, teacher and communication reports based on enabled modules.

SwiftMaze is planned for institutions that need connected admissions, student records, academic operations, fee management and role-based access without maintaining disconnected registers.
Manage classes, sections, admissions, students, parents, attendance, fees, examinations, results and institutional reports.
Manage enquiries, batches, teachers, attendance, fee plans, tests, marks, homework and student communication.
Organize course or batch enrollment, student attendance, payment history, offline tests and progress information.
Separate admission, student, fee, receipt and reporting actions according to approved staff permissions.
Provide role-specific access to attendance, timetable, homework, notices, results and receipts as modules are released.
Plan institute-wise data separation, module entitlements, subscriptions and operational controls for scalable management.
A school ERP should preserve the journey from the first inquiry to confirmed admission instead of forcing staff to enter the same information repeatedly. SwiftMaze is planned around a traceable inquiry, follow-up, admission and student-creation workflow.
Schools can work with classes and sections, while tuition institutes can use batches and courses. Parent or guardian information remains connected to the student, and academic-year enrollment history is retained for future reporting.
Capture source, interested class or batch, next follow-up, notes and current status for every prospective student.
Review student, guardian, address and admission details before creating the permanent student record.
Maintain organized student and guardian information with institute-scoped access and role-based visibility.
Track class, section, batch and academic-year movement without losing earlier institutional records.
Fee collection requires more than a payment entry. The planned ERP connects fee categories, class or batch plans, collection schedules, concessions, partial payments, overdue status, payment history and receipt snapshots.
Cash, bank, UPI, cheque and future online payment records can follow controlled validation rules. Optional payment gateway and WhatsApp receipt delivery remain institute-configurable integrations rather than mandatory dependencies.
Create reusable fee categories with monthly or fixed-session schedules and assign them to eligible students.
Record allowed payment amounts accurately while keeping paid, pending and overdue states separate.
Prepare print-ready, downloadable and versioned receipts backed by the payment snapshot at collection time.
Give authorized parents access to receipts for their linked students through the planned parent experience.
Connected academic modules help administrators and teachers avoid fragmented spreadsheets. Attendance, examinations, marks, timetables, homework, notices and student progress can use the same class, batch, subject and academic-year structure.
Version 1 focuses on offline exams and tests. Online exams, question banks and homework submission workflows are not presented as standard v1 features.
Record and review attendance with access appropriate to administrators, teachers and linked parents or students.
Manage subjects, maximum marks, obtained marks, grades, percentages and optional rank information.
Prepare Gujarati or English progress-report templates with planned PDF viewing and download support.
Publish routine academic information for the relevant class, batch, teacher, parent or student audience.
SwiftMaze School ERP is being planned as a reusable multi-institute SaaS product. Institute data, settings, subscriptions, limits and enabled modules remain separate, while the platform owner controls institute access and module availability.
Planned roles include SwiftMaze SuperAdmin, Institute Admin, Clerk, Teacher, Parent, Student and optional Driver. Admin workflows remain web-first, while the future common Flutter app can deliver role-specific parent, student and teacher experiences through the same backend.
Enable or disable modules institute-wise so unavailable features stay hidden from navigation, reports, routes and APIs.
Limit each user to permitted actions and records instead of giving every staff member unrestricted access.
Keep each school or tuition institute data set logically separated throughout web, mobile and backend workflows.
Use shared API contracts and server-side validation while keeping web and mobile interfaces optimized for their users.
Not every institute needs every feature. Optional modules can be planned according to the institute type, selected plan, operating process and approved implementation scope.
This keeps the daily interface simpler for staff and avoids presenting advanced integrations as mandatory parts of the core ERP.
Optional payment gateway, DLT SMS, WhatsApp templates, receipt sharing and app notifications with provider-wise settings.
Template-based certificate and student I-Card generation with validation, preview and print-oriented output options.
Optional staff attendance workflows and driver-phone GPS bus tracking when enabled for the institute.
Optional assigned lecture viewing for relevant classes or batches using a suitable external video provider.
A successful school ERP starts with process clarity. We identify the institute structure, confirm module scope and prepare data, permissions and rollout stages before full adoption.
Review existing inquiry, admission, student, attendance, fee, examination and reporting processes with your team.
Define school or tuition type, academic years, classes and sections or batches and courses, subjects and operational rules.
Choose the required modules and integrations instead of loading the institute with features it will not use.
Map Admin, Clerk, Teacher, Parent and Student access, then prepare migration files, fee plans and document templates.
Validate high-risk workflows such as admission and fee collection, train users and release modules in manageable stages.
Move your admissions, student records, fees, receipts, reports, and staff access into one simple school management system. Registered users can log in directly, and new schools can contact us on WhatsApp.
The planned architecture treats backend validation, institute isolation, permissions and module access as core requirements across web and future Flutter clients.
Define permitted records and actions for SuperAdmin, Institute Admin, Clerk, Teacher, Parent, Student and optional Driver roles.
Keep every institute’s records, settings, subscriptions and module entitlements separated within the SaaS architecture.
Hide and block disabled modules across menus, dashboards, direct routes, reports, mobile surfaces and backend APIs.
Plan audit logs, backups, background jobs, exports and important change history for accountable operations.
Give institute teams efficient access to operational modules, configuration, data entry and reports.
Provide planned role-specific Parent, Student and Teacher experiences through a common Flutter app codebase.
Keep server-side validation and shared API contracts consistent while web and mobile interfaces remain purpose-built.
The current product foundation prioritizes admission, student, fee and receipt workflows. Additional academic, communication and mobile modules can follow through reviewed implementation phases.
Establish institute configuration, roles, module control, inquiry, admission, students, fee plans, collection and receipts.
Add attendance, teacher records, exams, marks, results, timetable, homework, notices and institute reporting.
Release approved Flutter experiences and optional payment, SMS, WhatsApp, I-Card, certificate or tracking capabilities.
Explore SwiftMaze products for school operations, WhatsApp communication, medical business workflows, and structured team productivity.
Important answers about module coverage, school and tuition workflows, access control, mobile apps and planned integrations.
School ERP software connects administrative, academic and financial workflows such as admissions, student records, attendance, fees, examinations, results, communication and reports in one structured system.
Planned core modules include inquiry, admission, students, parents, classes or batches, teachers, attendance, fees, receipts, offline exams, marks, results, timetable, notices, homework and reports. Availability depends on the implementation phase and modules enabled for the institute.
Yes. Tuition institutes, coaching classes, commerce or science classes and education centers can use batch and course workflows instead of school-specific class and section workflows.
The planned flow captures an inquiry and follow-ups, preserves its history, creates a linked admission for review and creates the student only through an explicit final confirmation.
The planned fee module covers categories, class or batch plans, collection schedules, partial and full payments, discounts, late fees, payment modes, pending amounts, receipt history and fee reports.
Yes. SwiftMaze SuperAdmin controls module enablement institute-wise. Disabled modules should remain unavailable in navigation, dashboards, reports, direct routes, apps and backend APIs.
A common Flutter mobile app with role-specific Parent, Student and Teacher experiences is part of the planned architecture. Exact screens and release timing depend on the approved rollout phase.
These are planned optional integrations. Payment gateway, DLT SMS and WhatsApp provider settings can be configured institute-wise when included in the implementation scope.
The planned v1 scope supports offline exams or tests, subject-wise marks, grades, percentages and Gujarati or English progress-report templates. Online exams and question banks are outside the standard v1 scope.
The architecture is planned around institute-wise data separation, backend-enforced permissions, module entitlements and shared API rules across web and mobile clients.
Excel upload is planned for supported records such as students, marks and fees, with validation required before accepted data is saved.
Yes. We can review the requirement against the reusable ERP architecture and confirm whether it belongs in the core product, an optional module or a separately scoped customization.
The product direction is focused on daily education operations, admission flow, student records, fee collection, and role-based access.