Simple Job Board stores jobs in one CPT and applications in another, with custom form-field values landing in postmeta against each application. Stage, source, applicant name, role link, and any screening answer all sit there as queryable values. The default admin lets a recruiter open one application at a time but offers no aggregate read on the pipeline itself.

SleekView Charts pivots application postmeta into chart inputs. A Number card surfaces total active applicants. A Donut breaks the pipeline down by stage. A Bar shows applications per role. An Area plots submissions per week. The dashboard answers the questions recruiters actually ask: how many candidates are at Phone screen right now, which role drew the most applicants this month, when did the funnel slow down?

Charts read live postmeta and refresh on save, so a stage change in the SleekView table view (or in Simple Job Board itself) immediately moves the count between stage slices. Saved dashboards per role (hiring manager, recruiter, HR ops) replace the spreadsheet exports recruiting teams currently use to track pipeline health.

Recruiting is a process measured in counts and conversions. Active applicants, applications per stage, applications per role, time at stage, source mix. Simple Job Board collects every input that math needs but offers no surface that does the math.

Recruiters end up exporting application lists to Sheets, building pivot tables by hand, and pasting screenshots into the recruiting weekly. The numbers are always one export old, and the time spent producing them is time not spent moving candidates. A charts layer that reads the same postmeta the application list reads, and turns it into KPI tiles, stage donuts, and weekly volume trends, makes pipeline reporting a passive output of the system rather than a manual task.

Hiring managers see their own roles. HR ops sees the board. The data refresh happens on save.