Skip to main content
Disclaimer: This software is for radiation protection education, screening calculations, and professional support only. It does not replace qualified health physicist judgment, regulatory requirements, approved procedures, emergency response tools, or formal shielding design review. Exposure, absorbed dose, equivalent dose, and effective dose are distinct quantities; do not equate R and Sv without explicit context and assumptions.

Reports & Exports Help

What a calculation report contains

A report summarizes one calculation run: calculator identity, timestamp, unit preference, user-selected units, raw inputs, converted numeric inputs used by physics, intermediate steps, primary result (label, value, unit), formula text, assumptions, warnings, structured references, and the screening disclaimer.

Some calculators add a structured extension block (for example shielding μ provenance, internal dose tool metadata, or spectroscopy tool hash and readiness flags) so exports stay machine-readable and reviewable.

Export actions

  • Copy Summary — builds a plain-text clipboard summary after the payload passes schema validation. If validation fails, copy is skipped and the UI lists what to fix.
  • Download JSON — downloads a JSON envelope suitable for archival or tooling; the core payload is validated against the same schema the app uses internally.
  • Download Markdown — human-readable report for notebooks, reviews, or version control.
  • Print view — opens a print-friendly layout; you can print to paper or use the OS “print to PDF” workflow (HPCalc does not embed a proprietary PDF engine).

Integrity badges, schema validation, and export blocked

Badges summarize whether the in-memory payload is valid and whether JSON/Markdown/copy paths are ready.

reportReady (where present on workspace extensions such as spectroscopy, waste, contamination, or air sampling) means the structured report passed calculator-specific documentation gates for export—not a regulatory sign-off. warningLevel (none / screening-caution / elevated) summarizes how noisy or fragile the screening warnings are for quick review; it does not block export by itself unless an export rule ties to it.

Export blocked usually means one of: Zod/schema validation failed on the payload; required documentation fields are missing (for example custom μ provenance on shielding, or calibration/source notes on some spectroscopy tools); or a calculator-specific rule prevented building a compliant report. Read the on-page messages—they mirror validation errors you would see in development.

Source notes and structured IDs exist so downstream readers can trust where screening numbers came from. User-supplied coefficients and some spectroscopy exports expect explicit notes before export succeeds.

Using reports for documentation

Use exports to capture assumptions, warnings, and references at decision time. Keep regulated approvals, ALARA programs, and final dose assignments under your facility's qualified review and procedures—reports are support artifacts, not automatic sign-offs.

Tip

If an export fails, fix validation issues first; retrying without fixing the payload will produce the same block. When in doubt, open the matching Help topic for that calculator.
Open reports page