Plan a rollout, prove it works, and export the workbook.
A charter that fits on one page. Goal, problem, scope in and out, stakeholders, and a definition of success you could be proved wrong about.
A plan that numbers itself. Phases of WBS-numbered tasks with owners, dates, finish-to-start dependencies and milestones. Percent complete rolls up on its own.
Schedule problems found for you. Dependency loops, tasks starting before what they wait on, milestones past their date — all named, not just flagged.
A timeline. The same tasks against the calendar, with progress inside each bar and slipped milestones in red.
A proof of concept that can come out against you. Weighted objectives over measurable criteria, with must-haves that block the recommendation however well everything else scores.
A real test plan. Scenario, preconditions, steps, expected and actual — each case tied to the criterion it settles.
A scorecard that says why. Go, go with conditions, or no-go, with the blocking criteria named.
RACI that enforces the one rule worth enforcing. Exactly one person accountable per row.
A risk register that sorts itself on likelihood times impact, and a decision log that asks for the reasoning as well as the decision.
A status report you cannot write directly. It is derived from everything else, which is what stops it drifting from the plan it describes.
Templates to start from — a SaaS rollout, an incident-response platform rollout, or a bare skeleton — seeded with the phases, criteria and risks these projects usually involve.
Exports worth circulating. A nine-sheet Excel workbook with live formulas, dropdowns and conditional formatting; a Word-compatible RTF report; and Markdown.
See the Keyboard tab for every shortcut.
Where your data lives
Everything is stored in your browser's localStorage, on this device and this browser only. Nothing is uploaded anywhere.
This is the whole database. If you clear site data, use a private window, switch browsers, or lose the device, it is gone. Back up regularly.
Backing up
Every project exports on its own. Excel (.xlsx) is the version to circulate; Word (.rtf) and Markdown give you the status report as prose. For a backup you can load again, use Export project data, which writes a .pumapack file — drop one back onto the window to import it.
Clear all local data
Danger zone. This erases every PumaPlanner record in this browser. Export a backup first.
Type DELETE EVERYTHING to confirm:
?
Open this help
Esc
Close dialog / menu
⌘ / Ctrl + K
Command palette — jump to a section or a project
⌘ / Ctrl + S
Save a .pumapack backup of this project
Enter
Commit an inline add (scope item, stakeholder)
Double-click a tab
Rename the project
Right-click a tab
Project menu — about, exports, close
Drag a tab
Reorder projects
Drop a file on the window
Import a .pumapack
About PumaPlanner
PumaPlanner is for the person who has been handed a piece of work to run and has never been taught how. It holds the four documents that get asked for — a charter, a plan, a proof-of-concept result and a status report — and it takes the view that the useful part of project management is a small number of habits rather than a methodology: say what is out of scope, write success criteria that can come out against you, put exactly one name against each decision, and never write a status report by hand. It explains each of those where you meet it, then gets out of the way and exports something you can send to a sponsor.
About PumaWorx
PumaWorx is a suite of offline, single-HTML productivity apps that run entirely in your local browser. The entire suite is a personal, open source vibecoding project.