Build · Create · Ops & Automation

Reference-check call script and scorecard

A structured reference-check script with a confidentiality preamble, probing questions, and a numeric endorsement scorecard.

You receive: A JSON object: { candidate_label, role_title, confidentiality_preamble_field, relationship_question_field, questions[] (each {prompt, probes_for enum: strengths-weaknesses|reliability|open-mindedness|collaboration|other, followup_field}), endorsement_capture {scale_min, scale_max, why_required bool}, scorecard_fields {summary, recommendation enum: strong-yes|yes|reservations|no} }.

Part of Lead Team

Opens soon

Cost20 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

This objective is verified and ready. It opens soon, once sign-in and payments are live.

Deliverable interface

The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.

{
 "buyerParamKeys": [
  "required_probe_areas"
 ],
 "checkNames": [
  "format_parses",
  "preamble_present",
  "relationship_first",
  "question_count",
  "probe_enum",
  "endorsement_scale",
  "recommendation_enum",
  "probe_coverage"
 ],
 "constants": {},
 "deliverableLabel": "reference_check_script",
 "documentKeys": [
  "confidentiality_preamble_field",
  "endorsement_capture",
  "probes_for",
  "questions",
  "recommendation",
  "relationship_question_field",
  "scale_max",
  "scale_min",
  "scorecard_fields",
  "why_required"
 ],
 "enumLiterals": [
  [
   "strengths-weaknesses",
   "reliability",
   "open-mindedness",
   "collaboration",
   "other"
  ],
  [
   "strong-yes",
   "yes",
   "reservations",
   "no"
  ]
 ],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}

Get early access to STUD the day it goes live.