Reporting HRIS Issues
Provide examples that help the team understand the issue from the first report
A clear issue report gives support the right information to begin investigating. Explain the task, the steps before the issue appeared, the expected result, and what actually happened. Technical terms are unnecessary when the process is described concretely.
Explain the process and steps taken
Identify the menu or task and the sequence of actions before the issue appeared. Record when it happened and whether it occurred again on a later attempt.
If you have not tried again, state what you already know. Avoid repeating actions that could create duplicate transactions merely to demonstrate the problem.
Compare expected and actual results
For example, a report was filtered for one branch, but the displayed result is not as expected. Explain the filters and period used so that the team understands the difference.
A screenshot can show a message or screen. Send only the necessary portion through official channels; do not send passwords or access codes.
Describe the impact and provide a user contact
Explain whether the process has stopped completely or can still run in part. State the deadline and who can help with the investigation.
Use a communication thread the team can follow. When continuing a previous report, include its context so that investigation results stay connected.
Check again after receiving guidance
Follow support's instructions and report the result. If the issue remains, explain the differences you found so that investigation can continue.
The Sigma team helps Sigma HRIS and Forte HRIS customers through dedicated support, a dedicated WhatsApp contact, and support groups, with escalation as needed until the issue is resolved.
Keep reports concise but detailed enough to investigate
An attendance report with unexpected results
Instead of only writing “the report is wrong,” identify the branch, period, and attendance results that differ from your reference. Include the filter selection steps, time of occurrence, and one data example showing the discrepancy. The team can then investigate settings and information sources more precisely.
If the issue affects only one user, say so. Differences in access or devices may help the investigation, but users do not need to guess the technical cause. Separate visible facts from assumptions so that the team does not start with an unproven conclusion.
Keep communicating until the result is confirmed
After the team explains the corrective steps, try the same process again as instructed. Say whether the result is now correct or which parts still differ. This confirmation matters because sending instructions alone does not complete the handling; users need to be able to continue their work with the correct result.
Sigma Solusi Informatika prioritizes application quality and support until problems are resolved. Customers' experience with Sigma HRIS and Forte HRIS also informs regular development. Clear reports support the current investigation while providing context for improvements to the user experience.