Teacher & Adviser Playbook
Two jobs make up almost your entire week in ERPat School: taking daily attendance for your sections, and encoding grades on the class record each quarter. This playbook gives you the exact click paths for both, explains how the grading engine turns your three scores into a DepEd-compliant grade, and — importantly — draws the line the system enforces: you submit grades, but you never release them. That final step belongs to the school head.
Who you are
You are a core ERPat staff user who has been registered as school personnel by
the admin (on school/personnel) — that registration marks you as school staff
and, if applicable, as adviser-eligible. Advisers are then assigned to a section in
Academic Structure. As a teacher you:
- Take the daily attendance register for the sections you teach.
- Encode Written Work, Performance Task and Quarterly Assessment scores on the class record for each section + subject + term.
- Submit a finished class record so the school head can approve and release it.
Permissions you need
| Permission | What it lets you do |
|---|---|
school | See the School menu and Dashboard. |
school_attendance + _update | Open the Attendance page; _update lets you save the register (mark and bulk-save). |
school_grades + _update | Open the Grades page and the class record; _update lets you save scores. |
school_grade_release | Submit grades for release. This is your final grading action — it moves a class record from draft to submitted. |
school_grade_approve. That permit — which
approves and releases grades — is deliberately held by a different person
(the school head). The system will not let the same person submit and release. This is
segregation of duties, and it protects you as much as the
learner.
Your screens
school/attendance — the per-section daily register plus a records browser.
school/grades — the class record where you encode and submit quarter grades.
SOP — Take daily attendance
School attendance in ERPat is its own thing — it is separate from the employee / biometric HR attendance. You mark learners against a section's roster for a given day.
Pick section, date and session
Go to
school/attendance. Choose the section, the date, and the session (defaults to whole day). The section's current-SY enrolled roster loads into a register grid.Mark each learner
Set every learner to present, absent, late, or excused. For absent or excused, choose a reason from the list; for late, enter a time in.
Bulk-save the register
Click save once to record the whole grid at once (needs
school_attendance_update).Review saved records
Use the records browser to see saved rows — date, learner, section, status, reason, time in, and who encoded it — filterable by status.
SOP — Encode grades on the class record
A class record is one section + subject + term (grading period). You encode three percentage scores per learner and the engine does the rest.
Open the class record
Go to
school/gradesand pick the section, subject and term. The roster loads with the resolved grading scheme and its WW/PT/QA weights shown.Enter the three scores per learner
For each learner, type the percentage scores (0–100) for Written Work (WW), Performance Task (PT) and Quarterly Assessment (QA).
Save
Saving (needs
school_grades_update) computes each learner's weighted score, initial grade, and the final transmuted quarterly grade via the grade engine. You can re-open and re-save as often as you like — while the record is still draft.
How your three scores become a grade
You never do the arithmetic. The engine resolves the applicable scheme (which policy, which weights) from configuration by the subject's subject group, the grade level, and the school year, then:
- Weighted score
- Each component is multiplied by its policy weight (e.g. under DO8 a Science subject uses WW 40% / PT 40% / QA 20%).
- Initial grade
- The weighted components are summed into a raw “initial grade”.
- Transmuted final
- The initial grade is passed through the policy's transmutation rule to the final grade — a whole number, floored at 60 and capped at 100.
The final grade carries a descriptor. Passing is 75.
| Final grade | Descriptor |
|---|---|
| 90–100 | Outstanding |
| 85–89 | Very Satisfactory |
| 80–84 | Satisfactory |
| 75–79 | Fairly Satisfactory |
| Below 75 | Did Not Meet Expectations |
SOP — Submit grades for release
When a class record is complete and correct, hand it off. This is the last thing you do to a class record.
Final check while it is still draft
Confirm every learner has all three scores and the computed grades look right. Once you submit, you cannot edit the record — it leaves draft.
Submit
Use Submit grades for release (needs
school_grade_release). The record moves draft → submitted, and the transition is logged (you may add remarks).Hand off to the head
From here the school head approves and then releases the grades. Only released grades reach report cards and the parent/student portals.
Adviser extras
If you are a section's adviser, you also carry the whole-section view:
- Your roster is the section's current-SY enrolled learners — the same set that drives your attendance register and every class record for that section.
- Report-card context. When the head generates a report card, it aggregates each learner's released quarterly grades across their subjects into a general average and a Promoted/Retained remark. Your job is to make sure your subject grades are submitted on time so the card is complete.
If your section is linked to a Learn course
Your school may bridge a section to an online Learn course through the LMS Bridge. When that happens, the section roster can be pushed into the course as enrollments — but only learners who already have a student portal account are enrolled; the rest are reported as skipped. The bridge is fail-safe: if the Learn module is turned off, the page simply shows a notice and your grading and attendance are unaffected.
Tips & common mistakes
| What you see | What it means | What to do |
|---|---|---|
| “This class record is locked.” | The record is no longer in draft (it was submitted, approved, or released). | Editing is only allowed while draft. Ask the head to hold/return it, or correct at report-card time — see FAQ. |
| “No grading scheme configured.” | There is no scheme for that grade level / subject group / school year, so the engine can't compute. | Ask the admin to configure the scheme; check the Schemes tab (Administration). |
| A learner is missing from the class record. | They aren't on the section's approved current-SY roster. | Confirm their enrollment with the registrar. |
| Attendance register is empty. | No approved enrollments for that section in the current school year. | Check the enrollment/roster; the current SY is set in Academic Structure. |
| “I submitted but a grade is wrong.” | Submitting takes the record out of your control. | Ask the head not to release; the record can be handled before release — see FAQ. |
- Save often while drafting — the record is fully editable until you submit, so there's no harm in partial saves.
- Enter all three scores (WW, PT, QA) before you submit; a blank component skews the computed grade.
- Take attendance the same day. The records browser makes it easy to see a gap; a missed day is harder to reconstruct later.
- Don't confuse the two attendances. Marking a learner here has nothing to do with the HR/biometric time logs.
Where to next
DO8 vs MATATAG, weights, transmutation, descriptors, and the release governance in full.
Every field on the register, the reasons list, and the records browser.
How released grades become an SF9-style card — the destination of your work.
What happens after you submit: approval and release, held by a separate person.
Linking a section to a Learn course, and the core messaging/announcement tools.
The recommended permission preset for a teacher/adviser.