Project Manager

Where every project actually stands.

What it replaces

The Friday afternoon spent reconstructing where every project actually stands.

The job

Keeps a live record of where each project stands, citing its source for every claim. Reads mail, site reports, meeting notes and change orders. It retrieves and quotes; it does not hold the project in its head.

What it does

• Ingests everything a project generates: mail, notes, reports, revisions
• Keeps a live status per project, with no tracker to update
• Answers status questions with the source quoted
• Flags passed dates and commitments with nothing filed
• Drafts the weekly status note for the client

What you get

• A current status per project, cited line by line
• A weekly status note drafted for you to approve
• A list of commitments made and not yet evidenced
• An answer to 'what did we agree about X', quoting the document

How far it goes on its own

Tracks and drafts unattended. Every client-facing status note is approved before it goes out.

Where it is weak

• It retrieves and quotes rather than reasoning across a whole project at once. Published long-context work shows most models losing more than half their accuracy well before the window is full — while sounding certain.
• It only spots a contradiction if both documents come back for the same question. Narrow questions: reliable. Find-what-I-missed: not.
• Not scheduled.

What leaves your building

• Your mail and shared drive, if they are cloud services. Project documents are indexed and read locally.

Works with

• Mail and shared drives
• Project folders
• Whatever tracker you already use