# 4. Family Plans

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

---

## 4. Family Plans

### 4.1 Multiple Children Under One Account
**What it does:** Provides the family plan: multiple children (the learner profiles) under one family account, so a parent manages the children's subscriptions from a single account. The Super Administrator defines the family plan (the number of children, the scope, the period, the price) so a family with several children gets a single account with the children's profiles, rather than separate accounts per child.

**Sub-features:**
- Family account: the single account for the family (the parent's account)
- Child profiles: the children's profiles under the family account (the learner profiles)
- Child count: the number of children under the account (the limit)
- Family scope: the access per child (the subjects/courses the child gets)
- Plan definition: the plan defined by the Super Admin (the child count, the scope, the period, the price)
- Profile management: the children's profiles added/managed under the account
- Audit logging of the plan definition and the family accounts

**Super Administrator User Journey:**
1. Super Admin defines the family plan: the child count (the number of children under the account), the scope (the subjects/courses per child), the period, and the price.
2. Sets the family scope: the access per child (the subjects/courses the child gets); the children's profiles are under the family account.
3. Saves; the plan is live, and a parent can subscribe to the family plan.
4. A parent subscribes to the family plan; the family account is created, and the children's profiles are added under it.
5. The parent manages the children's profiles (the add, the edit) under the family account; the children's access is per their profile.
6. For a family that exceeds the child count (a new child), the parent upgrades the plan (the child count increased); the change is recorded.
7. Reviews the family accounts: the count, the child counts, the periods, so the family demand is visible.
8. The plan definition and the family accounts are audit-logged with the plan, the family, and the timestamp.

**Rules & Edge Cases:**
- The family account is the single account for the family (the parent's account); the children's profiles are under it.
- The child count is the limit (the number of children under the account); exceeding it requires an upgrade.
- The family scope is the access per child (the subjects/courses); the children's access is per their profile.
- A profile management (the add, the edit) is under the family account; the parent manages the children.
- A plan adjustment (the child count, the scope, the period, the price) is recorded (the change, the time); it is auditable.
- Plan definition and family accounts are audit-logged with the plan, family, and timestamp.

### 4.2 Shared Payment Method
**What it does:** Provides the shared payment method: the family account uses a single payment method (the parent's card) for the family's subscription, so the billing is consolidated (one payment for the family, not per child). The Super Administrator enables the shared payment (the payment method on the family account) so the family's billing is simple (one payment, one invoice).

**Sub-features:**
- Shared payment: the single payment method for the family (the parent's card)
- Consolidated billing: the billing is for the family (one payment, one invoice)
- Payment method: the payment method on the family account (the card, the method)
- Payment setup: the payment method set (the parent adds the card)
- Payment processing: the payment processed (the family's subscription billed)
- Payment record: the payment recorded (the family, the amount, the time)
- Audit logging of the payment setup and the payments

**Super Administrator User Journey:**
1. A parent subscribes to the family plan; the family account is created.
2. The parent sets the shared payment method (the card, the method) on the family account; the payment is the family's, not per child.
3. The billing is consolidated: the family's subscription is billed (one payment, one invoice); the payment is processed.
4. The payment is recorded: the family, the amount, and the time; the record is the proof.
5. For a payment failure (the card declined), the parent is notified (the retry prompt); the subscription is at risk (the suspension is the consequence).
6. For a payment method change (a new card), the parent updates the payment method; the change is recorded.
7. Reviews the family payments: the count, the amounts, the failures, so the family billing is visible.
8. The payment setup and the payments are audit-logged with the family, the payment, and the timestamp.

**Rules & Edge Cases:**
- The shared payment is the single payment method for the family (the parent's card); the billing is consolidated.
- The consolidated billing is for the family (one payment, one invoice); it is not per child.
- A payment failure triggers the notification (the retry prompt); the subscription is at risk (the suspension is the consequence).
- A payment method change is recorded (the change, the time); it is auditable.
- The family payments are visible (the count, the amounts, the failures); the billing is managed.
- Payment setup and payments are audit-logged with the family, payment, and timestamp.

### 4.3 Individual Progress Tracking
**What it does:** Provides the individual progress tracking: each child's progress is tracked separately (the child's learning, the assessments, the completion), so the parent sees each child's progress individually, not just the family's aggregate. The Super Administrator enables the individual tracking (the progress per child profile) so the parent can see how each child is doing, and address the gaps per child.

**Sub-features:**
- Individual tracking: the progress per child profile (the learning, the assessments, the completion)
- Child progress: the child's progress (the topics completed, the assessments taken, the scores)
- Progress view: the progress shown per child (the parent sees each child's progress)
- Progress comparison: the children's progress compared (the sibling comparison)
- Progress alert: the alert for a child's gap (the topic not completed, the assessment failed)
- Progress history: the progress over time (the child's trajectory)
- Audit logging of the tracking (where applicable)

**Super Administrator User Journey:**
1. A family subscribes to the family plan; the children's profiles are under the family account.
2. Each child's progress is tracked separately (the learning, the assessments, the completion); the progress is per child profile.
3. The parent views the progress per child (the topics completed, the assessments taken, the scores); the progress is individual, not aggregate.
4. For a child's gap (a topic not completed, an assessment failed), the parent sees the alert (the gap flagged); the parent addresses it (the child re-studies, re-takes).
5. The parent compares the children's progress (the sibling comparison); the comparison is the context (the child's progress relative to the siblings).
6. Reviews the progress history: the child's trajectory over time (the progress, the gaps, the improvement); the history is the trend.
7. For a child with a persistent gap (a recurring issue), the parent (or the teacher) addresses the root cause (the topic, the method); the gap is closed.
8. The tracking is audit-logged where applicable (the child, the progress, the timestamp).

**Rules & Edge Cases:**
- The individual tracking is per child profile (the learning, the assessments, the completion); the progress is individual, not aggregate.
- The progress view is per child (the parent sees each child's progress); it is not just the family's aggregate.
- A progress alert is for a child's gap (the topic not completed, the assessment failed); the gap is flagged.
- The progress comparison is the sibling comparison (the child's progress relative to the siblings); it is the context.
- The progress history is the child's trajectory over time (the progress, the gaps, the improvement); it is the trend.
- Tracking is audit-logged where applicable.

### 4.4 Volume Discount for Siblings
**What it does:** Provides the volume discount for siblings: the family plan offers a discount for the number of children (the more children, the greater the discount per child), so a family with several children gets a better deal per child. The Super Administrator defines the volume discount (the child count, the discount per child) so the family's cost per child decreases with the number of children.

**Sub-features:**
- Volume discount: the discount for the number of children (the more children, the greater the discount)
- Child count: the number of children (the discount key)
- Discount per child: the discount per child (the cost per child decreases with the count)
- Discount definition: the discount defined by the Super Admin (the child count, the discount per child)
- Discount application: the discount applied (the family's price is the discounted price)
- Discount record: the discount recorded (the family, the child count, the discount)
- Audit logging of the discount definition and the applications

**Super Administrator User Journey:**
1. Super Admin defines the volume discount: the child count (the number of children) and the discount per child (the cost per child decreases with the count).
2. Sets the discount tiers: the child count tiers (the 2 children, the 3 children, the 4+ children) and the discount per tier; the tiers are explicit.
3. Saves; the discount is live, and a family's price is the discounted price (per the child count).
4. A family subscribes to the family plan; the discount is applied (the family's price is the discounted price, per the child count).
5. The discount is recorded: the family, the child count, and the discount; the record is the proof.
6. For a family that adds a child (the child count increases), the discount is re-applied (the new child count, the new discount); the change is recorded.
7. Reviews the volume discounts: the count, the child counts, the discounts, so the volume discount is visible.
8. The discount definition and the applications are audit-logged with the discount, the family, and the timestamp.

**Rules & Edge Cases:**
- The volume discount is for the number of children (the more children, the greater the discount); the discount is the incentive.
- The child count is the discount key (the number of children); the discount per child decreases with the count.
- The discount tiers are explicit (the child count tiers, the discount per tier); the tiers are the structure.
- A child count increase (a new child) re-applies the discount (the new child count, the new discount); the change is recorded.
- A discount adjustment (the child count, the discount per child) is recorded (the change, the time); it is auditable.
- Discount definition and applications are audit-logged with the discount, family, and timestamp.