Scrap Reduction Meeting Agenda
A meeting agenda for reviewing top scrap drivers, root causes, and countermeasures in manufacturing. Use it to leave the meeting with clear decisions, action items, and owners for yield improvement.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Manufacturing · Plastics And Molding · Food Processing · Automotive Suppliers
Overview
This template structures a scrap reduction meeting around the facts that matter: the top scrap drivers, the likely root causes, the decisions made in the room, and the action items that need follow-up. It is designed for manufacturing teams that need a repeatable way to review material loss, compare trends across lines or shifts, and assign clear ownership for countermeasures.
Use it when scrap is recurring, when a new defect pattern appears, or when you need a cross-functional discussion with production, quality, maintenance, and materials. The agenda keeps the meeting focused on context, outcome, and next time so the team can see what changed since the last review and what still needs attention. It works well for line-level reviews, plant-level scrap meetings, and corrective-action follow-ups.
Do not use it as a freeform problem-solving session with no data or no follow-up. It is also not the right fit for unrelated operations meetings, customer complaints that require a separate escalation path, or one-off incidents that do not need recurring review. The value of the template is in its repeatable structure: identify the scrap issue, discuss the likely cause, record the decision, and leave with action items that have an owner and due date.
Standards & compliance context
- Use the template as part of your internal quality record when scrap trends may affect process control or product conformance.
- If your site follows a formal corrective-action process, map the meeting's decisions and action items into that workflow.
- Keep the record factual and time-stamped so it can support internal audits or management review without relying on memory.
- Do not use the agenda to replace required nonconformance, containment, or escalation documentation where those procedures apply.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Start by entering the meeting date, line or product scope, and the scrap metrics or defect categories that will be reviewed.
- 2. Assign a facilitator and make sure each agenda item has a clear owner for presenting the data or explaining the issue.
- 3. Review the top scrap drivers one by one, capture the discussion, and record the decision or the next investigation step for each item.
- 4. Convert every agreed follow-up into an action item with an owner, due date, and any needed blocker or dependency.
- 5. Close the meeting by confirming what will be reviewed next time and what data or evidence each owner must bring back.
- 6. After the meeting, share the notes promptly so the team can track progress and avoid reopening the same issue without new information.
Best practices
- Use the same scrap categories and defect names each meeting so trends are easy to compare over time.
- Bring line-level or shift-level data instead of plant-wide averages when the goal is to find the source of loss.
- Record the decision in plain language, not just the discussion, so the team knows what was actually agreed.
- Assign one owner per action item and include a due date to prevent shared accountability from becoming no accountability.
- Capture the suspected root cause separately from the countermeasure so the team can test the right fix.
- Note any blocker, such as missing parts, unavailable maintenance time, or incomplete data, before the meeting ends.
- Review open action items at the start of the next meeting so follow-up does not get lost.
- Attach photos or defect samples when possible, because visual evidence often speeds up root-cause alignment.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this scrap reduction meeting agenda template for?
This template structures a manufacturing meeting around the highest scrap drivers, the root causes behind them, and the countermeasures being tested or assigned. It helps the team move from discussion to decisions and action items instead of leaving with a vague list of problems. Use it when scrap is recurring, costly, or tied to a specific line, shift, material, or process step.
How often should we run this meeting?
Most teams use it weekly or biweekly, depending on scrap volume and how quickly the process changes. If a line is unstable or a new material is being introduced, a shorter cadence can help the team react faster. Once the main drivers are under control, the meeting can shift to a lighter review cadence focused on trend monitoring and follow-up.
Who should run the meeting?
A production manager, continuous improvement lead, quality engineer, or plant supervisor usually facilitates it. The best facilitator keeps the agenda tight, confirms the data, and assigns action items with an owner and due date. Operators, maintenance, quality, and materials representatives should attend when their input is needed to explain the scrap pattern or implement a countermeasure.
What should be included in the agenda?
The agenda should cover the top scrap categories, the current trend or context, suspected root causes, decisions made in the meeting, and action items with owners and due dates. It should also leave space for blockers, follow-up, and what to review next time. That structure makes it easier to compare meetings and track whether countermeasures are actually reducing scrap.
Is this template useful for compliance or audit purposes?
Yes, because it creates a traceable record of the issue, the discussion, the decision, and the assigned follow-up. That can support quality management systems, internal audits, and corrective-action workflows when scrap is tied to process control or nonconformance. It is not a substitute for formal CAPA documentation when your organization requires one, but it can feed that process cleanly.
What are the most common mistakes when using a scrap meeting agenda?
A common mistake is turning the meeting into a general complaint session without data, owners, or next steps. Another is focusing only on the symptom, such as the scrap count, without recording the likely root cause or the countermeasure being tested. Teams also lose value when they skip the follow-up section and never close the loop on prior action items.
Can this template be customized for a specific line, product, or shift?
Yes, and it should be. You can tailor the agenda to a single line, product family, shift, or defect type so the discussion stays relevant and actionable. Many teams also add fields for machine, material lot, defect category, or containment status if those details help them spot patterns faster.
How does this compare with ad-hoc scrap discussions?
Ad-hoc discussions are faster to start, but they often miss key details and make it hard to track whether a countermeasure worked. This template gives the meeting a repeatable structure so the team can compare one review to the next and see whether scrap is trending down. It also makes ownership clearer because each action item has a named person and due date.
What data should we bring to the meeting?
Bring the latest scrap counts or rates, the top defect types, affected machines or lines, and any recent changes in material, setup, staffing, or process settings. If available, include photos of defects, containment status, and notes from operators or quality checks. The goal is to discuss evidence, not guesswork.
Related templates
Ready to use this template?
Get started with MangoApps and use Scrap Reduction Meeting Agenda with your team — pricing built for small business.
