Turns a job description and your intake notes into must-haves, nice-to-haves and disqualifiers, asks about anything unclear, and keeps every version. You approve the blueprint before a search runs.
One says Secret, the other says TS/SCI. The search runs on whichever the recruiter read last, and the client turns down the shortlist for a requirement nobody wrote down.
46%
of recruiters report difficulty telling essential skills and experience from non-critical criteria when working with hiring managers.
The job description, your intake notes and the client's rules, if there are any.
ANDY sorts must-haves, nice-to-haves and disqualifiers using your industry pack, flags where the documents disagree, and asks up to five questions.
Edit any criterion, then approve. A search can't run on a blueprint nobody approved.
Every edit is a new version. The approved one stays in force until you approve the next, and old versions are kept.
Request: Draft a blueprint for the ASR III req in Lorton from the job description and my intake notes.
In this pack SAP means Special Access Program, never the ERP software.
Request: Draft a blueprint for the desktop support req at Harbor & Vine LLP.
Pay comes only from the range you enter on the requisition.
Fictional example. Role Blueprint works this way in ANDY today.
Each blueprint version, before a search can use it.
Every version, who saved it and who approved it, and the model and prompt version that drafted it.
Nothing this agent does leaves ANDY on its own, so there is no autonomy setting to change.
How approval works