alrahma_sunday_school/docs/attendance-policy-implementation-plan.md

# Attendance and Tardiness Policy Implementation Plan

## 1. Purpose

Implement a consistent, documented process that:

- records attendance for every scheduled Sunday class;
- records arrival time and annual tardy counts separately from attendance outcomes;
- makes it easy for parents or guardians to report an absence in advance;
- enforces the 10:00 AM start time, tardy-slip process, and 10:10 AM door rule consistently;
- identifies unnotified absence patterns using the policy's rolling time windows;
- sends the correct follow-up at each escalation level;
- gives students a clear process for completing missed work; and
- prevents a student from being sent home or removed based on incomplete or incorrect data.

## 2. Policy Rules to Implement

### 2.1 Attendance outcomes

Assign exactly one attendance outcome to each enrolled student for each scheduled Sunday session. Record punctuality separately under Section 2.4 so a student can be both present and tardy.

| Status | Definition | Counts toward escalation? |
| --- | --- | --- |
| Present | Student attended the session. | No |
| Notified absence | Parent or guardian informed the administration before the session through an approved channel. | No |
| Unnotified absence | Student was absent and no valid advance notice was recorded by the attendance cutoff. | Yes |
| Tardy-generated absence | Student arrived after 10:10 AM without timely late-arrival notice, or was sent home on the fifth or later late showing in the school year. | Pending leadership decision in Section 3 |
| Pending verification | Attendance or notice is disputed or incomplete. | No, until reviewed |
| Not enrolled / withdrawn | Student was not expected to attend that session. | No |

School closures and Sundays on which a student had no scheduled class are not attendance sessions and must not appear as absences.

### 2.2 Escalation thresholds

Evaluate unnotified absences after attendance and advance notices have been reconciled for each Sunday.

| Level | Trigger | Required action |
| --- | --- | --- |
| 1 — Teacher follow-up | One unnotified absence | The teacher asks for the reason when the student next attends and assigns a deadline for missed work. |
| 2 — Administrative follow-up | Two consecutive unnotified absences **or** at least two unnotified absences in the latest three scheduled sessions | Administration calls and emails the parent or guardian. |
| 3 — Final warning | Three consecutive unnotified absences **or** at least three unnotified absences in the latest four scheduled sessions | Administration issues a final warning by call, text, and email. |
| 4 — Removal review | Four consecutive unnotified absences **or** at least four unnotified absences in the latest five scheduled sessions | Administration reviews the record and, if confirmed, permanently removes the student and documents the decision. |

### 2.3 Attendance rule interpretation

- A "week" in the policy means a **scheduled Sunday session**, not a calendar week.
- A rolling window includes the current session and the immediately preceding scheduled sessions for which the student was enrolled.
- Only **unnotified absences** count toward Levels 2–4.
- If several thresholds are met at the same evaluation, apply only the highest newly reached level; do not send several escalation messages for the same event.
- Send each level once per attendance incident sequence. Log the date, method, recipient, sender, and delivery result.
- A present or notified-absence status breaks a consecutive-unnotified-absence sequence, but older unnotified absences may still count in a rolling window.
- The system may recommend Level 4, but it must not remove a student automatically. An authorized administrator must verify attendance, notice records, enrollment dates, and prior communications before approving removal.
- If an attendance status is corrected, recalculate the student's current escalation level and cancel any action that is no longer justified.

### 2.4 Tardiness rules

Use the school's official local time and record the actual arrival time at the administration desk.

| Arrival condition | Required action | Attendance outcome | Annual 10:00–10:10 late count |
| --- | --- | --- | --- |
| At or before 10:00 AM | Admit normally. | Present | No change |
| After 10:00 AM and at or before 10:10 AM; first through fourth late showing of the school year | Administration issues a numbered tardy slip; student gives it to the teacher before entering. | Present | Increase by one |
| After 10:00 AM and at or before 10:10 AM; fifth or later late showing of the school year | Administration does not issue classroom admission; student is released back to the parent or guardian and marked absent. | Tardy-generated absence | Increase by one |
| After 10:10 AM; qualifying late-arrival notice received before 10:10 AM | Administration verifies the notice, issues a tardy slip, and admits the student under the approved-late-arrival procedure. | Present | Do not change unless leadership adopts a different rule |
| After 10:10 AM; no qualifying late-arrival notice received before 10:10 AM | Do not admit; release the student back to the parent or guardian and mark the student absent. | Tardy-generated absence | No change |
| Arrival time or notice is disputed | Hold the consequence for administrator review. | Pending verification | No change until resolved |

