Use case

Programme evidence

The record your intelligence programme leaves behind: the requirements you set, the reporting they produced, and who it reached, dated as it happened.

Every
PIR dated

set, changed and retired, on the record

Every
Report versioned

snapshotted at publication, never overwritten

Every
Send logged

who received which report, and when

What you get

What Conundrum delivers

One workflow, one record

The process that produces your intelligence is the same one that evidences that you ran it. Nothing is assembled after the fact.

Requirements on the record

Every priority intelligence requirement is stored with the date it was set and the date it changed, so the question of what you were watching for has an answer.

Versioned at publication

Publishing a report snapshots it. What was said, and when, stays fixed even as the live document moves on.

Dissemination as proof

Every report records that you prioritised the threat, produced intelligence on it, and told the right people.

Exportable per report

Any report prints or exports on its own, fully expanded. There is no per-framework evidence pack, because we do not assess you against a control set.

Frameworks

One workflow, every shared standard

Priority Intelligence Requirements, open-source collection, consolidated reporting and recorded dissemination, expressed in the language each framework uses.

See the record it keeps while it works

A demo runs on your sector's intelligence, not a canned dataset.