Skip to main content

Give stakeholders a date you can defend.

Pocket PMO checks the tasks, estimates, risks and budget behind your plan with real project mathematics, then shows you what the finish date actually looks like. Free while in beta. Your tools stay yours.

Your plan. Your numbers. Your odds.

Website launchExample project
Pocket PMO

A date you can put confidence behind.

MONTE CARLO
80%

completion confidence
within 55 days

P50P80P9537 days45 days53 days61 days70 days

Drag the marker, or focus it and use the arrow keys, to test a finish date.

Median · P5051.1 days
Higher confidence · P8055.4 days
Conservative · P9559.6 days
A forecast, not a promise.Sample plan · sequential tasks · working days
Built on established project methods.
PERTCPMMonte CarloEarned value
Explore the toolkit

Written fast isn't the same as finished

A sentence is enough for AI to draft a plan, a RAID log and a kickoff deck now. Drafting was never the hard part. The hard part is knowing whether the date survives contact with real tasks, real estimates and real risks. Pocket PMO doesn't write your plan for you. It pressure-tests the one you have, so the date you give stakeholders comes with the odds attached.

One project.
A clearer picture at every step.

From the estimate your team hands you to the Monday morning portfolio review: the methods connect and the picture gets sharper.

Estimate realistically.

Start with what you know. Make uncertainty visible.

Size the effort with ROM (Rough Order of Magnitude), then give each task a best, likely and worst case. Your assumptions become part of the plan instead of a footnote. As you work through the estimate you can see what is known, what still needs checking, and which assumptions could make the biggest difference. That gives you a more useful starting point for conversations with your team and stakeholders. You don’t need every answer upfront; you need to be clear about what you know, where the uncertainty sits, and how it might affect the work.

ROM estimationPERT analysis
Website launchExample project
Pocket PMO

Give uncertainty a place in the plan.

ROM / PERT
ActivityBest → worst · daysExpected
Design review
3 / 5 / 9
5.3 d
API build
8 / 12 / 20
12.7 d
Data migration
5 / 8 / 15
8.7 d
Frontend build
10 / 14 / 24
15.0 d
QA & launch
4 / 6 / 11
6.5 d
One sequential task chain. Every assumption stays visible.

Forecast with confidence.

A finish date is more useful when you know how likely it is.

See the chain of work that drives completion and explore thousands of possible outcomes. That shows the difference between an optimistic date and a commitment you can defend. You can also see which tasks and dependencies have the biggest effect on the forecast, and how a change to your assumptions would shift the finish date. Instead of sharing a date without context, you can explain what it is based on, and when the plan changes you can update the forecast and see what that means for delivery.

Critical pathMonte Carlo
Website launchExample project
Pocket PMO

A date you can put confidence behind.

MONTE CARLO
80%

completion confidence
within 55 days

P50P80P9537 days45 days53 days61 days70 days

Drag the marker, or focus it and use the arrow keys, to test a finish date.

Median · P5051.1 days
Higher confidence · P8055.4 days
Conservative · P9559.6 days

Stay in control.

Connect cost and schedule performance to your weekly report, then see how your project fits into the wider portfolio. Spend less time pulling updates together and more time understanding what they’re telling you. You can see what changed, where progress is slipping, and which areas may need attention. Seeing one project alongside the rest of the portfolio gives your next conversation or decision more context, and it keeps people informed and issues raised sooner.

Earned valueStatus reportsPortfolio oversight
Website launchExample project
Pocket PMO

See what changed before you share your forecast

PROJECT OVERSIGHT
Active projects3
Need attention1
Portfolio budget$240k
Illustrative portfolio health
ProjectHealthCPISPI
Website launchYour forecast, in contextAttention0.940.89
Customer portalOn track1.031.01
Brand rolloutOn track1.001.02
Website launch needs a schedule review before the next commitment.

Illustrative execution data, not calculated from the sample estimates.

Website launchExample project
Pocket PMO

