# Move feedback close enough to the event to keep the evidence

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Move feedback close enough to the event to keep the evidence

ID: MHC-D-RESEARCH-0596 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/move-feedback-close-enough-to-the-event-to-keep-the-evidence

Delay converts examples into impressions.

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

### Use when

- Feedback arrives months later as a vague performance-memory summary.

### Avoid when

- Timing should still allow emotional de-escalation and fact checking; 'immediate' is not always 'better.'

### Explanation

When stakes and context allow, capture feedback soon enough that the event, decision and alternatives are still reconstructable. Keep formal cycles for aggregation if needed, but do not make the annual review the first time a correctable behavior is mentioned.

### Steps

1. Event is still reconstructable.
2. Example is concrete.
3. Recipient has a future chance to apply the change.
4. Urgent safety or conduct concerns are not deferred.
5. Formal documentation requirements are still followed.

### Example

A review comment on a handoff arrives after the next comparable handoff, not six months later.

### Check

The recipient can connect the feedback to a specific recent event and reuse it soon.

### Limits

- Timing should still allow emotional de-escalation and fact checking; 'immediate' is not always 'better.'

### Evidence and sources

- supports: Workplace health-profession trials found face-to-face feedback may improve task performance on average, but prediction intervals and prior syntheses show substantial variation including possible harm. — RS-C261A3B526BEC2C0. Evidence quality was low and context-specific; do not generalize the effect size to ordinary office work. (Results and discussion)
- RS-C261A3B526BEC2C0: Effect of face-to-face verbal feedback on workplace task performance of health professionals — https://pmc.ncbi.nlm.nih.gov/articles/PMC7170595/

### Vedokrok editorial review

Capture the event, then choose a useful feedback moment

A useful comment can arrive too late to help with the next attempt. Preserve the example while it is clear, then choose when the person can use it.

#### Keep evidence separate from delivery

For ordinary work feedback, save the specific observation and enough context to check it. When practical, agree a short conversation before the next comparable task, rather than after that opportunity has passed. In a hypothetical document handoff, note the missing decision date, clarify it with the author, and agree how to include it in tomorrow’s handoff. If clarification must wait, label the gap and the next opportunity to revisit it.

#### Prompt does not mean immediate at any cost

Allow time for fact checking, reflection and de-escalation. Ask when the feedback will be useful; do not interrupt every attempt merely to be fast. CIPD’s evidence summary distinguishes promptness from frequency and reports mixed timing findings. This example is an editorial application, not a validated schedule. Urgent safety or required reporting follows its own rules and must not wait for a coaching conversation.

**Editorial takeaway:** Capture a checkable event soon and give feedback in time for an appropriate next attempt. Judge the timing by its usefulness and context, not by how quickly the comment was sent.

#### Editorial evidence

- supports: CIPD recommends discussing feedback timing with the recipient and prioritizing its quality over its frequency. — RS-5B538054D9CC9CEC. Selected official practice-summary passages inspected on 2026-10-05. The handoff example is an ordinary-work editorial adaptation, not a tested timing intervention. (Frequency and promptness of feedback; Recommendations for practice)
- challenges: Immediate or more frequent feedback is universally more effective. — RS-5B538054D9CC9CEC. The summary reports limited workplace evidence and mixed findings from education, with timing dependent on the task. No universal delay or effect size is inferred. (Frequency and promptness of feedback)
- RS-5B538054D9CC9CEC: Performance feedback: An evidence review — practice summary — https://www.cipd.org/globalassets/media/knowledge/knowledge-hub/evidence-reviews/performance-feedback-evidence-review_tcm18-111378.pdf

Editorial version: 1.0.0 · evidence checked 2026-10-05 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/track-the-next-two-opportunities-not-the-next-six-months
