FIRST 30 MINUTESStart here: the safe implementation order
Complete the foundation in this order so later modules inherit the right academic year, classes, users and fee rules. Menu names can vary by role, plan and enabled modules.
Sign in securelyUse your school account, complete 2FA when required and confirm your profile and role.
Set the foundationOpen School Settings; confirm school identity, timezone, session, logo and communication preferences.
Build academicsCreate sessions, classes, sections and subjects before importing or admitting students.
Invite the teamCreate staff accounts, assign least-privilege roles and ask each user to verify access.
Ready when: your academic structure is visible, one test user can sign in, and the school admin can see only the modules they need.
01
School setup & academic structure
Admin · one-timeConfigure the base that drives every report, invoice, attendance list and result.
School SettingsConfirm school name, address, logo, timezone, currency and contact channels.
SessionsCreate or activate the academic session and mark the correct current session.
Classes & sectionsAdd grades, sections, capacity and class teachers; review ordering before admission.
Subjects & rolesMap subjects, assign teachers and test each role with a non-production account.
Control point: never start bulk admission or fee setup until the active session and sections are correct.
02
Admissions, students & guardians
Front desk · adminCreate a clean student record once, then reuse it across fees, attendance, exams, documents and parent communication.
Capture enquiryUse Front Desk → Enquiries for new leads, callbacks, source and follow-up ownership.
Admit studentOpen Students → Admit, select session/class/section and enter required identity and guardian data.
Verify documentsUpload permitted documents, check duplicates and confirm the student status before saving.
Activate accessReview guardian contact, app/portal access and communication consent before sending credentials.
Good practice: search existing records before creating a new student to avoid duplicate fee and attendance histories.
03
Fees, invoices, receipts & dues
Accountant · adminSet the fee rules first, then generate demand and collect against the correct student and session.
Define categoriesCreate fee categories, heads, frequency, concessions and late-fee rules.
Build Fee MasterMap the fee structure to classes or groups; preview before publishing.
Create demandGenerate invoices individually or through the approved bulk workflow; inspect exceptions.
Collect & reconcileRecord offline payments or use Pay Now; verify receipt, gateway status and outstanding balance.
Control point: use reports and dues notices for follow-up; do not edit a settled receipt to correct an unrelated transaction—use the approved correction workflow.
04
Attendance: manual, QR and face workflows
Teacher · adminChoose the method that fits your school, then check exceptions daily instead of waiting for month-end.
Prepare rosterConfirm session, class, section, date and student status before marking.
Mark attendanceUse the teacher attendance screen, QR Attendance or approved face workflow.
Review exceptionsCheck absentees, late arrivals, duplicates and manual corrections with reason.
Notify & reportSend approved parent alerts and review daily/monthly attendance reports.
Privacy: biometric or face features should be enabled only with school approval, consent and the retention policy your institution follows.
05
Exams, marks, rank & report cards
Academic admin · teacherKeep assessment setup, marks entry and publication as separate checkpoints so results are reviewable.
Create examOpen Exams → Create Exam, select session, classes, subjects, dates and maximum marks.
Enter marksTeachers enter marks for their assigned subjects; save drafts and resolve missing entries.
Review resultsCheck totals, grades, rank rules, absent status and class-level anomalies.
Generate & publishPreview report cards, approve internally, then publish to the intended parent/student audience.
Release rule: treat publish results as an approval action. Keep a final review owner and date for every result cycle.
06
AI workspace: questions, papers, quizzes & homework
Teacher · academic adminUse AI to accelerate preparation, not to remove teacher judgement. Review every generated output before assigning or printing it.
Prepare contextChoose class, subject, topic, difficulty, board context and any approved source material.
GenerateUse AI → Generate Questions or QBank; select format such as MCQ, short, long or case study.
Review & editCheck correctness, syllabus alignment, answer keys, difficulty, language and duplication.
Publish safelyMove approved items to the question bank, build a paper/quiz or use homework auto-check with teacher review.
Human-in-the-loop: AI suggestions must be reviewed by an authorised educator before student use or final grading.
07
Teacher workspace, homework & live classes
TeacherTeachers can manage the daily learning loop from class context to feedback and follow-up.
Open dashboardCheck assigned classes, timetable, attendance, pending marks and notices.
Assign workCreate homework or a quiz, attach instructions/material and set due date and audience.
Run classStart or schedule a live class using the approved provider and share the correct join link.
Review progressCheck submissions, mark work, add feedback and flag students needing support.
08
Staff, HR, leave & payroll
HR · adminKeep staff identity, attendance, leave and pay rules consistent across the people workflow.
Create employeeAdd the staff record, department, designation, joining details and required documents.
Configure attendanceSet approved attendance method, holidays, shifts and correction permissions.
Approve leaveReview requests against policy, staffing needs and leave balance before approval.
Run payrollValidate attendance, deductions and salary inputs, then review payroll output before release.
09
Transport, hostel, library, inventory & documents
Operations teamOperational modules work best when master data is maintained before transactions begin.
Set master dataConfigure routes/stops, hostel blocks/rooms, library catalogue or inventory items.
Assign people/assetsMap students and staff to routes, rooms, books, stock or responsible operators.
Record daily eventsCapture trips, bus attendance, issue/return, stock movement or document generation.
Review exceptionsUse history and reports to identify missing returns, stock variance, route issues or expired documents.
10
Superadmin: schools, modules, plans & governance
Superadmin onlySuperadmin controls the SaaS layer. Use these actions carefully because they can affect multiple schools.
Manage schoolsCreate or review institution records, domains, status and responsible contacts.
Control modulesOpen Superadmin → Modules and enable only the features included in a school plan.
Billing & plansReview subscriptions, invoices, plan settings, SMTP and monthly generation controls.
Audit & supportUse activity monitor, audit views, notifications and security controls for traceability.
Production rule: test changes on a controlled school or staging environment first. Never use cleanup, migration or entitlement controls as a first response to a data issue.
HELP & SUPPORTFrequently asked questions
Why can’t I see a module?
Your role, school plan or current route may not include it. Ask a school administrator to verify permissions and module entitlement.
Why are my students missing from a list?
Check the active academic session, class/section assignment, student status and your role’s access scope.
Can I correct a payment, mark or attendance entry?
Use the module’s approved correction or audit workflow. Avoid direct database edits or deleting settled records.
Where do I request onboarding help?
Use Contact TACHY or request a guided demo. Include your school name, role, module and the step where you are blocked.