MS Project, MeisterTask or Excel: where the project status belongs in machine building.
MS Project plans the schedule and MeisterTask distributes tasks, while Excel holds everything else together. What each tool does well in machine and plant building, where it stops and why the project status often sits in none of them.
MS Project suits schedules with dependencies and a critical path, MeisterTask suits team tasks on a board, and Excel suits quick lists. Machine and plant builders often run all three side by side. None of them keeps the actual status with customer changes, commitments and open points by itself, because it is created in emails and minutes.
Contents
Management asks where the plant for the customer in Poland stands. The project manager opens three windows. In the MS Project plan, assembly is still in the green. On the engineering team's MeisterTask board, four cards are on "In progress". In the Excel list of open points there is a question to the customer that, according to the "Done" column, was answered two weeks ago. What the customer replied is in none of the three files. It is in an email to the head of engineering.
That is what project work looks like in many machine building companies. Each tool does its part well. None of them knows the whole status of the project.
What do MS Project, MeisterTask and Excel each do?
MS Project is a planning tool. Tasks, dependencies, milestones and the critical path can be modelled cleanly. If delivery of the control cabinet slips, you can see what slips behind it, right through to the FAT and commissioning. A baseline lets you compare plan against actual. The downside is that MS Project needs maintaining, and usually only the project manager can do that.
MeisterTask is a tool for team tasks. A project is a board with columns, and each task is a card with an owner, due date, checklist and attachments. Design engineers see at a glance what is on their desk. Introducing it takes hours, not weeks. It is not built for long chains of dates across several departments.
Excel is the tool everyone has. Open points list, change list, schedule overview, bill of materials comparison: each one is created in a few minutes and looks exactly the way the project manager needs it. That is precisely what becomes a problem later. Every list has its own format, its own logic and, after a few weeks, several versions.
How do the three differ in day-to-day project work?
| MS Project | MeisterTask | Excel | |
|---|---|---|---|
| Schedule with dependencies | yes, core function | limited | by hand only |
| Distributing tasks in the team | possible, but cumbersome | yes, core function | as a list |
| Introduction | training needed | a few hours | none |
| Who maintains it | usually only the project manager | every team member | whoever has the file open |
| Customer changes, commitments, decisions | only as a note on the task | as a comment on the card | as a row, if someone enters it |
| Source for an entry | no | attachment possible | reference by hand |
The last two rows are why the project manager in the example opens three windows and still has to search for an email. The details on the tools are as of November 2026.
Which tool fits which project?
Special-purpose machine or plant with a long lead time and many trades. A schedule with dependencies is essential here, in MS Project or a comparable planning tool. Costs and purchase orders usually stay in the ERP.
Engineering team with many parallel tasks. A board like MeisterTask shows who is working on what and replaces the question "How far along are you?" at every desk.
Small projects, retrofits, spare parts orders. Excel is often enough. What matters is that there is one list per project, not one per person.
In practice many machine builders run all three side by side, plus the ERP. That is not a mistake. Each tool covers a different question.
Why is the project status still missing?
Because the substance of a project's status is not created in these tools. It is created in the email in which the customer confirms a change to the safety enclosure. In the minutes of the design review where the decision was made to swap the drive. In the order confirmation in which the supplier names a later date than the one requested.
For that information to reach MS Project, MeisterTask or Excel, someone has to read it, understand it and copy it across. That takes time, and it does not always happen. A head of engineering in special-purpose machine building with ten design engineers described what that means for him. By the time the status of all projects has been collected, the first 12 hours of the week are gone.
Why another list does not solve this problem is covered in the article on project status in Excel, OneNote and email. A broader overview of planning and ERP tools is in the article on project management software in plant engineering.
What can you improve with the tools you already have?
One place for the status. Decide which tool gives the binding answer to "Where are we?". The others refer to it.
Decisions with a source. Whoever enters a change links the email or minutes it came from. That takes ten seconds and saves the search later.
Do not keep open points twice. One open points list per project, not cards on the board and notes in the plan as well.
Reconcile weekly, not in the meeting. If plan, board and list are reconciled before the status meeting, the meeting can be used for decisions. What that looks like is described in the article on project status without status meetings.
Where does KoAssist fit into this picture?
KoAssist is the AI agent for machine and plant builders, not another project management tool. It does not plan dates or distribute tasks.
Project Memory starts where the table above stays empty. It reads the specification, emails and minutes for a project and records what they say: status, open points, decisions and risks, each entry with a reference to its source. When an email with a customer change arrives, a proposal is created. It only becomes valid once someone on the team accepts it. Project Memory is currently in pilot operation with existing customers.
Schedule and tasks stay where they are today. If you would like to see how this looks on one of your own projects, you can book a demo.
Frequently asked questions
More from the blog
Back to overview- 15 November 2026Article5 min
Can ChatGPT analyse a customer specification?
An 80-page customer specification, and the quotation has to go out by Friday. What ChatGPT does well in the analysis, where it reaches its limits and what to settle before a customer specification ends up in a chat window.
5 min - 15 November 2026Article4 min
Backing change orders in plant engineering: how additional work from customer changes gets paid
Customer changes create additional work, and it only gets paid when it is backed by evidence. What a change order in plant engineering needs, when to submit it and which documents make the difference at the final invoice.
4 min - 15 November 2026Article4 min
How much time does coordination cost in design engineering?
Collecting status, answering questions, preparing status meetings: in design departments, coordination takes up many hours a week. Two cases from special-purpose machine building and a simple method for measuring your own effort.
4 min
