All guides
16 August 2026
On Hold vs Blocked
Both columns mean the sheet is not moving. They mean different things, and Beech treats them differently on Home, in history, and in reports.
Blocked
Usually automatic: an unfinished dependency or a vendor request that is not Delivered yet. The assignee cannot usefully continue. When upstream finishes, Beech unblocks and notifies. You will also see it in the blockers feed on Home.
On Hold
A human choice: stop this to do something else. Beech requires a written reason before the move completes. Who paused it, when, and why are stored on the task. That trail is the answer when someone asks why a deadline slipped.
The task history can copy a hold/resume summary in one click. Use On Hold for priority, not for “waiting on structure” — that should be a dependency so Blocked stays honest.
Full reference: On Hold in the user guide