Create scorecard

Id of the interview kit this scorecard is filled out against. Must belong to the same job as the application_id.

Id of the Greenhouse user this scorecard is assigned to (the interviewer being scored against).

Timestamp the interview took place, in ISO 8601. Used to compute time-to-submit and to align the scorecard with the interview slot.

Free-text "key takeaways" the interviewer is recording (pros, cons, follow-ups). Plain text; @-mentions are accepted and stored alongside the rendered names.

Overall recommendation for the candidate. One of strong_no ("Definitely Not"), no, yes, strong_yes, or no_decision. Pass no_decision to submit the scorecard without picking a recommendation.

Free-text private notes; only users with the "see private notes" permission can read these back.

Initial lifecycle status. Send draft to create an in-progress scorecard, or complete to submit it immediately — sending complete also stamps submitted_at.

Free-text "note to other interviewers" shared with the rest of the hiring team.

Id of the application the scorecard belongs to. The application's job must own the supplied interview_kit_id.

Id of the user submitting the scorecard. Usually matches interviewer_id; set differently when an admin is filing the scorecard on the interviewer's behalf.

Id of the interview kit this scorecard was filled out against. The kit determines the questions, focus attributes, and rating scale on the scorecard. The kit also identifies which interview slot on the job's interview plan produced this scorecard.

Id of the Greenhouse user who participated in the interview and to whom this scorecard is assigned. Each interviewer on a multi-interviewer interview gets their own scorecard.

Timestamp the interview took place, in ISO 8601. Mirrors the underlying interview's scheduled time and is set when the scorecard is created (manual scorecards may set this independently).

Free-text "key takeaways" the interviewer recorded on the scorecard (pros, cons, follow-ups). Plain text with @-mentions rendered as user names; use notes_with_tags for the version where mentions are tagged for downstream parsing.

notes with @-mentions rendered as embedded user tags (e.g. @[User Name](user:123)) instead of plain user names, for partners that need to resolve mentioned users.

Id of the Greenhouse user who actually submitted the scorecard. Usually the same as interviewer_id, but differs when an admin submits a scorecard on another interviewer's behalf.

Interviewer's overall recommendation on whether the candidate passed the interview. One of strong_no ("Definitely Not" in the UI), no, yes, strong_yes, or no_decision. no_decision is recorded when the interviewer submitted the scorecard without choosing a recommendation.

Free-text private notes visible only to users with the "see private notes" permission. Plain text with @-mentions rendered as user names; use private_notes_with_tags for the tagged version.

private_notes with @-mentions rendered as embedded user tags instead of plain user names.

Lifecycle status of the scorecard. draft is in-progress and not yet submitted; complete is submitted (and submitted_at is set). Only complete scorecards count toward interview completion and downstream analysis.

Free-text "note to other interviewers" the interviewer leaves for the rest of the hiring team. Plain text with @-mentions rendered as user names; use public_notes_with_tags for the tagged version.

public_notes with @-mentions rendered as embedded user tags instead of plain user names.

Id of the application this scorecard belongs to. Use it to look up the candidate via the applications endpoint.

Timestamp the scorecard was submitted (moved from draft to complete), in ISO 8601. null while status is draft. The delta between interviewed_at and submitted_at is a common "time to submit scorecard" measure.