Copying a report, and moving to a new standard version
Carrying last year's answers forward, and what happens when the standard itself has changed.
The version of the standard on a report is fixed. Reporting again, next year or under a newer version, means making a new report from the old one.
Copying
From the actions menu on a report in the Reports list, choose Copy report.
| Field | Notes |
|---|---|
| Name | Prefilled with the old name plus "(copy)". |
| Period from / to | Prefilled with the source period shifted one year. |
| Comment | Optional. |
| Keep changelog | Off by default. Carries each field's version history across, so you can see where a value came from. It copies a lot of extra data. |
| Change report version | Opt-in. Off means a straight copy onto the same standard version. |
With Change report version off, every answer is carried over unchanged and the new report is ready to edit immediately.
Copying requires write access to the source report.
Moving to a newer standard version
Tick Change report version and pick the target standard. Only versions that have a mapping from your source version are offered.
The Cards then maps the old answers onto the new structure:
- fields that map cleanly are copied straight over,
- fields that need judgement are queued for review,
- nothing uncertain is filled in silently.
The review queue
The new report's overview shows a card explaining where the answers came from and how many still need attention, with a Review them button. The card disappears by itself once nothing is outstanding.
The review flow takes one field at a time:
Read what the previous report said
Each step leads with the field's plain-language title and shows the old report's answer underneath, so you are never reading bare standard codes.
Check the suggestion
Where the mapping needed interpretation, a suggested answer is prepared for you and marked as written by AI. It is shown in the same editor the report itself uses, so you can edit it in place.
Accept, edit or skip
Use this answer writes it into the new report and moves on. Skip for now leaves the field untouched and keeps it in the report to deal with later. Back returns to the previous field.
If no suggestion could be produced, the step says so and invites you to write the answer yourself, leave it empty, or skip it.
The queue is resumable, so leaving and coming back picks up where you were, and accepting an answer never renumbers the remaining steps.
