What is a Candidate Option?

In most organisations the options behind a decision never really exist. They live as bullet points on a slide, described in a meeting, amended in the corridor afterwards, and quietly rewritten once the outcome is known. Ask a year later what the alternatives actually were, and what each would have cost, and the honest answer is that nobody can say. The decision survives as a choice without a menu.

A candidate option is the repair. A candidate option is a first-class, immutable object: one possible course of action, carrying its own dates and costs, frozen at the moment it is created. First class means the option is a thing the system holds, compares and ranks, not a phrase in a document. Immutable means that once created it is never edited, by anyone, for any reason.

An object with its own dates and costs

Each candidate option is priced. It carries the costs of taking it and the dates that govern it, above all the earliest date it clears every constraint that binds it: people ready, systems integrated, contract clauses satisfied. That overall date is the latest of the option’s binding dates, because the worst constraint decides; an option is not partially possible.

Options are born inside a Scenario Run: a timestamped evaluation of the possibilities against the facts as they stood. The run is the evaluation; the candidate options are its product. When the facts change, nobody updates the old options. A new run is made, and it creates a new set. Sets from different runs sit side by side in the record, each one true to the moment that produced it.

Why immutability keeps learning honest

The moment an outcome is known, the past comes under pressure. The option that failed gets remembered as obviously flawed; the option that was rejected gets remembered as never serious; the costs everyone accepted get remembered as warnings someone gave. None of this is dishonesty. It is what memory does, and any system that lets options be edited will find its history edited by it.

Immutability removes the temptation at the root. The outcome is scored against the options exactly as they stood when the choice was made: the same dates, the same costs, the same ranking. If the second-ranked option was chosen, that fact remains true forever, along with what the first-ranked option promised at the time. The scored record accumulates in an Outcomes Ledger, and patterns are mined from it only once enough evidence gathers. That mining is only worth doing on a record hindsight cannot retouch. An edited menu teaches nothing; a frozen one teaches exactly what the organisation knew, chose and got.

How ONX ranks candidate options

In an ONX Decision Room, candidate options are ranked by the earliest date each one clears every binding constraint. The ranking is a recommendation, never a verdict. A person makes the choice, and if they overrule the ranking, the override is recorded: who, when, and against what evidence. The option chosen, the options declined and the reasoning between them all persist on the decision itself.

One concrete example

Clearly illustrative, with no customer implied. A services firm must stand up a new delivery team for a programme starting next quarter. A scenario run prices three candidate options: expand an existing site, open a new one, or split the team across two. Each option carries its costs and the earliest date it clears every binding constraint, from hiring readiness to systems access to what the client contract permits. Then a fact the client had merely stated is measured and comes back worse. A new run creates three new options with new dates; the first set stays in the record untouched. The delivery lead chooses the second-ranked option for reasons the ranking could not see, and the override is recorded. A year on, the outcome is scored against the option as it was priced, not as anyone remembers it.

The menu becomes memory

A single frozen option set makes one decision auditable. Years of them make the organisation smarter, because the record now includes the roads not taken with their prices attached. That is the quiet asset at the centre of Enterprise Decision Intelligence: not just what was decided, but what was declined, at what cost, and how the comparison actually looked before anyone knew the ending.