# R15 · Governance, responsibilities and versions

**What it is for.** Document who decides, who can publish and how knowledge changes.

**When to use it.** Before making a decision or updating the corresponding product. You can use a spreadsheet, a document or a notebook; no software licences are needed.

## How to use it

1. Start with the real decision or question you need to resolve and set a cut-off date.
2. Fill in only what can be verified; write **NOT VERIFIED** when data is missing.
3. Separate observed facts, hypotheses and implications, and name a reviewer.
4. Keep the original version and record relevant changes when you update it.

## Editable template

| Activity / product | Contributes | Analyses | Reviews | Approves | Receives | Access level |
|---|---|---|---|---|---|---
| | | | | | |

| ID | Version | Cut-off date | New / withdrawn evidence | What changed | Reason | Approver |
|---|---|---|---|---|---|---
| | | | | | |

## Guided example · Company A

Company A adds a piece of evidence that invalidates an earlier inference; it publishes version 1.1 with the change explained and an identified owner.

## Mistake to avoid

Do not confuse a register of owners with real authorisation to access sensitive information.

## Final check

- Is it clear which decision or need it serves?
- Can the evidence be located, and is it dated?
- Are uncertainties and limits made explicit?
- Can someone else repeat or review the work?

**Notice:** entirely fictional case. The tools are for educational purposes; they do not represent an audit or certification.
