Daily Operations

The day-to-day administrative engine for the HOD — covering student leave management, department-wide communication, the notice board, and leave policy configuration. All four modules work together to keep the department running without paperwork or missed requests.

graph LR
    A[student-leave-approvals.php
Leave Inbox] --> B[leave-settings.php
Leave Policy]
    A --> C[leave-reports.php
Leave History]
    D[notices.php
Notice Board] --> E[Students & Teachers
See Notices on Portal]
    F[messages.php
Internal Mailbox] --> G[Individual / Class /
All Staff Messages]
    

Module 1: Student Leave Approvals (`admin/student-leave-approvals.php`)

The HOD's dedicated leave management inbox. Every student leave application that has been approved by the class teacher arrives here for the HOD's final decision. This is the second and final tier of a mandatory two-step approval process.

How the Two-Step Process Works

• Pending Leave Cards (Main Inbox):
  All leave applications approved by the class teacher but awaiting the HOD's final decision appear as individual cards. Each card shows:
  • Student's name, roll number, class, and division
  • Leave type (Medical, Personal, Family, Event, etc.)
  • Leave dates and total number of days
  • The approving teacher's name and any comment they added
  • Student's stated reason (truncated if long)
  • A link to any attached supporting document (e.g., medical certificate)
  • Submission timestamp
  Core Benefit: All the information needed to make an informed decision is visible on the card itself. The HOD never needs to open a separate screen or ask for more details for routine applications.
• Approve or Reject with Comments:
  Clicking Approve opens a small confirmation dialog where the HOD can add an optional comment (e.g., "Approved — please submit assignment on return"). Clicking Reject requires a written rejection reason. The student immediately sees the decision with the HOD's comment on their portal.
  Core Benefit: Every approval and rejection is timestamped and permanently stored. If a student disputes a decision, the HOD has a complete, irrefutable record of when and why the decision was made.
• Teacher-Rejected Leave Override:
  When the "Show Teacher Rejected Leaves" setting is enabled in Leave Settings, a separate tab appears showing leaves that the class teacher rejected. The HOD can review these and, if the teacher's decision was inappropriate, override it and approve the leave directly. The system permanently records this as an "[HOD Override]" action for accountability.
  Core Benefit: The HOD retains final authority over all leave decisions in their department. Teacher rejections are not final — the HOD can correct them when circumstances warrant.
• Confirm Teacher Rejections:
  For teacher-rejected leaves, the HOD can also formally confirm the teacher's rejection (marking it as "[HOD Confirmed Teacher Rejection]") rather than doing nothing. This converts an informal rejection into a department-level final decision with a timestamp.
• Recent Actions Log (30-Day History):
  A separate "Recent" tab shows all leave decisions made in the past 30 days — approved or rejected — with their dates and outcomes. This gives the HOD an instant audit trail of their own recent actions without needing to open reports.
• Student Profile Photo Display:
  Each leave card shows the student's profile photo (or initials if no photo). Clicking the avatar opens a full-size photo preview — useful for verifying identity when the HOD receives leave applications from unfamiliar student names.

Module 2: Leave Policy Settings (`admin/leave-settings.php`)

The control panel for the HOD to configure how leave approvals behave for their department. These settings only affect the HOD's own department — other departments are not impacted.

• Auto-Approve 1-Day Leaves:
  When this toggle is enabled, any single-day leave that the class teacher approves is automatically approved at the HOD level without requiring manual HOD action. The system marks these with an "Auto-Approved" flag.
  Core Benefit: Eliminates administrative friction for routine single-day absences. The HOD's attention is preserved for multi-day or complex leave requests that genuinely need judgment.
• Require Reason for Rejection:
  When enabled, the system prevents a teacher or HOD from rejecting a leave application without typing a reason. The rejection form enforces a written explanation before the rejection can be saved.
  Core Benefit: Ensures students always receive an explanation for rejections — preventing arbitrary or undocumented leave denials that could trigger escalations.
• Show Teacher Rejected Leaves to HOD:
  When enabled, a "Teacher Rejected" tab appears in the Leave Approvals page, allowing the HOD to review leaves that were turned down by teachers and decide whether to uphold or override the decision.
• Email Notification on Auto-Approval:
  When enabled, the system sends an automated email to the student whenever their leave is auto-approved by the system (for 1-day leaves). The student receives confirmation without waiting for any manual action.
