Most candidate submissions are advocacy documents. Strong communicator, excellent cultural fit, hit the ground running. Hiring managers have read a thousand of them and discount the adjectives automatically, which means the recruiter's actual assessment arrives at zero credibility and the CV does the work instead.
The submissions that change a client's behavior do something different. They say what the evidence shows, name what it does not, and let the reader see the difference.
What should a candidate submission contain?
Five parts. Anything else is padding.
The five parts of a usable submission
- Why this person, for this role: two or three sentences tied to the outcomes the client described, not to the job title.
- Evidence against the must-haves: one line per requirement, with the specific work that supports it.
- What is not established yet: the requirements the material and the screen have not settled, stated plainly.
- Practicalities: availability, notice, location and expectations, in the candidate's own terms.
- The next step you are recommending, and what you need from the client to make it happen.
The third part is the one recruiters resist and clients value most. Naming a gap before the client finds it converts a potential objection into evidence that you read the material properly.
The difference in practice
| Requirement | Advocacy version | Evidence version |
|---|---|---|
| Production Python at scale | Excellent Python engineer with strong production experience. | Built and ran payment APIs in Python handling 4,000 requests per second at Northwind, 2022 to 2026. |
| Team leadership | A natural leader who mentors well. | Mentored two junior engineers at Harlow & Reed. No line management described; worth testing at interview. |
| Regulated environment | Comfortable in regulated settings. | Not established in the material. I have asked and will confirm before Thursday. |
The right-hand column takes no longer to write once the evidence work is already done. That is the actual dependency: submissions are hard to write honestly when you assessed the candidate holistically and are now reverse-engineering reasons.
Can AI help write candidate submissions?
Yes, for the drafting, provided it is drafting from evidence you have already reviewed rather than from the CV directly. Given a set of classified findings and their sources, producing a clean client-facing document is a formatting task. Given a raw CV and an instruction to sell the candidate, a model will produce exactly the adjective soup described above.
Two things to keep human: the recommendation, and anything that reads as a guarantee. If the draft says a candidate "will" do something, change it.
How Creo Access does it
In Creo Access, a candidate submission is generated from a Candidate Case, which already holds each requirement classified as evidenced, partly evidenced, claimed or not established, with the lines in the material each finding came from. The submission inherits that structure, so the honest version is the default rather than an act of discipline.
The client-facing export strips the internal citation markers, because your client does not need the S2 and S3 references that helped you check the mapping. Every section is editable before it leaves, and you can copy it or download it as a PDF.
A submission statement and the evidence under it
Select a statement to see its citation, or the missing evidence behind it.
The submission is built from evidence already mapped against the Role, not from the CV in isolation.
Read this figure as text
- Evidence-backed: Owns a month-end close. Role requirement, Owned a month-end close in a group finance function.
- Stated with its limit: ERP migration experience. Role requirement, Has worked on the ERP the group is migrating to.
- Missing evidence: Board-level reporting. Role requirement, Produced reporting consumed by a plc board.
There is no overall fit score in the submission, because there is none in the evidence. A client asking "how strong is this candidate?" gets your assessment, in your words, supported by findings they can check. That is a harder document to argue with than a percentage.
Try it on a live shortlist
Send a submission a hiring manager can check
Map a candidate against your Role, then export the client-facing version. Start free for 14 days. Then choose monthly or annual billing. Cancel anytime.
Start 14-day free trial