A day with Priya Patel, VP EHS at MeridianFlow Logistics.

Priya's day starts before sunrise at her kitchen counter on the North Side of Chicago, on a laptop next to a still-empty coffee mug. The network dashboard opens to the four-region executive view. Twenty-eight distribution centers, four region cards, color-coded against her configured thresholds. The headline numbers are healthy: network TRIR 2.8 against a NAICS 4931 industry rate of 3.9 from the most recent BLS publication, twenty-four-month trailing trend pointing down.

Underneath the headline are the outliers worth seeing before her 8 AM emails start. The East card flags Atlanta DC-14: near-miss reporting twenty-eight percent below the trailing four-week baseline. The Central card flags Indianapolis DC-7: on customer-audit watch — Cresentine Foods' quarterly audit lands there tomorrow morning. The West card flags a conveyor caught-in observation cluster across three of seven DCs. The Mountain card flags Phoenix DC-3: a DOT/OSHA recordability cross-check pending review (a trucking-carrier-employed driver injured during a delivery; the OSHA-recordability question is whose books it lands on). Priya marks Atlanta DC-14 for a 7:30 AM drill and moves on to find the coffee.

Priya filters Atlanta DC-14's incidents by third-shift, struck-by category. Three observations in seven days, all on the eastbound receiving lanes, all involving reach trucks, all post-Q3 dock-geometry refresh. The pattern is operational, not behavioral — a layout change that introduced blind corners at three intersection points the third-shift traffic patterns now collide through. Reporting rate dropped because the operators stopped flagging the near-misses as exceptional; they're starting to be the normal background of the new geometry.

Priya opens a Teams thread with the East Region Safety Manager and the Atlanta DC-14 Site Safety Lead. The cluster ID + the three observation records + a screen-share annotation on the new dock layout. They agree: an emergency layout-amendment review for the three intersection points this morning at the site; floor-marker plus convex-mirror plus low-speed-zone signage before the end of next shift; the AI-assisted hazard-template runner suggests a temporary one-way traffic flow on R-3 and R-5 for two weeks until the floor markings settle. Priya doesn't run this fix herself. The Site Safety Lead does. Priya's job today is making sure the data found the cluster before the cluster found a body.

Priya's 8:30 AM inbox check surfaces an email from Cresentine Foods' Compliance Manager. Cresentine is one of MeridianFlow's top-three 3PL customers by volume. Their Q2 audit was scheduled for late June. The Compliance Manager has pulled it forward by about five weeks: tomorrow 11:00 AM Eastern at MeridianFlow's Indianapolis DC-7. Twenty-four-hour notice. This is the kind of move that's normal in 3PL contract relationships — customers reserve the right to audit on short notice, and a 24-hour heads-up is more courtesy than obligation.

The requested package isn't surprising in its shape: training-compliance roster + PIT-certification status + 12 months of incident records + OSHA 300/300A + SDS access verification for all Cresentine-customer SKUs + corrective-action history for any Cresentine-product incident. It's the standard quarterly-audit checklist. What's unusual is the timeline. Three years ago this email would have triggered a fire drill — half the East Region team pulling reports from four different systems, the Indianapolis Site Safety Lead working through the night, Priya on a 6 AM flight to Indy to make sure nothing fell off the truck. Today the question is whether Priya needs to fly out at all. The answer turns out to be no.

Priya opens DC-7 Indianapolis Establishment view, navigates to Customer Audit Readiness, selects the Cresentine Foods customer profile from the dropdown, clicks Generate. The PDF builds in forty-seven seconds. Eighty-four pages. Every dimension Cresentine's Compliance Manager asked for plus a couple she didn't (the storage-compatibility AI prevention log for the past 30 days; the SDS-access verification with QR-code deployment summary).

Priya forwards the package to the Indianapolis Site Safety Lead with two flags to spot-check before the audit: confirm the two in-flight corrective actions have clear completion targets, and confirm the Plant Manager will be in the trailer at 10:45 AM tomorrow for the opening conference. She also forwards a copy to Cresentine Foods' Compliance Manager — getting ahead of the audit. The unspoken signal: we knew this was coming the moment your email landed; the package is real; the audit tomorrow is verification, not discovery. Customer-relationship work matters. The platform doesn't drive that work, but it makes it possible for Priya to lead with confidence instead of with hedge.

Priya joins the weekly Q3-ramp planning call with the Chief HR Officer + the Director of Training + the per-region Operations VPs. Q3 ramp starts in about six weeks. The forecast: 2,400 seasonal hires across the network for Q4 peak. The training pipeline will run at twenty-four onboarding cohorts per week at the ramp peak — orientation, HazCom briefing, emergency-action plan walk-through, bloodborne-pathogen training, equipment certifications for those who'll touch the PIT fleet. The PIT-certification queue will see roughly 340 new operators across the network between Week 27 and Week 35.

Last year's gotcha was a Texas DC PIT-certification queue overflow in Week 33 — the certification class capacity capped at 12 operators per week and the volume of new operator hires exceeded the queue depth by Week 31; the East Region Safety Manager caught it internally but only with four days of margin before uncertified operators would have had to wait on assignment. This year the PIT-certification dashboard has threshold alerts wired at 80%, 95%, and 100% queue depth per site; East + Central are on alert from Week 28 onward. Priya signs off on the trainer-contractor headcount budget (+18 trainer FTEs across the network for the ramp), confirms the bulk Excel import path is exercised through the dev environment with last year's data shape, and the call wraps in thirty-eight minutes. Three years ago this planning effort took a six-hour offsite with three spreadsheets that never reconciled. Today it's the dashboard plus a calendar block.

