When a deadline is close, the task may need fewer decisions rather than more pressure. The emergency outcome is an end-to-end minimum version, protected review and delivery time, and clear communication about risk.
Reviews have associated procrastination with negative emotions and proposed that stressful contexts can increase vulnerability to avoidance. These are associations and a conceptual model, not proof of one cause for every freeze (Nie et al., 2025; Sirois, 2023).
Calculate usable time first
Do not count every hour until midnight. Remove sleep, fixed meetings, travel, food, technical upload time, and minimum recovery.
Official deadline:
Usable work time:
Review time:
Delivery / upload time:
Last safe starting point:When the calculation already makes the full scope impossible, communicate rather than hiding the risk behind more planning.
Define the minimum delivery
Sort the work:
| Category | Question |
|---|---|
| Mandatory | without what will the result be rejected |
| Critical risk | where would an error make it wrong or unsafe |
| Useful | what improves quality after the mandatory work |
| Not now | what can be removed without destroying the purpose |
Minimum does not mean careless. It preserves requirements while removing optional scope.
Build an end-to-end version
Do not begin with visual polish or a perfect first section. Move across the complete output:
- structure every required part;
- mark missing data;
- add central calculations or arguments;
- expose critical gaps;
- reserve review and delivery.
For example:
| Block | Output |
|---|---|
| 40 minutes | complete rough structure |
| 60 minutes | mandatory data and content |
| 20 minutes | critical-error check |
| 10 minutes | export, delivery, confirmation |
Use your own times and do not spend the delivery reserve on cosmetic edits.
Communicate risk before failure
Use this structure:
X is complete. Y is creating risk for the deadline. By __, I can deliver intermediate output Z. I propose removing A or moving the complete result to B. Which option has priority?
Do not promise a revised date without calculating it. When scope is not yours to change, ask the owner to make the trade-off explicitly.
After the deadline
First complete delivery and record status. Review causes separately: when the risk became visible, which signal was missed, and which checkpoint should exist next time.
If freezing, anxiety, or stress regularly and substantially disrupt work and wellbeing, planning techniques may not be enough; consider appropriate professional support.
In Flammy, the minimum delivery can become a quest and the blocks concrete tasks. XP cannot create time or replace early communication.
For an academic upload, use the safe submission ladder. If energy appears only near the date, examine motivation before a deadline.