1. Introduction and Scope

This guide is a comprehensive, in-depth resource for administrators, principals, teachers, parents and local facilitators who use the MSTAR (ePunjab) school management portal. It consolidates practical SOPs, step‑by‑step workflows, troubleshooting playbooks, templates and publishing guidance so you can operate the portal reliably and publish safe help content for your community. It explains the portal’s modules, step‑by‑step procedures for admission, teacher records, attendance, transfers and payslips, and provides practical advice for daily operations, security and troubleshooting.

Important: This guide uses anonymized examples and always blur or redact sensitive fields.

2. Portal Structure and User Roles

2.1 High‑level architecture

MSTAR is designed as a modular MIS (Management Information System) for school administration. Typical modules include:

• Admission and student registration
• Student master and personal details
• Teacher profiles and service records
• Attendance (student and teacher)
• Examination and result management
• Payslip and payroll interfaces
• Reports and MIS dashboards
• Integration layer for state services (document storage, notifications)

2.2 User roles and permissions

Role-based access control is essential. Define responsibilities and permissions clearly and document them in a role matrix. Typical roles include:

• State Admin: master data, policy configuration, statewide reporting and system updates.
• District Admin: district‑level validation, reporting, vacancy management and escalations.
• Block/Cluster Admin: local monitoring, training coordination and first‑level support.
• School Admin / Principal: school‑level data entry, verification, attendance publishing and local MIS exports.
• Teacher: personal profile management, leave application, payslip access (read only) and attendance marking where policy allows.
• Parent / Student: admission status, attendance and result view (read only).
• CSC VLE: facilitation for parents without internet access; limited data entry under supervision.

2.3 Data flows and integrations

Understand how data flows between modules: admissions feed the student master; attendance feeds payroll and MIS; transfers update service records and payroll routing. Integration points often include state document stores, SMS gateways for OTP, and bank interfaces for salary disbursal. Document each integration and maintain a mapping table for fields exchanged between systems.

2.4 Governance and auditability

Maintain an audit log for critical actions: document verification, attendance publishing, payslip generation, transfer approvals and role changes. Use exportable logs and retain them per state retention policy. Implement quarterly audits and a simple checklist for auditors to verify key controls.

3. Admission Module — Complete Step‑by‑Step Guide

3.1 Overview

The Admission module supports online registration, document upload, verification, seat allocation and final confirmation. It is used by parents, school staff and district officials. A published admission calendar, clear eligibility criteria and a small helpdesk reduce errors and improve the user experience.

3.2 Pre‑admission preparation (for schools)

Before the admission window opens, schools should:

• Publish the admission calendar and eligibility criteria on the school notice board and portal.
• Assign an Admission Coordinator and publish their internal contact for district use only.
• Prepare a document checklist and sample redacted screenshots to guide parents.
• Set up a helpdesk or CSC facilitation window for parents who need scanning or upload assistance.
• Test the portal’s upload limits and provide guidance on acceptable file types and sizes.

3.3 Parent step‑by‑step: registering a new admission

1. Create an account: Visit the portal login page and register using a mobile number or email. Verify with OTP and keep the login credentials secure.
2. Start New Admission: Choose the academic year and class for admission and fill the student details (name, DOB, parent details, category).
3. Upload documents: Birth certificate, residence proof, passport photo and previous school Transfer Certificate (if applicable). Use allowed formats (JPG, PNG, PDF) and keep file sizes within limits.
4. Submit application: Note the application ID and print or save the confirmation receipt for future reference.
5. Track status: Use the portal to track verification status and respond to any remarks from the school promptly.
6. Final confirmation: After seat allotment, confirm admission and follow the school’s instructions for final documentation submission and fee payment if applicable.

3.4 Document upload best practices

• Scan documents at 150–200 DPI to keep file sizes small but legible.
• Use PDF for multi‑page documents and JPG/PNG for single images.
• Compress images if the portal rejects due to size limits; avoid over‑compression that reduces legibility.
• Redact or blur unrelated personal identifiers before sharing publicly or in training materials.

3.5 Common admission errors and fixes

• OTP not received: Check network and DND settings; try an alternate number or use CSC facilitation.
• Document rejected: Reformat or compress the file; ensure correct file type and legibility.
• Duplicate applications: Contact district helpdesk to merge or remove duplicates; keep application IDs handy.
• DOB mismatch: Provide original birth certificate to school for correction and follow the portal correction workflow.

