Skip to main content
Who this is for: Talent acquisition leaders, recruiting managers and program owners: the people who decide how hiring runs, not just who gets hired. Most of this page needs the Manage Job Req Settings and Company Dashboard Access permissions, and some of it needs Company Settings Access. Ask your Journeyfront admin if a page or tab below isn’t there.
Hiring in Journeyfront runs in three phases, and they happen in order: you set up a job req, you bring candidates to it, and then you manage the hiring that follows. This page follows that order, so you can read it start to finish the first time you build a role and come back to one section later.

Your first week

1

Learn the model

A job req is a role, not an opening; hiring classes are the waves you fill it with; a workflow is the path candidates follow. Start with How the pieces fit together below, then see the Job reqs overview.
2

Audit your job reqs

Open Job Reqs and check what’s Active, Inactive, Closed or Archived. Close what you’re no longer hiring for so your dashboards aren’t counting dead reqs. See Job req statuses.
3

Read one workflow end to end

Pick your highest-volume job req, open Setup, then Workflow, and follow it from START to HIRED. Note every step a candidate waits on a person. See Workflows overview.
4

List the automation you already have

On the same page, the purple bars with a lightning bolt are your automation rules. Know which ones move, message or assign candidates before you change anything. See Automation rules.
5

Set your baseline numbers

Click Dashboard and open Funnel Analytics and Time To Hire. Write down today’s drop-off and time to hire so you can tell whether your changes helped. See Dashboards overview.
6

Check who can do what

Review your security roles and who holds them, especially Manage Job Req Settings, Hire Candidates and All Job Req Access. See Security roles and permissions.

How the pieces fit together

Job profiles, job reqs, job postings, job boards and referral portals each do one job, and their names are close enough to blur together. The short version: a job profile is a role your employees hold, a job req is a role you’re hiring for, a job posting is the public ad for that req, and a job board or referral portal is where the ad is seen. Every applicant, from every channel, lands back in the same job req. Click any box below to see what it is, where it lives and what it connects to. For each relationship on its own, with examples and the cardinality spelled out, see How the pieces connect.

Phase 1: Set up a Job Reqs

Create the job req in Job Reqs, then work down the Setup menu from top to bottom. Each page is one decision, and the menu is already in a sensible order: what the role is, what you ask candidates, what you measure, how they move, who does the work, and where the job is advertised.
1

Details

The role itself: Job Req Name for your team, External Job Title for candidates, the Linked to Job Profile the hires land in, and the description, location and employment type. See Create a job req.
2

Application Form

What candidates fill in when they apply, including whether a resume or LinkedIn profile is required. Every field here is a field you can later filter and report on, so ask for what you’ll use. See Application form.
3

Attributes

The traits and skills this role is measured on. Do this before the workflow: activities score against these attributes, so settling them first means your screening, assessments and interviews all measure the same things. See Attributes.
4

Workflow

The steps candidates move through, the activities inside each step, and the automation rules that move them. Every new job req starts with a draft, Workflow 1.0, which you reshape to your process. Interview activities are set up here too: the interviewers, the length and what goes on the calendar invite. See Workflows overview, Build a workflow and Set up an interview activity.
5

Team

The recruiters, hiring managers and interviewers who work on this job req, and what each of them can do on it. Anyone who interviews also needs their own calendar connected and their hours set, under Interviews, then My Profile and My Availability. See Hiring team and Your availability and calendar.
6

Job Postings

The public ad: the title candidates search for, the location, the pay and the description. One job req can have many postings, each linked to one job board, and you send a posting out to Indeed, JobTarget or Appcast from the posting itself. See Job postings.
7

Configurations

Five cards of per-req settings: Candidate Assignment (who owns each candidate), Interviews (including interview reminders), Referrals (which portals list this job and what a referral earns), Candidate Experience and Scoring & Reporting. See Job settings.
8

AI Resume Scoring

Where it’s turned on for your account, score resumes against what the role needs. See AI resume scoring.
9

AI Agents

Where it’s turned on, let an agent handle parts of the candidate conversation inside the workflow. See AI agents.
10

Publish and activate

A new job req starts Inactive and can’t take applications. Publish the workflow, or use Actions, then Activate, when the rest is ready. See Publish workflow changes and Job req statuses.
There’s no Interview Scheduling page in the Setup menu. Scheduling is set in three places instead: the interview activity in the Workflow (interviewers, length, calendar invite), Interview Reminders on the Configurations page, and each interviewer’s own calendar and hours under Interviews. See Set up an interview activity and Interview reminders.
Write your scoring criteria before your questions. When every attribute says plainly what a weak, average and strong answer sounds like, interviewers score the same candidate the same way, and your Attributes and Interview Questions dashboards start telling you something real. See Interview guides.
Standardize once, then duplicate. Get one job req right, all the way down the Setup menu, and use Actions, then Duplicate Job Req for the next site, shift or client. Postings aren’t copied, so create those on the copy. See Create a job req.

