Where does the real project status live, if not in the status meeting?

Monday, 9 o'clock, status round. Project management, engineering, purchasing, electrical, assembly. The first half hour goes round the table. Has the bill of materials been released? Has the supplier confirmed the date for the drives? Which drawing revision went to the customer? Has the customer replied about the safety enclosure?

Every one of these questions has an answer, and the answer is usually written down already. In an email, a set of minutes, a delivery confirmation. The meeting exists to bring it out of everyone's heads and inboxes onto one table. That leaves little time for the decisions themselves.

Why do status meetings in plant engineering take so long?

Because they are asked to do two jobs at once. Collect facts and make decisions. The first job eats the second.

In engineer-to-order work, a lot changes between two rounds. Customer changes, shifted delivery dates, new revisions, questions from assembly. Each department knows its own part, nobody knows the whole. So the meeting pieces together what belongs together.

On top of that, the status is often scattered across Excel, OneNote and email and has to be maintained by hand. The project manager updates a list before the meeting, the meeting corrects it, and by the following week it is out of date again. The lead article on project status in Excel, OneNote and email looks at this pattern in more detail.

The result is familiar. Important points slip to the end of the agenda and get postponed. Whoever missed the meeting knows less on Tuesday than everyone else.

Where does the real project status sit?

Not in the status list. That is a summary, and any summary is only as fresh as its last update. The real status sits in the documents the project produces anyway.

Minutes. Customer meetings, internal coordination, design reviews. This is where decisions and commitments are recorded, often with a date and a name.

Emails. Most agreements in a project run through Outlook. The customer confirms a change, the supplier moves a date, assembly reports a problem. How to stop such agreements getting lost in one person's inbox is covered in the article on project decisions from email.

Delivery and order confirmations. They decide whether the commissioning date holds. A typical case is the order confirmation in which the supplier names a later date than the one requested, and nobody notices.

Revisions of drawings and bills of materials. Which revision is released, which went to the customer, which is on the shop floor? A wrong revision costs more in assembly than any meeting.

So anyone who wants to know the status does not need to ask, they need to read. The problem is that nobody has time to read all of it every week.

What does a good project status show at a glance?

An overview that takes the load off the meeting answers five questions without anyone having to ask.

1. Where are we? A short status in a sentence or two, such as "Design complete, manufacturing under way, FAT in three weeks".
2. What is the next step? With an owner and a date.
3. What is open? Open points, questions for the customer, pending approvals.
4. What has been decided, and what could go wrong? Decisions with date and source, risks with a short reason.
5. What has changed since I last looked? For anyone who is not in the project every day, this is the most important question.

Every entry should point to its source. If the overview says "Delivery date for drives confirmed", one click should take you to the confirmation. Otherwise someone will ask about it in the meeting anyway.

How does the status stay current without someone maintaining it?

It never runs entirely without upkeep, but the upkeep can change. Instead of the project manager reading every email and updating a list, changes arrive as proposals and someone on the team confirms them. That is the difference between copying and approving.

Two habits help, with or without software. First, one fixed place for everything that changes the status, so minutes, customer emails and confirmations go into the project folder rather than staying in a personal inbox. Second, a short daily look at what is new instead of a long weekly reconciliation.

How does KoAssist help keep the project status current?

Project Memory, part of KoAssist, the AI project assistant for machine and plant engineering, is in pilot operation. It runs alongside MS Project, your ERP and your existing file storage and replaces none of them.

A project's overview shows status, next step, open points, decisions and risks, plus "New since your last visit". It draws on the connected folders and on the emails you file into the project from your own mailbox, with attachments and only after you approve.

From emails and minutes, KoAssist proposes changes to the project status, marked as "Change", "New" or "Done". Only what someone on the team accepts becomes valid. Responsibility stays with the team, the copying goes away.

On working days at 6:30 a briefing arrives by email. It contains only a link, no project content. Behind it is what needs doing today, and you tick items off with one click. If you need a status report for the customer meeting, you get it as a Word file in two versions, internal with open points, risks and cost status, and one for the customer without them. How to keep that split clean is the subject of the article on customer status reports. Nothing is sent automatically.

Permissions come from your file storage. Anyone who cannot open a folder in the source system will not see it in KoAssist either.

So what is the status meeting still for?

For what it was meant for. When everyone knows the status beforehand, the round no longer opens with "Where are we?" but with "What do we decide?". Whether the customer change is handled as a change order, whether the FAT moves, who resolves the bottleneck in assembly. The meeting does not become unnecessary, but it can get shorter and stay focused on what matters.

You can see what the overview looks like on the Project Memory page, and look at it with one of your own projects in a demo.