FAQ: Why don’t all my jobs appear?

The Jobs page shows a view, not always the organization total

A Jobs count is based on the filters and view currently active on your screen. It may be smaller than the total number of jobs stored for your organization without any records being lost.

The most common explanation is that the list is showing a focused working set, such as active jobs assigned to one recruiter, instead of every job in the organization.

Status and ownership can change the count

Status filters can exclude paused, filled, or closed jobs. A recruiter filter can exclude jobs assigned to another teammate or jobs that have not been assigned yet. Search, location, job type, department, and priority filters can narrow the list further.

For example, an organization might have 19 jobs in total: 12 active jobs assigned to the current recruiter, 6 active jobs waiting for assignment, and 1 job that is paused. An Active plus Recruiter filter would correctly show 12.

• Active jobs may be the only statuses included in the current view
• Unassigned jobs do not appear when a specific recruiter is selected
• Paused, filled, and closed jobs may be outside an active workflow view

How to find the jobs you expect

Open Filters on the Jobs page and review each active filter chip. Clear Recruiter and Job Title filters, remove location or department constraints, and choose the status option that includes the workflow stages you want to review.

If the page restores a saved or in-session view, switch back to the default view or clear that working state before comparing the number with an organization-wide total.

• Clear the Recruiter filter to include jobs owned by teammates and jobs awaiting assignment
• Include paused or terminal statuses when you need a complete operational review
• Check the Jobs page again after clearing search, location, type, department, and priority filters

When to ask for help

If a job still does not appear after you clear the filters and review all statuses, note the job title, company, and expected owner before contacting your administrator or RecruitIQ support. That gives the team enough context to compare the job record with the list view safely.

A difference caused by a filter is expected behavior. A job that remains absent from every unfiltered status view is the case that needs investigation.