# Swap commitments openly when a priority changes

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

---

## Swap commitments openly when a priority changes

ID: MHC-D-RESEARCH-9791 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/swap-commitments-openly-when-a-priority-changes

An extra priority is a trade-off, not a new hour.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A new urgent request arrives halfway through a full day.

### Avoid when

- Immediate emergencies may require action first and retrospective coordination; this rule is for normal reprioritization.

### Explanation

Show the existing planned work and ask what should be delayed, delegated, reduced or canceled to accommodate the new request. Record the changed output and recipient. Avoid silent overtime as the default way to handle reprioritization.

### Steps

1. Identify which current commitment will move or shrink.
2. Communicate the effect on the original owner before accepting the new deadline.

### Example

A production incident displaces a planned report; tell the report owner the revised delivery.

### Check

The replacement is explicit and someone can make an informed priority decision.

### Limits

- Immediate emergencies may require action first and retrospective coordination; this rule is for normal reprioritization.

### Evidence and sources

- supports: UK government delivery guidance suggests regular explicit prioritization based on evidence, user research and available resources. — time-priority. Claim limit: General public-service prioritisation guidance. It does not prescribe the card-specific effort/date comparison or establish forecasting accuracy. Commitment substitution and estimate review are editorial adaptations, not demonstrated productivity effects.
Source reading history: selected_passages; 2026-10-10; Regular priority review using user research, delivery performance and stakeholders. The cited official page was retrieved on 2026-10-10 and the named passages were inspected. Card-specific adaptations are independent editorial reasoning, not validated improvements. Introductory prioritisation and capacity passages reread on 2026-10-12; they do not specify the card-specific forecasting procedure.
Agent release review: Atlassian calendar guidance and the UK Government Service Manual supply context for calendar and prioritization practices. The precise estimate comparison and scheduling methods are editorial adaptations; the original data and emergency limits remain attached. (Regular priority review using user research, delivery performance and stakeholders)
- time-priority: Deciding on priorities — https://www.gov.uk/service-manual/agile-delivery/deciding-on-priorities

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
