A review of billing question should explain the transition to “Escalate”, rather than treating the label as self-explanatory. A short answer can be wrong in a different environment. Removing the conditions makes documentation easier to read and harder to use. State the question, applicable conditions and source of the answer. Retire an old card explicitly when the process changes.
Review the next move
Bilgi Notes is a knowledge-card concept for support teams who need concise answers with enough context to trust them.
Example: Billing question
The illustrative record contains finance contact. Its state is escalate. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Compare the proposed next step with the original objective. For billing question, use “Finance contact” as the starting context.
- Review the assumption that would change the outcome. For billing question, use “Finance contact” as the starting context.
- Leave a dated explanation for the next person. For billing question, use “Finance contact” as the starting context.
A small exercise
Take one recent knowledge management example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Password reset” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More notes →