Workflow and automation in more depth

The workflow is your process, written down and enforced. Changes land in a draft and only reach candidates when you publish, so you can rework a process without disturbing the people already in it.
Candidates already in progress stay on the workflow version they started with. If you need a change to reach people mid-process, plan to move them yourself, or with an automation rule, rather than assuming the new version catches them.
Put your quickest, most decisive activities first. Short screening questions before a long assessment means candidates who aren’t a fit find out fast, and the ones who are don’t burn time on steps they don’t need.

Phase 2: Bring candidates in

With the job req live, the job is getting the right people to it and recording where each one came from. Tag every channel as you go: the source is what later tells you which spending was worth it.
Make a separate source link for every placement, not every channel. “Facebook” tells you little; “Facebook - Tampa Night Shift - Nov” tells you which creative and which market to repeat. Hand this part to your sourcing team with Getting started for sourcing teams.

Phase 3: Manage the hiring

Setup is done and candidates are arriving. From here your job is filling the classes, watching the funnel and keeping work from sitting still.

Hiring classes

A hiring class is a wave of hires from one job req, usually one per start date, with its own openings. A job req can have as many classes as you need, which is how one req fills wave after wave without ever being recreated.
Hiring the same role again next month? Add a hiring class to the job req you already have instead of creating a new one. Your workflow, postings, dashboards and candidate history stay in one place, and your reporting stays comparable year over year.

Dashboards

Company dashboards cover every job req; a job req’s own Dashboard tab covers one. See Dashboards overview for what each one holds, how to filter it and how to save your filters as bookmarks, and Job req dashboards for one req at a time.
Save a bookmark for the filters you check every week, and make it the default on that dashboard. Then your Monday number is the same number every Monday.
The Turnover, Performance, Attributes, Interview Questions and Interviewers dashboards only show something once your employee data is in Journeyfront: start dates, separations and performance reviews. Getting that feed in place is what turns hiring reporting into outcome reporting. See Turnover and performance.
Review the funnel and the process together. When Funnel Analytics shows a step bleeding candidates, open that step in the workflow before you change the ad spend: a long assessment, a slow hand-off or a missing reminder explains more drop-off than the source usually does.

Saved views

A saved view is a set of filters on the Candidates or Job Reqs page that you can come back to, make your default and share with your team. Views are how a leader turns “keep an eye on things” into something checkable in a minute. See Saved views, and Export data when you need the list in a spreadsheet.

Keep the job req list honest

Close or archive the job reqs you’re no longer hiring for, so your dashboards stop counting them, and use a req’s Activity tab when something changes behaviour unexpectedly: it records who changed the workflow, the steps and the activities, and when. See Job req statuses and Job reqs overview.

FAQ

Anyone with Manage Job Req Settings can edit and publish a job req’s workflow. Keep that list short, and use the job req’s Activity tab to see who changed what. See Security roles and permissions.
They don’t all count on the same date. Most use the application date, but others use the hire, start, interview or test date. Match the date range and the filters before comparing. See Dashboards overview.
Five, if the workflow, location or client really differs; one, with a hiring class per wave, if the process is the same. Separate reqs are easier to report on by location, but every change has to be made five times.
Build it as a draft on one job req, publish it there, watch Funnel Analytics and Hiring Process Fidelity for a couple of weeks, then copy it to the rest. See Publish workflow changes.
In three places, not one. The interview activity in the Workflow holds the interviewers, the length and the calendar invite; Interview Reminders on the Configurations page decides when candidates are reminded; and each interviewer connects their own calendar and sets their hours under Interviews. See Set up an interview activity, Interview reminders and Your availability and calendar.
New job reqs start Inactive. Publish the workflow, or click Actions, then Activate, when you’re ready. Check the posting too: both Make job posting page active and Post job to job board have to be on. See Job req statuses and Job postings.
Yes. Their Candidate Application’s Comments & Activities tab holds their history, and the job req’s Activity tab holds changes to the process itself.
Send recruiters to Getting started for recruiters, hiring managers and interviewers to Getting started for hiring managers, your sourcing team to Getting started for sourcing teams, and whoever handles new-hire paperwork to Getting started for onboarding teams.

Admin setup checklist

Everything to put in place before candidates flow.

Workflows overview

Steps, activities, automation and versions.

Dashboards overview

Find the dashboard that answers your question.

How scoring works

What the scores behind your decisions mean.