Skip to content

UC-ADM-104: Meal Distribution Tracking

1. Metadata

Property Value
ID UC-ADM-104
Actor School Kitchen Manager / Admin
Trigger Arrival of food parcels or start of meal service
Pre-conditions Daily menu assigned; Batch ID scanned
Post-conditions Distribution count verified; Waste logged; Real-time inventory updated
Side Effects Trigger low-stock alert if inventory < 15%

2. Description

Ensures that nutritional meals reaching schools are tracked from receipt to consumption, preventing leakages and ensuring every student receives their allocated nutrition.

3. Success Scenario

  1. Receipt Verification: Kitchen manager scans the QR code on arriving food crates.
  2. Quality Check: Manager enters temperature and visual audit status into the handheld terminal.
  3. Allocation: System calculates "Expected Servings" based on today's attendance data.
  4. Service Logging:
    • During meal hour, staff increments 'Served' count via tap-interface.
    • System verifies against 'Student Swipes' if individual tracking is enabled.
  5. Close-out: Manager logs 'Leftovers' and disposal method (e.g., Compost, Donation).
  6. Reporting: Distribution statistics are synced to the central Dashboard.

4. Acceptance Criteria

  • [ ] Data Accuracy: Distribution count must not exceed 105% of recorded attendance.
  • [ ] Auditability: Every crate must be traceable back to its production batch and kitchen of origin.
  • [ ] Speed: QR scanning and service logging must support throughput of 10 students/minute.

5. Distribution Logic

flowchart LR Scan[QR Scan Crate] --> Audit[Quality/Temp Check] Audit --> Match{Attendance Match?} Match -- Yes --> Serve[Log Serving] Match -- Excess --> Flag[Flag for Variance] Serve --> Close[Log Waste/Leftover] Close --> Sync[(Sync to Cloud Index)]