Online Belief-State Planning

There is the same escape here as in Part II: don't solve the whole belief space. From your current belief, work out the best next move by looking a little way ahead — then do it again once the next noisy signal lands.

Online belief-state planning is the partially-observable counterpart of the online planning in Chapter 8. Instead of precomputing a policy over all beliefs, it plans at decision time from the belief you're actually in: it looks ahead over the actions you might take and the observations you might then receive, estimates which first move fares best, commits to it, and re-plans from the updated belief after the real observation arrives. It scales by reasoning only from where you are.

1Looking ahead through actions and observations

The lookahead tree now alternates two kinds of branching. From the current belief you branch on each candidate action; from each action you branch on each possible observation, and each observation leads to a different updated belief. Values are backed up from the leaves to rank the first actions. Because observations multiply the branching, the practical methods keep it manageable — sampling a limited set of observations, and pruning lines that can't win.

Figure 1. Online belief planning alternates action branches and observation branches from the current belief, backs up expected values, and commits only to the best first action. After the real observation lands, the belief updates and the search runs afresh.

2Monte Carlo planning over histories

The standout practical method extends the tree search of Chapter 8 to partial observability. It represents the current belief with a swarm of sampled state hypotheses (a particle set) and grows a search tree over sequences of actions and observations, running simulations to the horizon and backing up the results — concentrating effort on the most promising lines. This lets online methods handle POMDPs far larger than any exact approach, precisely because they never reason about beliefs they'll never reach.

Key idea

Plan from the belief you're actually in, not from all possible beliefs. Simulate a few action-and-observation steps ahead, commit to the best next move, and re-plan when reality answers back — trading stored policy for fresh, focused computation each time.

What it means in practice

This is real-time decision-making under imperfect visibility. From your current read on a project — uncertainty and all — reason forward not just about what you might do, but about what you might then learn, and choose the move that fares best across those futures. Then, when the next report or test result arrives, update your belief and decide again. Crucially, factor in that some actions are worth taking because of what they'll reveal, not only what they'll achieve — the value of an early probe is often the information it returns.

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 Online 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 Online Belief-State Planning as a decision instrument rather than an administrative form. The subject terms—planning, online, belief, looking, ahead—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 Online Belief-State Planning?