School Overview Public

School

Complete multi-role user guide for the ERPat School module: a Philippine K-12 Student Information System covering learners, guardians, admissions and enrollment, learner attendance, DepEd-compliant grading (DO8 & MATATAG), report cards, and parent/student portals.

Guide version: r1 Module version: 0.2.0 Updated: 2026-07-22 Estimated time: 5 min 1 views

School

A Philippine K-12 Student Information System built into ERPat — enrol a learner, place them in a section, take daily attendance, compute and release DepEd-compliant grades, print report cards, and let parents and students see the results online.

???? 1 “School” menu group · 14 pages ◈ 42 school_* tables ⚖ DepEd DO8 & MATATAG · RA 10173 ???????? Philippine-market ready

The School module turns ERPat into a compliant Student Information System (SIS) for a Kindergarten-to-Grade-12 institution. It owns the school domain — learners, guardians, admissions, class rosters, learner attendance, grading and report cards, plus parent and student portals — and deliberately reuses the rest of ERPat rather than rebuilding it: the optional LMS bridges to Learn, messaging/announcements/calendar use the core tools, facility tickets use Helpdesk, and portal logins reuse the existing customer account. The slug is school, screens live under the /school URL prefix, and the module is enabled with the module_school setting.

????
This guide is written for people, by role. Everyone should skim Getting Started and Core Concepts once, then jump to the Role Playbook that matches your job — Registrar, Teacher/Adviser, Principal, Guidance/Clinic, System Admin, Parent, Student, or Gate Security. The Roles & Access Map shows who does what and which permission unlocks it.

Who this system is for

A school is many jobs at once. School gives each of them one focused workspace, gated by permission so people see only what they should. Pick your playbook:


The learner lifecycle in 60 seconds

Set up
School year, sections, subjects
Admit
Application → requirements → approve
Enrol
Roster placement in a section
Attend
Daily section register
Grade
Draft → submitted → approved → released
Report
Report card + portals

The registrar sets up the academic structure (school year, grading periods, sections, subjects, rooms — grade levels and SHS tracks/strands are pre-seeded), then admits a learner by processing an application through its document checklist to approval, which materialises the roster enrollment. Teachers take daily attendance and encode grades on the class record; the head approves and releases. Only released grades reach report cards and the parent/student portals.

⚠️
Two rules protect the whole system. (1) Segregation of duties on grades — the teacher who submits (school_grade_release) can never be the one who approves & releases (school_grade_approve). (2) The Data Privacy gate — a parent can only ever see a child whose guardian link has been verified, and only released grades. Both are enforced in code, not by convention. See Data Privacy & Safeguarding.

Explore the guide

Start here

Operate the system

Administer & comply

Reference


What the module ships with

14
Staff back-office pages
2
Public portals (parent · student)
2
Grading policies (DO8 · MATATAG)
42
school_* database tables

The staff sidebar carries a single School group with a permission-gated child per page: Dashboard, Enrollment, Learners, Guardians, Personnel, Academics, LMS Bridge, Attendance, Grades, Communication, Support, Visitors, Facilities, Reports, Settings. Kinder–G12 grade levels, SHS tracks and strands, and the DO8 subject-group weight buckets are seeded reference data. Sensitive domains — learner health and child-protection / anti-bullying cases — are segregated behind restricted permits and audited on every read.

????️
Scope & honesty. This guide documents what the module does today (version 0.2.0). The SF-style exports and the LIS validator are internal preparation and validation aids only — the official school forms and submission stay in DepEd LIS/EBEIS; the module never submits to or replaces them. The LMS bridge and facility tickets are fail-safe: they degrade to a notice when Learn / Helpdesk is disabled, never a fatal error.
Was this guide helpful?

Report a content problem