Give uncertainty a place in the plan.

ROM / PERT
ActivityBest → worst · daysExpected
Design review
3 / 5 / 9
5.3 d
API build
8 / 12 / 20
12.7 d
Data migration
5 / 8 / 15
8.7 d
Frontend build
10 / 14 / 24
15.0 d
QA & launch
4 / 6 / 11
6.5 d
One sequential task chain. Every assumption stays visible.

The same project. From assumptions to attention.

You promised a date. What are the odds?

Start with a sample plan, or enter a few tasks. Save into the app to see the same schedule sentence: chance, defendable date, deciding tasks.

Website launch · promised in 50 working days41% chance of hitting it

P80 finish 55.4 working days · 5 sequential tasks · 10,000 checked sample outcomes

No signup. Calculations run in your browser.

Make the promised date the product

You promised a date. The chance of hitting it is a percentage. The date you can defend is later, or it isn’t, and a few tasks decide which. Pocket PMO says that sentence in one sitting, ranks the portfolio on thin data, and puts it at the top of the weekly file you can already download.

Add promised-date odds to your schedule

You’re running more than one project. The plan lives in one tool, actuals in another, status in a slide someone rebuilt this morning. Nothing agrees, and nobody can say which version is true.

Traditional software tracks what already happened: tasks done, hours logged. It can’t tell you what happens next, or which project slips first.

Pocket PMO answers the only questions that matter: When is it likely to finish? What will it really cost? Which project should you worry about first?

Plan your next move and explain your finish date

Running two or more projects

Say the sentence out loud

You promised a date. Pocket PMO answers with the chance of hitting it, the date you can defend, and the tasks that decide it. Every number comes from your own ranges, not a status colour. And when someone floats a different date, check it on the same simulation before you promise it. Every finished project settles the forecast against reality, so your next date starts from evidence.

Running a PMO

Which project needs you first

The portfolio ranks thin forecasts: promised date, chance, defendable date. Monday’s card shows what moved since last week, and a PDF summary pack carries it into the steering room. Single-tenant today, with no pretend multi-user accounts.

From guesswork to grounded, in three moves

  1. Step 1

    Promise a date

    Create a project with a due date and a handful of tasks. Point estimates get a visible best / likely / worst band so the forecast can run in one sitting.

  2. Step 2

    Read the sentence

    See the chance of hitting the promised date, the defendable P80 date, and the deciding tasks. Assumptions about ranges and dependencies sit next to the numbers.

  3. Step 3

    Forward the weekly file

    Download the markdown or PDF with the sentence, what moved, and decisions owed. Update tasks and the next report says how the defendable date moved.

Run it per project. Read it across all of them.

Built to make you a better project manager

Every forecast you record is kept, and every finished project settles the question: did it finish when the forecast said? Pocket PMO keeps that record per project and reads it back to you as facts about your plans, never as a grade about you.

Each project’s record shows whether your dates for it tend to run late or early and whether your precision is improving from one forecast to the next. And when a project’s own history shows a new commitment repeating an old mistake, a quiet heads-up about that project can appear on your next dashboard visit. The record is yours alone: private by default, never a scorecard, never a leaderboard.

Frequently asked questions

What is Pocket PMO?

Pocket PMO is a probabilistic forecasting project delivery software. Pocket PMO takes the due date you promised and turns it into a sentence you can defend: the chance of hitting it, the date you can stand behind, and the few tasks that decide it. Monte Carlo runs in your browser, and the weekly file is what you forward.

Why not just keep using spreadsheets and a task manager?

Spreadsheets and task tools track what already happened. Pocket PMO computes what happens next: the chance of hitting the promised date, a P80 finish you can defend, and the tasks that move that date when remaining work changes.

I run six projects. Do I have to open six dashboards?

No. The portfolio ranks projects by their chance of hitting the promised date, worked out from thin data like a name, a due date and rough ranges. The one that needs you first is at the top.

Can I see the portfolio before entering my own projects?

