Project Management Tools
Project analysis that runs in your browser — scheduling, estimating and responsibility, worked out from your own figures. No account, no upload, and no cloud task board to migrate into. A project plan carries client names, budgets and who is doing what, and none of that has any business leaving your machine.
Everything in one place
The tools below each answer one question well. This one puts a whole project in a single workspace, sharing one task list across every view.
Agile and flow
Metrics and forecasting for teams working in sprints or on a board. These need no estimates beyond what you already record.
Decisions
Four methods for choosing between options, each honest about what it can and cannot settle. A simpler scorer without sensitivity analysis lives on the business decisions page.
Risk
Qualitative scoring, quantitative cost exposure, and the structural view. A simpler register is on the business decisions page.
Resources and compression
Two ways to fix a plan that does not work: move the work, or buy time. Both are honest about what they cost.
Governance and documents
Structured records with real validation. Nothing on these pages writes your document for you — a blank section is reported as blank, because invented text in a governance document ends a conversation that needed to happen.
Seeing and testing the plan
Three views of the same schedule engine: what it looks like, what a change to it costs, and which promises it can keep.
Cost
Earned value is above with the schedule tools. These two are about the money itself — what is committed, and what different assumptions do to it.
When it is not going to plan
Understanding the network, working back from a date that will not move, and comparing recovery options that all cost something.
Time and meetings
A single meeting cost calculator lives on the business operations page. This one is about the recurring ones.
One scheduling engine, not four calculators
These tools share a single tested scheduling engine rather than each reimplementing the maths. The critical path calculator, the date calculator and anything added later all run the same forward and backward pass, the same working-calendar arithmetic, and the same dependency handling. That is worth stating because the alternative — a page of calculators that each do their own date maths — is how two tools on one site end up disagreeing about the same project.
The engine is covered by 301 tests, including a critical-path network worked by hand so a wrong answer fails loudly rather than quietly rendering.
What is deliberately not here
No cloud task board. There are excellent products for assigning tickets and chasing status, and they need accounts and servers to do it. This is for the analysis those tools are usually worst at: what is actually driving the date, how much float exists, what an estimate is really worth.
No invented conclusions. Every number traces to something you entered. Where a method rests on an assumption — and PERT rests on several — the assumption is stated on the page rather than buried.
No false precision. A probability from a three-point estimate is conditional on the estimates being honest and the delays being independent. Real delays are correlated, and the pages say so rather than quoting a percentage as though it were measured.
Nothing sent anywhere. Task names, owners, budgets and dates stay in the browser. Project content is never passed to the advertising or analytics scripts on these pages.
Related tools already on the site
Some of what a project needs is already here rather than duplicated into this section: meeting cost, decision matrix, risk register, scope creep impact, capacity planner and timesheet. Building second copies of those under a different heading would make the site larger and no more useful.