// the idea
The plan says one thing. The client needs to hear it one way, the executive another, the dev team a third. The status report is a rewrite of the schedule. The risk register is a rewrite of what everyone already suspects. Each rewrite is a chance for the story and the plan to drift apart.
Anchor keeps a single plan and derives everything else from it. Each project carries its own context: brief, team, rates, phase. Change a task and the finish date, the burn-down, the allocation heatmap, the risk list and the next status update all move together.
Briefs, schedules, budgets, risk registers, status digests and replies are drafted from the project's own context. Drafts are marked in teal and labelled for review.
A draft joins the project when someone accepts it. Acceptance and sign-off are marked in gold, so it is clear which words a human stood behind.
Where the brief is silent, the draft says so. Guesses are tagged [ASSUMED], logged, and counted as risk until confirmed.
// 01 · scope, brief and context
Each project starts with its phase (Intake through to Hypercare), a brief and working notes: who the stakeholders are, which dates are immovable, where the unknowns sit. That context is passed to everything Anchor drafts later, which is why a reply written in week eight still knows who the sponsor is.
Upload, paste, or generate one from notes. Accepts .txt, .md, .docx and text-based PDF. A client brief becomes a creative brief in one step, with PDF and Word export.
People are given roles, then assigned to tasks, so load is tracked per person and not just per discipline.
Day rate and hours per day for each role, in dollars, pounds or euros. The card belongs to the project; it can be imported, or saved as the default for future projects. The budget is calculated from it.
// 02 · plan
The plan is versioned. It opens on a baseline with its finish date and milestone status, followed by the Gantt: gold bars are the critical path, teal bars are everything else, and a dot marks any task the risk read has flagged.
Below the schedule is the part a static Gantt never gives you: a predictive risk read. Each task is scored on plain, checkable reasons, such as being on the critical path, depending on something unconfirmed, or belonging to someone who is over-allocated that week.
HIGH Chat backend & session service
on the critical path — any slip moves the finish date
Devin Park is over-allocated (320%) in W50
MEDIUM Discovery review & sign-off
on the critical path — any slip moves the finish date
depends on "Content model & migration audit [ASSUMED scope]", which is unconfirmed
totals 4 high · 14 medium · 2 low
Try a change without committing it: scale a task's effort, add a resource, drop a task, shift the start, or scale everything.
Effort-days and budget remaining, each plotted against the ideal line.
Hours, days, rate and cost by role, totalled. Below it, a weekly heatmap per person: each cell is a percentage of a five-day week, and anything over 100% turns red.
Log a slipped or cut task and re-plan. That creates a new version, so the baseline is never overwritten.
The schedule, the budget and a full project pack export as CSV, PDF or Word.
// 03 · board
The board is a second view of the same plan. Cards sit in To Do, In Progress, Blocked and Done, carrying task type, phase, owner and a critical-path marker. Filter by type or by person.
Done is not the same as signed off. Finished work can carry an explicit sign-off, and the header counts the two separately. Blocked is a column, so a blocker is visible to everyone instead of sitting in someone's inbox.
// 04 · respond
Describe a situation, risk or blocker in a sentence or two and choose who needs to hear about it: client, stakeholder, executive, dev team, QA, design or strategy. Each audience has its own register. For a client that means external, warm and confident, with one clear ask.
Anchor first gives you the read: what the situation means for this project, a short list of options with the trade-off of each, and a recommended play. Then it drafts the message.
You see the choices and what each one costs before any message is written.
The client hears the ask and the deadline. The designer hears what to hold and what to keep moving.
Missing names and dates are left as marked placeholders for you to fill in.
Each read lists the project context and briefs that informed it, and draws on earlier, similar situations as precedents. Then copy, redraft or accept.
// 05 · updates
The status digest turns the live plan into an update for a chosen audience: what is progressing, what is at risk, and the one thing you need from the reader. It reads from the current schedule and risk read, so it can't describe a project healthier than the one on the Plan tab.
Meeting notes → plan runs the other way. Paste notes from a call and Anchor reads them against the current plan and pulls out what changes: tasks to add, drop or re-estimate, plus new risks and the decisions captured.
// 06 · artefacts
Four artefacts, each built from the one before it, so the chain from brief to risk stays intact:
brief → work breakdown phase / deliverable / task
tasks → schedule dated plan + Mermaid Gantt
schedule → budget costed estimate + scenarios
plan → risk register scored risks + mitigations
A drafted schedule opens with its assumptions log. If the brief never gave a start date, the draft says so and flags the one it chose. Accept a draft and it becomes part of the project. Redraft and it tries again.
Anchor has dark and light themes. Both are shown here.
// status
Anchor Project Manager is a single-file React app from Wyse Labs. It is in testing ahead of release. The screenshots on this page use the built-in example project: a fictional client, team and CMS build.
There is no public link yet. This page will be updated when there is.