Route the issue to its function, with context
If production meets an issue or an open readiness item during launch, send it to the function that can act on it and include four things: the product and revision, the plant and line, the shift, and the reference you were working to.
Anything involving an immediate safety concern follows your site's approved escalation procedure first. This page covers coordination afterwards.
Who picks up what
Roles, not named people. Your site's help route lists who currently holds each role.
Engineering change
A drawing, tolerance or design-intent question. Goes to the design engineer for the product, with the revision and the feature affected.
Material or supplier dependency
A late, short or mismatched part. Goes to the sourcing lead or material planner with the part number and affected build.
Production coordination
A line, fixture or shift-handover question. Goes to the production engineer for the receiving line.
Quality evidence
A recurring observation or an evidence review question. Goes to the quality engineer with the log entry and reference.
Write the request so it can be acted on
-
1
Describe what you saw
One or two sentences on the observation, without guessing the cause, for example: connector needs repositioning on 4 of 20 units at position 3.
-
2
Link the reference
Cite the drawing, log entry or register line with its revision.
-
3
State the impact and the owner role
Say what is blocked or at risk, and which role you are asking to take it.
-
4
Agree how updates will be shared
Name the forum or channel where the answer will be posted and who will post it.