# 4. Family Plans — Test Cases

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: family_plans.md — every feature, sub-feature, and rule covered

---

## Test Execution Policy
- Zero tolerance: any deviation from documented behavior = FAILED = bug
- Every bug is immediately logged/reported (Bug ID, feature, sub-feature,
  expected vs actual, severity) and fixed 100% before the group passes
- Feature group passes only at 100% test pass rate

## Coverage Matrix
| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 4.1 Multiple Children Under One Account | Family account: the single account for the family (the parent's account) | TC-SA-11-04-001 |
| 4.1 Multiple Children Under One Account | Child profiles: the children's profiles under the family account (the learner profiles) | TC-SA-11-04-002 |
| 4.1 Multiple Children Under One Account | Child count: the number of children under the account (the limit) | TC-SA-11-04-003 |
| 4.1 Multiple Children Under One Account | Family scope: the access per child (the subjects/courses the child gets) | TC-SA-11-04-004 |
| 4.1 Multiple Children Under One Account | Plan definition: the plan defined by the Super Admin (the child count, the scope, the period, the price) | TC-SA-11-04-001 |
| 4.1 Multiple Children Under One Account | Profile management: the children's profiles added/managed under the account | TC-SA-11-04-005 |
| 4.1 Multiple Children Under One Account | Audit logging of the plan definition and the family accounts | TC-SA-11-04-006 |
| 4.1 Multiple Children Under One Account | Rule: the family account is the single account for the family (the parent's account); the children's profiles are under it | TC-SA-11-04-001, TC-SA-11-04-002 |
| 4.1 Multiple Children Under One Account | Rule: the child count is the limit (the number of children under the account); exceeding it requires an upgrade | TC-SA-11-04-003, TC-SA-11-04-007 |
| 4.1 Multiple Children Under One Account | Rule: the family scope is the access per child (the subjects/courses); the children's access is per their profile | TC-SA-11-04-004 |
| 4.1 Multiple Children Under One Account | Rule: a profile management (the add, the edit) is under the family account; the parent manages the children | TC-SA-11-04-005 |
| 4.1 Multiple Children Under One Account | Rule: a plan adjustment (the child count, the scope, the period, the price) is recorded (the change, the time); it is auditable | TC-SA-11-04-008 |
| 4.1 Multiple Children Under One Account | Rule: plan definition and family accounts are audit-logged with the plan, family, and timestamp | TC-SA-11-04-006 |
| 4.2 Shared Payment Method | Shared payment: the single payment method for the family (the parent's card) | TC-SA-11-04-009 |
| 4.2 Shared Payment Method | Consolidated billing: the billing is for the family (one payment, one invoice) | TC-SA-11-04-010 |
| 4.2 Shared Payment Method | Payment method: the payment method on the family account (the card, the method) | TC-SA-11-04-009 |
| 4.2 Shared Payment Method | Payment setup: the payment method set (the parent adds the card) | TC-SA-11-04-011 |
| 4.2 Shared Payment Method | Payment processing: the payment processed (the family's subscription billed) | TC-SA-11-04-012 |
| 4.2 Shared Payment Method | Payment record: the payment recorded (the family, the amount, the time) | TC-SA-11-04-013 |
| 4.2 Shared Payment Method | Audit logging of the payment setup and the payments | TC-SA-11-04-014 |
| 4.2 Shared Payment Method | Rule: the shared payment is the single payment method for the family (the parent's card); the billing is consolidated | TC-SA-11-04-009, TC-SA-11-04-010 |
| 4.2 Shared Payment Method | Rule: the consolidated billing is for the family (one payment, one invoice); it is not per child | TC-SA-11-04-010 |
| 4.2 Shared Payment Method | Rule: a payment failure triggers the notification (the retry prompt); the subscription is at risk (the suspension is the consequence) | TC-SA-11-04-015 |
| 4.2 Shared Payment Method | Rule: a payment method change is recorded (the change, the time); it is auditable | TC-SA-11-04-016 |
| 4.2 Shared Payment Method | Rule: the family payments are visible (the count, the amounts, the failures); the billing is managed | TC-SA-11-04-017 |
| 4.2 Shared Payment Method | Rule: payment setup and payments are audit-logged with the family, payment, and timestamp | TC-SA-11-04-014 |
| 4.3 Individual Progress Tracking | Individual tracking: the progress per child profile (the learning, the assessments, the completion) | TC-SA-11-04-018 |
| 4.3 Individual Progress Tracking | Child progress: the child's progress (the topics completed, the assessments taken, the scores) | TC-SA-11-04-019 |
| 4.3 Individual Progress Tracking | Progress view: the progress shown per child (the parent sees each child's progress) | TC-SA-11-04-020 |
| 4.3 Individual Progress Tracking | Progress comparison: the children's progress compared (the sibling comparison) | TC-SA-11-04-021 |
| 4.3 Individual Progress Tracking | Progress alert: the alert for a child's gap (the topic not completed, the assessment failed) | TC-SA-11-04-022 |
| 4.3 Individual Progress Tracking | Progress history: the progress over time (the child's trajectory) | TC-SA-11-04-023 |
| 4.3 Individual Progress Tracking | Audit logging of the tracking (where applicable) | TC-SA-11-04-024 |
| 4.3 Individual Progress Tracking | Rule: the individual tracking is per child profile (the learning, the assessments, the completion); the progress is individual, not aggregate | TC-SA-11-04-018 |
| 4.3 Individual Progress Tracking | Rule: the progress view is per child (the parent sees each child's progress); it is not just the family's aggregate | TC-SA-11-04-020 |
| 4.3 Individual Progress Tracking | Rule: a progress alert is for a child's gap (the topic not completed, the assessment failed); the gap is flagged | TC-SA-11-04-022 |
| 4.3 Individual Progress Tracking | Rule: the progress comparison is the sibling comparison (the child's progress relative to the siblings); it is the context | TC-SA-11-04-021 |
| 4.3 Individual Progress Tracking | Rule: the progress history is the child's trajectory over time (the progress, the gaps, the improvement); it is the trend | TC-SA-11-04-023 |
| 4.3 Individual Progress Tracking | Rule: tracking is audit-logged where applicable | TC-SA-11-04-024 |
| 4.4 Volume Discount for Siblings | Volume discount: the discount for the number of children (the more children, the greater the discount) | TC-SA-11-04-025 |
| 4.4 Volume Discount for Siblings | Child count: the number of children (the discount key) | TC-SA-11-04-026 |
| 4.4 Volume Discount for Siblings | Discount per child: the discount per child (the cost per child decreases with the count) | TC-SA-11-04-027 |
| 4.4 Volume Discount for Siblings | Discount definition: the discount defined by the Super Admin (the child count, the discount per child) | TC-SA-11-04-025 |
| 4.4 Volume Discount for Siblings | Discount application: the discount applied (the family's price is the discounted price) | TC-SA-11-04-028 |
| 4.4 Volume Discount for Siblings | Discount record: the discount recorded (the family, the child count, the discount) | TC-SA-11-04-029 |
| 4.4 Volume Discount for Siblings | Audit logging of the discount definition and the applications | TC-SA-11-04-030 |
| 4.4 Volume Discount for Siblings | Rule: the volume discount is for the number of children (the more children, the greater the discount); the discount is the incentive | TC-SA-11-04-025 |
| 4.4 Volume Discount for Siblings | Rule: the child count is the discount key (the number of children); the discount per child decreases with the count | TC-SA-11-04-026, TC-SA-11-04-027 |
| 4.4 Volume Discount for Siblings | Rule: the discount tiers are explicit (the child count tiers, the discount per tier); the tiers are the structure | TC-SA-11-04-031 |
| 4.4 Volume Discount for Siblings | Rule: a child count increase (a new child) re-applies the discount (the new child count, the new discount); the change is recorded | TC-SA-11-04-032 |
| 4.4 Volume Discount for Siblings | Rule: a discount adjustment (the child count, the discount per child) is recorded (the change, the time); it is auditable | TC-SA-11-04-033 |
| 4.4 Volume Discount for Siblings | Rule: discount definition and applications are audit-logged with the discount, family, and timestamp | TC-SA-11-04-030 |

## 4.1 Multiple Children Under One Account

### TC-SA-11-04-001 — Family account: the single account for the family (the parent's account)
**Type:** Positive
**Covers:** 4.1 → Family account: the single account for the family (the parent's account); Plan definition: the plan defined by the Super Admin (the child count, the scope, the period, the price); Rule: the family account is the single account for the family (the parent's account); the children's profiles are under it
**Preconditions:** The Super Admin opens the family plans.
**Steps:**
1. Define the family plan: the child count (the limit), the scope (the subjects/courses per child), the period, and the price.
2. Save the plan.
3. Verify the plan is live and a parent can subscribe with a single account for the family.
**Expected Result:** The family plan is defined (the child count, the scope, the period, the price) — the plan is live and a single account covers the family.
**Priority:** Critical

### TC-SA-11-04-002 — Child profiles: the children's profiles under the family account (the learner profiles)
**Type:** Positive
**Covers:** 4.1 → Child profiles: the children's profiles under the family account (the learner profiles)
**Preconditions:** A parent has subscribed to a family plan.
**Steps:**
1. As the parent, create the children's profiles under the family account.
2. Verify each child has a learner profile under the family account.
**Expected Result:** The children's profiles are under the family account — each child has a learner profile.
**Priority:** Critical

### TC-SA-11-04-003 — Child count: the number of children under the account (the limit)
**Type:** Positive
**Covers:** 4.1 → Child count: the number of children under the account (the limit); Rule: the child count is the limit (the number of children under the account)
**Preconditions:** A family plan is defined with a child count limit.
**Steps:**
1. Verify the child count limit is set (the number of children under the account).
2. Verify the limit is enforced.
**Expected Result:** The child count is the limit — the number of children under the account is bounded.
**Priority:** High

### TC-SA-11-04-004 — Family scope: the access per child (the subjects/courses the child gets); the children's access is per their profile
**Type:** Negative
**Covers:** 4.1 → Family scope: the access per child (the subjects/courses the child gets); Rule: the family scope is the access per child (the subjects/courses); the children's access is per their profile
**Preconditions:** A family account has multiple children with different scopes.
**Steps:**
1. As child A, access their subjects/courses.
2. As child B, access their subjects/courses.
3. Verify each child's access is per their profile (not shared across children).
**Expected Result:** The access is per child — each child's access is per their profile.
**Priority:** Critical

### TC-SA-11-04-005 — Profile management: the children's profiles added/managed under the account; the parent manages the children
**Type:** Positive
**Covers:** 4.1 → Profile management: the children's profiles added/managed under the account; Rule: a profile management (the add, the edit) is under the family account; the parent manages the children
**Preconditions:** A parent has a family account.
**Steps:**
1. As the parent, add a child profile.
2. Edit a child profile (the name, the grade).
3. Verify the profile management is under the family account.
**Expected Result:** The children's profiles are added/managed under the family account — the parent manages the children.
**Priority:** High

### TC-SA-11-04-006 — Plan definition and family accounts are audit-logged with the plan, family, and timestamp
**Type:** Positive
**Covers:** 4.1 → Audit logging of the plan definition and the family accounts; Rule: plan definition and family accounts are audit-logged with the plan, family, and timestamp
**Preconditions:** Plan definition and family account events have occurred.
**Steps:**
1. Open the audit trail and filter by "family plan".
2. Verify entries show the plan, the family, and the timestamp.
**Expected Result:** The plan definition and family accounts are audit-logged with the plan, family, and timestamp.
**Priority:** Critical

### TC-SA-11-04-007 — Exceeding the child count limit requires an upgrade
**Type:** Negative
**Covers:** 4.1 → Rule: the child count is the limit (the number of children under the account); exceeding it requires an upgrade
**Preconditions:** A family account has reached the child count limit.
**Steps:**
1. Attempt to add a child profile beyond the limit.
2. Verify the addition is blocked.
3. Verify the parent is prompted to upgrade (a higher child count).
**Expected Result:** The addition beyond the limit is blocked — the parent is prompted to upgrade.
**Priority:** Critical

### TC-SA-11-04-008 — A plan adjustment (the child count, the scope, the period, the price) is recorded (the change, the time); it is auditable
**Type:** Positive
**Covers:** 4.1 → Rule: a plan adjustment (the child count, the scope, the period, the price) is recorded (the change, the time); it is auditable
**Preconditions:** A family plan is live.
**Steps:**
1. Adjust the plan (change the child count, the scope, the period, the price).
2. Verify the adjustment is recorded (the change, the time).
3. Verify the change is auditable.
**Expected Result:** The plan adjustment is recorded (the change, the time) — it is auditable.
**Priority:** High

## 4.2 Shared Payment Method

### TC-SA-11-04-009 — Shared payment: the single payment method for the family (the parent's card)
**Type:** Positive
**Covers:** 4.2 → Shared payment: the single payment method for the family (the parent's card); Payment method: the payment method on the family account (the card, the method); Rule: the shared payment is the single payment method for the family (the parent's card); the billing is consolidated
**Preconditions:** A parent has a family account.
**Steps:**
1. As the parent, add a single payment method (the card) to the family account.
2. Verify the payment method is on the family account (not per child).
**Expected Result:** The single payment method is on the family account — the billing is consolidated.
**Priority:** Critical

### TC-SA-11-04-010 — Consolidated billing: the billing is for the family (one payment, one invoice); it is not per child
**Type:** Negative
**Covers:** 4.2 → Consolidated billing: the billing is for the family (one payment, one invoice); Rule: the consolidated billing is for the family (one payment, one invoice); it is not per child
**Preconditions:** A family account has multiple children and a billing cycle is due.
**Steps:**
1. Trigger the billing cycle.
2. Verify one payment is processed for the family (not per child).
3. Verify one invoice is issued for the family.
**Expected Result:** One payment and one invoice are for the family — the billing is not per child.
**Priority:** Critical

### TC-SA-11-04-011 — Payment setup: the payment method set (the parent adds the card)
**Type:** Positive
**Covers:** 4.2 → Payment setup: the payment method set (the parent adds the card)
**Preconditions:** A parent has a family account.
**Steps:**
1. As the parent, set the payment method (add the card).
2. Verify the payment method is set on the family account.
**Expected Result:** The payment method is set — the parent's card is on the family account.
**Priority:** High

### TC-SA-11-04-012 — Payment processing: the payment processed (the family's subscription billed)
**Type:** Positive
**Covers:** 4.2 → Payment processing: the payment processed (the family's subscription billed)
**Preconditions:** A family account has a payment method and a billing cycle is due.
**Steps:**
1. Trigger the billing cycle.
2. Verify the payment is processed (the family's subscription is billed).
**Expected Result:** The payment is processed — the family's subscription is billed.
**Priority:** Critical

### TC-SA-11-04-013 — Payment record: the payment recorded (the family, the amount, the time)
**Type:** Positive
**Covers:** 4.2 → Payment record: the payment recorded (the family, the amount, the time)
**Preconditions:** A family payment has been processed.
**Steps:**
1. Open the payment record.
2. Verify it shows the family, the amount, and the time.
**Expected Result:** The payment is recorded — the family, the amount, and the time are shown.
**Priority:** High

### TC-SA-11-04-014 — Payment setup and payments are audit-logged with the family, payment, and timestamp
**Type:** Positive
**Covers:** 4.2 → Audit logging of the payment setup and the payments; Rule: payment setup and payments are audit-logged with the family, payment, and timestamp
**Preconditions:** Payment setup and payment events have occurred.
**Steps:**
1. Open the audit trail and filter by "family payment".
2. Verify entries show the family, the payment, and the timestamp.
**Expected Result:** The payment setup and payments are audit-logged with the family, payment, and timestamp.
**Priority:** Critical

### TC-SA-11-04-015 — A payment failure triggers the notification (the retry prompt); the subscription is at risk (the suspension is the consequence)
**Type:** Negative
**Covers:** 4.2 → Rule: a payment failure triggers the notification (the retry prompt); the subscription is at risk (the suspension is the consequence)
**Preconditions:** A family payment fails (the card is declined).
**Steps:**
1. Trigger a billing cycle with a failing card.
2. Verify the parent is notified (the retry prompt).
3. Verify the subscription is at risk (the suspension is the consequence).
**Expected Result:** The payment failure triggers the notification (the retry prompt) — the subscription is at risk (the suspension is the consequence).
**Priority:** Critical

### TC-SA-11-04-016 — A payment method change is recorded (the change, the time); it is auditable
**Type:** Positive
**Covers:** 4.2 → Rule: a payment method change is recorded (the change, the time); it is auditable
**Preconditions:** A family account has a payment method.
**Steps:**
1. Change the payment method (a new card).
2. Verify the change is recorded (the change, the time).
3. Verify the change is auditable.
**Expected Result:** The payment method change is recorded (the change, the time) — it is auditable.
**Priority:** High

### TC-SA-11-04-017 — The family payments are visible (the count, the amounts, the failures); the billing is managed
**Type:** Positive
**Covers:** 4.2 → Rule: the family payments are visible (the count, the amounts, the failures); the billing is managed
**Preconditions:** Multiple family payments exist.
**Steps:**
1. Open the family payments view.
2. Verify the count, the amounts, and the failures are visible.
3. Verify the family billing is visible.
**Expected Result:** The family payments are visible (the count, the amounts, the failures) — the billing is managed.
**Priority:** Medium

## 4.3 Individual Progress Tracking

### TC-SA-11-04-018 — Individual tracking: the progress per child profile (the learning, the assessments, the completion); the progress is individual, not aggregate
**Type:** Positive
**Covers:** 4.3 → Individual tracking: the progress per child profile (the learning, the assessments, the completion); Rule: the individual tracking is per child profile (the learning, the assessments, the completion); the progress is individual, not aggregate
**Preconditions:** A family account has multiple children with progress.
**Steps:**
1. Open the progress view for the family.
2. Verify the progress is per child profile (the learning, the assessments, the completion).
3. Verify the progress is individual, not aggregate.
**Expected Result:** The progress is per child profile — the progress is individual, not aggregate.
**Priority:** Critical

### TC-SA-11-04-019 — Child progress: the child's progress (the topics completed, the assessments taken, the scores)
**Type:** Positive
**Covers:** 4.3 → Child progress: the child's progress (the topics completed, the assessments taken, the scores)
**Preconditions:** A child has learning activity.
**Steps:**
1. Open the child's progress.
2. Verify it shows the topics completed, the assessments taken, and the scores.
**Expected Result:** The child's progress is shown — the topics completed, the assessments taken, and the scores.
**Priority:** High

### TC-SA-11-04-020 — Progress view: the progress shown per child (the parent sees each child's progress); it is not just the family's aggregate
**Type:** Negative
**Covers:** 4.3 → Progress view: the progress shown per child (the parent sees each child's progress); Rule: the progress view is per child (the parent sees each child's progress); it is not just the family's aggregate
**Preconditions:** A family account has multiple children with progress.
**Steps:**
1. As the parent, open the progress view.
2. Verify each child's progress is shown individually.
3. Verify it is not just the family's aggregate.
**Expected Result:** Each child's progress is shown individually — it is not just the family's aggregate.
**Priority:** Critical

### TC-SA-11-04-021 — Progress comparison: the children's progress compared (the sibling comparison); it is the context
**Type:** Positive
**Covers:** 4.3 → Progress comparison: the children's progress compared (the sibling comparison); Rule: the progress comparison is the sibling comparison (the child's progress relative to the siblings); it is the context
**Preconditions:** A family account has multiple children with progress.
**Steps:**
1. Open the progress comparison view.
2. Verify the children's progress is compared (the sibling comparison).
3. Verify the comparison is the context.
**Expected Result:** The children's progress is compared — the sibling comparison is the context.
**Priority:** Medium

### TC-SA-11-04-022 — Progress alert: the alert for a child's gap (the topic not completed, the assessment failed); the gap is flagged
**Type:** Negative
**Covers:** 4.3 → Progress alert: the alert for a child's gap (the topic not completed, the assessment failed); Rule: a progress alert is for a child's gap (the topic not completed, the assessment failed); the gap is flagged
**Preconditions:** A child has a gap (a topic not completed, an assessment failed).
**Steps:**
1. Create a gap for a child (a topic not completed, an assessment failed).
2. Verify the parent is alerted (the gap is flagged).
**Expected Result:** The parent is alerted — the child's gap is flagged.
**Priority:** High

### TC-SA-11-04-023 — Progress history: the progress over time (the child's trajectory); it is the trend
**Type:** Positive
**Covers:** 4.3 → Progress history: the progress over time (the child's trajectory); Rule: the progress history is the child's trajectory over time (the progress, the gaps, the improvement); it is the trend
**Preconditions:** A child has progress over time.
**Steps:**
1. Open the child's progress history.
2. Verify the progress over time is shown (the progress, the gaps, the improvement).
3. Verify the history is the trend.
**Expected Result:** The progress over time is shown — the child's trajectory is the trend.
**Priority:** Medium

### TC-SA-11-04-024 — Tracking is audit-logged where applicable
**Type:** Positive
**Covers:** 4.3 → Audit logging of the tracking (where applicable); Rule: tracking is audit-logged where applicable
**Preconditions:** Progress tracking events have occurred.
**Steps:**
1. Open the audit trail and filter by "progress tracking".
2. Verify entries are logged where applicable.
**Expected Result:** The tracking is audit-logged where applicable.
**Priority:** Medium

## 4.4 Volume Discount for Siblings

### TC-SA-11-04-025 — Volume discount: the discount for the number of children (the more children, the greater the discount)
**Type:** Positive
**Covers:** 4.4 → Volume discount: the discount for the number of children (the more children, the greater the discount); Discount definition: the discount defined by the Super Admin (the child count, the discount per child); Rule: the volume discount is for the number of children (the more children, the greater the discount); the discount is the incentive
**Preconditions:** The Super Admin opens the family plans.
**Steps:**
1. Define the volume discount: the child count tiers, and the discount per child (the more children, the greater the discount).
2. Save the discount.
3. Verify the discount is live.
**Expected Result:** The volume discount is defined (the child count, the discount per child) — the discount is live.
**Priority:** Critical

### TC-SA-11-04-026 — Child count: the number of children (the discount key)
**Type:** Positive
**Covers:** 4.4 → Child count: the number of children (the discount key); Rule: the child count is the discount key (the number of children)
**Preconditions:** A volume discount is defined.
**Steps:**
1. Verify the child count is the discount key (the number of children).
2. Verify the discount is keyed on the child count.
**Expected Result:** The child count is the discount key — the discount is keyed on the number of children.
**Priority:** High

### TC-SA-11-04-027 — Discount per child: the discount per child (the cost per child decreases with the count)
**Type:** Negative
**Covers:** 4.4 → Discount per child: the discount per child (the cost per child decreases with the count); Rule: the discount per child decreases with the count
**Preconditions:** A volume discount is defined with tiers.
**Steps:**
1. Compare the cost per child for a 2-child family vs. a 4-child family.
2. Verify the cost per child decreases with the count.
**Expected Result:** The cost per child decreases with the count — the discount per child is applied.
**Priority:** Critical

### TC-SA-11-04-028 — Discount application: the discount applied (the family's price is the discounted price)
**Type:** Positive
**Covers:** 4.4 → Discount application: the discount applied (the family's price is the discounted price)
**Preconditions:** A family subscribes with a child count that qualifies for the discount.
**Steps:**
1. Subscribe a family with a qualifying child count.
2. Verify the discount is applied (the family's price is the discounted price).
**Expected Result:** The discount is applied — the family's price is the discounted price.
**Priority:** Critical

### TC-SA-11-04-029 — Discount record: the discount recorded (the family, the child count, the discount)
**Type:** Positive
**Covers:** 4.4 → Discount record: the discount recorded (the family, the child count, the discount)
**Preconditions:** A discount has been applied to a family.
**Steps:**
1. Open the discount record.
2. Verify it shows the family, the child count, and the discount.
**Expected Result:** The discount is recorded — the family, the child count, and the discount are shown.
**Priority:** High

### TC-SA-11-04-030 — Discount definition and applications are audit-logged with the discount, family, and timestamp
**Type:** Positive
**Covers:** 4.4 → Audit logging of the discount definition and the applications; Rule: discount definition and applications are audit-logged with the discount, family, and timestamp
**Preconditions:** Discount definition and application events have occurred.
**Steps:**
1. Open the audit trail and filter by "volume discount".
2. Verify entries show the discount, the family, and the timestamp.
**Expected Result:** The discount definition and applications are audit-logged with the discount, family, and timestamp.
**Priority:** Critical

### TC-SA-11-04-031 — The discount tiers are explicit (the child count tiers, the discount per tier); the tiers are the structure
**Type:** Positive
**Covers:** 4.4 → Rule: the discount tiers are explicit (the child count tiers, the discount per tier); the tiers are the structure
**Preconditions:** A volume discount is defined with tiers.
**Steps:**
1. Open the discount tiers.
2. Verify the child count tiers and the discount per tier are explicit.
3. Verify the tiers are the structure.
**Expected Result:** The discount tiers are explicit — the child count tiers and the discount per tier are the structure.
**Priority:** High

### TC-SA-11-04-032 — A child count increase (a new child) re-applies the discount (the new child count, the new discount); the change is recorded
**Type:** Positive
**Covers:** 4.4 → Rule: a child count increase (a new child) re-applies the discount (the new child count, the new discount); the change is recorded
**Preconditions:** A family has a discount applied and adds a new child (a higher tier).
**Steps:**
1. Add a new child to the family (a higher child count tier).
2. Verify the discount is re-applied (the new child count, the new discount).
3. Verify the change is recorded.
**Expected Result:** The discount is re-applied (the new child count, the new discount) — the change is recorded.
**Priority:** High

### TC-SA-11-04-033 — A discount adjustment (the child count, the discount per child) is recorded (the change, the time); it is auditable
**Type:** Positive
**Covers:** 4.4 → Rule: a discount adjustment (the child count, the discount per child) is recorded (the change, the time); it is auditable
**Preconditions:** A volume discount is live.
**Steps:**
1. Adjust the discount (change the child count tiers, the discount per child).
2. Verify the adjustment is recorded (the change, the time).
3. Verify the change is auditable.
**Expected Result:** The discount adjustment is recorded (the change, the time) — it is auditable.
**Priority:** High