A dashboard is not automatically a record
Live dashboards are valuable because they respond to the latest state. That same quality makes them a poor historical artifact. A number reviewed on Monday may look different on Friday after an operational correction, yet the interface offers no indication that the basis changed. Screenshots and manually exported spreadsheets appear as a workaround, but they detach the numbers from structured source context and leave teams to manage versions by filename.
Professional reporting needs both modes. The operation should remain correctable, and a generated report should retain the exact view that was approved or discussed. Treating these as separate records gives a team continuity without freezing the underlying Event. It also makes later comparisons more honest: differences between versions can be understood as changes in a retained result rather than mysterious movement in a live query.
Event Performance is stored by version
A generated Event Performance report is persisted as a versioned snapshot with the source context required to interpret it. New source data can inform a later version, but it does not silently replace the earlier one. The compact Event Recap remains available across all plans, while Full Event Performance begins with Core under Pricing V3. This distinction lets every Event retain a useful completion view while reserving the fuller analytical surface for the appropriate commercial tier.
Versioning is not decorative metadata. It defines which result the reader is seeing and allows the application to keep historical material readable even if the Workspace later changes plan. The report belongs to the customer record. A downgrade can remove entitlement to generate a new full version, but it does not revoke access to the versions already retained.
Periodic reporting uses the same durable model
Periodic reports aggregate an explicit weekly, monthly or yearly range and persist the generated result. They begin with Scale, alongside PDF, XLSX and CSV report exports. When a team asks to generate or export a new periodic report, NOCTRA verifies that the Workspace and the acting member can perform that operation. The interface explains when the plan needs to change, but the action never depends on a hidden button alone.
A plan describes commercial availability, not universal access. Reporting must still be available in the configured product and the member must have the relevant permission. This keeps an upgrade from unexpectedly changing internal responsibility: the commercial plan can make a workflow available to the Workspace, while the Workspace continues to decide who is allowed to use it.
Downgrades restrict creation, not memory
A Workspace that moves below Scale keeps its persisted periodic reports and can continue reading them. A Workspace that moves below Core keeps historical Full Event Performance versions. Existing customer data is neither deleted nor hidden, and unrelated Event work remains possible. What changes is the ability to perform a newly entitled operation: generate another full or periodic report, or create a new gated report export.
This boundary is important commercially and operationally. A subscription decision should control future service, not rewrite the historical record of work completed while access was valid. It also avoids a coercive product pattern in which a team must maintain a higher plan merely to see its own prior reporting. NOCTRA preserves necessary customer-data export paths separately so entitlement gates do not become a trap around customer information.
Exports are outputs, not alternate authorities
PDF, XLSX and CSV serve different downstream workflows, but they originate from the same retained report. An export does not recompute an unofficial version in the browser or create a parallel interpretation of the Event. Once the requested report and Workspace context are verified, the chosen format expresses that result for reading, analysis or circulation.
That consistency reduces a familiar source of disagreement: one number in the application, another in a spreadsheet and a third in a PDF created from a slightly different query. Durable report versions provide the common basis. Exports can travel, while their meaning still begins with a defined NOCTRA report rather than an incidental interface state.
Reporting becomes part of the operating loop
NOCTRA is organized around Plan, Operate and Understand. Durable reporting completes that sequence by allowing understanding to survive the moment in which it was generated. Teams can return to an Event version, review a period and use that retained evidence in the next planning cycle without pretending the operation stopped evolving afterward.
This release does not enable commercially unavailable Intelligence, and it does not claim that a report makes decisions on behalf of an organizer. It provides the more fundamental capability: a trustworthy, versioned account of the implemented operational data, governed at creation and preserved afterward.