Product · August 17, 2026
Open job pipelines with the right workflow already prepared
RecruitIQ now prepares an organization’s candidate workflow before a job pipeline opens, avoiding a brief swap from default stages to the team’s saved stages.
Prepare the team workflow before showing columns
RecruitIQ now loads the organization’s saved candidate workflow as shared session data. The dashboard prepares it in the background, and opening or approaching Jobs can warm the same data before a job pipeline is shown.
A job pipeline waits for its candidate data and saved workflow before displaying columns. Teams with customized stage names, order, or colors should therefore see the correct workflow on the first painted pipeline instead of briefly seeing RecruitIQ’s default stages.
One current workflow across recruiting surfaces
Jobs, job details, the Candidate Workflow editor, and the dashboard workflow card now read the same user-scoped workflow cache. Repeated background, hover, focus, touch, and page requests reuse work that is already running or still fresh.
When an owner saves workflow changes, RecruitIQ updates that shared copy immediately so the next pipeline uses the saved stages without waiting for an older cache entry to expire.
Safe loading and fallback behavior
A direct first visit can still show a normal candidate-loading state while RecruitIQ retrieves the workflow. If the workflow request fails, the existing default pipeline remains available as a fallback rather than blocking the job completely.
This change does not alter candidate stages, move candidates, or create a separate workflow for an individual job. The saved organization workflow remains the source of truth.