Additional controls:

- "After 10:00 AM" means any verified arrival time later than `10:00:00`; an arrival recorded exactly at 10:00 AM is on time.
- "After 10:10 AM" means any verified arrival time later than `10:10:00`; the doors are locked immediately after that boundary.
- The annual late count resets on the first scheduled session of each defined school year, not on January 1 unless the school year does so.
- The first four late showings are forgiven only in the sense that the student is admitted; they must still be recorded.
- The fifth and every later qualifying late showing in that school year results in being sent home and marked absent unless an approved exception applies.
- Administration—not the classroom teacher—determines admission and issues the tardy slip.
- A teacher must not admit a late student without a valid tardy slip and must return any questionable case to administration without disrupting the class.
- A student who is not admitted must remain with or be released directly to the responsible parent or guardian; staff must never leave the student unattended outside locked doors.
- Corrections to arrival time or notice status must immediately recalculate the annual late count and reverse any unsupported consequence.

## 3. Decisions Required Before Launch

The policy text leaves several operational questions unanswered. School leadership should approve and publish the answers before enforcement begins.

1. **Advance-notice cutoff:** Define the exact deadline on Sunday and the school's time zone.
2. **Late notice:** Decide whether notice received after the cutoff can be accepted and who may approve the change.
3. **Acceptable reasons:** Decide whether any timely notice is sufficient or whether only specified reasons qualify.
4. **Emergency exception:** Define how a parent can request reconsideration when advance notice was impossible.
5. **Communication failure:** Decide what happens when an email bounces, a text fails, or a phone number is disconnected.
6. **Removal authority and appeal:** Name the role that approves removal, the effective date, and any reconsideration or appeal process.
7. **Re-enrollment:** State whether and when a removed student may apply again.
8. **Existing records:** Set a clean enforcement start date and decide whether earlier absences count.
9. **Record retention:** Establish how long attendance, notice, and communication records are kept.
10. **Tardy-generated absence classification:** Decide explicitly whether an absence created by the tardy policy counts as an `Unnotified absence` for Levels 1–4. The tardy policy says it counts as an absence, while the attendance escalation policy counts only unnotified absences.
11. **Pre-reported arrivals after 10:10 AM:** Confirm that these students are admitted with a tardy slip and decide whether such arrivals count toward the four annual late showings; the current text defines those showings only as arrivals between 10:00 AM and 10:10 AM.
12. **Notice timing at exactly 10:10 AM:** Confirm whether a notice timestamped exactly 10:10 AM qualifies. A strict reading of "before 10:10 AM" excludes it; if leadership intends "by 10:10 AM," the published policy and system rule should say so explicitly.
13. **Tardy exceptions:** Define whether transportation emergencies, disability accommodations, severe weather, or other approved circumstances can prevent or reverse a tardy consequence.
14. **Clock and arrival point:** Designate the official time source and define whether arrival means reaching school property, the locked door, or the administration desk.
15. **Safe release:** Approve the identity-verification and custody procedure for returning a student to a parent or guardian.

Until these decisions are approved, disputed cases should remain `Pending verification` and must not advance to removal.

## 4. Roles and Responsibilities

