TAP TAP GO
Capture the actual question
Record the question in the language the reviewer used. Add the requesting person, date, topic and response owner. Avoid rewriting a difficult question into an easier one. Separate an answered item from one that merely received an acknowledgement. If several questions overlap, link them while preserving their original context. This lets the team recognise repeated concerns without losing the exact information requested.
Define a complete response
A strong response includes a direct answer, relevant evidence, important limitations and a next step if something remains open. Mark partial answers honestly. Use a shared status vocabulary such as open, in preparation, answered and clarification requested. Before a meeting, review the oldest unresolved items instead of simply counting how many replies were sent. The practical measure is whether the reader can progress, not whether the inbox looks busy.
Put the guide to work
At the end of each review meeting, read back the open questions and confirm their owners. This catches questions that were discussed but never actually answered. Record whether the requester considers an item resolved instead of letting the preparation team close it solely because a response was sent.
Hypothetical example
An enterprise prospect asks who handles a service interruption. The first reply contains a generic company overview. The question log keeps the item open until the team provides named escalation roles, operating hours and the boundaries of partner responsibility.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
