Individual AI tasks are easy to demonstrate and easy to abandon. What makes a difference is whether the output of one step is the input to the next, so nothing has to be re-entered and nothing depends on remembering.
Here is the loop we run in Creo Access, described so you can follow the shape of it with other tools if you prefer.
The workflow
- 1. RoleStructured context, approved by you
- 2. ConversationsIntakes, screens and debriefs captured
- 3. EvidenceMaterial read against requirements
Step 1: Build the Role, once
Input: whatever the client sent, plus your intake call. Output: outcomes, must-haves with reasons, preferences, client context and the questions still open. In Creo Access, Creo Align proposes that structure and your approved version becomes Creo Role Memory.
Your decision: which requirements are real. This is the step that determines the quality of everything after it, and the one most often rushed. Detail in turning a messy brief into a recruiter-ready Role.
A job description turned into outcomes and questions
Select an output to see the wording in the description it came from.
Each search starts as a Role, and the Role carries the context every later step reads from.
Read this figure as text
- Outcome: Outcomes the hire is being made for. Job description, paragraph 2, Own the migration of our settlement platform off the legacy stack this year.
- Established: Requirements, split by how firmly they are stated. Job description, requirements, Must have run production Go services at scale.
- Gap: What the description never says. Missing, Team size, on-call expectation, and who this role reports to.
- Intake question: Questions to take back to the client. Question, Who does this role report to, and does that change after the migration?
- Evidence to seek: What to look for in the material. Requirement, Production Go at scale.
Step 2: Turn conversations into work
Input: notes, a pasted transcript or an uploaded recording from a screen, client intake or debrief. Output: notes worth keeping, evidence captured against requirements, gaps, and proposed next actions. That is Creo Capture.
Your decision: what to accept. Capture proposes, you approve, and only approved items enter the search. More in turning call notes into useful admin.
Step 3: Read the candidate's material against the Role
Input: pasted CV text or an uploaded PDF or DOCX, plus any captured conversations. Output: each requirement classified as evidenced, partly evidenced, claimed or not established, with the source lines, conflicts and questions worth asking. That is Creo Evidence.
Your decision: everything that matters. There is no score, no ranking and no reject action. The reasoning is in assessing candidate evidence without letting AI rank candidates.
Step 4: Close the gaps
Input: the questions the evidence left open. Output: next actions attached to the Role, the candidate and the conversation that raised them, in Creo Actions and visible in Today. Where the action is a piece of writing, "Do it with Creo" drafts it from context already recorded.
Your decision: what is worth chasing before submission and what can wait. See recruitment follow-ups.
Step 5: Write the submission
Input: the evidence you reviewed. Output: a client-facing candidate submission that states what is established, what is not, the practicalities and your recommended next step, with internal citation markers stripped for the client version.
Your decision: the recommendation, and the commercial position. Detail in writing candidate submissions clients can trust.
Step 6: Keep the search coherent
Input: everything above. Output: a Role whose context is current, a set of actions with their reasons intact, and a history of how the search changed. Ask Creo answers questions against that state without you pasting the brief again.
What this workflow does not include
- Sourcing from a candidate database. Creo Access has no candidate database and does not scrape LinkedIn.
- Sending anything. No outreach sending, no email, no calendar.
- Joining your calls. You bring notes, a transcript or a recording.
- Replacing your ATS. There is no write-back; Capture produces notes you paste.
- Deciding anything about a candidate. No scores, no rankings, no automatic rejections.
That list is deliberate rather than a roadmap gap. The workflow above is the part of recruitment where context is repeatedly lost, and closing that loop is enough work for one product.
Run the loop
Take one live search from brief to submission
Build the Role, capture a call, map a candidate and export the submission. Start free for 14 days. Then choose monthly or annual billing. Cancel anytime.
Start 14-day free trial