Use this guide when something looks wrong in the product but you need a structured way to identify whether the issue is data quality, permissions, process design, or integration behavior.
First-response checklist
- Confirm the affected user role and permissions
- Review whether the source record exists and is complete
- Check dependent modules such as attendance, leave, payroll, or project ownership
- Look for approval stage or status mismatches
- Validate whether the issue is user-specific or system-wide
Frequent root causes
Most issues trace back to incomplete master data, stale permissions, missing assignment context, or workflows being used in the wrong order. For example, tasks without a source context, resignations approved out of sequence, or payroll previewed before attendance lock will produce confusing outcomes.
Escalation guidance
Escalate product issues with exact entity IDs, screenshots, expected behavior, actual behavior, and whether the issue blocks payroll, employee compliance, customer delivery, or only UI convenience. This makes investigation much faster for engineering and support.