# Notifications & Status Monitoring

## Module Overview

PMS sends **notifications** when action is required on your PC forms, meetings, visit plans, M&E reports, or messages. The **notification bell** in the top header gives quick access; the full **Notifications** page lets you filter, search, and mark items read.

Staying on top of notifications is how checkers, approvers, meeting participants, co-signers, and the Chairman avoid missing deadlines.

---

## Navigation

### Quick Access — Header Bell

1. Look at the **top-right** of any page.
2. Click the **bell icon**.
3. A dropdown shows recent unread notifications with titles and timestamps.
4. Click any item to jump to the related PC form, meeting, plan, or report.
5. Click **View all notifications** to open the full page at `/notifications`.

### Full Notifications Page

Open from the bell dropdown or navigate directly when bookmarked.

---

## Screen Overview — Notifications Page

### Toolbar

| Control | Purpose |
|---------|-------------|
| **All / Unread / Read tabs** | Filter by read status |
| **Period filter** | Today, This Week, This Month |
| **Search box** | Search title or message text |
| **Search button** | Run search |
| **Mark all as read** | Clears unread badge for all items |
| **Unread badge** | Shows count of unread notifications |

### Notification List

Each row displays:

| Element | Description |
|---------|-------------|
| **Dot indicator** | Blue/highlighted = unread; faded = read |
| **Icon** | Type icon (meeting, PC, report, etc.) |
| **Title** | Short action summary |
| **Message** | Detail line explaining what happened |
| **Meta** | Time ago (e.g., "2 hours ago") |
| **Click action** | Opens linked record |

Empty state shows when no notifications match your filters.

---

## Notification Types

### PC Form / Approval Notifications

| Type | When You Receive It |
|------|---------------------|
| **Forwarded for checking** | A submitter sent a PC form you must review |
| **Forwarded for approval** | Checker completed; department approver action needed |
| **Forwarded to P&D** | Department approved; P&D queue |
| **Approved** | Your submission or review item was approved |
| **Deferred** | A reviewer returned your submission with remarks |
| **PC-I advice forwarded** | Chairman: advice letter forwarded from PDWP meeting |

**What to do:** Click notification → open PC Form Details → **Approve** or **Defer** (or **Edit** if you are submitter and deferred).

---

### Meeting Notifications

| Type | When You Receive It |
|------|---------------------|
| **Meeting attendance** | You are invited; accept or decline schedule |
| **Meeting notice** | Notice letter sent; signature or acknowledgment may be required |
| **Meeting response** | Meeting approved, rejected, cancelled, or rescheduled by organizer |
| **Minutes of meeting** | You are a co-signer; MoM needs your signature |

**What to do:** Click → open Meeting Workspace → Accept/Decline, sign notice, or co-sign MoM.

---

### Visit Plan Notifications

| Type | When You Receive It |
|------|---------------------|
| **Visit plan submitted** | Plan entered workflow |
| **Visit plan forwarded** | Plan sent to you for review |
| **Visit plan approved / declined** | Decision recorded |
| **MO reassigned** | Monitoring officer changed on a plan |
| **Field visit letter** | Letter generated or published for a plan |

**What to do:** Click → open Visit Plans module → review or approve as your role requires.

---

### M&E Report Notifications

| Type | When You Receive It |
|------|---------------------|
| **Report submitted** | New report in queue |
| **Report forwarded** | Report sent to you for review |
| **Report approved / declined** | Review decision |
| **Report published** | Report is public/internal final |

---

### Scheme Change Notifications

| Type | When You Receive It |
|------|---------------------|
| **Cancellation/replacement submitted** | Scheme modification request started |
| **Forwarded / approved / rejected** | Modification workflow updates |

---

### Compliance Notifications

| Type | When You Receive It |
|------|---------------------|
| **Compliance submitted** | Department replied to compliance request |
| **Revisit assigned** | You are assigned a revisit after published report |

---

### Other Notifications

| Type | When You Receive It |
|------|---------------------|
| **Working paper comment** | Comment requested on shared working paper |
| **Messenger** | New direct message |
| **PC-I advice (Chairman)** | Chairman-specific forward from meeting |

---

## Status Monitoring

Notifications tell you *what changed*; these screens tell you *current state*:

### PC Form Status

| Screen | What to Monitor |
|--------|-----------------|
| **PC Forms list** | Status column, Modified/Revised labels |
| **Schemes page** | PC-I through PC-IV pills |
| **Dashboard** | PC forms submitted, pending counts |

