Candidate screening vs candidate coordination: choosing the right workflow
Compare candidate screening and candidate coordination using the same source packet, distinct useful outputs, and a reviewable Righthand brief.
Quick answer
Use candidate screening support to organize evidence against the hiring team's stated job criteria. Use candidate coordination to arrange the approved interview process and its outstanding logistics.
The practical test is the question your reviewer needs answered. Start both workflows from the same dated input packet, then judge the usefulness of their different outputs. Righthand can help prepare either draft from owner-provided records or an approved read view; the reviewer retains authority over decisions and external actions.
Compare the same input
Use this shared packet: A restricted packet containing candidate IDs, job criteria, permitted application materials, interview stage, panel availability, and candidate-supplied scheduling preferences. Keep stable identifiers, source links, and a cutoff so another person can reproduce the comparison. Missing information stays explicitly unknown rather than becoming an invented fact.
| Workflow | Useful output | Review owner |
|---|---|---|
| Candidate screening | Evidence mapped to each criterion, unanswered questions, and human review flags | The hiring lead |
| Candidate coordination | Interview scheduling options, missing confirmations, and responsible coordinators | The hiring lead |
Greenhouse scorecards use predetermined job criteria to organize interviewer feedback in a structured hiring process. The official Greenhouse scorecards reference supports this specific distinction; the rest of the example is a suggested operating practice, not a universal provider feature or requirement.
Illustrative worked comparison
Illustratively, a candidate's application demonstrates one required skill but does not address another. Screening support marks that evidence gap for a reviewer. Coordination can still prepare panel availability for an already approved interview without interpreting the missing detail as an automatic rejection.
Evaluate both drafts against that packet before introducing more sources. Changing the input halfway through makes it difficult to tell whether the workflow or newly available evidence caused the difference. Keep assumptions next to the conclusions they affect, and make the next requested decision visible to the reviewer.
Delegation brief for both workflows
Use only the approved input packet described above, with its recorded cutoff. First, map permitted application evidence to the supplied job criteria, quoting source references and leaving unsupported criteria unknown. Separately, prepare scheduling options and a confirmation checklist for candidates whom the hiring owner has approved to advance. Use America/Los_Angeles for the review deadline and preserve the original dates and time zones. Run this comparison once and return both drafts in this conversation by Friday at 3 PM Pacific for The hiring lead to review. Include source IDs, missing inputs, assumptions, and a next step with an owner. Do not send messages, modify records, make purchases, or approve decisions. If access is unavailable or the packet contradicts itself, report that limitation before completing the affected section.
Check the result
Check that screening contains evidence rather than inferred personal traits. Confirm that scheduling options respect both candidate preferences and panel availability, with explicit time zones.
A completed draft is evidence of preparation, not evidence that its recommended action occurred. The owner should accept or revise the outputs before any separate execution request. For a recurring version, specify the next input window, review deadline, and destination rather than reusing an old snapshot silently.
Failure and recovery
A similar name can attach one person's notes to another application. Match candidate and application IDs, stop the affected section, and ask the recruiter to correct the source packet.
Keep hiring decisions with humans. Do not infer protected characteristics, rank people from irrelevant personal data, reject candidates, or contact them without explicit authority.
FAQ
Should I use both workflows?
Use both when the outputs answer distinct questions that are currently useful. Start with the smaller deliverable when review capacity is limited; preserve the shared source packet so the second can be prepared later without guessing.
Does delegation require a native integration?
An approved export or owner-prepared packet can support the first comparison. A live read or later write requires verified connection tools and the appropriate permission; a catalog entry alone does not establish either.
Use Righthand Docs for delegation and permission guidance, check available integrations, and review Pricing before expanding the task.