Project Management›Project Risk Management›Algorithms for Decision Making›Chapter 20
20Part IV · State Uncertainty
Offline Belief-State Planning
Exact is impossible, so approximate — and do it in advance. Compute robust responses for the belief-states you're actually likely to face, before you need them.
If solving the whole belief space exactly is hopeless, don't try. Compute good responses for a representative handful of belief-states ahead of time — a pre-built playbook keyed to how sure you are the project is in trouble.
Offline belief-state planning computes an approximate policy before execution, so that at run time you simply look up the response for your current belief. The breakthrough is to stop insisting on the value of every belief and instead pin it down only where it matters — at a set of sampled, representative beliefs you're realistically likely to encounter.
1Point-based value iteration
The workhorse family is point-based value iteration. Rather than maintaining alpha vectors across the whole continuous belief space, it samples a finite set of reachable beliefs and maintains one alpha vector anchored at each. Backing up value only at those points keeps the computation bounded while still building a piecewise-linear approximation to the optimal value function. Refined versions concentrate their sampled beliefs on the regions the optimal policy actually visits, getting excellent policies for surprisingly large problems.
2Cheaper bounds and shortcuts
Simpler approximations trade more accuracy for speed. The QMDP shortcut pretends the state will become fully observable after the next step — fast to compute, but it systematically undervalues gathering information, so it can be reckless about acting to reduce uncertainty. Other bounds and grid-based schemes offer different points on the accuracy-versus-effort curve. The right choice depends on how much your decisions actually hinge on resolving uncertainty.
You cannot pin down the value of every belief, so pin it down only at the beliefs you'll actually face, computed in advance. A policy that's near-optimal on the belief-states your projects really reach beats an exact one you can never compute.
This is contingency planning made rigorous. Rather than improvising when a project's status turns ambiguous, work out your best responses ahead of time for a representative set of situations — "fairly sure it's fine", "genuinely uncertain", "fairly sure it's in trouble" — and concentrate that effort on the states your projects actually tend to reach, not every theoretical possibility. And be wary of shortcuts that assume uncertainty will conveniently resolve itself: they'll under-invest in the very information-gathering that de-risks a project.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Offline Belief-State Planning. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to convert the subject into a governed decision, owned work, usable evidence and a reviewable outcome. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Offline Belief-State Planning as a decision instrument rather than an administrative form. The subject terms—value, planning, point-based, iteration, offline—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Clarify the decision. Name the outcome, sponsor, affected stakeholders and decision that this work must enable.
- Set boundaries. Record scope, assumptions, constraints, dependencies, tolerances and escalation conditions.
- Plan the evidence. Define deliverables, measures, owners, due dates and acceptance criteria before execution.
- Control delivery. Compare actual performance with the baseline, assess changes and manage risks and issues explicitly.
- Close the loop. Confirm acceptance, transfer ownership, capture lessons and track benefits beyond handover.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Producing a document with no named decision or accountable owner.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Mixing risks, current issues, assumptions and actions in one unstructured list.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Measuring activity or output while leaving the intended outcome undefined.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Accepting changes without evaluating effects on value, scope, schedule, cost and risk.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Closing the project at delivery even though benefit ownership has not transferred.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Which decision or commitment does this artefact support?
- Who owns each action, risk, acceptance and post-project benefit?
- What is the baseline and what variance triggers escalation?
- Where is the evidence that the result was accepted and transferred?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Offline Belief-State Planning?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about value would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- Benefits Realization Management: A Practice Guide — Project Management Institute. Used for linking organisational strategy, deliverables, outcomes and sustained benefits. Accessed 2026-08-13.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.