Foreman / Supervisor field #2

New Issue

spencerm · 2026-08-04T20:02:16Z

spencerm commented

2026-08-04 20:02:16 +00:00

One more thing to weigh in on. We already capture the Department on each NCR, which gives good visibility for department-level trending. I've been going back and forth on whether we should also capture Foreman/Supervisor, since that level of detail could help us spot patterns like a particular crew or shift showing up repeatedly (useful for the root cause trending in API Q1 §6.4.2). But I don't want the intake form to get bogged down or feel like it's calling people out. Thoughts????
We could add Foreman/Supervisor as a field captured during the Root Cause step, not at initial NCR intake and pull it from a dropdown tied to existing job/crew assignments rather than a manual free-text entry.
That would keep it useful for a trend analysis without slowing down the initial report, and it stays framed as a process factor rather than a blame factor.
Let me know if that's workable, or if there's an easier way to pull that data automatically from job records instead of adding another manual field.

One more thing to weigh in on. We already capture the Department on each NCR, which gives good visibility for department-level trending. I've been going back and forth on whether we should also capture Foreman/Supervisor, since that level of detail could help us spot patterns like a particular crew or shift showing up repeatedly (useful for the root cause trending in API Q1 §6.4.2). But I don't want the intake form to get bogged down or feel like it's calling people out. Thoughts???? We could add Foreman/Supervisor as a field captured during the Root Cause step, not at initial NCR intake and pull it from a dropdown tied to existing job/crew assignments rather than a manual free-text entry. That would keep it useful for a trend analysis without slowing down the initial report, and it stays framed as a process factor rather than a blame factor. Let me know if that's workable, or if there's an easier way to pull that data automatically from job records instead of adding another manual field.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spencerm/pesco-ncr#2