Project Manager

Assembling the status pack from system state

Issue, milestone and spend state pulled on a schedule, with deltas computed against the baseline. Documented tracker APIs do this exactly; a model asked to do the same arithmetic does it worse and less reproducibly.

Chasing overdue updates and missing actuals

A rule that notices what is absent and reminds the owner once, then escalates on a threshold you set. Worth asking first whether the update exists only so somebody can retype it, in which case deleting the step beats automating it.

Schedule arithmetic and dependency roll-up

Critical path, float and date propagation are exact calculations the scheduling engine you already own performs correctly. This is the clearest case in the profession of a problem that is not an AI problem.

Register and document housekeeping

Version control, distribution, and keeping a risk or action register tidy. Low value individually, and collectively a real share of the administrative load.

Drafting the status narrative

A first pass over figures you assembled, in a structure you chose. The judgement about whether the project is in trouble stays yours, and a paragraph you would not have written yourself is not a draft you can sign.

Preparing the options for a scope conversation

Laying out what moves, what breaks and what it costs under each option. Genuinely useful preparation; the choice between the options is not an information problem and never was.

Reading long documents for obligations

Contracts, statements of work and requirement sets contain commitments nobody has listed. Extraction with mandatory citation turns a week of reading into a register you can check clause by clause.

Estimating from what comparable work actually took

History widens the input to an estimate you still own. UK Treasury guidance requires explicit uplifts to cost and duration precisely because appraisers are systematically over-optimistic, and generating an estimate faster does not correct that.

Deciding what to cut when the date will not move

Somebody has to choose which promise is broken and be answerable for it. Most of the information that decides it - who was told what, what the organisation can survive - is not in any system.

Setting the reported status of a project

This looks like data entry and is a decision about what to tell the board. A generated status is the clearest case of displaced accountability available in the profession.

Delivering news nobody wants

The value is not the wording. It is that a person who knows the project said it, can be questioned about it, and will still be there next week.

Feedback about how people are working

Assessing a team member's performance is part of this job, and an assessment a model wrote is one the recipient will usually be able to recognise as such.

Confirming status with the people doing the work

Most verification in this series resolves to an artefact somebody opens. Delivery status does not: the check is asking the person doing the work what is left and listening to the hesitation. It is also the first thing dropped when reporting gets faster.

Tracing every reported figure to its source

If a number in the pack cannot be clicked through to a ticket, a timesheet or a ledger line, it is not a reported figure. It is an assertion.

Independent assurance, where it is imposed

On governed and public-sector projects the review is mandated rather than designed. UK government's delivery standard sets out three levels: operational management, independent senior management, and impartial audit. Find out what already applies before designing a check of your own.

Goal

Assemble the weekly status pack from system state, and produce the short list of places where a reported status and the systems disagree.

Rules

Never soften a slipping date. Always report the raw date alongside any forecast. Never infer a status nobody set, and never write to a source system.

Tools and memory

Tracker and finance systems, read-only. Memory holds workstream owners, recurring blockers and what "done" means in this organisation - never a stored opinion about a person.

Output contract

One row per workstream: planned, actual, delta, reported status, computed status, owner and a link to the source record. Plus a separate exceptions list.

Verification

Every figure opens to its source record. You read the exceptions list before the summary, and you confirm the top three with the people doing the work.

Escalation

Any item where reported status contradicts system state, any missing actuals, and anything it cannot trace to a record. These stop and come back to you.

What it must not do

Set a status, write a recommendation, contact the team, or change anything in the tracker. The exceptions list is the product; the pack is the cheap half.