Describe the condition that would unblock work
Waiting on supplier is incomplete if nobody knows which answer matters. State the particular input, decision or permission required. Link to the approved context and name a review owner. Do not include private account information merely to make the description more detailed; a scoped reference is often enough.
Separate dependent and independent tasks
One blocked input need not stop an entire project. Identify what can proceed without assuming the missing answer. Conversely, do not start a dependent action just because the software allows editing or moving a card. Nifty’s documented completion lock is a technical behavior, not a complete operational rule for every task.
A fictional decision tree
An internal checklist update waits for a final equipment specification. The cover person can verify the existing list and prepare questions, but should not finalize the replacement entry. If the response arrives, the named reviewer checks it. If it does not arrive by the review point, the team chooses whether to change the schedule; silence is not an answer.
Escalate the narrow question
A useful escalation asks for the missing decision and explains which work it affects. Avoid sending a long transcript with no clear request. Record the answer’s scope and update the task only after it is understood. If the blocker concerns legal, financial, safety or personnel authority, use the appropriate qualified process rather than improvising a workaround.
Use an explicit branching note
Write two branches: if the final specification arrives, route it to the named reviewer; if it does not arrive by the review point, ask the schedule owner to decide the next date. Keep both distinct from independent preparation that can proceed now. This makes the record useful during absence without pretending the future answer is known. Do not encode a provisional assumption as a completed approval just to unblock a downstream checklist.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Nifty task, subtask and milestone dependencies — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01