V1 / Value — Project Manager
The PM command centre — built for the way you actually run a projectYour project, distilled.
Programme health. Float erosion. Gate impacts at L3, L4, L5 and IST. Recovery actions. Risks, delays, early warnings. Commercial exposure. Cx readiness. Safety status. Workforce presence. The daily briefing from the AI Friend, drafted overnight, ready for sign-off at 06:55. One screen. Signal, not noise.
You open the dashboard and know exactly what's slipping, why, and what to do next.
PMs drown in noise. Loadbearer gives signal: a ranked, attributed, recommended next-action list — with the clause cited, the cost costed, the cascade traced. The system never decides. Halloran reads, judges, signs.
The PM command centre · ten channels, one record
Command, clarity, speed, decision-readiness — in the order Halloran needs them.
The command centre is the PM's working surface, ranked the way the day actually runs. Top-of-screen: programme health and the float that's eroding fastest. Mid-screen: gate impacts, recovery options, commercial exposure, contract notices in flight. Bottom-of-screen: safety, workforce, Cx readiness and the AI Friend's overnight briefing. Every cell is a live query against the same record that feeds Cassidy on safety, Shankar on commercial, and Krupa on the client view. Reconciled the moment it changes; defensible the moment it's questioned.
Programme health
Live status across L3, L4 and L5 — progress against plan, productivity ratios, earned-value variance per package. Baselined against the contract programme, not against last week's working copy. Halloran sees green/amber/red against pods, halls and storeys at a glance.
Float erosion
Days of float left on the critical path, by package and by gate — and the rate at which they are being consumed. Erosion velocity flagged when it exceeds the contractual threshold. The day a package goes negative-float is the day it surfaces, not the day it's noticed.
Gate impacts · L3 / L4 / L5 / IST
Every contractual milestone gate — design freeze, procurement gate, access gate, witness gate, integrated systems test — with named owner, current health, projected hit-or-miss date and the package that drives it. The IST date is the one date the data hall is built around.
Recovery actions
For every slipping gate, three pre-costed recovery options — overtime, parallel pod, renegotiated gate — each pre-checked against the contract clauses on acceleration, no-fault relief and time-bar. The PM picks. The system records who picked, when, against what evidence.
Risks, delays, early warnings
The risk register is live. Every early warning raised on the gantry, in a meeting or on the gateway is on the register before the next morning's briefing, with the clause cited, the time-bar set, and the response owner named. Nothing surfaces six weeks late.
Commercial exposure
Forecast cost-at-completion against contract sum, by event and by clause. Delay events with attributable cause, evidence pack and the recommended commercial position — ready for the QS to walk into the next CV review with a single agreed number, not a guess.
Cx readiness
Witness register live to the commissioning calendar. Every L3, L4, L5 and IST witness slot tied to its prerequisite installations, sign-offs and pre-commissioning tests. The conflict that breaks the witness day is visible 28 days ahead, with named owner.
Safety status
Cassidy's spine, summarised: high-risk activities live, near-miss closure rate, lapsing inductions, BSA gateway readiness. The PM does not run safety — but the PM sees the safety posture without asking, and is informed before any item becomes a programme issue.
Workforce presence
Inducted, on-site, RAMS-current, permit-linked. By subcontractor and by package. The day Verdant is short-handed on Hall 3 is the day Halloran knows at 06:55, not at the 11:00 walk-round. Notice goes to the sub admin and the package manager simultaneously.
Daily briefing · AI Friend
Drafted overnight from every change to the record since 06:00 yesterday. What slipped, what closed, what was issued, what is due today, what to ask whom. Halloran reads, edits, signs at 06:55. Goes to the planner, the QS, the package leads. The briefing is a starting point, not an answer — the system never decides.
The day before · the day with
The day before Loadbearer
- Three WhatsApp groups (commercial, MEP, fire) running in parallel, none of them admissible if the dispute escalates.
- Two duplicate programme spreadsheets — one the QS maintains, one the planner maintains, neither reconciled since Tuesday's progress meeting.
- An 11pm RFI chase that has been chased four times and is now blocking pod-by-pod release.
- Friday board paper rebuilt from memory, screenshots, and a printout the planner emailed at 17:50.
- An early warning that was raised verbally on the gantry on Wednesday and has not made it onto the register.
- A subcontractor's RAMS that nobody can find — the latest revision lives on someone's iPad.
- "Did we issue the variation notice?" answered with "I think Lorraine sent it on Monday."
The day with Loadbearer
- Every conversation that affects programme, cost or risk is captured against the contract clause it cites and the deliverable it changes.
- One programme. One source. The QS, the planner and the PM read the same Gantt at the same minute.
- RFIs auto-escalate at the response window the contract specifies — the chase is the system's job, not a junior's calendar.
- The Friday board paper is the live record at 16:00 Thursday, ready for review, not rebuilt from screenshots.
- An early warning raised on the gantry is in the register before the operative reaches the canteen.
- RAMS for every operative on site at this minute — current revision, reviewed by the right competent person.
- "Did we issue the variation notice?" — yes, at 14:07 on Monday, signed by Halloran, citing CT.14.3, served to Phoenix Digital, acknowledged at 14:42.
At your fingertips, every shift
The information the PM never had to ask for.
Lessons learned · forensic, not decorative
Every project teaches the next one — by stat, not by anecdote.
-
L-014
Voltaic switchgear deliveries slip an average of 9.4 days against contract date across the last six packages. Slippage correlates 0.78 with weeks containing UK bank holidays.
System recommends moving the procurement gate forward by 14 days and adding a CT.6.5 progress submission for weeks 14, 22 and 36. PM accepts; planner sees the Gantt update at 06:58.
-
L-021
RFIs raised after 16:00 on a Thursday close 2.6× slower than RFIs raised before 11:00 on a Tuesday — across 412 historic items. Friday-afternoon RFIs are the worst-performing cohort.
Operatives submitting an RFI after 16:00 see a soft prompt: "This will probably wait until Monday — do you need to raise an EW now?" Decision logged either way.
-
L-027
Cooling-to-electrical witness conflicts caused 31 days of programme loss across the last two halls — every one of them was visible 21 days in advance from the witness register, and missed.
Cross-package witness conflicts now surface on the PM dashboard 28 days ahead with named owners. The conflict that broke Hall 1 is the one that won't break Hall 2.
-
L-033
Friday board papers historically contained an average of 4.1 inconsistencies against the live programme — typically because someone copied a number off Tuesday's print.
The board paper is generated at 16:00 Thursday from the live record. Halloran reviews; the planner reviews; both sign. The number in the paper is the number in the system.
What stops happening
- The 23:00 phone call from the QS asking what the planner sent the client.
- "I'll find out on Monday" — because the system has already found out and put it on a Monday card.
- The duplicate spreadsheet war between commercial and operations.
- The Friday board paper rebuilt from screenshots and memory.
- The early warning raised on the gantry that never made it to the register.
- Verbal variations that surface six weeks later as a £180k surprise in the CV.
- "Did we issue the notice?" — there is one record, and it is the record.
The signed loop
A competent person ends every loop. The system never does.
Loadbearer drafts the variation notice with the clause cited and the evidence attached. Halloran reads it, edits the wording where her judgement says something else, signs it, issues it. The system records who reviewed, who approved, when, and what the wording was at the moment of issue. If the dispute escalates four months later, the chain of custody is on one screen, not in seven WhatsApp groups.
The system writes; the PM reads, judges, and signs. Principle 7. Recommendation only. Always.
"I used to spend the first hour of every day finding out what happened overnight. Now I spend it deciding what to do about it."
— Halloran · PM · Marauder Construction (fictional)
Adjacent
See the same forensic rigour for the other roles on site.
The PM command centre is one of eleven. Each role gets the same treatment — the same fingertip information, the same lessons, the same signed loop. The system is the same; what each role sees is what their day actually requires.