A companion reads them wherever they arrived, creates each candidate on the right job, comments what it found, and proposes the stage moves as one batch.
The CVs did not arrive through the careers page. A hiring manager’s inbox, a referral thread, an agency that sends PDFs twenty at a time, and a Google Form somebody built in a hurry. Sixty candidates in a shape nobody can filter.
A companion reads all sixty. It opens each attachment, checks Workable by email so an agency resend does not become a duplicate, creates each person on the right job, and posts a comment with what it found. Stage moves arrive as one batch, with a reason on every name.
01
From attachment to pipeline in one pass
The companion starts where the CVs actually are: a Gmail label or a shared folder.
It opens each attachment, pulls the real fields, then checks Workable by email for someone who already exists. Jobs are addressed by shortcode, so it lists them and matches by name.
Then it creates each candidate on the right job and posts a comment carrying what it found: the two relevant projects, the link it checked, the thing on the CV that does not add up. You see the batch before it lands.
02
What does moving a candidate a stage cost?
A stage move is visible to your whole team and can fire whatever your account has configured on transitions. A move into a hired stage can need requisition details a companion will not invent. So it proposes the moves as a batch, with a reason on each.
You approve fourteen moves in one screen with the evidence beside every name, instead of clicking through fourteen profiles to reconstruct why you liked them last Tuesday.
03
How do I screen sixty CVs without missing anyone?
Ask for evidence rather than a verdict.
“Find every applicant who has shipped a mobile app, and show me the line where they said so” gets you a pile you can act on.
A companion reads all sixty, quotes the proof, and puts the ones it could not verify in their own list. That second list is where career-changers sit, and it is the one worth reading yourself. The recruiting use case runs the same split across sourcing and screening.
04
Friday: the pipeline note that writes itself
Late Friday, a companion lists the candidates on each job by stage, spots who has been sitting in Phone Screen since the 3rd, and posts a comment on the profiles that need a decision, after showing you the summary with the names in it.
Run weekly as a routine, that is a pipeline you review instead of one you meant to review. The mechanics are in operations. Comments in Workable are read by colleagues, so they are written for colleagues.
A companion reads CVs from your inbox or a folder, checks for an existing candidate by email, and creates the profile on the right job. It shows you the batch first, because candidate creation is visible to your team the moment it happens.
Yes, and this is one of the few applicant tracking integrations where that is true. The companion reads the actual stages configured on the job and proposes moves with reasons; you approve them. Moves into a hired stage may need requisition details only a person can supply.
Workable is a native integration. Reads cover jobs, candidates, the candidates on a specific job, pipeline stages and account members. Writes cover creating a candidate, posting a comment, and moving a candidate to another stage, each behind an approval step.
Ask for evidence rather than a verdict: every applicant who has shipped the thing you care about, with the line from their CV or portfolio that proves it, and a separate list of the ones the companion could not verify. Read that second list yourself.
A companion proposes it with the reason attached, and the decision waits for your explicit approval, because a rejection is something a person finds out about.
Workable Strawberry