3.6 School admin checklist for admissions

• Verify documents against the checklist and mark verification actions in the portal.
• Keep a local log of application IDs and verification timestamps for audit.
• Publish a short FAQ and sample redacted screenshots to reduce common mistakes.
• Schedule weekly reconciliation of pending applications and unresolved remarks.

Caption: Blurred login dashboard screenshot — all personal identifiers redacted. Both Login and dashboard screenshot.

4. Teacher Module — Profiles, Service Records, Leave and Appraisal

4.1 Teacher profile essentials

The teacher profile is the single source of truth for service history, payroll routing and HR actions. Mandatory fields typically include full name, employee ID, date of birth, appointment date, designation, qualifications and bank details. Keep scanned appointment orders and qualification certificates attached to the profile for audit readiness.

4.2 Updating and correcting profile data

1. Teacher logs in and navigates to Profile → Edit.
2. Update fields and attach supporting documents (appointment order, qualification certificates).
3. Submit for school admin verification; admin forwards to district if required. Track the verification status and keep copies of supporting documents locally.

4.3 Service history and record keeping

Service history should capture postings, promotions, increments, leaves and disciplinary actions. For audit readiness, attach scanned copies of orders and approvals to each service event and maintain a local backup of critical documents. Use consistent naming conventions for scanned files (e.g., EMPID_YYYYMMDD_OrderType.pdf).

4.4 Leave management workflow

• Teacher applies for leave via portal with start and end dates and reason.
• Attach supporting documents for medical leave where required.
• Principal reviews and approves or rejects; district HR may be involved for long leaves.
• Leave balance is updated automatically; encashment rules apply as per state policy.

4.5 Appraisal and promotion

Appraisal modules capture performance indicators such as student outcomes, attendance, training participation and self‑assessment. Promotion cycles follow state rules and DPC procedures. Keep training certificates and appraisal records uploaded to the profile to support promotion claims and arrear calculations. Maintain a folder of appraisal evidence mapped to appraisal criteria for each review cycle.

4.6 Appraisal evidence checklist

• Training certificates (with dates and provider)
• Student outcome summaries (class-level improvements, sample assessments)
• Attendance records and punctuality logs
• Peer and principal feedback forms (redacted)
• Self-assessment forms and improvement plans

Caption: Blurred MSTAR school dashboard screenshot. Both Login and dashboard screenshot.

Appraisal modules capture performance indicators such as student outcomes, attendance, training participation and self‑assessment. Promotion cycles follow state rules and DPC procedures.

5. Attendance Management — Student and Teacher

5.1 Attendance capture methods

Attendance can be recorded in several ways depending on local infrastructure: manual entry by class teachers or school admins, teacher self‑entry where policy allows, biometric devices integrated with the portal, or mobile OTP for remote staff and field visits. Choose a primary method and a fallback method and document both in the school SOP.

5.2 Daily attendance process

1. Open Attendance module each school day before classes begin.
2. Mark present/absent for each class and teacher.
3. Save and publish daily summary.
4. Resolve exceptions (late entries, device failures) via correction requests and log reasons for audit.

5.3 Monthly consolidation and reporting

At month end, generate consolidated attendance reports for students and staff. These reports feed into payroll (for leave deductions) and into state MIS for monitoring chronic absenteeism. Export CSV/Excel for local records and audits and reconcile totals against class registers.

5.4 Handling biometric or device failures

• Switch to manual entry and log the reason in the portal.
• Raise a vendor support ticket and record the ticket ID.
• Use the correction workflow to reconcile biometric gaps once the device is fixed; maintain a reconciliation sheet for payroll.

5.5 Attendance reconciliation template (example)

6. Transfer and Posting Procedures

6.1 Transfer policy fundamentals

Transfers are governed by state rules which define grounds (personal, medical, spouse posting), seniority, vacancy lists and reservation categories. The portal supports online transfer applications and vacancy publishing. Always consult the latest state circular for policy details and maintain a local copy of relevant circulars linked to the employee profile.

6.2 Applying for transfer — step by step

