Period and Scope
Define the timeframe, department, or location under review. Data from different periods must be distinguished to ensure meaningful comparisons.
Review applicant numbers, selection progress, and completed hires with Sigma HRIS or Forte HRIS. Identify delays and agree on the next steps with the departments requesting staff.
The number of applications received is not enough to fully gauge recruitment success. HR must also consider selection status, unfilled requirements, and the timeframe involved. Clear reports enable the team to discuss progress based on a shared understanding.
Define the timeframe, department, or location under review. Data from different periods must be distinguished to ensure meaningful comparisons.
Agree on how applicants and applications are counted, especially when one person applies for several roles. Use the same definitions throughout the report.
Summarize candidates based on agreed status categories. Stages awaiting a decision can serve as a basis for follow up actions.
Link the report discussion to recruitment needs and actual outcomes. Clarify which positions have been filled and which are still being recruited for.
A vacancy may receive many applications while only a few candidates have received a decision. Review the current selection stages before deciding why progress is slow. The report should help the team identify pending decisions and who needs to act.
Differentiate between the number of candidates, the number of applications, and the number of positions to be filled.
Ensure that selection results and joining dates are updated before the report is prepared.
Bring examples of the reports required by HR and management to discuss during the demo.
Recruitment reports can show progress in filling positions and highlight process stages that require attention. The number of applicants alone is insufficient for assessing outcomes, as each position has unique requirements. HR needs to interpret the data alongside selection statuses, target timelines, and departmental needs. With this context, the report helps clarify which activities should be prioritized.
A useful report should help the team answer specific questions. Management may want to identify unfilled vacancies, while HR needs an overview of the stages with the most pending actions. Aggregating figures without a clear purpose can make a report difficult to use. Define recruitment reports based on the readers' needs and the decisions to be made. Companies should agree on definitions for metrics such as applicant counts, positions, and fulfillment outcomes to ensure the summary is interpreted consistently. With shared definitions, discussions can more easily focus on necessary follow up actions.
Use one recruitment period to compare the plan, selection activity, and results. Explain any changes in staffing needs during that period so changes in the figures are clear. For an open role, check whether the team is waiting for suitable candidates, a selection decision, or an agreed start date. Bring a report used by HR and management to the demo to discuss fields, grouping, and required detail. The report can then guide action with the requesting department, rather than only count applications received.
For instance, a large number of candidates may have been processed, yet key positions remain unfilled. The team needs to determine whether the bottleneck lies in candidate suitability, selection decisions, or start dates. When defining requirements for recruitment reporting tools, specify the questions HR and management aim to answer. The chosen reports should support discussions on action steps rather than merely displaying activity volumes.
Start with the questions management asks most often, such as which roles remain open or which decisions are pending. Use these questions to choose the reports you need. During the demo, check whether the detail is sufficient to explain the situation and decide what to do next. A useful report does not need to be crowded with figures. It needs to give HR and departments a shared view of hiring requirements and progress.
You can discuss your recruitment needs with the Sigma Solusi Informatika team. Sigma HRIS is available for on premises and private cloud deployment, while Forte HRIS is cloud based. The choice depends on your company's workflows and IT policies. Please prepare examples of positions or selection processes for the demo so the discussion aligns with your HR needs. Our team assists with implementation and provides ongoing support after the application is in use.
Both products serve small businesses through large enterprises. Their main distinction is how you deploy and manage the system. We help you choose based on operational needs and IT policies.

Choose Sigma HRIS for on premises deployment on your own servers or in a private cloud. Our team helps configure the application around your HR processes and IT policies.
Learn More
Choose Forte HRIS for a cloud based application. We help select modules, prepare records and guide users according to your HR requirements.
Learn MoreSigma HRIS and Forte HRIS are continuously updated to reflect user needs, including ESS, mobile applications and AI powered capabilities. Explore them in a demonstration using examples from your business.
Compare the ProductsSigma Solusi Informatika has developed HR and payroll systems for more than 10 years. Drawing on this experience, our team can map your business processes in just a few hours.
Start with the records and workflows you already use. We help prepare and migrate data and configure the application to fit your processes from the outset.
Our support team and project manager remain available after launch. We answer questions and help resolve issues so HR can keep work moving.
A single applicant can submit applications for multiple positions. Therefore, the number of individuals and the number of applications are calculated separately to avoid a misleading report.
A report summarizes process progress, while a hiring progress report compares filled positions with the approved plan.
They can differ. Reporting periods, fields, grouping, and readers should reflect each company's process and decisions.
Use consistent reporting periods and status definitions, while considering the different requirements of each role.
The report might show candidates as "pending" even though a decision has already been made. Status updates are necessary before the summary data is used.
Access is determined by job requirements. Management may require a summary, while detailed candidate information is restricted to those directly handling the process.
Tell us which tasks you want to simplify and the challenges your team faces. We are ready to demonstrate how the application works, assist with setup, and provide guidance on its use.