Many manufacturing companies believe that effective production planning requires an MES.
In reality, planning must work before automation.
Microsoft Project, combined with a simple and structured method, can already answer the most important production questions:
- How loaded are my machines?
- Where are the bottlenecks?
- Which orders are at risk?
- What is my real lead time?
This page explains how to use Microsoft Project for production planning, even when no MES is available.
The real role of Microsoft Project in manufacturing
Microsoft Project is not an MES and was never designed to manage shop floor execution.
Its real strength is different:
- planning
- sequencing
- workload visibility
- realistic dates based on constraints
Used correctly, Project becomes a decision-support tool, not a reporting tool.
Planning must work before MES
An MES can close the loop, but it cannot create order where no method exists.
If:
- orders are unclear
- cycles are not defined
- phases are inconsistent
- waiting times are ignored
then an MES will only digitize confusion.
A solid planning method must work even without MES.
Orders, cycles, phases, waiting times
Effective planning starts with structure.
Each order must have:
- a clear work cycle
- defined phases
- assigned resources (machines or departments)
- realistic waiting times between operations
Waiting times are not errors.
They represent:
- queues
- setup delays
- transport
- availability constraints
Ignoring them produces optimistic plans that fail immediately.
What Project should answer (and what it should not)
Microsoft Project should answer one core question:
How loaded is each machine over time?
It should not be used to:
- track real-time progress
- collect shop floor feedback
- manage operators minute by minute
That is MES territory.
Project decides priorities and capacity, not execution.
The turning point: filtering by resource
The most powerful way to use Microsoft Project is resource filtering.
When you filter by:
- lathe
- milling machine
- work center
- department
Project automatically shows:
- all assigned tasks
- distributed over time
- with calculated durations and overlaps
This is real machine workload visibility, without manual calculations.
Overlaps are not errors (yet)
When you look at machine workload, you will see:
- overlapping activities
- multiple orders competing for the same resource
This is not a mistake.
It is an honest picture of demand.
Overlaps mean:
- priorities must be decided
- sequencing must be adjusted
- not everything can be done at the same time
Balancing will come later.
First, visibility.
Working without an MES: how to guide the shop floor
Without an MES, production still needs clear instructions.
The rule that works in practice:
- short planning horizon
- one week, maximum two
- frequent updates
Reality always changes:
- machines break
- operators are absent
- materials arrive late
- priorities shift
Long plans become obsolete quickly.
Two practical ways to create a work list
Method 1 — Manual Excel list (simplest)
A simple Excel file is often enough.
It contains:
- machine or department
- order or job code
- phase
- priority
- notes
This list:
- is updated weekly
- is shared with the shop floor
- drives daily work
Clarity beats automation.
Method 2 — Using Project as a work-list generator
Microsoft Project can also generate the list.
The method:
- filter by resource
- filter by start date ≥ today
- filter by finish date ≤ today + 1 or 2 weeks
Project returns:
- ordered phases
- consistent with the plan
- ready to print and use
This is not rigid scheduling.
It is operational guidance.
Why planning too far ahead makes no sense
Without an MES:
- Project does not know what was actually done
- no automatic feedback exists
- no real-time updates are available
For this reason:
- planning must be reviewed often
- not extended endlessly
Short, realistic planning is more reliable than long, optimistic plans.
Project decides, the shop floor executes
Each tool has a role:
- Microsoft Project → priorities and capacity
- Excel / work lists → daily execution
- MES (when available) → closes the loop
This method works:
- today, without MES
- tomorrow, with MES
That is why it is solid.
Starting from a ready structure
If you want to start with a ready-to-use structure instead of building everything from scratch, I’ve prepared a small starter pack based on this exact method.
It includes:
- an Excel file for orders and workload
- Microsoft Project base files
- a ready calendar setup
- examples you can adapt to your reality
👉 You can find it here:
Production Planning – Starter Pack
(No registration required. Download after payment.)
What comes next
In the next pages, we will see:
- how to refine priorities
- how to reduce overlaps
- how to prepare the transition to an MES, when needed
For now, the foundation is clear:
Planning must work before automation.
Production Planning Tools: Excel, Microsoft Project and Beyond
👉Get the Production Planning Tools: Excel Microsoft Project and Beyond
Looking for a structured solution?
If your production planning has grown beyond spreadsheets and basic tools, and you are evaluating a more structured approach, you can get in touch to discuss your context.