HR
Recruitment
Reports

Recruitment Reports

Recruitment Reports is the reporting view of the Recruit module. It reads the data already captured by your job postings, applications, interviews and offer letters, so you can review hiring activity in one place instead of opening each job record individually.

Who can use it

Access follows your PMSuite role and the permission matrix in Settings → Roles & Permissions. Users whose role grants the Recruit module and its reports will find the report in the sidebar; users without that permission will not see it at all.

If a colleague reports a missing report or missing rows, check Roles & Permissions first, then have them log out and back in — permission changes do not always apply to an already-active session.

Prerequisites

  • The Recruit module must be enabled for the relevant user type in Settings → Module Settings (modules are toggled on or off independently for Admin, Employee and Client).
  • Recruitment data must already exist. The report reflects records created elsewhere in the module:

How to Access

Navigation: Sidebar → Recruitment → Reports

Direct URL: /account/recruit-job-report

Related Recruit screens sit alongside it in the same menu: Dashboard (/account/recruit-dashboard), Jobs, Job Applications, Interview Schedule, Offer Letters, Skills (/account/job-skills) and Candidate Database (/account/candidate-database).

Steps

  1. Open the sidebar and expand Recruitment.
  2. Click Reports (or go straight to /account/recruit-job-report).
  3. Use the on-screen filters to narrow the report to the jobs and period you want to review.
  4. Read the results against your open roles — the report is built from the pipeline stages recorded on each application.
  5. To act on anything you find, open the underlying record: a job in Jobs, an applicant in Job Applications, a scheduled round in Interview Schedule, or a pending offer in Offer Letters.

Understanding the pipeline behind the numbers

Reporting is driven by the recruitment pipeline stages that applications move through:

applied → screening → phone_screen → interview_round_1 → interview_round_2 → assessment → offer → hired

An application can also end in rejected, withdrawn, or be parked as on_hold. Where candidates concentrate across these stages is what the report is showing you — so keeping stages up to date on the Applications screen is what keeps the report accurate.

Where the source values come from

Candidate Source values come from the Source tab in Settings → Recruit Settings. If a source is missing or mislabelled in the report, correct it there rather than on the report screen.

Effect on other features

  • Recruit Dashboard (/account/recruit-dashboard) — the module's at-a-glance view, drawn from the same recruitment records.
  • Job Applications — changing an application's pipeline stage changes what the report shows; the report is a read view, not an editing surface.
  • Recruit Settings — the Source, Job Application Status and Recruiter tabs define the categories the report groups by.
  • Career Page — applications arriving through the public career site (enabled by the Enable Career Site toggle in Recruit Settings) feed the same data set as manually added ones.

Limitations

  • The report only reflects what has been recorded. Interviews held informally, or candidates never entered as applications, will not appear. Workaround: add the person to the Candidate Database and attach them to the relevant job so the activity is captured.
  • Stage-based figures are only as current as the pipeline. If recruiters leave applications sitting in an old stage, the report will misrepresent progress. Workaround: make stage updates part of the interview-day routine, and review the Applications list before each hiring meeting.
  • The report does not change any records. You cannot advance, reject or reassign a candidate from it. Workaround: open the candidate in Job Applications and act there, then reload the report.
  • Recruitment reporting is scoped to the Recruit module. It does not merge with HR reports such as Attendance Report (/account/attendance-report) or Leave Report. Workaround: run those separately from the HR menu and combine the results outside PMSuite.

Troubleshooting

  • "Reports" is not in my Recruitment menu. Check that the Recruit module is enabled for your user type in Settings → Module Settings, then check your role in Settings → Roles & Permissions. Log out and back in after any permission change.
  • The report is empty. Confirm that jobs and applications exist for the period and filters you selected; widen the date range or clear the filters and retry.
  • A job is missing from the report. Open /account/jobs and check the posting's status and start/end dates — a job outside the selected period will not be included.
  • A candidate's source is blank or wrong. Sources are defined in Settings → Recruit Settings → Source and set on the application record; fix it there and reload.
  • Counts disagree with what a recruiter expects. Compare against the Applications list for the same job — the report follows the recorded pipeline stage, so an un-updated application is the usual cause.

Related Articles

Offer LettersSettings