| Role | Responsibility |
| --- | --- |
| Parent or guardian | Submit absence notice through the portal, phone, text, WhatsApp, or email; submit late-arrival notice through the portal, email, text, or WhatsApp before the approved cutoff; keep contact information current; support completion of missed work. |
| Teacher | Record attendance promptly; require a tardy slip before admitting a late student; verify questionable entries; speak with students after an unnotified absence; assign and track makeup work. |
| Attendance coordinator | Consolidate absence and late-arrival notices from every approved channel; reconcile attendance and arrival records; run threshold checks; prepare daily exceptions. |
| School administrator | Staff the tardy desk; verify arrival times and notices; issue tardy slips; make admission and safe-release decisions; complete Levels 2 and 3 communications; review disputes; authorize corrections; approve or reject Level 4 removal. |
| Door monitor / authorized staff | Apply the 10:10 AM door rule, direct late families to administration, and never make an undocumented admission or release decision. |
| System administrator | Configure access, automation, templates, audit logs, backups, and reports; resolve technical delivery failures. |

## 5. Required Records

Maintain the following data in the attendance system or a controlled attendance register.

### 5.1 Student and enrollment record

- student ID and name;
- class and teacher;
- enrollment start and end dates;
- parent or guardian names;
- verified phone, text/WhatsApp, and email contacts;
- preferred language and accessibility needs; and
- current enrollment and attendance-enforcement status.

### 5.2 Session and attendance record

- session ID and date;
- whether the session was scheduled, held, or cancelled;
- attendance status;
- arrival time and official time source;
- punctuality status (`On time`, `Late 10:00–10:10`, `Approved late arrival after 10:10`, `Late—sent home`, or `Pending verification`);
- annual late-showing sequence number;
- tardy-slip ID, issue time, and issuing administrator, when applicable;
- admission or safe-release decision and responsible staff member;
- time and person who entered or changed the status;
- reason or correction note, if applicable; and
- links to the related notice and communication records.

### 5.3 Absence and late-arrival notice record

- student ID;
- date of affected session;
- date and time received;
- channel used;
- parent or guardian identity;
- reason, with access restricted to staff who need it;
- staff member who logged or verified it; and
- notice type (`Absence` or `Late arrival`);
- whether it met the applicable cutoff and approved notice rules; and
- related exception approval, if any.

### 5.4 Escalation and communication record

- calculated trigger and supporting session dates;
- escalation level;
- action due date and assigned staff member;
- call attempt and outcome;
- text/WhatsApp delivery result;
- email delivery or bounce result;
- copies of messages sent;
- parent response and follow-up; and
- administrator decision, correction, or removal approval.

### 5.5 Missed-work record

- assignments or learning materials missed;
- date provided to the student;
- teacher-set due date;
- completion status; and
- support or extension provided.

## 6. Operational Workflow

### 6.1 Before each Sunday session

1. Keep all approved reporting channels active and monitored.
2. Send parents a concise reminder of the 10:00 AM start, 10:10 AM door rule, reporting methods, and applicable cutoffs.
3. Route portal, phone, text, WhatsApp, and email notices into one attendance queue.
4. Match each notice to the correct student and session.
5. Flag ambiguous or unmatched notices for staff review rather than discarding them.
6. Confirm that the official clock, tardy-slip log, annual tardy counts, and safe-release process are ready.

### 6.2 During and immediately after class

1. At 10:00 AM, administration begins processing every later arrival through the tardy desk.
2. For arrivals through 10:10 AM, staff records the official arrival time, checks the school-year count, and either issues a tardy slip for counts one through four or applies the safe send-home procedure for counts five and above.
3. Immediately after 10:10 AM, the authorized door monitor locks the doors and directs late families to administration.
4. For arrivals after 10:10 AM, administration checks for a qualifying notice received by the approved deadline. Staff admits the student with a tardy slip only when notice is verified or an authorized exception is approved.
5. Teachers admit late students only after collecting a valid tardy slip and then record attendance using the approved roster.
6. Teachers submit rosters and collected slip IDs by the configured deadline.
7. The attendance coordinator checks for missing rosters, duplicate records, missing slips, and inconsistent arrival or admission data.
8. The coordinator matches absences and late arrivals to timely notice records.
9. Unresolved records are marked `Pending verification`, not `Unnotified absence` or `Tardy-generated absence`.

### 6.3 Tardy-slip and send-home workflow

