# Do not call a calendar appointment an if-then plan when the action still needs preparation

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

---

## Do not call a calendar appointment an if-then plan when the action still needs preparation

ID: MHC-D-RESEARCH-0942 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/do-not-call-a-calendar-appointment-an-if-then-plan-when-the-action-still-needs-preparation

'Thursday at six' is a schedule; it is not automatically a cue-response mechanism.

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

### Use when

- A scheduled task is labeled an implementation intention even though the trigger does not make the action executable.

### Avoid when

- Both methods can be useful; the distinction is mechanistic, not a ranking.

### Explanation

The 2026 review explicitly distinguishes strict if-then plans from broader when/where/how scheduling. Use calendars for reserving time. Use if-then plans when you want a recurring cue to trigger a ready action. Combining them is fine, but naming the mechanism correctly helps you fix the right failure.

### Example

'Thursday 18:00 gym' is scheduling; 'if I close the laptop at 17:45, then I put on the prepared gym clothes' is a cue-action plan.

### Check

Scheduling and cue-response design are used for different problems rather than conflated.

### Limits

- Both methods can be useful; the distinction is mechanistic, not a ranking.

### Evidence and sources

- supports: The 2026 if-then review separates strict cue-response plans from generic time/place action planning. — RS-767B2D886087DA3B. Both methods can be useful; the distinction is mechanistic, not a ranking. (See source record)
- RS-767B2D886087DA3B: A systematic review and meta-analysis on the effectiveness of if-then plans – in a strict sense – to facilitate fruit and vegetable consumption in adults — https://link.springer.com/article/10.1186/s12966-026-01915-y

No review details supplied.
