Moving candidates through stages

How candidate movement works in CVViZ

Candidate stages in CVViZ change via a status dropdown form, not a kanban board. The candidate list is presented as a table; the "Stage" / "Status" column shows where each candidate is, and you change status via a dedicated form.

This is a deliberate design — drag-and-drop kanban hides important fields like remarks, reasons, and salary that CVViZ captures on the same form.

Changing one candidate's status

1. Open the candidate (from a job's candidates tab or from the Candidate Database).
2. Click Change Candidate Status in the actions area, or use the status indicator in the header.
3. Pick a new status from the dropdown (populated from the master stage catalog).
4. Optionally fill any contextual fields (see below).
5. Click Update Status.

Behind the scenes the action calls and the change lands on the candidate's timeline.

Bulk status change

1. From a job's candidates list, tick multiple candidates.
2. Click Change Candidate Status in the bulk actions bar.
3. Same form, applied to every selected candidate.

The bulk path uses.

Status filter

The job's candidates view has a left sidebar with a stage filter (currentStage). Click any stage to filter the list to candidates in that stage. The default is "all_candidates".

Optional fields on the status change form

Different statuses surface different fields:

Job Offered (status codes 60, 61, 62)

• Final Salary Offered — numeric value.
• Currency — picker.

Any status

• Reason — when status-change reasons are configured for the target status. Shown viafiltered by progress_id.
• Remarks — rich-text editor with bold, italic, underline, and link formatting. Captures context for the status change.

Disposition events

Behind the scenes, status changes can trigger disposition events — used by automations to send emails, notify users, etc.

Sub-stages

Many status codes have sub-statuses via. For example, "Interviewed" includes sub-stages like 1st Interview Invited / Accepted / Scheduled / Passed. Pick the specific sub-stage that matches reality — it makes pipeline reports more useful.

Reverting a status change

Status changes are recorded on the timeline. To revert, just open the status form again and pick the previous status. The history of all changes is preserved.

Why no kanban?

• Required context — reasons, remarks, salary, and disposition info are part of every move. A drag in a kanban hides those.
• Bulk-friendly — moving 50 candidates is one form fill in CVViZ; in a kanban it's 50 drags.
• Mobile-friendly — the form view works just as well on a phone, where kanban-style drag-and-drop is awkward.

Tips

• Use the Reason field consistently. It's the foundation of pipeline drop-off reporting.
• Don't skip Remarks on rejections — even a one-liner pays off when you revisit the candidate later.
• Bulk-move at the end of a screening pass rather than one-by-one — faster and the timeline reads cleanly.