1. Open Transfer module and select transfer type (inter‑district, intra‑district, compassionate, etc.).
2. Fill grounds and attach supporting documents (medical certificate, spouse posting order).
3. Submit application and note the application ID for tracking.
4. Track status through the approval workflow and respond to any remarks promptly.

6.3 Vacancy lists and seniority

Districts publish vacancy lists and seniority rosters. Applicants should verify their seniority position and check the vacancy list before applying. Use the portal’s vacancy search and filter options to find suitable openings and maintain a local copy of vacancy lists for reference.

6.4 Relieving and joining formalities

Once transfer is approved, the relieving school issues a relieving certificate and the receiving school issues a joining certificate. Update the portal with relieving and joining dates to keep service records accurate. Ensure handover of responsibilities and update attendance and payroll records accordingly to avoid salary gaps.

6.5 Relieving/joining checklist

• Relieving certificate issued and uploaded
• Joining certificate uploaded by receiving school
• Attendance and payroll updated for relieving/joining dates
• Handover notes and asset return recorded

7. Payslip and Payroll Management

7.1 Payslip components explained

Payslips typically include basic pay, Dearness Allowance (DA), House Rent Allowance (HRA), other allowances (special, transport), deductions (PF, TDS, loan recoveries) and net pay. Maintain a component mapping table so payroll components are consistent across months and systems.

7.2 Accessing and downloading payslips

1. Teacher logs in and navigates to Payslip section.
2. Select month and year and click Download PDF.
3. For discrepancies, raise a payroll ticket with supporting documents (orders, bank statements).

7.3 Arrears, corrections and claims

Arrears arise from delayed increments, promotions or corrections. Submit an arrear claim with a calculation sheet and supporting orders. Finance will process the claim and route payment after approvals. Keep a copy of the claim and ticket ID for follow up and track the claim through the finance workflow until payment is posted.

7.4 Payroll reconciliation best practices

• Finance officers should reconcile payroll entries with bank statements monthly.
• Maintain a voucher trail and attach scanned supporting documents to each voucher.
• Use standardized component codes and maintain a mapping table for audit.

7.5 Sample arrear claim checklist

• Arrear calculation sheet (detailed)
• Supporting orders (promotion/increment)
• Bank details verification
• Ticket ID and follow-up notes

8. School Admin Dashboards and MIS

8.1 Key dashboards and what they show

Dashboards provide quick insights for school leadership. Typical dashboards include:

• Enrollment Dashboard: total students, gender ratio, category distribution and trends over time.
• Attendance Dashboard: daily attendance %, chronic absentee list and class‑wise comparisons.
• Staffing Dashboard: sanctioned vs actual teachers, vacancies and upcoming retirements.
• Exam Dashboard: marks distribution, subject performance and pass/fail analytics.

8.2 Common MIS reports

• Monthly attendance summary
• Exam results and subject analysis
• Infrastructure and facilities report
• Staff deployment and vacancy reports

8.3 Exporting data and audit readiness

Use CSV/Excel export for MIS reports. Ensure column mapping is consistent and include UDISE codes and component codes for cross‑system reconciliation. Keep a local, encrypted backup of monthly exports for audit purposes and maintain a retention policy for exported files.

8.4 Export checklist

• Confirm column mapping and headers
• Include UDISE and component codes
• Encrypt exported files and store in secure location
• Log export date, user and purpose for audit

9. Business Rules, School Setup and Admin Tasks

Business Rules control school-level configuration. Document each rule and provide a one-line purpose statement for new admins.

• Manage Holidays: Business Rules → Manage Holidays
• Roll No. Generation: Business Rules → Roll No. Generation
• Manage Class Sections: Business Rules → Manage Class Sections
• School Setup: Business Rules → School‑Institute Setup
• Optional Subjects Allocation: Activities → Optional Subjects Allocation
• Class Monitors: Activities → Class Monitors

Keep a short SOP for each Business Rules task with redacted screenshots and a one‑line purpose statement so new admins can onboard quickly.

10. Security, Privacy and Safe Publishing

10.1 Data security for portal users

• Use strong passwords and change them periodically.
• Enable two‑factor authentication where available.
• Limit administrative access and use role‑based permissions.
• Keep local backups encrypted and restrict physical access to devices.

10.2 Safe publishing guidelines for bloggers and admins

If you publish tutorials or screenshots from the portal, follow these rules:

