Before you begin
Access to the job and its application. · Move candidate stage permission.
Work through this checklist
1. Read the transition message
Open the intended job pipeline and confirm the candidate and destination stage. Read the blocker shown by the board. A visual card movement can be reversed if the save fails.
2. Complete the stated requirement
Depending on the stage configuration, InferOwl can require a candidate email, phone, finalized resume, qualified screening, or readiness. Complete the actual requirement before trying the move again. Do not mark work complete merely to clear a blocker.
3. Provide a reason when asked
Some destination stages request a transition reason. Explain the real recruiting event that justifies the move. Cancel if you do not yet have the information needed to support it.
4. Respect the configured workflow
A pipeline can limit allowed next stages or prevent movement out of a terminal stage. Ask the workspace owner to review an unexpected rule; do not change shared rules simply to force one card through.
5. Confirm the saved state
Read the success or rollback notice. If the result is uncertain, refresh the pipeline and inspect the application’s current stage before trying another move.
If you still need help
For a persistent failure, report the job context, source and destination stages, approximate time, and exact non-sensitive error text. Do not tell teammates the stage changed until the board confirms it.
Read the complete product guide
Check the job-specific context
Confirm that you are moving the application for the intended job. The same candidate can have different progress on another requirement. Read the current stage and timeline before deciding which event justifies the move. A candidate's general interest does not prove that screening, submission, or another stage requirement is complete.
If the blocker names missing evidence, resolve the actual source record through its normal workflow. If it concerns an allowed transition, ask the workflow owner to review the intended path. These are different problems and may need different people to resolve them.
Report the result accurately
After a retry, inspect the saved stage and confirmation. If the board reverses the movement, tell the team that the application remains in its saved stage. For support, include whether the failure occurred before confirmation or after the visual move. A screenshot can help when redacted, but do not expose candidate details or unrelated pipeline cards in an initial report.
Was this guide helpful? Send feedback to the team.