How the dossier engine works, in seven short steps. An interview pack for a permanent role, a booking pack for a locum one — and every claim in either shows its source.
One note per client on /clients. It holds how they interview, and now the locum side too: which portal they book through, credentialing quirks, site access, how extensions tend to go. Every pack for that client is built on it.
Paste each one, or drop a file on the box. PDF, Word or plain text, read in the browser. The tool stores nothing about the candidate.
A clock counts the seconds while it works. A minute or two, usually.
Primary
Press the button and leave the page open.
Fallback
Paste the prompt into your own Claude tab, then paste the reply back here.
The tool reads the brief and picks the shape itself. Either way, every claim is checked word for word against the CV and the client note, and the sources render beside the pack.
Locum brief
Compliance at a glance — HCPC, DBS, training — with availability, rate and the scanner matrix. Built so the client can say yes today.
Permanent brief
The case for the interview: fit, evidence, and what this client values.
Anything unverified says so.
One button, then it goes wherever the submission goes.
Enter the date and the candidate's email. A preview shows exactly what will be sent: only the note fields you ticked, never the pack.
The candidate arrives by emailed link, without an account or a password.
The role, what this client values, where to focus.
A practice session, plus one reminder the day before.
/counts shows two numbers, prep sent and prep opened. Nothing else is tracked.
Write the client note once. After that it is brief and CV in, a checked pack out, and a candidate who walks in prepared.