# 2. Updates & Concerns

User Type: **Parent**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 2. Updates & Concerns

### 2.1 Request a Progress Update
**What it does:** Lets the Parent request a progress update from the child's teacher. The Parent submits a request specifying what they would like to know, and the teacher provides an update. The Parent is notified when the update is available. This helps the Parent stay informed about the child's progress.

**Sub-features:**
- Request a progress update from the teacher
- Specify what to include in the update
- Teacher provides the update
- Notification when the update is available
- Update history
- Requests available on web and mobile
- Request event logging (submitted, fulfilled)
- Audit logging of the request a progress update

**Parent User Journey:**
1. Parent opens the teacher communication section.
2. Parent requests a progress update.
3. Parent specifies what to include (recent performance).
4. The teacher provides the update.
5. The Parent is notified when the update is available.
6. The update appears in the update history.
7. Parent opens Profile → "Activity" and confirms the request events are recorded.

**Rules & Edge Cases:**
- The request specifies what to include.
- The teacher provides the update.
- A notification is sent when the update is available.
- Request events (submitted, fulfilled) are logged with the account and the timestamp.
- The request a progress update is audit-logged with the account and the timestamp.

### 2.2 Discuss a Concern
**What it does:** Lets the Parent raise a concern with the child's teacher: a drop in performance, a behavior issue, or a learning difficulty. The Parent describes the concern, and the teacher responds with their perspective and a plan. The concern and its resolution are tracked. This gives the Parent a structured way to address issues.

**Sub-features:**
- Raise a concern with the teacher
- Describe the concern (performance, behavior, learning)
- Teacher responds with perspective and plan
- Concern status (open, in progress, resolved)
- Concern resolution tracking
- Concerns available on web and mobile
- Concern event logging (raised, responded, resolved)
- Audit logging of the discuss a concern

**Parent User Journey:**
1. Parent opens the teacher communication section.
2. Parent raises a concern (drop in performance).
3. Parent describes the concern.
4. The teacher responds with their perspective and a plan.
5. The concern status is shown (in progress).
6. The concern is resolved and marked as such.
7. Parent opens Profile → "Activity" and confirms the concern events are recorded.

**Rules & Edge Cases:**
- The concern is described by the Parent.
- The teacher responds with a plan.
- The concern status is tracked to resolution.
- Concern events (raised, responded, resolved) are logged with the account and the timestamp.
- The discuss a concern is audit-logged with the account and the timestamp.

### 2.3 Teacher Feedback on Concerns
**What it does:** Provides the Parent with the teacher's feedback on raised concerns: the teacher's assessment, the actions taken, and the outcome. The Parent sees the feedback in the concern thread and can follow up. This closes the loop on the Parent's concerns.

**Sub-features:**
- Teacher feedback on a concern
- Teacher's assessment of the concern
- Actions taken by the teacher
- Outcome of the concern
- Follow-up on the feedback
- Feedback available on web and mobile
- Feedback event logging (received, followed up)
- Audit logging of the teacher feedback on concerns

**Parent User Journey:**
1. Parent opens a concern thread.
2. The teacher's feedback on the concern is shown.
3. The teacher's assessment is displayed.
4. The actions taken by the teacher are listed.
5. The outcome of the concern is shown.
6. Parent follows up on the feedback.
7. Parent opens Profile → "Activity" and confirms the feedback events are recorded.

**Rules & Edge Cases:**
- The feedback is on a raised concern.
- The feedback includes the assessment, actions, and outcome.
- A follow-up can be made on the feedback.
- Feedback events (received, followed up) are logged with the account and the timestamp.
- The teacher feedback on concerns is audit-logged with the account and the timestamp.