Why does project status in Excel, OneNote and email take so long to pull together?

Monday, just before eight. The project meeting with the customer is at nine, and the project manager wants to know where the project really stands. She opens the open-points list in Excel. She opens OneNote with the notes from the last site meeting. And she searches her inbox for the email in which the customer confirmed the change to the safety guarding.

An hour later she has a status. By Wednesday it is out of date again.

Almost everyone who runs projects in machine building and plant engineering knows this pattern. The status exists, but nowhere in full. It has to be rebuilt every single time.

How is project status assembled in plant engineering today?

A typical case in one-off and special-purpose manufacturing looks like this. Three sources carry the status, and each follows its own logic.

The Excel list of open points. Number, topic, owner, due date, status. It is what goes up on the screen in the meeting. But it is only as current as the last person who updated it, and there are often two versions because someone saved a copy locally.

The OneNote notes from meetings and phone calls. This is where you find what was agreed in the FAT preparation meeting, which question about the bill of materials is still open and who is calling back by when. Everyone takes notes a little differently, some in the team notebook, some in their own. How to bring order to that is covered in the article on OneNote in projects.

The emails. This is where the actual decisions are made. The customer sends a change to the specification, the supplier moves a delivery date, sales promises the customer something. These emails sit in individual mailboxes, often deep in a thread whose subject line is about something else entirely.

Building the status therefore means reading, reconciling, chasing and copying. Every time someone needs it.

What does scattered status gathering really cost?

The obvious cost is the hours spent pulling it together. The more expensive costs only show on a second look.

Duplicate work. The same information is recorded two or three times. Once in the email, once in the minutes, once in the list. Every copy is a chance for an error, such as a date carried over wrongly.

Stale lists. When the list is wrong, the team stops trusting it. Then everyone asks directly instead, and the list gets updated even less often. It reinforces itself.

The project manager as a human router. Because only the project manager has an overview of all three sources, every question goes through them. Engineering, purchasing, assembly and commissioning ask about the current revision or the confirmed date. If the project manager is away for a week, the information stops flowing.

Lost agreements. The most dangerous decisions are the ones that exist only in an email. When the customer asks at acceptance who approved the modified design, the team ends up searching the mailbox of someone who may no longer be on the project. How to secure those agreements is the subject of the article on project decisions from email.

Why does one more list not solve the problem?

The obvious reflex is a new tool. A better template, a task board, a project module in the ERP. That is not wrong, but it only moves the problem.

Every new list needs someone to fill it. Decisions are still made in emails and meetings, not in the tool. So someone still has to copy them across, now into one more system. A few weeks later there is the old Excel list, the new board and the emails, and none of them is complete.

Project management software is strong at schedules, resources and costs. But it manages what someone types in. Where exactly it helps and where the status is still missing is explained in the article on project management software in plant engineering.

The core point is simple. As long as the status has to be copied by hand from the sources into a list, how current it is depends on the discipline of individual people. And in project business they have more important things to do.

What can you improve straight away without a new tool?

Quite a lot can be done better with what you already have.

• One place for decisions. Agree that every decision lands in a column or on a page with date and source, even if it was made in an email. One sentence plus a reference is enough.
• Minutes with a fixed structure. Every set of meeting minutes ends with three blocks, decided, open, dates. Then nobody has to search the running text for outcomes.
• Project emails in the project folder. Important emails belong in the project files as documents, not only in a personal mailbox.
• One list, no copies. The open-points list lives in exactly one place on SharePoint or the network drive, and nobody saves it locally.

That reduces friction. It does not change the fact that, in the end, someone reads and copies. Many teams also notice at this point that the weekly status meeting mostly exists to pull the status together, a topic of its own covered in project status without status meetings.

What does a status that assembles itself from the sources look like?

Instead of carrying the status from the sources into a list, you can read it directly from the sources. That needs four properties.

The sources stay where they are. Project folders, OneNote and mailbox are connected, not replaced. Nobody has to change how they work.

Every item has evidence. A delivery date in the overview points to the email or the minutes it came from. Anyone in doubt opens the source.

Changes are suggested, not quietly applied. When an email arrives with a customer change, a suggestion appears. A person on the team decides whether it stands.

The status can be looked up rather than built. Whoever needs it checks it, instead of asking the project manager.

How does KoAssist Project Memory help with this?

Project Memory is the project feature of KoAssist, the AI project assistant for machine building and plant engineering. It is currently in pilot operation and delivers exactly these four properties.

You create a project and connect the project folder or upload the specification. OneNote, including team notebooks, can be connected, as can SharePoint, OneDrive or the network drive. Emails from your own mailbox can be filed in the project, with attachments and only after you approve them.

From emails and minutes, KoAssist suggests changes, meaning update a point, add a new one or mark one as done. Only what someone on the team accepts becomes valid.

The overview shows status, next step, open points, decisions and risks, plus what is new since your last visit. Every working day at 6:30 a briefing arrives by email, containing only a link and no project content. For the meeting you generate a status report as a Word file, in an internal version with open points, risks and cost status and in a customer version without them. KoAssist sends nothing, that stays with you.

MS Project, the ERP and your file storage remain the master. Anyone who may not open a folder in the source system will not see it in KoAssist either.

How much time goes into your next project status?

Work it out for your next customer meeting. How long does it take to get the status together from Excel, OneNote and the inbox, and how many times a month does that happen? If the answer is uncomfortable, the Project Memory page shows how the status emerges from your own documents.