Yes. The empty dashboard offers a sample portfolio: eight projects, healthy to at-risk, each with a forecast computed by the real engine as it loads. The weekly what-changed card and the summary pack work on the sample, and exiting the demo leaves nothing behind.

Can I bring tasks from a spreadsheet or another tool?

Yes. Start with a short task list or a task CSV (Task, Likely, optional Best/Worst/DependsOn). You can also import a full schedule from a Primavera P6 (.xer) or Microsoft Project (.xml) export, then open the imported project in Forecast to compute its forecast. Point estimates get a visible default range. When you are ready, keep the plan current from your task tool; the forecast and the weekly file stay the product.

Do I need to be a certified project manager?

No. Ranges, the critical path and Monte Carlo come built in, with the math hidden. The techniques certified PMs charge for are already there. You bring the promise; Pocket PMO brings the sentence.

Does Pocket PMO score or rate me as a project manager?

No. There is no score, rating, or leaderboard, and there never will be. The app keeps a calibration record per project: your past forecasts resolved against what actually happened. It is private to you, and it exists so your next commitment starts from a record, not a hunch.

Can Pocket PMO help me get better at estimating?

Yes, with evidence rather than encouragement. Each finished project updates that project’s calibration record: whether your dates for it ran late or early, your average error in days, and whether your precision is improving. When a project’s own history shows a new commitment repeating an old mistake, the dashboard can give you a quiet heads-up about that project.

Does it replace the tool my team already uses?

No. Pocket PMO is a forecasting layer. It does not replace your task manager; it tells you when the promised date is in trouble.

Forecasting from Jira throughput?

Flow tools such as ActionableAgile and Nave do that. Pocket PMO forecasts from estimates and the critical path, for plans that are schedules.

How much does Pocket PMO cost?

Pocket PMO is fully free while in BETA release. When paid tiers ship, the reason to pay is that the forecast stays current and the weekly file keeps its history, not backup alone. See the pricing page for details.

Explore the toolkit

Break the work down; the forecast builds from it

Break scope into work packages with three-point estimates, so the Monte Carlo forecast and P80 finish date are built from the work itself. Free while in beta.

ROM estimates that feed the forecast

Build a rough order of magnitude (ROM) range early, then refine into three-point estimates that feed the critical path and P80 finish date. Free while in beta.

PERT analysis software for schedule estimates

Estimate project schedules with optimistic, most likely, and pessimistic durations using PERT analysis in Pocket PMO.

Critical path method software for schedule control

Critical path software that identifies the activities, dependencies, and float that set your finish date, with CPM forward and backward passes built in.

Monte Carlo schedule forecast: the odds of hitting the date you promised

Estimate-driven Monte Carlo on the plan you already have: three-point estimates through the critical path give P50/P80 dates and the probability of any promised date.

Earned value management software for project control

Track project health with earned value management metrics including planned value, earned value, actual cost, CPI, and SPI.

Risk scores that shape the estimates

Score risks on a 5x5 matrix, attach mitigation, and connect the ones that matter to the Monte Carlo P80 date. Use the scores to guide the duration estimates; they do not replace the forecast.

Who needs the forecast

Map power and interest, so the P80 date and promised-date odds reach the right people. A RASCI matrix shows who owns each piece of the work.

Project budget tracking alongside the P80 forecast

Track project budget and cost signals next to the P80 schedule forecast, risks and EVM, so cost variance and the date are read in one picture.

Cost variance next to the forecast

Compare project spend to the budget baseline and show favourable or unfavourable variance with the delivery data behind it. For project budgets, not procurement savings.

Truth Engine: keep your project records in sync

Keep the task tool your team already uses. Truth Engine reads its data or a CSV and flags status, due date, or assignee drift from your local position of record.

Guides for honest planning

Work breakdown structure template guide

Learn how to structure a WBS template with phases, deliverables, work packages, owners, and estimate-ready details.

ROM estimate example: early range before the P80