### Meeting Status

| Screen | What to Monitor |
|--------|-----------------|
| **Meeting Workspace calendar** | Draft, Scheduled, Completed |
| **Meeting detail** | Document generate/view status, co-signature completion |
| **Participant responses** | Accepted/Declined on meeting page |

### Report Status

| Screen | What to Monitor |
|--------|-----------------|
| **M&E Reports menus** | Draft / In Process / Review / Published filters |
| **M&E Dashboard** | Published, SAT/UNSAT, Under Process cards |

---

## Step-by-Step User Guide

### Processing Your Morning Queue

1. Sign in to PMS.
2. Click the **bell**—note unread count.
3. Open **View all notifications**.
4. Select **Unread** tab.
5. Process each item oldest-first:
   - PC reviews → Approve or Defer
   - Meeting invites → Accept or Decline
   - MoM co-sign → Open and sign
   - Deferred returns → Edit and resubmit (if submitter)
6. Click **Mark all as read** when caught up.

### Finding an Old Notification

1. Open **Notifications** page.
2. Set **Period** to **This Month** (or wider).
3. Type keywords in **Search** (scheme name, "Defer", "PDWP").
4. Click **Search**.
5. Click the matching row.

### Monitoring Without Notifications

If you expect an update but have no alert:

1. Open **PC Forms**; sort/filter by status relevant to your role.
2. Check **Schemes** stat card **PCs pending approvals**.
3. Ask colleague if they completed forward action—notifications require correct role assignment.

---

## Approval vs Return Notifications

| You See | Meaning | Your Action |
|---------|---------|-------------|
| "Forwarded for checking" | Checker queue | Review → Approve/Defer |
| "Forwarded for approval" | Dept approver queue | Review → Approve/Defer |
| "Forwarded to P&D" | P&D queue | Review → Approve/Defer / schedule meeting |
| "Deferred" | Your submission returned | Read remarks → Edit → Submit |
| "Approved" | Final or stage approval | Archive / proceed to next PC type |
| "PC-I forwarded for advice" | Chairman queue | Review documents → Approve/Defer |

---

## Chairman Notifications

Chairman users should watch for:

- **PC-I forwarded for advice** — primary decision queue after PDWP
- **Meeting response** — if involved as participant
- **Minutes of meeting** — if listed as co-signer on MoM

Always open **Advice Letter** and **MoM** links from the notification target page before approving.

---

## Meeting Notifications Detail

### Accept / Decline Schedule

1. Click **Meeting attendance** notification.
2. Meeting detail opens.
3. Click **Accept** or **Decline**.
4. Organizer sees your response on participant list.

### Sign Meeting Notice

1. Click **Meeting notice** notification.
2. Notice letter editor or sign prompt opens.
3. Review agenda and apply signature if required.
4. Save.

### Co-Sign MoM

1. Click **Minutes of meeting** notification.
2. MoM editor opens (may be read-only except signature area).
3. Review deliberations.
4. Apply co-signature.
5. Save—organizer tracks until all co-signers complete.

---

## Business Scenarios

### Scenario: Checker Daily Routine

Sana logs in; bell shows 3 unread. Two are **Forwarded for checking** PC-I forms; one is **Messenger**. She reviews and approves both PC-Is before noon; marks notifications read.

### Scenario: Submitter Responding to Deferral

Hassan receives **Deferred** notification with remarks excerpt. Clicks through to PC-II, edits climate section, resubmits. Checker receives new **Forwarded for checking** notification.

### Scenario: Co-Signer Before Advice Forward

PDWP MoM needs three co-signatures. Each co-signer gets **Minutes of meeting** alert. Organizer cannot **Forward for Advice to Chairman** until co-signatures complete—monitor on meeting page even if notifications are cleared.

### Scenario: Chairman Weekly Batch

Chairman filters **Unread** notifications for "advice", processes five forwarded PC-Is, approves four and defers one, then **Mark all as read**.

---

## Tips for Trainers

- Show unread badge increment when another user forwards a test PC form.
- Demonstrate deep-link: notification click lands directly on Details modal.
- Explain **Mark all as read** does not delete notifications—only clears unread highlight.
- Encourage checkers to clear unread daily; deferred submitters depend on quick turnaround.

---

*Previous: [Reports & Tracking](14-Reports-Tracking.md) | [Back to Training Index](README.md)*