InferOwlInferOwl
overview

Start here: your first recruiting workflow

Use this ordered reading path to set up your account, review candidate and job records, and learn the steps for pipeline work and client submission.

Recruiter, ManagerVerified September 9, 2026
Browse documentation

Start with a task assigned by your manager and practice with approved sample records. This path links to the existing product guides. Each guide explains the access and prerequisites for its own task.

1. Set up your account

Follow Set up your recruiter workspace. Then read Navigate InferOwl by role to understand why your navigation or actions may differ from a teammate's. Ask the workspace owner to review missing access.

2. Review the person and the requirement

Read Create a candidate record and Create a job. Check for existing records before creating new ones. Review extracted resume information against its source and keep incomplete requirements in draft.

3. Review possible matches

Use Match candidates to jobs to understand the available matching workflow. Confirm the candidate's actual interests and the job requirements before taking the next step. A match does not establish consent, readiness, or a client decision.

4. Track the work against the job

Follow Move candidates through a job pipeline. Choose stages that reflect completed work. If the board blocks or reverses a move, read the message, complete the actual requirement, and confirm the saved state.

5. Prepare for client review

Read Create and track submittals when the candidate is ready and authorized for submission. Complete any required package and record the real client or candidate outcome when it occurs.

Check your understanding

You should be able to identify the candidate, the job, the current application stage, the evidence supporting it, and the person responsible for the next action. If a term is unfamiliar, use the glossary. If a specific task fails, search the help centre for that task and its error.

Practice with one connected example

Use a manager-approved sample candidate and job throughout the path. For example, Maya Rao and the Night-shift registered nurse role at Cedar Hospital are fictional practice records. Keep the sample label visible and avoid contacting real people while learning the workflow. The purpose is to understand how the records and review steps relate.

Start by identifying what the sample source actually says. Maya may express interest while leaving a start date unconfirmed. The candidate record can capture the information supported by that source, while the job record describes the approved requirement. Keep unanswered questions explicit as you move between the guides.

Check each handoff before continuing

After candidate creation, reopen the record and compare it with the sample source. After job preparation, confirm the title, location, status, and requirements. When reviewing matches, read the evidence and unknowns rather than treating the score as a completed assessment. These checks establish whether the next step has reliable inputs.

Before moving an application, explain which real or simulated event justifies the destination stage. If a requirement is missing, complete the appropriate source record or stop the practice at that point. Do not invent a completed screening, document review, or candidate response to make the exercise advance.

The candidate is the person. The job is the requirement. The application connects that person to that job, and the pipeline stage describes progress within that process. A submittal supports the client-review workflow. A list can organize attention, while a task identifies work still to do.

If these distinctions become unclear, open the glossary before changing shared state. A candidate can be considered for several jobs, so an outcome on one application should not be treated as the person's status for every opportunity. Ask your manager how the agency records those separate situations.

Review the exercise with your manager

At the end, show the source, candidate, job, and current application state. Explain what was saved and what remains unconfirmed. Identify the next action and its owner. If a step failed, describe the error and what you checked before retrying, rather than recreating records until the screen looks complete.

Use the task-specific help article for recovery and keep the sample records in the agency's approved practice process. Once your manager confirms the workflow and your access, apply the same evidence and saved-result checks to authorized live work. Continue with the communication, document, or submittal guide that matches the next assigned task.