Reports and publications
Editions, exports, and why a render can be refused.
Who this is for
Anyone producing a deliverable somebody outside will read.
Report families and editions
A report is a family. Each language edition belongs to that family and inherits its dataset version and evidence lineage rather than recomputing them — which is what keeps five editions on one chain instead of producing five unrelated reports.
Creating a translated edition
A non-source edition must reference a governed translation artefact that your organization owns and that targets the edition’s language. Without one the edition cannot be created — an edition in another language with no record of how the words got there is a publication with untraceable provenance.
Exports
PDF, DOCX, PPTX and XLSX. Arabic editions render right-to-left with embedded Unicode fonts.
Why a render is refused
Export is governed. A render is refused when the evidence behind the report cannot be resolved — most commonly because a claim cites nothing, an element carries no citation, or the report predates governed evidence linkage entirely.
What this does not do
Stated here rather than discovered later
- A report cannot be published in a language outside the five institutional editions. The request is refused, not approximated.
- A translated edition cannot be created without a governed translation artefact. The platform does not produce the translation for you.
- A refused export is not a bug to work around.