Production Scheduling for Job Shops: When the Whiteboard Stops Working

Job shop production scheduling outgrows a whiteboard when the board can no longer hold the four things a schedule depends on: capacity, routing, material, and due dates. The fix is getting those inputs into one place, visible on the floor, before you automate anything clever.

Here is a Monday we hear about often in job shops. The production manager arrives at 6:45, and the whiteboard says the CNC mill runs brackets first, then housings. Over the weekend, a customer called the owner and a rush job jumped to the top. Housing material has not arrived. Second shift scrawled a note that the bracket fixture is cracked. By 7:30, three people have rewritten the same column, and the saw sits idle because nobody knew it was free.

Nobody did anything wrong here. The board just had no room for all the information it was being asked to hold.

The whiteboard stops working before anyone admits it

Shops rarely decide to leave the whiteboard. They drift away one workaround at a time: a spreadsheet, then another for material, then a text thread for hot jobs. The signs:

• Constant reshuffles. The job order changes several times a day, by memory.
• Hot jobs that never cool down. When everything is urgent, nothing is clearly next.
• Idle machines next to a backlog. Work is waiting at the wrong machine or for the wrong part.
• Late news on due dates. Someone learns a job is late on the day it should ship.

Kyo has written before about why small production issues turn into big delays. The schedule is where every one of those delays eventually lands.

What does a real schedule need to know?

In most job shops, four inputs matter, and each usually lives somewhere different today.

• Capacity. Hours each work center (a machine, cell, or crew doing one kind of operation) actually has this week, after maintenance and absences. Often it lives in the production manager’s head.
• Routing. The sequence of operations a part follows (saw, mill, deburr, inspect), with setup and run time for each. It may sit on a traveler (the paper packet that follows a job through the shop), in an ERP (enterprise resource planning, the system that handles orders, inventory, and accounting), or nowhere at all.
• Material. Whether stock, purchased parts, and outside processing are on hand. Usually that is a purchasing spreadsheet or the buyer’s inbox.
• Due dates. The date promised to the customer, and whether it changed. That is in the order system, in email, or in the owner’s last phone call.

When these live in four places, people reconcile them by hand at the whiteboard. Kyo’s article on managing work order requirements and milestones covers keeping job details in one record, the foundation scheduling builds on.

Do you need finite capacity scheduling or a better priority board?

Finite capacity scheduling means the schedule only loads each machine with as much work as it can actually do in the time available. If the mill has 40 hours this week, the schedule will not give it 55. Infinite capacity planning, by contrast, lines jobs up by due date and assumes the hours will be there.

A priority board is simpler. It ranks jobs and shows what is next at each work center, without checking whether everything fits.

• A priority board is often enough when routings are short and the real problem is that nobody can see the current order.
• Finite capacity starts to earn its keep when jobs share bottleneck machines, setups are long, and you regularly promise dates that the floor cannot hit.

Starting with the board and adding capacity math later is a perfectly good path.

Put the schedule on the floor without another login

A schedule on the production manager’s laptop is just a private whiteboard. Operators need to see what is next at their station and report when a job starts, stops, or hits a problem. That usually means a shared screen or tablet at each work center showing its queue, with one-tap start, complete, and hold. Operators do not need a separate login, and nobody has to walk to the office to see what is next.

Those updates also give you what the whiteboard never could: actual times. Kyo’s post on how to gather real-time production statistics shows how that data turns schedule guesses into numbers you can trust.

Automate in stages: visibility, then capacity, then what-if

Stage 1: visibility. One job list, one queue per work center, live status from the floor.

↓

Stage 2: capacity. Routing times and available hours, so overloaded machines get flagged.

↓

Stage 3: what-if. Test a rush job or machine outage and see which due dates move.

Each stage pays off on its own. Stage 1 alone can take a lot of the Monday-morning rewriting off the production manager’s plate.

The platform matters less than the inputs. Some shops use a scheduling module in their ERP. Others build a custom application on a platform like Claris FileMaker, which can keep jobs, routings, and floor updates in one place across desktop, iPad, and web browser. The right answer matches how your floor works.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help job shops pull capacity, routing, material, and due dates into one schedule the whole floor can see.

Frequently asked questions

Can a spreadsheet handle job shop production scheduling?

For a while, yes, if one person owns it and the job mix is stable. It struggles once several people update it at once and material and routing data live elsewhere.

What is the difference between an MES and a scheduling tool?

An MES (manufacturing execution system) tracks what is happening on the floor in real time: job status, labor, quality checks. A scheduling tool decides what should happen next. The two work best when they share the same job data.

Do we need accurate routing times before we start?

No. Start with the times you have and let actual floor data correct them over a few weeks.

Not sure your job data is solid enough to schedule from? Book a free 20-minute Data Health Check and we will tell you what we see.