# Prepare the facts, impact and desired change before the meeting

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Prepare the facts, impact and desired change before the meeting

ID: MHC-D-RESEARCH-0761 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/prepare-the-facts-impact-and-desired-change-before-the-meeting

Prepare what happened and what should change before rehearsing the argument.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- You need to raise a problem but your current story is dominated by frustration or motive attribution.

### Avoid when

- Some harms are primarily relational or emotional; practical impact does not need to be financial to matter.

### Explanation

Write three short sections: the observable event or pattern, its practical impact, and the change you want. Bring relevant evidence. Keep motive as a hypothesis unless you actually know it.

### Template

Observed: [specific event/pattern]. Impact: [work/relationship consequence]. Requested change: [specific future behavior or process]. Evidence: [if relevant].

### Example

'Three approvals were reassigned after the deadline; testing lost a day. Please name the backup approver before the next release.'

### Check

The issue can be understood without agreeing with your judgement of the other person's character or intent.

### Limits

- Some harms are primarily relational or emotional; practical impact does not need to be financial to matter.

### Evidence and sources

- supports: Acas informal-meeting guidance recommends preparing what to say, gathering relevant evidence, considering what would fix the problem, listening to the other side and recording what is agreed. — RS-37217726DC46F74A. A workplace meeting may carry legal or policy requirements beyond these general practices. (Preparing; at the meeting; putting things in writing)
- RS-37217726DC46F74A: Informal meetings — https://www.acas.org.uk/how-to-raise-a-problem-at-work/going-to-an-informal-meeting

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/let-the-other-account-exist-before-you-rebut-it