Priya's weekly hazmat-storage-compatibility summary lands in her inbox. The AI storage-compatibility analysis prevented fourteen incompatible co-locations across the network this week at the receiving-inspection step — before any of them reached a storage bay. Alternative bay assignment fired within ninety seconds in every case. Zero co-locations made it to the floor; zero became Tuesday's near-miss; zero became Wednesday's investigation.

Two of the fourteen were at Indianapolis DC-7. Both involve Cresentine Foods — a flammable solvent inbound from a Cresentine supplier, staged adjacent to another customer's oxidizer that arrived twenty minutes earlier on a different carrier. The AI flagged both at the gate-inspection step, blocked the assignment, suggested an alternative bay, the receiving clerk acknowledged in twelve seconds, and the operation moved on. Tomorrow when Cresentine's Compliance Manager asks about storage-compatibility procedures, Priya's audit-readiness PDF will show two preventions in the past week that involved her own customer's product. The absence is the signal. The moat is that the absence is documented.

Priya opens the recordability-cascade review for the Phoenix DC-3 incident from yesterday. A NorthRoad Transit Group driver — delivering NorthRoad Industrial Supply product to MeridianFlow's Phoenix DC under a 3PL contract — slipped descending the trailer at receiving dock R-2 and fractured an ankle. Treatment beyond first aid. The OSHA recordability question is whose books it lands on.

SE's cascade has already run the 1904.31(b) test: the injured driver is an independent contractor whose work is not supervised day-to-day by MeridianFlow personnel. Recordability falls on NorthRoad Transit Group's OSHA logs, not MeridianFlow's. The platform has flagged the determination on MeridianFlow's 300 log with a "contractor — not recordable per 1904.31(b)" note + the regulation citation; the case is not counted in DC-3's TRIR. The DOT FMCSA driver-injury contemporaneous-record requirement applies separately on NorthRoad Transit Group's side (49 CFR 390.15); MeridianFlow provides incident facts + dock-condition assessment + the camera footage as contractually-required cooperation. A separate internal action — dock R-2 surface + lighting + handrail condition review — opens on the Phoenix DC-3 Site Safety Lead's task list.

Priya reviews the cascade in four minutes. The determination is right. She acknowledges and the case closes against MeridianFlow's recordability surface. Three years ago this would have been a thirty-minute thread between Priya, the Phoenix Site Safety Lead, General Counsel, and the Risk Manager — debating which company's books the case belongs on, whether NorthRoad would agree, whether the contract language covered it. Today the platform ran the regulation against the contractor-supervision facts and surfaced the determination + the citation; the rest of the conversation is acknowledgment, not adjudication.

Priya spends an hour drafting Friday's board-deck quarterly safety review. The COO + CFO + Chief Customer Officer + Chief HR Officer + General Counsel will be in the room; the CEO joins for the front half. Eight slides total — three lagging-indicator slides, two leading-indicator slides, one customer-audit-pass-rate slide, one growth-adjusted framing slide, one slide for the Q2 outlook including the Q3 ramp plan.

The headline is the growth-adjusted framing: network W-2 headcount up 11.4% year-over-year, contracted ops up 6.1%, but recordables only up 4.2% and DART down 3.8%. Per-100-FTE injury-cost down 7%. The leading indicators are the support: hazard-reporting rate +18%, safe-behaviour observation ratio 0.94 against a 0.90 target, PIT certification compliance at 99.3%. Customer audits seven-for-seven in Q1 with Cresentine's Q2 audit landing tomorrow. SE's executive-dashboard exports give Priya the numbers in fifteen minutes; the rest of the hour is the narrative + the ramp-plan slide that has to land cleanly with the CFO. The board deck three years ago was a four-day analyst project. Today it's an afternoon of writing the story over data that already existed.

Priya closes the laptop at 5:30 PM Central. Tomorrow's Compliance Calendar item: the Cresentine Foods Q2 audit at Indianapolis DC-7, 11:00 AM Eastern. She'll join via Teams from her Chicago office — not from Indianapolis. Three years ago this audit would have meant a 5:30 AM flight out of O'Hare; today the Indianapolis Site Safety Lead leads the audit, the Plant Manager handles the opening conference, and Priya joins the call when Cresentine wants to ask the strategic-relationship questions. The readiness package is real. The team on the ground is trained. The platform did the data work overnight.

The other Calendar items are routine: SARA Tier II quarterly attestation auto-drafted from live chemical-inventory data for Priya's review by next Tuesday; the Atlanta DC-14 dock-geometry corrective actions running on the Site Safety Lead's clock through next shift; the West Region conveyor-cluster corrective actions across three DCs; Friday's board-deck final. Tonight's commitments: dinner with her partner; a quick check at 9 PM that the Cresentine readiness PDF didn't bounce anywhere it shouldn't have; sleep. Tomorrow at 10:55 AM CT she'll join the Teams call. By 12:30 PM ET the audit will be closed. By 2 PM CT she'll know whether Cresentine's Compliance Manager wanted the strategic conversation or just the checklist. Either way, the data already answered.