Helm — Automated Project Manager

Helm

STRATEGY · CLARITY · RESULTS

MERIDIAN PROGRAMME · HELICOPTER VIEW

{{ portfolioDate }} · Christopher Farmer · Senior view

← All workspaces

+ New project from a brief

{{ pgProjects }} projects {{ pgOnTime }} tasks done on time {{ pgLate }} done late {{ pgMoves }} auto-adjustments vs baselines {{ pgAdded }} missing tasks added by the system {{ pgEsc }} escalations need a human

CROSS-PROJECT PREREQUISITE LINKS

PORTFOLIO WATCH — SHARED RESOURCES & ESCALATIONS

Helm AUTOMATED PM

‹

{{ projClient }} · {{ dayChip }}

›

{{ projCycleLabel }} · ‹ › SWITCH

VIEWING AS

← Portfolio · Case study

The ninety days

current plan critical path ◆ gate {{ cmdBaselineLabel }}

◆

{{ cmdCaption }} · click a shaded block to open that task.

{{ cmdCaption }} — turn on Baseline (top-right) to overlay where each task moved from.

HANDLED FOR YOU{{ cmdHandledCount }}

NEEDS YOU

Nothing needs a human right now. Everything is planned, sequenced and inside slack.

WATCHING

Probabilities re-run nightly · Monte-Carlo

CAPACITY · THIS WEEK7.5h workdays · no weekend or overtime assumptions

{{ bannerLead }} {{ bannerBody }}

Work remaining — plan vs baseline

Tasks Effort-days

current plan Day-0 baseline {{ chartFootnote }}

Gates & milestones

NEEDS YOU · {{ needsCount }}

What happened. {{ n.what }}
Already tried. {{ n.tried }}
Recommendation. {{ n.recommend }}

Nothing needs you. The system is self-managing — {{ handledCount }} adjustments this week.

HANDLED FOR YOU · {{ handledCount }} Change log →

TACTICAL — {{ weekLabel }}

Exactly what is being worked on, day by day — who is on it, and what each task needs before it can finish. Click a task to edit it. Toggle Detail for definitions of done.

+ Add task

{{ di.title }} — {{ di.who }}

Nothing scheduled — capacity available; the system will pull work forward if any becomes safe to start.

Helm

STRATEGY · CLARITY · RESULTS

{{ projName }} — {{ dayChip }}

Target outcomes

·{{ bo.text }}

Stage-by-stage timeline

·{{ bl.text }}

Outputs. {{ bc2.outputs }}

Gate. {{ bc2.gateText }} {{ bc2.gateDay }}

Key dependencies and delivery boundary

·{{ bd.text }}

Provisional source-of-truth model

Record or activity

Provisional authoritative system

Original Current Delta

− {{ zoomLabel }} + zoom

+ Add task

done in progress scheduled — not started on the critical path blocked held / awaiting decision gate / milestone

Each bar spans a task's scheduled working days; a short task shows its name in the space beside it. Hover any bar for slack, dates & confidence — or zoom from the 90-day overview down to a day-by-day view, where every bar carries its date window and on-time confidence.

{{ dEarlier }} moved earlier {{ dLater }} moved later {{ dAdded }} added by system finish Day {{ dFinishB }} → {{ dFinishA }} buffer {{ dBufB }} → {{ dBufA }}d confidence {{ dConfB }} → {{ dConfA }}% Dashed marks under a bar show where that task sat in the Day-0 baseline — click one to open and edit the task.

DAY {{ dayNum }}

{{ ganttFootnote }} Click any bar to edit the task — delay it, split it, reassign it, resize it.

EVERY TASK — DRAG THE GRIP TO REORDER, CLICK A ROW TO EDIT + Add task

TASKWORKSTREAMOWNERWINDOWSLACKSTATE

⠿

{{ pl.ws }} {{ pl.owner }} {{ pl.window }} {{ pl.slack }} {{ pl.state }} ⋯

WORKSTREAM · AUTOMATED TEAM PM

Objective. {{ wsObjective }}

PROGRESS

NEXT GATE

STATUS

TASKOWNERWINDOWSLACKSTATE

{{ wt.title }}auto

{{ wt.owner }} {{ wt.window }} {{ wt.slack }} {{ wt.state }} blocker

Capacity — next three weeks 7.5h workdays · no weekend or overtime assumptions

critical-path work scheduled work idle — system will fill or escalate

Start guards — preventing waste

{{ dEarlier }} earlier {{ dLater }} later {{ dAdded }} added finish Day {{ dFinishB }} → {{ dFinishA }} buffer {{ dBufB }}d → {{ dBufA }}d confidence {{ dConfB }}% → {{ dConfA }}% baseline locked Day 0

EVENT HISTORY — TRIGGERS

SYSTEM MOVES vs BASELINE

No escalations.

The system is resolving everything within its own authority. It will escalate only when deadline, scope, budget or quality cannot be preserved.

What happened. {{ e.what }}

What the system tried. {{ e.tried }}

{{ e.optionsLabel }} {{ e.options }}

Impact. {{ e.impact }}

Recommended decision. {{ e.recommend }}

Every task as a node, arranged by stage, with an arrow from each dependency to the work it unblocks. The gold nodes and arrows are the critical (driving) path — the chain that sets the finish date. Dashed arrows are partial dependencies (a task only needs its predecessor part-complete). Click any node to open and edit it.

{{ dgCount }} tasks {{ dgEdgeCount }} dependencies {{ dgDriving }} on the critical path critical path partial dependency ◆ gate / milestone

When money is committed and when it is actually released — every paid line held behind the readiness gate so nothing is spent ahead of a releasable product. If the gate moves, the spend dates move with it.

