Every build-critical part needs a source, a date, a place and an owner

Before a planned build, each build-critical part should connect to four things: where it comes from, when it is expected, where it will be received, and which role is responsible for chasing it. A gap in any of the four is a readiness question, not yet a problem.

Sourcing owns supplier communication. Production and quality raise what they need; they do not agree dates with suppliers directly.

Sample readiness register

Fictional Atlas register for trial build 3. Dates refer to weeks of the sample program; unanswered items remain visible.

Part Source and expected availability Receiving point Owner and next question
Bracket B-214 Rev C Bracket supplier; provisional week 15 Tuesday Plant 2 receiving, Dock 4 Sourcing lead: confirm Rev C tooling at the pre-build review.
Connector C-77 Connector supplier; revised week 15 Thursday, one week later Plant 2; receiving dock still to confirm Material planner: confirm dock and effect on build 3 at the supply call.
Heat sink H-30 Heat-sink supplier; provisional week 15 Monday Plant 2 receiving, Dock 4 Design engineer: resolve compatibility with the Rev C bracket in the handoff session.
Fastener kit F-12 Plant 2 standard stock; quantity check before build 3 Plant 2 stores, trial-build kit area Stores role: confirm quantity at the kit pull before build 3.

Review supplier acknowledgements

  1. 1

    Compare the acknowledgement with the order

    Check part number, revision, quantity and delivery date line by line against what the build needs.

  2. 2

    Mark every mismatch

    Note differences in revision, quantity or date, and which build or line each one affects.

  3. 3

    Record the impact

    State in one sentence what is affected, for example: trial build 3 cannot start the connector step before the revised date.

  4. 4

    Hand the item to the owning role

    Pass unresolved mismatches to the sourcing lead or program role, with the register line and the next coordination point. The handoff does not promise a resolution.