•  When reporting an issue, help us quickly assess:

1. Business Logic Gap – Is it a case we didn’t foresee or test?

2. Data Error – Are prices, contact details, or configurations incorrect?

3. System Bug – Is the software behaving incorrectly (e.g., permissions, broken flows)?

4. User Misunderstanding – Is it a training issue (e.g., wrong button clicked)?

5. Something Else – Anything that doesn’t fit the above.

• To document issues effectively, focus on:

1. The context – What were you trying to do, and why?
2. The inputs – What data or action triggered the issue?
3. The expected outcome – What did you expect the system to do?
4. The actual behavior – What happened instead?
5. Any errors/messages – Include screenshots or messages when helpful.

Clarity now = speed later.

If we document issues well, we will fix them faster — and we’ll avoid unnecessary panic or delays.