1. Search the student record and verify identity, enrollment, school-year late count, and submitted notices.
2. Record the arrival using the official time source; do not rely on an estimated or later-entered time when a real-time record is possible.
3. Apply the applicable row in Section 2.4.
4. For admission, issue a unique tardy slip containing the student, date, arrival time, slip ID, and administrator authorization; retain a corresponding system record.
5. For non-admission, explain the policy to the parent or guardian, verify safe release, record the attendance outcome, and give a written or electronic record of the decision and correction channel.
6. Do not debate the decision at the classroom door. Route disputes to an administrator and mark the record `Pending verification` when the facts are uncertain.
7. At reconciliation, match every classroom tardy entry to a slip and every issued slip to a roster entry.

### 6.4 Reconciliation and escalation

1. Finalize reconciled attendance records.
2. For each student with a new unnotified absence, calculate:
   - the current consecutive-unnotified-absence count;
   - the number of unnotified absences in the latest three scheduled sessions;
   - the number in the latest four scheduled sessions; and
   - the number in the latest five scheduled sessions.
3. Determine the highest newly reached escalation level.
4. Create one assigned action with the applicable deadline and communication channels.
5. Require staff to record completion and delivery outcomes.
6. Add all Level 4 flags to an administrator review queue; do not change enrollment automatically.
7. Keep tardy-generated absences separate from unnotified absences until leadership resolves the classification decision in Section 3.

### 6.5 Following Sunday and makeup work

1. Give the teacher a private list of students requiring Level 1 follow-up.
2. When the student returns, the teacher asks for the reason discreetly and records that the conversation occurred.
3. The teacher provides missed assignments and a specific, reasonable due date.
4. The teacher records completion or needed academic support.
5. Sensitive absence reasons must not be discussed in front of classmates.

### 6.6 Level 4 review and removal

Before removal, the administrator must confirm all of the following:

- the student was enrolled and scheduled on every counted date;
- each counted session was actually held;
- every counted absence is accurately recorded;
- every tardy-generated absence included in the count is supported by an arrival record, annual count, notice check, admission decision, and approved classification rule;
- no qualifying notice was submitted through any approved channel;
- all pending disputes or corrections are resolved;
- required earlier communications were attempted and documented;
- current contact details were used; and
- the removal decision complies with the approved exception and appeal rules.

The administrator then records approval or rejection, the reason, the effective date, and the staff member responsible for notifying the family and updating enrollment systems.

## 7. Communication Standards

Create approved templates for each escalation level. Every message should:

- identify the student and the relevant absence dates;
- state that the recorded absences were unnotified;
- explain the current policy level and the next threshold;
- list all accepted methods for reporting future absences;
- provide a clear way to correct an error or explain an emergency;
- include a staff contact and response deadline; and
- avoid unnecessary medical or other sensitive details.

Phone calls should use a short script and require a documented outcome such as `reached`, `voicemail`, `no answer`, or `invalid number`. Final warnings and removal notices should be reviewed by an authorized administrator before sending.

For tardiness, provide parents with the recorded arrival time, the student's school-year late count, the immediate consequence, and the correction process. Do not disclose other students' records. When a student is sent home, notify the parent or guardian in real time; do not rely only on a later automated message.

## 8. System Logic

For each student, order all eligible sessions by date and calculate the result only from sessions during the student's enrollment.

```text
countable(session) = attendance_status == "Unnotified absence"

consecutive_count = count of countable sessions ending at the current session,
                    stopping at the first non-countable eligible session

rolling_3 = count of countable sessions in latest 3 eligible sessions
rolling_4 = count of countable sessions in latest 4 eligible sessions
rolling_5 = count of countable sessions in latest 5 eligible sessions

if consecutive_count >= 4 or rolling_5 >= 4:
    recommended_level = 4
else if consecutive_count >= 3 or rolling_4 >= 3:
    recommended_level = 3
else if consecutive_count >= 2 or rolling_3 >= 2:
    recommended_level = 2
else if current session is countable:
    recommended_level = 1
else:
    recommended_level = 0
```

The implementation must store both the calculated recommendation and the human-approved action. This separation preserves the original evidence if staff override a recommendation.

