Daily Production Scheduling Meeting Checklist

0%

0 of 33 items complete

9 critical items still open - these are the highest-risk gaps.

Free, optional. Reopen it on any device.

Download checklist:

Before the meeting (scheduler prep)

Refresh the open operations and dispatch list from the ERPCRITICALList jobs past due and jobs with critical ratio below 1CRITICALUpdate yesterday's output vs plan by work centerPull material shortage report for jobs due in the next five daysCRITICALCheck the maintenance calendar for planned stops today and tomorrowCheck labor attendance and skill coverage per shiftPrint or display the plan so every owner sees the same version

Yesterday: what happened

Plan vs actual output reviewed for the bottleneck resourceCRITICALTop three causes of lost time recorded with an ownerScrap and rework that changed the schedule notedJobs completed late and the reason code capturedSafety or quality events that affect today's work raised

Today: what must ship or finish

Ship-today list confirmed against what is actually completeCRITICALJobs due within 48 hours checked for open operations and open inspectionsCRITICALExpedite requests reviewed and ranked, not all acceptedFirst operation of each job confirmed to have material, tooling, programs and drawingsOutside processing returns due today confirmed with supplier statusCustomer promise date changes identified and sent to sales

Constraints and resources

Bottleneck work center has a full queue for the next two shiftsCRITICALOperators with the needed skills assigned to constrained machinesMachine down or degraded status reviewed with maintenanceTooling, fixtures and gauges due for the next jobs are availableNC programs and first-article requirements ready for upcoming setupsOvertime, extra shift or outsourcing decisions made against load, not habit

Material and supply

Shortages listed by part, job, needed date and buyerCRITICALPurchase orders past due reviewed with promised datesInventory accuracy issues that blocked a job raised for cycle countEngineering changes or deviations affecting open jobs identified

Close the meeting

Every action has an owner and a time it will be reported backCRITICALSchedule changes written into the ERP or scheduling tool the same dayFrozen window respected, with exceptions logged and approvedMeeting finished in the agreed time, no more than 15 to 20 minutesEscalations sent to plant manager, purchasing or sales as needed

Run it as a standing agenda. If critical items are repeatedly skipped, fix the data feed or the owner, not the meeting length.

Want the daily pack built from your ERP?

We can show how late jobs, shortages and capacity are pulled together automatically. Optional.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the checklist

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.

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

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

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

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.

Frequently Asked Questions

How long should a daily scheduling meeting take?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

MES & Shop Floor

More MES & Shop Floor tools

See all