• Redact personal data: Remove or blur names, phone numbers, email addresses, bank details and any unique identifiers.
• Use sample data: Create anonymized examples rather than real records.
• Respect copyright: Do not reproduce official documents in full; link to official circulars instead.
• AdSense compliance: Avoid publishing sensitive personal information; follow AdSense content policies.

10.3 How to blur sensitive fields (step‑by‑step)

1. Open the screenshot in an editor (Paint, GIMP, Photoshop, or an online editor).
2. Select phone numbers, emails, IDs and bank details and apply a blur or solid fill.
3. Save the edited image as a new file and use that file in your post.

11. Troubleshooting and Escalation

11.1 Common technical problems

• Login failures due to OTP or locked accounts
• File upload errors because of size or format
• Slow report generation during peak hours
• Payslip mismatches due to unsynced payroll data

11.2 Stepwise troubleshooting

1. Clear browser cache and cookies; try incognito mode.
2. Check portal announcements for scheduled maintenance.
3. Verify file formats and compress images if needed.
4. Raise a support ticket with redacted screenshots and application IDs.
5. Escalate to district IT cell if unresolved within SLA.

11.3 Escalation workflow and record keeping

Maintain a clear escalation path and record ticket IDs and response timestamps for audit:

• School IT Coordinator → Block IT Support → District IT Cell → State Helpdesk
• Keep a local log of tickets and follow up weekly until resolution.

11.4 Sample support ticket template

12. Best Practices, Training and Rollout

12.1 For state and district administrators

• Adopt a phased rollout with pilot blocks and a clear success criteria checklist.
• Publish a training calendar and conduct hands‑on sessions for school admins and IT coordinators.
• Provide short video tutorials and one‑page quick reference guides for common tasks.
• Collect feedback and maintain a portal improvement tracker with prioritized fixes.

12.2 For schools

• Appoint a School IT Coordinator and maintain a local SOP document.
• Maintain a document checklist for admissions and finance.
• Schedule monthly reconciliation meetings for attendance and payroll.

12.3 For teachers and parents

• Keep personal details updated and verify payslips monthly.
• Use CSCs for assistance if internet access is limited.
• Report discrepancies early to avoid delays in salary or scholarship payments.

13. Comprehensive FAQ

The following FAQ covers the most common questions users ask about MSTAR ePunjab. This section is intentionally extensive and ready to publish. Add local contact points and state circular references when publishing.

Admission & Accounts

• How do I create a parent account for admission? Register with mobile/email, verify OTP and complete the New Admission form. Save the application ID for tracking.
• What documents are required for admission? Birth certificate, residence proof, passport photo and previous TC if applicable.
• What if OTP is not received? Check network and DND settings, try alternate number and contact portal support if issue persists.

Attendance & Devices

• How to mark daily attendance? Open Attendance module, mark present/absent for each class and teacher, save and publish daily summary.
• How to handle biometric failures? Switch to manual entry, log the reason, raise a vendor ticket and reconcile attendance later.

Payslip & Payroll

• How can a teacher download payslip? Login → Payslip section → Select month → Download PDF. For discrepancies, raise a payroll ticket with supporting documents.
• What if salary is not credited? Verify bank details in your profile, check payment status and raise a ticket with finance.

Transfers & Service Records

• How to apply for transfer? Use Transfer module, attach documents, submit and track application ID.
• How to correct a teacher's service record? Submit a correction request with supporting documents to the school admin who forwards it to district.

Admin & MIS

• How to export exam results? Exam results can be exported from Exam module in CSV/Excel format.
• How to view MIS reports? Navigate to MIS Reports section for category, class and department wise reports.

14. Disclaimer and Conclusion

14.1 Disclaimer

This guide is for informational purposes only. Portal features, policies and workflows may change. For official procedures, circulars and financial rules consult the Department of School Education, Punjab and your district office. The examples in this guide use anonymized data. Do not publish or share real personal identifiers or financial details on public pages.

14.2 Conclusion

MSTAR ePunjab is a powerful tool for modernizing school administration. When implemented with clear SOPs, training and secure practices it improves transparency, speeds up administrative tasks and simplifies record keeping. This guide provides a practical roadmap for administrators, teachers and parents to use the portal effectively while protecting sensitive data.