Calculate the tardiness result independently:

```text
if arrival_time <= 10:00:00:
    punctuality = "On time"
    attendance_outcome = "Present"
else if arrival_time <= 10:10:00:
    annual_late_count += 1
    if annual_late_count <= 4:
        issue_tardy_slip()
        attendance_outcome = "Present"
    else:
        safe_release_to_parent_or_guardian()
        attendance_outcome = "Tardy-generated absence"
else:
    if qualifying_late_notice_received_by_approved_cutoff:
        issue_tardy_slip()
        attendance_outcome = "Present"
    else:
        safe_release_to_parent_or_guardian()
        attendance_outcome = "Tardy-generated absence"
```

Do not map `Tardy-generated absence` into the attendance escalation calculation until leadership has approved the classification rule in Section 3. Store raw arrival time, notice time, annual count, and decision evidence so recalculation remains possible.

## 9. Implementation Phases

### Phase 1 — Policy finalization

- Assign an accountable policy owner.
- Resolve every decision in Section 3.
- Define the enforcement start date.
- Review removal, privacy, accessibility, and record-retention requirements with qualified local counsel or the appropriate governing body.
- Publish a parent-facing policy and obtain any required acknowledgment.

**Exit criterion:** Leadership signs off on a complete policy with no unresolved enforcement rules.

### Phase 2 — Process and system configuration

- Configure sessions, rosters, statuses, user roles, and permissions.
- Create a single intake process for all notice channels.
- Implement rolling-window calculations and de-duplication of escalation actions.
- Implement the annual 10:00–10:10 late counter, tardy-slip IDs, door-rule logic, and safe-release records.
- Build staff task queues for reconciliation, tardy processing, communication, makeup work, disputes, and removal review.
- Configure communication templates and delivery logging.
- Enable an audit trail for status changes and administrator decisions.

**Exit criterion:** Staff can enter an absence or late-arrival notice, record arrival and attendance, issue and reconcile a tardy slip, calculate the correct annual tardy count and attendance level, document safe release, correct a record, and see the audit history end to end.

### Phase 3 — Testing

- Run the test cases in Section 10 using fictional students.
- Test boundary times, the first through sixth annual late showings, corrected arrival times, late-arriving notices, cancelled sessions, new enrollments, delivery failures, and duplicate records.
- Confirm that unauthorized users cannot view sensitive reasons or approve removal.
- Confirm that no automated process can remove a student.
- Confirm that no student can be marked as released without a verified parent or guardian handoff.
- Have teachers and administrators perform a pilot Sunday workflow.

**Exit criterion:** All critical tests pass, and named staff approve the workflow.

### Phase 4 — Training and launch

- Train teachers on attendance deadlines, tardy-slip validation, corrections, discretion, and missed-work follow-up.
- Train administrators and door monitors on official timekeeping, annual counts, notice verification, slip issuance, safe release, reconciliation, exceptions, and removal review.
- Give parents the attendance policy, 10:00 AM start time, 10:10 AM door rule, annual late allowance, reporting channels, cutoffs, and correction process before enforcement begins.
- Run the first two sessions in monitored launch mode and review every alert manually.

**Exit criterion:** All active classes submit complete rosters, notices reconcile correctly, and staff complete actions on time.

### Phase 5 — Monitoring and improvement

- Review unresolved attendance records weekly.
- Review overdue communications and failed deliveries weekly.
- Audit a sample of threshold calculations monthly.
- Reconcile issued tardy slips to classroom records after every session and audit annual counts monthly.
- Report attendance and escalation trends to leadership without exposing unnecessary personal details.
- Review removal cases for consistent treatment.
- Reassess the policy and parent communication at least annually.

## 10. Minimum Test Cases