Cumulative spend — planned vs guard-adjusted

planned outflow guard-adjusted schedule

The line rises gently as labour is earned day by day; payroll settles on calendar month-ends (Days 27 / 55 / 86, plus a small Day-90 run for the days after 31 Mar), so each run differs by the working days in that month. Guarded lump costs — vendor config, security, the optional add-on — only step in on or after the readiness gate (shaded band), so no discretionary cash leaves ahead of a releasable product. Dashed is the unguarded plan, for comparison.

Spend pace vs schedule {{ budPace.verdict }}

Budget spent

{{ budPace.spentPct }}%

Time elapsed

{{ budPace.timePct }}%

SPEND LINEAMOUNTSTATUS · RELEASE DAYRELEASE LOGIC

Basis. {{ bl.basis }}

How the system protects spend. {{ budNote }}

MORNING BRIEFING · {{ briefRole }} {{ dayChip }} · {{ dayDate }}

Reader-ready status pack — what's going well, where we're falling short, and what changed against the approved baseline.

Print / save as PDF

Helm

STRATEGY · CLARITY · RESULTS

AUTOMATED PROJECT
MANAGEMENT SYSTEM

{{ projClient }} — {{ projName }} · STATUS REPORT

TASK STATUS MIX

TASKS

GOING WELL

FALLING SHORT / NEEDS ATTENTION

ORIGINAL vs CURRENT

WORKSTREAMS

WORKSTREAMPROGRESSFLAGNOTE

Inject a realistic problem and watch the system re-plan: it re-levels resources, pulls safe work forward, protects gates — and escalates only when it runs out of moves. Everything here also updates the overview, timeline, briefing and portfolio.

Reset all demo events

New project from a brief Close ✕

Anything from a one-line idea to a full documented plan. The system reads it, interrogates it — implied tasks, missing information, integration work — then schedules it and tells you if the deadline is realistic.

Upload .txt / .md / .pdf / .docx {{ ingFileNote }} Analyse the brief →

Text and Markdown parse natively; PDFs with a text layer parse here too. Scanned PDFs, DOCX and images route through the full build's OCR/vision pipeline (specced in the handoff) — paste their text for now.

READ & INFERRED

· {{ ingSummary.explicit }}

· {{ ii.t }} — {{ ii.why }}

ASSUMPTIONS TO CONFIRM

· {{ ia.t }}

· {{ inx.t }}

TASK PREVIEW · {{ ingSummary.taskCount }} SCHEDULED

Create the workspace ← Edit the brief

{{ insp.id }} · {{ insp.ws }}

Close ✕

Owner. {{ insp.owner }}

Window. {{ insp.window }}

What it is. {{ insp.desc }}

Definition of done. {{ insp.dod }}

Needs. {{ insp.reqIn }}

Depends on. {{ insp.depsTxt }}

Unblocks. {{ insp.succTxt }}

Properties. {{ insp.flags }}

EDIT — THE PLAN RE-SOLVES AROUND WHATEVER YOU CHANGE

On-time confidence is Monte-Carlo over PERT-style duration spreads — it shifts continuously with effort, owner, risk class and upstream changes, never just on/off.

Edit all details… + Add task after

− {{ insp.days }} days +

Delay by this

Mark complete Split into two… Log blocker… Flag: needs help

EFFORT − {{ insp.durTxt }} + REASSIGN

Close ✕

TASK NAME

WHAT IT IS / WHAT'S REQUIRED

DEFINITION OF DONE — optional

EFFORT

− {{ editor.durTxt }} +

RISK

TRADE / OWNER

WORKSTREAM

PRIORITY

DEPENDS ON {{ editor.depNote }}

{{ editor.saveLabel }} Cancel

Split into two tasks Close ✕

“{{ split.title }}” becomes two sequential tasks — name each half and set how the effort divides. Everything that depended on the original now depends on part two. Edit either half further afterwards.

PART ONE — {{ split.durA }}

PART TWO — {{ split.durB }}

EFFORT SPLIT — {{ split.splitTxt }}

− +

Split & re-plan Cancel

This change pushes {{ cascade.count }} task(s) later Cancel ✕

Re-planning moves the work below to later dates rather than overlapping it. Tick anything that's already complete — those get locked where they are. Everything left unticked has its timeline extended.

{{ cascade.confirmLabel }} Cancel the change

Log a blocker Close ✕

The system will re-plan around it automatically — and escalate only if the deadline, a gate or quality is threatened.

WHICH TASK IS BLOCKED?

EXPECTED DELAY

− {{ blkDays }} days +

REASON

Log blocker & re-plan Cancel

Helm

STRATEGY · CLARITY · RESULTS

AUTOMATED PROJECT MANAGEMENT

{{ homeDate }} · Christopher Farmer · Senior view

← Portfolio · Case study

Two ways in. The same automated project manager.

Helm reads a brief, builds the plan, schedules the work and re-plans around problems on its own — whether that is a single fixed-term contract or a multi-project programme where several projects gate each other. Choose a workspace to step inside.

Demo modified. {{ homeModifiedNote }}

Reset to the seeded state

FORECAST FINISH

TASKS DONE

ON-TIME CONFIDENCE

STRUCTURE

Open the contract →

PROJECTS

DELIVERY

CROSS-PROJECT LINKS

MISSING TASKS ADDED

Open the programme →

YOUR INGESTED BRIEFS · STANDALONE PROJECTS

remove Open workspace →

+ Ingest a new brief — PDF, text or image Helm reads it, interrogates it for missing work and unclear assumptions, then stands up a fresh standalone workspace — proving the same engine handles a single project as readily as the programme above.