Issue a correction
A published report can't be edited. When something is wrong on it, you issue a revision — a new document alongside the original, with the reason stated on it.
Required role: Project Manager.
Prerequisites: a published meeting.
Steps
- Open the published meeting.
- Select Issue a correction.
- Enter Why is this correction being issued? — for example, Wrong due date on point 3.
- Confirm.
Result: Correction issued. A new revision is produced — rev. 2, then rev. 3, and so on. The first document is labelled Original issue.
What happens to the original
Nothing. The published version keeps its file, unchanged. The revision is produced alongside it, and everyone on the distribution list is told why.
Both documents remain downloadable. That's the point: the record shows what was circulated at the time and what replaced it.
The reason is part of the document
The reason you type is printed on the document, prefixed Reason:, and included in the email to recipients. It has a character limit, shown as you type.
Write it for the reader who receives the second PDF and needs to know in one line what changed.
When to revise, and when not to
Issue a revision when the published document is wrong — a due date printed incorrectly, a company named on the wrong point, an attendance badge that misstates who was there.
Don't revise for things that simply moved on. A point that has since been closed, a new subject raised, a due date renegotiated — those belong in the next meeting. The register carries them forward on its own.