Checklist

MPS & BOM Reconciliation Script

An interactive weekly reconciliation checklist to keep BOMs, routings, and the Master Production Schedule aligned. Records results, captures mismatches and examples, and creates a simple escalation record so change-control owners can act before schedules fail.

Interactive Tool

MPS & BOM Reconciliation Script

This interactive checklist helps production, planning, and engineering teams run a short weekly reconciliation between Master Production Schedule (MPS), Bills of Materials (BOMs), and routings. Use it to confirm changes are captured, identify mismatches that threaten execution, and escalate unresolved problems to the change-control owner. Aim to complete this once per weekly planning cycle. Keep entries factual: reference part numbers, revision IDs, impacted orders, and any immediate actions taken.

Acceptance criteria: BOM change log reviewed; MPS demand checked against BOM and routing constraints; any mismatch is recorded with examples and either resolved or escalated with an assigned owner and ticket/reference.

Enter date (YYYY-MM-DD).
Person who completed the check (name and role).
Select site or line for this reconciliation.
Free-text name when Other is chosen.
Confirm you reviewed the BOM/engineering change log covering the reconciliation period.
List affected part numbers, revisions, and brief impact notes (examples: PN123 rev B -> rev C affects qty or component substitution). Include links or ticket IDs if available.
Confirm you compared current MPS planned orders against the BOM and routing constraints for mismatches (missing components, superseded parts, change in routing steps).
Enter a count (0 if none).
For each example include part number, MPS order or date, BOM revision difference, and expected execution impact (e.g., expedited order, possible scrap, hold).
Note temporary fixes applied (manual workarounds, short-term buys, schedule hold) and who was notified.
If Yes, provide escalation details below. Escalate anything that could cause expedites, cancellations, stoppages, or scrap.
Owner responsible for resolving the mismatch.
Reference number, ticket URL, or change request ID if created.
Rate urgency 1 (low) to 5 (critical).
Planned date to resolve or re-review (YYYY-MM-DD).
Select the best description of schedule impact.
Provide details for Other.
List next steps, responsible people, and deadlines. Examples: update BOM rev, update routing step, create PO for missing component, update digital work instruction.
Select the current status after this check.
Anything else planners, engineers, or production should know (root-cause hints, recurring patterns, supplier notes).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.