Changeover SMED Verification

It covers the full changeover walk-through from pre-changeover readiness through external setup, internal step timing, standard work adherence, and final results. The template is designed to verify whether the changeover can be completed within the target window and whether the observed sequence matches the approved method. It also captures non-conformances, so you can assign follow-up actions instead of relying on memory. This makes it useful for both production audits and continuous improvement reviews.

Use it during planned product, SKU, tooling, or format changes where changeover speed and repeatability matter. It is especially useful when you want to separate external work from internal work and confirm that setup tasks are being staged before downtime. It is not meant for emergency repairs, unplanned breakdown response, or routine operator checks that do not involve a formal changeover. If the line is not switching over to a new run, a different inspection template is usually a better fit.

A supervisor, industrial engineer, continuous improvement lead, or trained auditor can run it, and the best results usually come from someone who understands the standard work and the actual machine sequence. Operators should be involved because they know where waiting, motion, and handoff delays occur in practice. If the changeover affects safety controls, maintenance or EHS support may also need to observe. The key is that the inspector can compare the observed method against the approved changeover SOP.

It can be used every time a critical line changes over, or on a scheduled cadence such as weekly or monthly for audit sampling. Many teams start with frequent checks on high-impact equipment, then reduce frequency once the process is stable and the standard work is being followed consistently. It is also useful after a tooling change, new SKU launch, or any change to the setup method. If changeover time starts drifting, increase the cadence until the root cause is corrected.

It supports operational control and documentation, but it is not a substitute for a safety program or lockout-tagout procedure. The template helps verify that safety controls are planned before downtime and that the changeover follows the approved method, which aligns with OSHA general industry expectations and ANSI/ASSP-style standard work discipline. If the changeover involves guarding, energy isolation, or hazardous motion, the team should also follow the applicable safety program and site procedures. For food or regulated environments, the same structure can support FDA Food Code or quality system expectations where change control matters.

Common misses include staging parts too late, using the wrong tooling or gauges, and losing time because tools are not labeled or organized. Teams also often discover that the observed sequence does not match the approved standard work, or that internal steps include unnecessary motion and waiting. Another frequent issue is failing to document deviations clearly enough to assign corrective action. This template makes those gaps visible in one pass instead of after the line is already back in production.

Yes, and it should be customized to the equipment family, product format, and the specific changeover steps that matter for that line. You can add machine-specific gauges, torque values, fixture checks, or safety controls without changing the overall structure. Many teams create one version for each major line or product family so the timing and readiness checks stay relevant. The goal is to keep the template close to the actual work, not generic across every asset.

An informal checklist often confirms that the changeover happened, but it does not show where time was lost or whether the sequence was followed correctly. This template captures external and internal step timing, readiness, and deviations, which makes it much more useful for SMED improvement work. It also creates a record you can trend across shifts, operators, or product families. That makes it easier to identify recurring non-conformances instead of treating each changeover as a one-off event.