A day with Marcus Reed, COO at Stratford Industrial Group.

Marcus's day starts at 5:55 AM Eastern at his kitchen table in Shadyside, Pittsburgh, on a tablet next to coffee that hasn't finished brewing yet. The executive operations dashboard opens to the six-tile summary view. Six tiles, six metrics, six color states. Production output 96.4% of plan — Akron is the drag at -8.2% (quality hold on a powder-metal lot in containment). Quality DPMO 312 across the network — Akron's lot 4480 is the centre of gravity. Customer OTD 97.1%, two at-risk promises (Akron's quality issue + a Fort Wayne press-line capacity squeeze). Safety: zero recordables overnight, one near-miss (Fort Wayne, 200-ton press, third shift). Cost-of-injury rolling 30-day at $94K — 32% below the trailing 12-month monthly average. Unplanned downtime 1.8% of run hours.

Three years ago this scan was eight emails, four spreadsheets, two phone calls to plant managers before 7 AM, and a hope that nothing was hiding under the surface. Today it's one screen + a forty-second read. The Akron quality hold + the Fort Wayne near-miss are the two items Marcus carries into his 7 AM operations call. Everything else is in a state Marcus would describe as "running." He doesn't open a single plant-level drill-down this morning. The point of the network executive dashboard is to surface the things that need attention without making him hunt for them.

At 7:00 AM Marcus joins the daily operations call. Six plant managers, the corporate EHS Director, the Quality Director, and the Supply-Chain Director on the line. Fifteen minutes. Each plant manager gets ninety seconds: production vs plan, quality issues, supply-chain blockers, customer escalations, safety items. Marcus's job is direction-setting + decision-routing, not running individual plant operations.

The call confirms what the morning dashboard showed. Akron's quality hold is in containment; the lot is segregated, the customer is notified, the root-cause team is forming. Marcus authorizes the Quality Director to lead the customer conversation. Fort Wayne's third-shift near-miss is the safety item; the plant manager has the engineering team looking at the press guard interlock + the press will run today on enhanced observation pending the 8 AM call. Memphis ahead, Phoenix nominal, Pittsburgh routine, Charlotte clean. Marcus closes the call at 7:14 with three decisions logged into SE's executive workflow: (1) Akron root-cause expected by EOB tomorrow; (2) Fort Wayne press-line status to be re-evaluated at the 8 AM safety call; (3) Memphis to confirm whether the up-shift is sustainable or one-time before tomorrow's call. The platform's audit trail captures each decision + owner + due date. Three years ago this call took thirty-five minutes + the action items were on paper.

At 8:00 AM Marcus is on a four-person call with the Fort Wayne plant manager, the corporate EHS Director, and the corporate Maintenance Engineering lead. Last night at 02:14 third shift, a tool changer on the 200-ton press line had a near-miss with the tooling guard interlock — the interlock didn't fully cycle as expected; the operator caught the discrepancy and pulled back; no injury, no equipment damage. The operator self-reported via mobile observation; the platform logged it; the plant supervisor escalated overnight; the daily operations call surfaced it at 7 AM; the 8 AM call is the trade-off conversation.

The Maintenance Engineering lead's hypothesis: an interlock cycle-timing drift after Tuesday's preventive maintenance. The engineering fix — a recalibration plus a software-cycle-time tightening — needs about thirty-six hours to land (Thursday afternoon). Marcus has two options on the table. Option A: run the line under enhanced observation until the fix lands; production continuity preserved, but incident probability elevated for thirty-six hours; if an incident occurs, the cost lands in the $2-4M range including the downstream supply-chain ripple to the auto OEM customer who's the line's biggest pull. Option B: four-hour shutdown for guard inspection + recertification; direct cost ~$120K, extended-day cost $180K if recertification reveals more work; full integrity verification before restart.

The Akron quality hold is already the OTD pressure this week — Fort Wayne shutting down for four hours doesn't add to customer-promised-date risk. Marcus's call: Option B. Shutdown 09:00-13:00; guard inspection + recertification; afternoon-shift restart with enhanced observation pending the Thursday engineering fix. He signs off in SE at 08:24 ET. The decision is logged with the rationale (cost-of-shutdown vs probabilistic cost-of-incident); the plant manager owns execution; the EHS Director monitors. **The platform didn't make the decision. The platform framed the decision for Marcus to make.** That's the executive-level use case — the data lays out the trade-off; the judgment is human; the audit trail captures both.

