# Daily Production Scheduling Meeting Checklist > Source: https://netray.co/tools/daily-production-scheduling-meeting-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A structured agenda for the daily scheduling meeting so late jobs, shortages and constraints are reviewed in the same order every day. ## Category mes-shop-floor ## Audience - Production scheduler - Production supervisor - Plant manager ## Tool **Kind:** checklist **Groups:** #### Before the meeting (scheduler prep) **Items:** **Text:** Refresh the open operations and dispatch list from the ERP **Critical:** true **Text:** List jobs past due and jobs with critical ratio below 1 **Critical:** true Update yesterday's output vs plan by work center **Text:** Pull material shortage report for jobs due in the next five days **Critical:** true Check the maintenance calendar for planned stops today and tomorrow Check labor attendance and skill coverage per shift Print or display the plan so every owner sees the same version #### Yesterday: what happened **Items:** **Text:** Plan vs actual output reviewed for the bottleneck resource **Critical:** true Top three causes of lost time recorded with an owner Scrap and rework that changed the schedule noted Jobs completed late and the reason code captured Safety or quality events that affect today's work raised #### Today: what must ship or finish **Items:** **Text:** Ship-today list confirmed against what is actually complete **Critical:** true **Text:** Jobs due within 48 hours checked for open operations and open inspections **Critical:** true Expedite requests reviewed and ranked, not all accepted First operation of each job confirmed to have material, tooling, programs and drawings Outside processing returns due today confirmed with supplier status Customer promise date changes identified and sent to sales #### Constraints and resources **Items:** **Text:** Bottleneck work center has a full queue for the next two shifts **Critical:** true Operators with the needed skills assigned to constrained machines Machine down or degraded status reviewed with maintenance Tooling, fixtures and gauges due for the next jobs are available NC programs and first-article requirements ready for upcoming setups Overtime, extra shift or outsourcing decisions made against load, not habit #### Material and supply **Items:** **Text:** Shortages listed by part, job, needed date and buyer **Critical:** true Purchase orders past due reviewed with promised dates Inventory accuracy issues that blocked a job raised for cycle count Engineering changes or deviations affecting open jobs identified #### Close the meeting **Items:** **Text:** Every action has an owner and a time it will be reported back **Critical:** true Schedule changes written into the ERP or scheduling tool the same day Frozen window respected, with exceptions logged and approved Meeting finished in the agreed time, no more than 15 to 20 minutes Escalations sent to plant manager, purchasing or sales as needed **Scoring Note:** Run it as a standing agenda. If critical items are repeatedly skipped, fix the data feed or the owner, not the meeting length. ## Content **Intro:** A good daily scheduling meeting is short, factual and the same every day. This checklist gives the agenda and prep list so late jobs, shortages and constraints are reviewed in order and every action leaves with an owner. **Sections:** #### How to use the checklist **Body:** The scheduler works through the prep group before the meeting and the other groups during it. Tick items live on a screen or print the page for the board. Items marked critical are the ones that cause late shipments when missed. Export the ticked list to PDF to keep a record of what was reviewed, or to Excel to track the repeating gaps over a month. The aim is a fifteen minute meeting that ends with decisions, not a status tour. **Bullets:** - Hold the meeting at the same time and place. - Stand up and keep to the agenda. - Take problem solving outside the meeting. #### Why this order works **Body:** The agenda starts with yesterday because causes of lost time are facts, then moves to what must ship today because that is the commitment, then to constraints and material because they decide whether the commitment can be met. Closing with owners and times turns discussion into action. This follows the common tier meeting pattern used in lean operations, adapted for a scheduler who owns the plan and must keep the ERP and the floor in agreement. #### What good data prep looks like **Body:** The meeting fails when someone says they will check. The scheduler should arrive with the dispatch list, the past due list, the shortage report and the capacity view for the bottleneck. In most ERPs these are standard reports or short queries. If building them takes an hour, automate them first. A prepared scheduler shortens the meeting more than any facilitation technique, and it makes attendees trust the numbers. #### Common mistakes **Body:** Letting the meeting become a place to solve each problem makes it run long and loses attendees. Accepting every expedite request destroys the plan for everyone else. Not writing schedule changes back into the system leaves the ERP dispatch list wrong for the next shift. Skipping the meeting when things are calm removes the habit you need when things are not. Keep the rhythm and log the exceptions. **Cta:** If prep takes too long because data sits in several screens, we can assemble the late job, shortage and capacity views from your ERP automatically. **Faq:** #### How long should a daily scheduling meeting take? **Answer:** Fifteen to twenty minutes is typical, standing, with the same agenda each day. If it runs longer, move problem solving to a separate session with only the people involved and keep the meeting for status, constraints and actions. #### Who should attend? **Answer:** The scheduler, production supervisors, a materials or purchasing representative, maintenance and quality when relevant. Add sales or customer service when promise dates are at risk. Keep attendance to people who own an action. #### Should every expedite be accepted? **Answer:** No. Rank them against customer impact and available capacity, and protect the bottleneck. Accepting everything removes the meaning of priority and usually makes more jobs late, including the ones already on time. #### What if our ERP data is not trusted? **Answer:** Start with the bottleneck and the ship-today list, which people can verify physically, and fix the data gaps that cause disputes. Trust returns when the same few reports are right for several weeks in a row. ## Search terms daily production meeting agenda, production scheduling meeting checklist, daily tier meeting manufacturing, morning production meeting template, scheduler daily checklist, shop floor daily review, production planning daily standup --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json