• Live Statistics Panel:
  The settings page also displays three live counters: Pending Approval (leaves currently waiting for HOD action), Auto-Approved Total (all-time count of system-approved leaves), and Approved This Month (HOD's manual approvals in the current calendar month).

Module 3: Notice Board (`admin/notices.php`)

A full-featured departmental publishing system. The HOD creates and manages notices, circulars, and announcements that are distributed directly to the targeted audience's portal — no email, no physical board, no delays.

• Three Content Types:
  • Notice: Formal administrative communication (e.g., "Exam schedule changed to Monday").
  • Circular: Recurring or policy-type communication (e.g., "Uniform policy reminder").
  • Announcement: General news or events (e.g., "Cultural fest registration open").
  Each type is displayed with a distinct icon and colour in both the HOD's admin view and the recipient's student/teacher portal.
• Three Priority Levels:
  Every notice is assigned a priority — Normal (green), Important (amber), or Urgent (red). A coloured left-border bar on each notice card makes the priority instantly visible at a glance without reading the content.
• Six Precision Targeting Options:
  The HOD controls exactly who receives each notice:
  • Everyone — All students and teachers in the department.
  • All Students — Every student in every class under the HOD.
  • All Teachers — Every teacher under the HOD.
  • Specific Class(es) — Select one or multiple classes using checkboxes. A "Select All / Deselect All" button makes batch selection fast.
  • Particular Student(s) — First select a class to load its students, then check individual names. Ideal for personal communications.
  • Particular Teacher(s) — Check individual teachers from the department's staff list.
  Core Benefit: A notice about a lab test applies only to the specific class. A message about missed assignment only goes to that one student. No one receives irrelevant communications — precision targeting prevents notice fatigue across the department.
• Rich Text Content Editor:
  The notice body uses a full-featured editor supporting bold, italic, underline, strikethrough, headings, coloured text, bullet and numbered lists, indentation, alignment, blockquotes, and embedded links and images. Notices are not restricted to plain text — they can be professionally formatted documents.
• File Attachments (Drag & Drop):
  Notices can include file attachments — PDFs, Word documents, Excel sheets, images, and plain text files (up to 10 MB each). Files are attached via a drag-and-drop zone or a standard file browser. Multiple files can be attached to a single notice. Recipients can download attachments directly from their portal.
• Active/Inactive Toggle:
  Any notice can be instantly deactivated without deleting it. An inactive notice disappears from the recipient's portal but remains in the HOD's management list. Reactivating it makes it visible again immediately.
• Edit Existing Notices:
  All published notices can be fully edited — title, content, category, priority, targeting, and attachments can all be changed after publication. Existing file attachments can be removed individually from the edit view.
• Live Stats Bar:
  The notice board header always shows: Total Notices created, Active Notices currently visible, This Month's count, and Notices with Attachments — giving the HOD instant awareness of the communication volume.
• Multi-Dimensional Filter:
  The notice list can be filtered simultaneously by Type (Notice/Circular/Announcement), Priority (Normal/Important/Urgent), Target Audience, and a free-text title search. Paginated at 10 per page for large libraries.

Module 4: Internal Messaging System (`admin/messages.php`)

A Gmail-style private messaging interface for direct, tracked communication between the HOD and their staff or students. Unlike notices (which are one-way broadcasts), messages are private, personal, and subject-based.

• Gmail-Inspired Interface Layout:
  The messaging page mirrors a professional email client:
  • Left sidebar — Navigation tabs (Inbox / Sent) with unread count badge and a prominent Compose button.
  • Centre panel — Message list showing sender avatar, name, subject, message snippet, and timestamp.
  • Search bar — Live full-text search across all messages by sender, subject, or content.
• Four Recipient Targeting Modes:
  When composing, the HOD chooses from:
  • Individual — Select any one person (teacher or student) from the department. Verified against active accounts before sending.
  • Specific Class — Sends to every active student in the selected class simultaneously. Each student receives a personal copy.
  • All Teachers — Broadcasts to every teacher under the HOD's management in a single send.
  • All Students — Broadcasts to every active student in the entire department.
  Core Benefit: A single compose action sends a private, personal message to 150 students simultaneously — each student sees it as a direct message from the HOD, not a mass notification. This maintains a professional, direct communication tone.
• Rich Text Message Body:
  Messages are composed using a rich text editor supporting all standard formatting — bold, italic, bullet lists, headings, and links. Messages are not plain text — they can be formatted like professional correspondence.
• Colour-Coded Sender Avatars in Inbox:
  Each message in the inbox shows a colour-coded avatar circle indicating the sender's role:
  • Blue = Student message
  • Green = Teacher message
  • Amber = HOD message
  • Purple = Admin message
  • Gradient = Group/Bulk message
  This makes the inbox scannable without reading sender names.
• Unread Message Highlighting:
  Messages not yet opened appear with a light blue background and bold text — identical to standard email unread indicators. The inbox badge count always reflects the exact number of unread messages.
• Sent Messages with Bulk Grouping:
  The Sent tab intelligently groups bulk sends. If the HOD sent the same message to 60 students, it appears as a single entry in the Sent list showing "Bulk Group (60)" rather than 60 identical rows — keeping the sent history clean and readable.
• Department-Scoped Contact List:
  When composing a message to an individual, the recipient dropdown only shows people who are actually in the HOD's department — their own students and their own teachers. It is not possible to accidentally message someone from a different department.
  Core Benefit: All messages are department-scoped and activity-logged. Every send is permanently recorded with the sender ID, recipient, subject, timestamp, and recipient count — providing a complete communication audit trail.

Notice Board vs. Messages — When to Use Which