During a training session, a useful question may arrive before the group has enough background to answer it. A visible place to hold that question prevents postponement from feeling like dismissal.
Agree on a simple arrangement with the facilitator: record the question, note who will follow up, and state when the group will hear back. Avoid putting confidential examples on a shared board; generalise the question or use the approved private channel.
Capture the question, not just a keyword
“Permissions” is difficult to answer later. “Who approves access when the usual reviewer is away?” preserves the actual uncertainty. Let the person who asked confirm the wording.
At the end of the session, review the outstanding items. Some may now have answers. Others need a document, a demonstration, or a decision outside the trainer’s role. Say which is which rather than implying every question can be solved immediately.
For the participant, the same approach works in personal notes. Keep unresolved questions separate from instructions you are expected to follow now.
A good follow-up does not need to be elaborate. A short message connecting the original question to an answer or responsible contact closes the loop more clearly than another collection of unrelated reading links.
What a useful follow-up entry contains
- Question: Who approves access during the reviewer’s absence?
- Next owner: the role authorised to clarify that process, not automatically the trainer.
- Response date: an agreed checkpoint rather than an invented promise of resolution.
- Status: answer confirmed, decision pending, or referred elsewhere.
These are illustrative fields. If the answer is still pending at the checkpoint, report that explicitly and state the next step. Do not quietly remove the item from the board because the session has ended. Closing an item should mean the group can find the response, not simply that somebody has stopped displaying the question.