All posts

Guides

How to See Where Every Project Stands Without a Status Meeting

Status meetings repeat what is already in your email and chat. How to see where every project stands, and what is owed, without one.

Guides

You can see where every project stands without a status meeting if the status is written from the work itself: the emails, chats, meetings and documents where decisions and commitments already happen. Status meetings exist because that information is scattered. Pull it into one place, keep it current automatically, and most of the meeting has nothing left to do.

TL;DR#

  • Status meetings mostly repeat information that already exists in email, chat and documents.

  • The fix is not a better status template. It is a project view written from the work as it happens.

  • Track commitments, not just tasks: who said they would do what, by when, and where they said it.

  • Keep a short weekly conversation for decisions and problems. Drop the round-the-table update.

Why status meetings happen#

Nobody books a status meeting because they enjoy it. They book it because they can’t answer three questions without asking around:

  1. Where does this project actually stand?

  2. What is owed, and by whom?

  3. What changed since last time?

The answers already exist. A client confirmed a date by email. A colleague promised a draft in Slack. A scope change was agreed on a call. The problem is that they live in ten places, and only the people who were there know about them.

So the team gathers once a week and says it all out loud. It works, but it is slow, it interrupts everyone, and it is out of date by Wednesday.

Why status docs and trackers don’t fix it#

The usual answer is a status document or a project tracker. Someone updates it every Friday. In practice:

  • It depends on people remembering to update it.

  • It records what someone chose to write, not what was actually agreed.

  • It drifts from reality between updates.

  • The person updating it still has to chase everyone for the facts.

You have moved the meeting into a document. You haven’t removed the work.

A better approach: status written from the work#

The alternative is to stop writing status by hand. Instead, let the project view build itself from the places work already happens.

1. Connect the sources, not just the task list#

Most of what matters on a project never touches the task tool. It is in email threads with clients, chat messages between colleagues, meeting notes and shared documents. A status view that only reads the task list will always be missing the important parts.

2. Track commitments, not just tasks#

A task is something someone remembered to create. A commitment is something someone said they would do. “I’ll send the revised proposal by Thursday” in an email is a commitment, even if nobody logged it. Capturing those is what stops things slipping.

3. Keep every update traceable#

Each line of status should link to where it came from. If the view says the launch moved to 3 March, you should be one click from the email that moved it. That is what makes people trust it enough to skip the meeting.

4. Show what changed, not everything#

Most people don’t need the full project history. They need a short brief: what moved, what is overdue, what needs a decision. A daily brief does more than a weekly meeting because it arrives while there is still time to act.

5. Comment on the item, not in a meeting#

When something is stuck, ask about it where it lives. Tag the owner on that commitment. The conversation stays attached to the work, and nobody waits a week to raise it.

What to keep from the meeting#

Dropping the status round doesn’t mean dropping all meetings. Keep a short, regular conversation for the things a view can’t do:

  • Making decisions where people disagree.

  • Working through problems that need several people.

  • Planning what comes next.

Everything else, who did what and what is late, should already be visible before anyone joins the call.

Who benefits most#

Founders stop spending their week asking for updates and can see what is owed at a glance.

Commercial and account teams can see what was promised to each client without digging through inboxes.

Consultancies, accountancies and property managers running many client projects at once get one view across all of them.

How Louvain does it#

Louvain is permissioned company memory for growing teams. It reads your email, documents, meetings, chats and calendar, and writes the status of each project from them. You see where things stand and what is owed, with every line cited to its source.

Each morning you get a brief of what changed. Commitments made in email or meetings are tracked until there is evidence they were kept. Permissions are enforced on every fact, so people only see what they are allowed to see. No status doc, no chasing people in Slack.

FAQ#

Can we really cancel our weekly status meeting?#

Most teams can cancel the update part. Keep a shorter meeting for decisions and problems.

Isn’t this just a project management tool?#

No. Project tools rely on people entering tasks. Company memory reads the work that is already happening and builds the picture from it.

What about confidential projects?#

Good company memory enforces permissions on every fact, so a project view only shows each person what they are allowed to see.

How long does it take to set up?#

Connecting email, calendar, chat and documents usually takes minutes. The project view fills in as work happens.

Written by

Louvain

Published in Guides

All posts

See it on your own questions.

We use Google Analytics, and Google’s and LinkedIn’s advertising tags, to see how this site is used and which ads bring people here. They set cookies only if you accept. Cookie Notice.