Move candidates through a job pipeline

The job pipeline groups applications by stage. Cards show the candidate, specialty, match score when available, assigned recruiter, next suggested action, and last update. Moving a card updates the shared application state rather than creating a separate copy.

Terminal and restricted stages

A stage can enforce specific next stages, require a reason, or be terminal. InferOwl checks the move before saving it. Do not describe a failed move as complete until the board confirms synchronization.

Identify the application you are changing

The same candidate can be considered for more than one job. Open the intended job pipeline and confirm the candidate before moving a card. A stage describes the application in that job's process. It should not be used as a general statement about the person's availability for every opportunity.

Read the timeline and the current stage before choosing a destination. If another recruiter owns the next action, confirm the handoff with them. Reordering a card within a stage changes shared board order, so use it consistently with the team's working practice rather than treating the board as a private to-do list.

Match the stage to an event that occurred

Choose the stage that reflects completed work. A candidate being ready for a screening call does not mean screening is complete. Likewise, preparing a client package does not establish that the client has received it. Ask the workflow owner how the agency defines a stage when its meaning is unclear.

For a fictional example, Maya Rao is interested in the Night-shift registered nurse job at Cedar Hospital, but her start date remains unanswered. The recruiter should resolve that question through the appropriate communication workflow before recording a stage whose requirements depend on confirmed availability. The board movement does not resolve the underlying uncertainty.

Handle preflight requirements directly

Read each requirement returned by the move. If an email address, phone number, resume, screening result, or readiness item is missing, complete the actual record through its proper workflow. A note saying the requirement is complete is not a substitute for the required information. Supply a transition reason when requested and make it specific to the event.

If the proposed transition is restricted or the current stage is terminal, ask the workflow owner to review the intended action. Do not use a different candidate record or a misleading stage to work around the restriction. Changes to the agency's pipeline configuration require their own authorized review.

Verify the board after a move

Wait for the result and check the destination stage. If a move fails or is reversed, use the current saved state as the basis for your next action. Refresh when needed to confirm the server's result, particularly if a connection problem interrupted the response. Avoid repeating a move simply because the first visual change was brief.

After a successful transition, review the related timeline and next work item when relevant to the handoff. Report a persistent problem with the job reference, attempted source and destination stages, visible message, and approximate time. The pipeline help article provides a shorter recovery checklist for a blocked move.