This diagram maps all core systems used in BrightPath's onboarding and operations stack: - JazzHR (ATS) - HR Inbox (notification hub) - DocuSign (paperwork) - DHS / NetStudy (background checks) - New Hire Onboarding Tracker - Staffing Pattern (Residential + UBS) - Master Training Tracker - Google Drive - CHR (HRIS) - When I Work (scheduling) It shows the lack of a single source of truth and highlights how manual handoffs and disconnected systems create risk and rework.

Example current-state data flow: JazzHR → HR Inbox → New Hire Tracker → Staffing Pattern → Training Tracker → CHR → When I Work Each arrow represents a largely manual handoff today (copy/paste, email, verbal updates). This is the backbone for identifying centralization and automation opportunities.

Key architecture-level issues: - No central source of truth - HR Inbox is the accidental hub for critical events - Three core trackers (New Hire, Staffing Pattern, Training) operate independently - CHR is not integrated with any upstream system - Scheduling in When I Work depends on incomplete or delayed data These are the structural reasons BrightPath struggles with accuracy and scalability.