Capital should buy information, not just activity

Exploration programmes are easy to describe in terms of activity.

Metres drilled.

Samples collected.

Survey lines completed.

Budget spent.

Programme percentage complete.

Those measures are necessary. They tell us whether work is occurring and whether the organisation is controlling time and cost.

But they do not necessarily tell us whether the programme is succeeding.

Exploration capital is not only buying activity.

It is buying information.

The programme should begin with a question

A useful exploration activity should usually be connected to an uncertainty the organisation is trying to resolve.

For example:

• Does mineralisation continue at depth?
• Is the geophysical anomaly caused by sulphides or something else?
• Is grade continuity sufficient to justify infill drilling?
• Is the metallurgy likely to support an economic recovery?
• Does the target remain viable after infrastructure and access constraints are considered?

Once the question is explicit, the programme can be evaluated against what it was designed to learn.

Without that connection, it is possible to complete a great deal of work without materially improving the decision.

Activity is not evidence

A completed drill hole is an activity.

Its geological log, assay results, structural interpretation and relationship to the target hypothesis become evidence.

This distinction sounds obvious, but operational systems often concentrate on the first part because it is easier to count.

A programme may report:

18,000 metres drilled, 96% of planned metres completed.

That is useful, but an investment committee may need a different answer:

Did those metres strengthen or weaken the interpretation that justified the programme?

The second question requires the activity to remain connected to the hypothesis it was testing.

Not every negative result is a failure

Exploration has a particularly difficult relationship with negative results.

A successful hole is easy to communicate.

A failed target can look like wasted expenditure.

But a well-designed programme that decisively rejects a weak hypothesis may have produced substantial value by preventing a much larger future allocation of capital.

That means the programme should record not only discoveries, but learning.

For example:

Before drilling

The mineralised contact is believed to continue below 250 metres.

Evidence

Three holes intersect the predicted structure but do not support the expected mineralisation.

Interpretation

Structural continuity is confirmed; mineralisation continuity is not.

Decision

Do not proceed with the planned deep drilling campaign. Redirect capital toward a second target.

The capital did not create an orebody.

It still changed the decision.

Measuring uncertainty carefully

This leads naturally to the idea of uncertainty reduction.

It may be useful to ask:

What uncertainty did this expenditure reduce?

But that does not mean uncertainty should always be represented as a precise mathematical score.

Some organisations may use structured ratings. Others may prefer qualitative assessments such as unresolved, reducing, stable or increasing.

The important part is not the number.

The important part is preserving the before-and-after reasoning.

What did we not know?

What test did we select?

What evidence did it produce?

What changed?

What remains unresolved?

Capital allocation becomes easier to explain

When this chain is preserved, the next funding request becomes more intelligible.

Instead of:

We have spent $6.4 million and require another $4 million.

The programme can explain:

The first phase tested three uncertainties. Two have been materially reduced, one remains unresolved, and a new risk has emerged. The next $4 million is intended to test the remaining continuity question and complete metallurgical work.

That is a different quality of conversation.

It does not remove the exploration risk.

It demonstrates why the next tranche of capital is rational given the information now available.

Programme assurance is therefore about learning

Traditional project control asks:

• Are we on time?
• Are we on budget?
• Are we completing the work?

Exploration programme assurance needs to add:

• Are we answering the questions that justified the programme?
• Is the evidence changing our understanding?
• Are assumptions being updated?
• Are we still testing the right target?
• Is the next capital request connected to remaining uncertainty?

That makes exploration less like a sequence of disconnected campaigns and more like an explicit learning programme.

But for that to work, the organisation must preserve something that is often lost: the reasoning behind the decision itself.