Make the open question explicit
A decision log should say what is undecided and which options are genuinely available. Link to the relevant approved material. The receiving person needs to know the next decision, not reconstruct the entire conversation. Include who can decide and when the question should be raised again, without inventing an answer on their behalf.
Distinguish recommendation from approval
A colleague suggesting an option is not necessarily the person authorized to approve it. Label proposed, decided and implemented separately. When a decision is recorded, preserve the date, scope and source of that decision. A more recent message about another part of the project should not automatically overwrite it.
A fictional example
An internal reporting template needs a new section. The coordinator recommends a shorter version, but the reporting owner has not agreed. The next action is to obtain that decision before changing the shared template. The log lists the affected task and the current version. It does not convert the recommendation into approval or send the request automatically.
Keep sensitive detail elsewhere
Use a minimal reference where the context involves personal, financial or confidential material. Do not paste private deliberations into a broadly shared project board. The account owner decides access. If the receiving role cannot access a required reference, record that as a handover gap rather than copying the material around the restriction.
Use a compact decision entry
An entry can say: question—whether the supplier response is final; decision owner—operations reviewer; evidence—approved response reference; outcome—still provisional; next review—agreed Tuesday check-in. Keep a later final answer as a new dated decision or an explicitly recorded revision. Do not quietly replace provisional with approved and lose the reason for the change. The log should let a receiver distinguish a proposal, an authorized decision and work performed under that decision.
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