| Scenario | Expected result |
| --- | --- |
| One unnotified absence | Level 1 teacher follow-up; no administrative message. |
| Two unnotified absences in a row | Level 2. |
| Unnotified, present, unnotified | Level 2 because two occur in the latest three sessions; consecutive count is one. |
| Unnotified, present, present, unnotified | Level 1 for the newest event; the two absences are outside a three-session window. |
| Three unnotified absences in the latest four sessions | Level 3. |
| Four unnotified absences in the latest five sessions | Level 4 review flag; no automatic removal. |
| Timely notified absence between two unnotified absences | It breaks the consecutive sequence but remains an eligible session in rolling-window calculations. |
| Cancelled Sunday between absences | The cancellation is excluded; it neither counts nor breaks the sequence of eligible sessions. |
| Notice exists but has not been matched to a student | `Pending verification`; no escalation until reviewed. |
| Teacher corrects an absence to present | Recalculate the level and cancel any unsupported pending action. |
| Student enrolled fewer than five sessions ago | Calculate only from sessions since enrollment. |
| Level 2 email bounces | Keep Level 2 action open for contact correction and another documented attempt. |
| Level 4 threshold reached with an unresolved dispute | Hold removal until the dispute is resolved. |
| Arrival exactly at 10:00:00 | On time; admit without a tardy slip. |
| Arrival at 10:00:01; annual late count becomes one | Issue a tardy slip, admit, mark present, and store late count one. |
| Arrival exactly at 10:10:00; annual late count becomes four | Issue a tardy slip, admit, mark present, and store late count four. |
| Arrival at 10:10:01 without timely late-arrival notice | Do not admit; safely release to the parent or guardian and record a tardy-generated absence. |
| Fifth arrival between 10:00 and 10:10 in the school year | Do not admit; safely release and record a tardy-generated absence with annual late count five. |
| Sixth arrival between 10:00 and 10:10 | Apply the same send-home consequence; the allowance does not restart after the fifth event. |
| Arrival after 10:10 with verified timely late-arrival notice | Issue a tardy slip and admit; apply the leadership-approved annual-count rule. |
| Parent claims a portal notice but staff cannot find it | Mark pending verification and hold the send-home or escalation decision while promptly checking the record. |
| Arrival time corrected from 10:00:01 to 10:00:00 | Change to on time, reduce the annual count, and reverse unsupported consequences. |
| Student presents a slip that has no matching administrative record | Do not treat it as valid; send the student discreetly to administration for verification. |

## 11. Launch Checklist

- [ ] Policy owner and removal approver are named.
- [ ] Notice cutoff, late-notice rule, exceptions, appeal, and re-enrollment rules are approved.
- [ ] Tardy-generated absence classification and pre-reported-after-10:10 count rules are approved.
- [ ] Official clock, arrival point, boundary-time rules, and school-year reset date are configured.
- [ ] Parent contact information and preferred language are verified.
- [ ] All reporting channels feed one tracked intake process.
- [ ] Attendance statuses and correction permissions are configured.
- [ ] Tardy-slip inventory or unique ID generation, annual counters, and reconciliation are configured.
- [ ] Door monitor, tardy-desk coverage, and safe-release procedure are assigned.
- [ ] Rolling-window rules pass every test case.
- [ ] Each communication level has an approved template or script.
- [ ] Makeup-work ownership and deadlines are configured.
- [ ] Delivery failures generate staff follow-up tasks.
- [ ] Level 4 requires administrator approval and cannot execute automatically.
- [ ] Staff training and parent notice are complete.
- [ ] Enforcement start date is recorded.
- [ ] Weekly review and monthly audit owners are assigned.

## 12. Success Measures

Track these measures after launch:

- percentage of Sunday rosters submitted by the deadline;
- percentage of late arrivals with a matching tardy slip and arrival record;
- number of late showings per student and class;
- number of students admitted or sent home under each tardy rule;
- number of tardy decisions corrected after review;
- percentage of parent notices correctly matched before reconciliation closes;
- number and age of `Pending verification` records;
- percentage of required communications completed on time;
- failed-delivery rate by channel;
- number of attendance corrections after escalation;
- percentage of missed assignments completed by the teacher-set deadline; and
- number of Level 4 recommendations, approvals, reversals, and appeals.

High correction or reversal rates are evidence of a process problem, not merely staff error; pause removals and fix the underlying data or workflow issue before continuing enforcement.