Frequently Asked Questions

Admin usually works across People, Academics, Communication, Reports, Settings, Transport overview, and high-level Finance/Inventory monitoring. This role is not only for data entry; it is also for coordination between departments. Because Admin can see the full picture, it can quickly identify where a problem starts and where it should be fixed. That is why this role is critical in large schools.

Admin should first create the academic session/year, then configure standards, sections, classes, subjects, and teacher mapping. After that, user role permissions should be verified so each role sees the correct menus and actions. This setup order is important because many modules depend on it. If done correctly at the start, daily operations become smoother and support issues become much lower.

Admin should check four key points: role permission, class/subject assignment, active session/term filter, and workflow stage. Most issues are caused by one of these, not by system failure. Once corrected, users usually see the missing screen or record immediately. This troubleshooting approach saves a lot of time and avoids unnecessary confusion.

Managers typically track pending approvals, academic progress flow, communication updates, and operational dashboard signals. They use these views to detect where delays are happening and which team needs support. This is very useful when many departments are active at the same time. It helps maintain service continuity.

Manager checks who owns the current step, what information is missing, and what decision is pending. Then Manager follows up directly and closes the handoff gap between roles. If the delay is policy-sensitive or recurring, it is escalated to Admin quickly. This approach prevents small delays from becoming large backlogs.

Manager clarifies ownership based on the current status in workflow and role responsibility. This removes repeated back-and-forth and stops duplicate effort. Manager may also standardize quick guidance so teams follow the same process next time. Over time, this reduces confusion significantly.

The primary areas are Finance/Fees, payment history, receipts, dues, and financial reports. Where enabled, Accountant also monitors inventory requisitions and movement summaries to ensure resource usage aligns with cost control. These modules help the school make practical decisions using real data. It is not only accounting — it is planning support too.

Accountant should first verify student mapping, payment timeline, and receipt history before responding. Then provide a clear explanation: what was paid, what remains due, and what reference supports it. This reduces repeat visits and confusion. Clear, evidence-based response builds trust with families.

Accountant should check transaction reference, date, student mapping, active session filters, and whether save/receipt steps completed successfully. In many cases, one mapping or filter issue causes the mismatch. After correction, record visibility returns to normal. This is why careful entry and verification at transaction time is important.

Teachers mainly work in homework, exam setup/papers, marks entry, and class-related communication features. Access depends on mapping, so each teacher sees only assigned contexts. This keeps workflows secure and relevant. It also prevents cross-class mistakes.

Teacher should create homework with correct class-subject selection, clear instructions, and accurate due dates. If the school uses approval flow, teacher should track status and avoid assuming student visibility before approval. This avoids confusion in classrooms. Consistent homework quality improves learning discipline.

Teacher should check term/session filters first, then verify assignment mapping and exam stage. Most missing-data cases come from one of these setup dependencies. If still unresolved, ask Admin to validate mapping and access configuration. This is the fastest way to fix visibility issues.

Teacher should enter marks carefully, review before submit, and confirm totals/coverage are complete. After submission, edit rights may reduce depending on stage. So pre-submit checking is essential. Good marks discipline prevents result correction issues later.

Book inventory, book requests/requisitions, issue-return tracking, and circulation status screens are usually core. These modules show what is available, requested, issued, overdue, or returned. With consistent use, librarians can keep resource access smooth for everyone.

Librarian should verify request details and stock availability, then process through approve/reject/fulfill status flow. Every status should be updated clearly so students and staff understand current state. This reduces repeat follow-up and queue confusion. Structured processing improves service speed.

Librarian should update status with a clear reason and give the next possible action (waitlist/resubmit/alternative resource). Transparent communication is important so users know what to expect. This avoids repeated requests and frustration.

Receptionist typically uses visitor/front-office records, request/requisition screens, and selected communication support views. These modules make front-desk actions traceable rather than informal. It improves clarity for both requesters and approvers.

Requests should include clear item/service name, quantity, purpose, and urgency if applicable. Better request quality leads to faster decisions and fewer follow-up questions. This is especially important during busy school hours.

Receptionist should check status ownership, confirm details are complete, and follow up with the current approver role using the request reference. This keeps movement active and avoids silent delays. Good follow-up discipline improves closure rate.

Drivers mainly use trip and assignment views with status update actions. These screens guide route execution and show current transport responsibilities. Correct usage helps school transport teams coordinate effectively.

Driver should start trip in system, follow assigned route, update progress states, and close trip after completion. This gives clear operational visibility to school staff. Consistent updates reduce uncertainty.

Driver should follow updated assignment from authorized source and continue status updates under new context. Off-system manual adjustments should be avoided because they create visibility gaps. Controlled change keeps records trustworthy.

Homework/tasks, notices/events, results view, and personal academic pages are the main student-facing areas. These modules help students track what to do and what is completed. Regular use improves planning.

Students should check deadlines, submission status, and teacher updates regularly. Using one place to monitor pending and completed tasks reduces missed work. This creates better learning discipline.

Student should first check active session/term and whether item is approved/published. If still missing, report with details (class, subject, date) to teacher or support. Most issues are stage or context related.