HRIS Issue Report Template
Explain what happened, its impact and an example of the result to help focus the investigation
An issue report template helps users provide complete information without needing technical terminology. Record what you did and what happened. Separate observed results from suspected causes so support can begin investigating the facts.
Describe the task and sequence of events
Identify the menu, period and steps taken before the issue appeared. Explain whether it affects one user or has also been observed by others.
If you do not know, write that it has not yet been checked. Do not repeat transactions that could duplicate data merely to complete the report.
Explain how the result differs
State the expected result and what you actually saw. A specific example is more useful than simply saying the application cannot be used.
If needed, send a relevant screenshot through an official channel. Do not include passwords or access codes.
Describe the impact and provide a contact
Explain the work being held up and the timing required. Identify someone who can assist with further investigation.
Keep the report in one conversation that the team can follow. When continuing an existing case, include a summary so the investigation remains connected.
Record actions and confirm the results
Keep support's instructions and the results after trying them. If the issue remains unresolved, explain what still differs from expectations.
Sigma's team provides dedicated support for Sigma HRIS and Forte HRIS customers. When further handling is needed, the Application Specialist can coordinate with the Support Manager or Project Manager and escalate up to chief level.
An example format you can use
Use this example as a starting point. Copy the table into your working document and adapt its contents, owners, dates and statuses to your company. The entries are illustrative, not findings from an actual company assessment.
| Report field | Example entry | Investigation notes | Next action |
|---|---|---|---|
| Process | Branch attendance report | Identify the menu and period | Confirm the report example |
| Steps | Select the branch, then the period | Record the sequence followed | Try the steps as instructed |
| Expected result | Information matches the filters | Explain the example concerned | Check the requirement |
| Actual result | Some results do not match expectations | Include a relevant example | Investigate the difference |
| Impact | HR review delayed | State timing requirements | Coordinate priorities |
| Result of action | Complete after trying the instructions | Record results and confirmation | Close or continue |
Use the template without making reporting complicated
When an attendance report differs from expectations
A user opens a branch report for a particular period and finds information that does not match expectations. When asking for help, provide the filters, period, time of occurrence and one example of the difference. Support then has a starting point for checking the same conditions.
Users do not need to conclude that the database or integration is at fault before it has been checked. Factual notes are more useful for investigation. If steps have already been tried, explain the results so the team does not request unnecessary repetition.
Update the report until the result is confirmed
After action is taken, try the process again as instructed and report the result. Confirmation helps establish whether the user can resume work. Keep the final notes to help if a similar question comes up again.
Sigma prioritizes application quality, user experience and support until issues are resolved. Feedback from using Sigma HRIS and Forte HRIS informs regular development, so clear reports also help us understand users' needs.