A worked ROM estimate example: build the early range, name the assumptions, then see how three-point estimates take over before a Monte Carlo P80.

PERT vs CPM: project schedule methods compared

PERT and CPM compared: what each method does, when to use PERT vs CPM, a worked five-activity example with real numbers, and how to run both together.

Earned value management formulas for CPI and SPI

A practical guide to EVM formulas including planned value, earned value, actual cost, CPI, SPI, CV, and SV.

Project risk matrix template for forecast-ready reviews

Build a project risk matrix with probability, impact, owners and responses, then use the top risks to decide what the Monte Carlo forecast must cover.

Stakeholder analysis for sharing your forecast

Map power, interest and cadence so you know who gets the full forecast curve and who gets a two-line P80 summary.

Defend your finish date without hiring a risk modeller

Size, simulate and sign off every project with audit-ready confidence: portfolio oversight, EVM and risk scoring without hiring a risk modeller.

Put a statistical number on the change request, while you are still in the room.

Put a statistical number on a change request while you are still in the room. PocketPMO gives consultants defensible project timelines and budgets. Start free.

Give your AI agent real project maths, not a hallucinated Gantt chart.

PocketPMO publishes an open-source, read-only MCP server that exposes PERT, CPM, Monte Carlo, EVM, and risk scoring to AI agents running locally.

Project forecasting: will we hit the date, and what are the odds?

Estimate-driven probabilistic forecasting: three-point estimates and the critical path feed a Monte Carlo run that gives the probability of any date and a P80 commitment.

Migrating from Project Online: what retired, and an honest look at what comes next

Project Online retired on 30 September 2026. What the successor lacks for PMO governance, three migration paths compared, and a capability map, stated plainly.

P50, P80 and P90: which date should you promise?

What P50, P80 and P90 dates mean, how Monte Carlo computes them, why P80 is the usual commitment, and how percentiles apply to cost estimates.

Alternatives and comparisons

When a task manager is not enough, and when a heavyweight suite is too much.

Plan in a spreadsheet? Get a P80 date from it

Import a task-list CSV or a schedule export and get a P80 date, the odds of the promised date and a computed weekly status instead of a RAG column.

Already on MS Project or P6? Add the forecast layer

See how Pocket PMO compares for teams that want PMI-based planning, estimating, risk, EVM, and reporting without heavy tooling overhead.

A Project Online alternative for post-retirement PMO forecasting

Project Online retired 30 September 2026. What a replacement needs, and how Pocket PMO covers forecasting, EVM, and portfolio oversight in the browser.

A Primavera P6 alternative that is a layer, not a rip-and-replace

Keep P6 for scheduling and add browser forecasting: import the P6 XER export, run Monte Carlo, CPM and EVM, and get weekly numbers without a report build.

Pocket PMO vs spreadsheets for project forecasting

A spreadsheet holds one date. Pocket PMO turns the same estimates into a P80 date and the probability of hitting the one you promised.

PocketPMO vs Primavera Risk Analysis

Oracle Primavera Risk Analysis vs PocketPMO: what PRA is genuinely better for, what PocketPMO changes, and who should pick which.

PocketPMO vs RiskyProject

RiskyProject by Intaver vs PocketPMO: what RiskyProject is genuinely better for, what PocketPMO changes, and how to compare both on your own project.

Schedule risk analysis tools, and which to pick when

A fair map of schedule risk analysis (QSRA) tools, desktop and browser, and which one to use when you need to see date risk early.

PocketPMO vs Safran Risk

Safran Risk vs Pocket PMO: what the integrated cost and schedule risk suite does best, and what a browser forecasting layer changes.

PocketPMO vs Deltek Acumen

Deltek Acumen (Fuse, Risk) vs Pocket PMO: what the schedule diagnostics and risk suite do best, and how to compare both on your own project.

Walk in with better numbers than the room has

Your stakeholders already rule on your dates. Open the app, check the odds, and start the record that makes your next forecast better than your last.