At 9:30 AM Marcus joins the Q3-Q4 capital allocation review with the CFO and the VP Engineering. Five requests on the table; $4.2M envelope; the asks total $6.5M. Two requests carry direct EHS payback components — Pittsburgh's $1.4M guard-replacement program + Charlotte's $520K ventilation upgrade for the PSM-applicable process — and one (Akron's $1.8M powder-metal press automation) carries indirect EHS benefit through reduced operator exposure to the manual press cycles.

The Pittsburgh guard-replacement narrative is the one Marcus has been building for two years. SE's TCOR data shows Pittsburgh's trailing-three-year cost-of-injury attributable to guard-related events at $1.92M — a combination of one DART case (a hand injury in 2024 that landed in restricted duty for nineteen days), four medical-treatment cases, and a cluster of guard-related near-misses that needed cycle-by-cycle observation as a stop-gap. The projected reduction from the guard-replacement program (based on the engineering team's per-station risk reduction estimates calibrated against industry benchmarks) is 62% over five years. Net present value of the avoided injury cost — discounted at Stratford's WACC — supports the 3.6-year payback before the indirect EMR benefit. Three years ago this business case would have been built in Excel from a workers' comp report that didn't tie cleanly to the operational record; today the case is built from SE's integrated cost-of-injury data with traceable per-event sourcing. The CFO accepts the case; the guard-replacement program is approved for the Q3 envelope. The Charlotte ventilation upgrade is also approved. Akron's automation gets approved at $1.5M (slightly down-scoped). Memphis's quality-inspection cell goes to a Q1 next-fiscal review. Phoenix's capacity addition gets approved for Q4 partial funding contingent on Q3 customer-order confirmation. Net commitment: $4.0M. Marcus signs the capital plan in SE's executive approval workflow.

Marcus eats a salad at his desk during a thirty-minute call with Stratford's strategic-planning lead — Q3 board deck preparation. The board wants to understand whether the multi-year safety investment trajectory is paying off. Three years ago Marcus committed to a program: guard upgrades + EHS staffing + AI-assisted RCA adoption + behavioural safety + the SE platform rollout. The capital + opex commitment over three years totaled about $7.4M. The board's question this quarter — set up in the proxy season cadence — is whether the investment is showing up in the financials and the operational metrics.

The strategic-planning lead has drafted five candidate slides. DART trajectory: 3.2 in Q3-2022 down to 1.9 in Q3-2025, a 41% reduction. Cost-of-injury trajectory: $2.8M in FY22 down to a $1.5M FY25 run-rate, 46% reduction. Production uptime: 94.1% to 96.6%, +250 basis points (the leading-indicator-to-downtime correlation Step 7 will explore further). Workers' comp premium: $4.2M to $2.9M, -31% on the back of the EMR trajectory 1.04 → 0.82. Leading-indicator KPI maturation: hazard reporting rate +71%, safe-behaviour observation ratio 0.91 → 0.96, near-miss-to-incident ratio 4.2 → 8.8. Marcus reviews each chart against the underlying SE data — every cell trace-able to its source. The narrative he wants for the board: "We're not finished — we're paying back faster than the original investment thesis said we would, and the leading indicators say the trajectory holds." Three years ago this deck would have taken a six-person task force two weeks to assemble from disparate sources. Today the strategic-planning lead exports the slides from SE's executive dashboards in an afternoon.

At 1:30 PM Marcus opens an email from the corporate EHS Director with the subject line "the correlation you've been wanting." Three years ago, when Marcus was making the original case for the SE platform investment + the leading-indicator KPI program, his argument to the CFO included a hypothesis he couldn't yet prove: plants that build a strong leading-indicator culture also run at lower unplanned downtime. The argument wasn't novel — Heinrich and DuPont and the academic safety literature had been suggesting it for decades — but Stratford didn't have the data to prove it on its own operations. He'd promised the CFO they'd revisit when they had enough trailing quarters of data to do the regression.

The EHS Director's email contains the chart. Six plants × twelve trailing quarters; the leading-indicator composite (hazard reporting rate × safe-behaviour observation ratio × near-miss-to-incident ratio, normalized) plotted against unplanned downtime. Correlation coefficient r=0.78. Pittsburgh and Charlotte sit in the top-right quadrant — high leading-indicator profile + low downtime. Akron and Fort Wayne sit in the bottom-left — weaker leading indicators + higher downtime. Memphis and Phoenix in the middle. The pattern Marcus has been carrying as an informal conviction for three years now has a chart attached. He forwards it to the strategic-planning lead for the Q3 board deck — adding to slide five with the framing he wants the board to read: "the leading-indicator program isn't just safety-economic — it's manufacturing-economic." He also forwards to a COO peer at a different mid-size manufacturer Marcus has been mentoring informally. The two of them have been discussing the same hypothesis for years; today Marcus can send him the regression. Three years ago this insight would have been a hand-built spreadsheet that nobody had time to maintain. Today the platform held the data continuously until the relationship was visible.

At 3:00 PM Marcus sits with the corporate EHS Director — Marcus's direct report on EHS — for the quarterly strategic 1:1. Forty-five minutes. This isn't an incident review (the daily operations call covers those); it's the "where are we with the strategic safety program" conversation. The structure is well-established: what's working / what's slow / Q3-Q4 priorities. Both sides walked in having read the same dashboard slices.

What's working: leading-indicator KPI maturation (the r=0.78 chart from this afternoon makes the case); AI-assisted RCA bringing average root-cause time from 4.1 days to 1.8 days; the Pittsburgh guard-replacement program just approved this morning; mobile observation reporting with operator self-report rate doubled year-over-year. What's slow: behavioural safety adoption at Akron (the long-tenure workforce has cultural friction with the new program); supervisor-coaching cadence at Fort Wayne (the supervisor ranks have churn from competitive plants in the region); PSM-applicable process documentation at Charlotte (three months behind cadence — a staffing gap the corporate EHS Director is closing); cross-plant observation-quality consistency (standard deviation widening — needs a calibration session for the six plant safety leads). They sketch the Q3-Q4 priorities together. Akron culture work via peer-led behavioural-safety champions. Fort Wayne supervisor-coaching playbook + a corporate Maintenance reset of the preventive-maintenance + interlock-cycle integrity audit (driven by this morning's near-miss). Charlotte PSM catch-up with the EHS Director on-site for a week in June. A network-wide observation-quality calibration session for the plant safety leads. Marcus signs the priority commitments in SE's executive workflow; the EHS Director will surface progress in his next quarterly review.

At 4:00 PM Marcus joins the acquisition-diligence call. Stratford is evaluating an acquisition target — codename Project Glenwood — a smaller specialty manufacturer in Ohio with ~600 employees across two plants. The acquisition diligence team is presenting initial findings; Marcus, the CFO, and Stratford's M&A counsel are on the call along with the diligence-team lead and an outside-counsel partner. EHS is one of about ten diligence threads (others: customer concentration, supply-chain dependencies, IP, tax, employment, environmental remediation, real estate, IT, financial restatement risk, regulatory). It typically gets ten minutes; today Marcus asks for fifteen.

The target's EHS profile reads poorly under Stratford's diligence framework. EMR trajectory climbing 0.91 to 1.18 over five years (the wrong direction for a target with operational-improvement upside on a leveraged transaction). OSHA citations past three years total $340K across seven citations — three of which were willful-eligible-but-cited-serious, signaling poor enforcement-relationship hygiene. No PSM coverage, but one process at ~78% of the threshold quantity — coverage-adjacent, which means a small operational change could trigger PSM and the target has zero PSM-program maturity. TRIR 4.6 against the Stratford network's 2.1 + the NAICS 3361 benchmark of 3.4. No leading-indicator program. No EHS technology; spreadsheet-driven.

Marcus reframes the EHS thread for the diligence team. The target's EHS profile isn't only a downside-risk surface (citation exposure, climbing EMR, threshold adjacency); it's also a value-creation lever. Apply Stratford's playbook — SE platform rollout, corporate EHS Director quarterly cadence, leading-indicator program, guard / preventive-maintenance audit — and the EMR can come down from 1.18 to roughly 0.90 in 24 months and roughly 0.78 in 36 months based on Stratford's own internal trajectory. The WC premium delta from that EMR move projects to about $1.1M annual run-rate by year three. EHS-driven value-creation across five years: roughly $3.4M NPV at Stratford's WACC, on top of whatever operational synergies the deal model already counts. The CFO asks Marcus to put that case in writing for the synthetic-EBITDA build. The deal continues into the next diligence phase. Three years ago "EHS diligence" was a single-page checklist about whether the target had a current OSHA log; today it's a value-creation lens informed by Stratford's own platform-validated trajectory data.

Marcus closes the laptop at 5:45 PM Eastern. The Fort Wayne plant manager texted at 14:08: "press line back up. recert clean. enhanced obs in effect." That's the all-clear Marcus has been waiting for since the 8 AM call. The Akron quality root-cause briefing is on the Quality Director's clock through Thursday. The Q3-Q4 capital plan went into the executive workflow this morning + flows to the CEO for ratification Thursday. The Q3 board deck has a final review with the CEO + CFO Friday morning — the r=0.78 leading-indicator-to-downtime chart from this afternoon now sits as slide six. The Glenwood diligence write-up is on Marcus's task list for tomorrow morning. Friday brings the Tier-1 OEM customer audit at Pittsburgh; Marcus joins remotely; the plant manager + the Quality Director carry it; the audit-readiness package went out this afternoon.

Tonight: dinner with his wife and their younger son who's home from college for the week; a 9 PM check that the Fort Wayne second-shift completion confirmed clean; a brief read of tomorrow's morning briefing pack the strategic-planning lead drafts. Tomorrow brings a different mix — fewer decisions, more strategic writing — the Glenwood synthetic-EBITDA EHS lens, the Q3 board deck final review prep, a one-on-one with the CFO about the FY26 budget build. Marcus has been doing some version of this role for thirteen years; the difference today versus 2018 isn't that the operation runs itself, it's that the operation is legible. He can see what's happening, why it's happening, and what's about to happen next. The platform doesn't replace executive judgment. It replaces the binders the executive used to keep judgment in.