Not every CV job your team runs is the same. Some CVs have to stay exactly as the consultant wrote them, section for section, because a framework contract depends on it. Others need to become interview notes before a client conversation. Others need to be tailored to a specific job or tender without losing what already works in them. Until now, AI Review handled all three the same way. AI Prompt Profiles change that. You build a profile with instructions for one of these jobs, then apply it either to an existing consultant’s profile or to a CV you are importing when you add a new consultant. This post walks through what a profile is, how to build one, and three scenarios teams are already using it for: parsing a CV without touching a word (the logic behind the DIGIT-TM II to DIGIT-TM III migration many consulting firms are working through right now), preparing interview notes, and tailoring a CV to a specific job.
Prefer to watch instead of read? Here’s the full walkthrough:
- AI Prompt Profiles let you configure exactly what the AI extracts from a CV and where it places that content, instead of applying one fixed behavior to every document.
- You build a profile once, in Company Settings under AI Review, and it stays available as a dropdown option for every future onboarding that matches the same case.
- A parsing profile can lock the AI to pure extraction: locate a section, copy it as written, place it in the matching field. Nothing rephrased.
- Other profiles can be built for preparing interview notes or for tailoring a CV to a specific job or tender, without discarding what already works in it.
- One real example already in use: a DIGIT-TM II Parser profile that converts consultant CVs into DIGIT-TM III format without altering the wording.
- The same approach applies to any recurring format, from another framework contract like ITS to a client’s own CV template.
- Because a prompt profile is reusable, onboarding a batch of consultants under the same case takes one upload each, not a manual rewrite each.
- The result is more control over how AI Review behaves, not less, since you decide the rule set for each workflow instead of accepting one default for everything.
Why One CV Review Behavior Does Not Fit Every Case
AI Review has always checked and cleaned up CVs as they come into the system. That is useful for a brand new consultant profile built from scratch. It is the wrong behavior for a CV that already went through a client review cycle and simply needs to be dropped into a different template.
Treat both cases the same way and one of two things happens. Either the AI is too aggressive on a CV that should not change, and a consultant asks why their summary reads differently. Or it is too passive on a CV that genuinely needed cleaning up, and someone on the team has to fix it manually anyway. Either way, the fixed, one-size behavior becomes the bottleneck.
What Are AI Prompt Profiles?
An AI Prompt Profile is a saved configuration that tells Sprint CV’s AI exactly how to handle a specific onboarding case: what to look for on the source document, what to do with each section, and where that section belongs in the consultant’s record. You build it once and select it whenever that case comes up again.
What exactly is an AI Prompt Profile?
It is a named, reusable rule set that controls how the AI reviews a CV, instead of one fixed behavior applied to everything.
Each profile is configured under Company Settings and appears as a dropdown option at the point where you upload a consultant’s CV. One profile can be built purely for extraction, mapping content from a source document into the right fields without changing it. Another can be built to translate content, prepare interview notes, or apply only minor formatting corrections. You pick the profile that matches the job in front of you.
The point is not to replace judgment with automation everywhere. It is to stop forcing every CV through the same review logic when the actual task in front of your team changes from one onboarding to the next.
How Do You Build an AI Prompt Profile?
Building a profile means writing a set of prompt fields that describe, section by section, what the AI should do with a source document. For a parsing profile, that description is deliberately narrow: locate a section, then copy it exactly, with no rewriting.
“Your job is just to take the information. So the CV summary comes from here. Do not change a comma. Take it as it is. Do not redo or apply anything.”
The same logic extends to every mapped section. Point the AI at the project description on the source document and tell it where that content belongs on the target template. Do the same for tasks and responsibilities, skills, or any other block that repeats across documents.
“Keeping the same wording, original styling, so you preserve everything. I don’t want to change the text.”
Once those prompt fields are saved as a profile, the configuration work is done. Every future CV that fits the same case runs through the same rules, without anyone rebuilding the logic from scratch.
What Can You Configure a Prompt Profile to Do?
Three use cases come up most often, and all three work the same way underneath: you write the prompt fields once as a named profile, then apply that profile either to an existing consultant’s profile in Sprint CV or to a CV you import when adding a new consultant.
The first is pure parsing, already shipping as a DIGIT-TM II Parser profile: it reads a consultant’s DIGIT-TM II CV and maps the summary, project description, and tasks and responsibilities directly into DIGIT-TM III fields, preserving the exact wording throughout. It uses the same AI CV Parser that reads a source document’s structure so the mapping holds even when formatting varies slightly between files.
The second is preparing interview notes: turning an existing CV into a structured draft a recruiter or delivery lead can walk into a client conversation with, without starting from a blank page. The third is job tailoring: adjusting emphasis and content so a consultant’s CV speaks to a specific job or tender, without discarding what already works in it.
| Profile type | What it does | When to use it |
|---|---|---|
| Default AI Review | Applies the platform’s standard cleanup and structuring to a new CV | General onboarding with no specific source template |
| Parsing profile (for example, DIGIT-TM II Parser) | Maps named sections verbatim from a source CV into the matching target fields | Onboarding consultants under a framework contract migration, such as DIGIT-TM II to DIGIT-TM III |
| Interview notes profile | Turns an existing CV into a structured draft for interview preparation, in the original language or translated | Preparing a consultant for a client interview |
| Job tailoring profile | Adjusts emphasis and content to match a specific job or tender, keeping what already works in the CV | Submitting a consultant for a specific role, client, or bid |
The DIGIT-TM example matters because it is concrete, but it is one profile among several, not the whole feature. A firm running CV management for consulting companies across several clients can build a parsing profile for each recurring template it receives, from another framework contract like ITS to a specific client’s internal CV format, alongside interview notes and job tailoring profiles for its day-to-day work, and keep every path consistent even when the source documents look nothing alike.
Explore More
Go Deeper on Each Use Case
Each configuration below is documented in full elsewhere on this blog, prompt by prompt, if you want to see exactly how it is built and run.
Why Preserving Original Wording Matters
It is tempting to let an AI review step tidy up a CV while it is at it. Tighter phrasing, a more consistent tone, a cleaner summary. In practice, that creates friction when the CV has already been reviewed, approved, and used successfully before.
“So the consultant then doesn’t have, ‘Why you are rewriting my CV again?'”
That line explains why a parsing profile is configured to leave wording untouched by design, not by accident. A consultant who sees their summary rewritten without being asked pushes back, and someone on the recruitment or delivery team ends up managing that conversation instead of moving on to the next onboarding.
Will an AI Prompt Profile rewrite my consultants’ CV content?
Only if you build it to. A parsing profile is configured specifically to leave wording untouched.
The same AI Review step can do both jobs, extract without changing anything, or apply heavier editing, depending entirely on how the profile in use is configured. A parsing profile copies text section by section. A different profile, built deliberately for a different task, can tighten phrasing when that is what you actually want, such as before a client submission.
Setting Up and Using a Profile, Step by Step
Configuring a profile is a one-time setup per case. Using it afterward takes seconds, whatever the underlying document looks like.
- ✓Go to Company Settings and open AI Review
- ✓Click Add AI Prompt Profile and name it for the case it covers, for example “DIGIT-TM II Parser”
- ✓Fill in the prompt fields, telling the AI exactly what to extract from each section and where it belongs
- ✓Save the profile
- ✓Click Add a New Consultant and fill in their details as usual
- ✓Check AI Review, then pick the relevant profile from the AI Prompt Profile dropdown
- ✓Check Generate CV, choose the output template you need, and pick a file format
- ✓Upload the consultant’s existing CV and click Create Account
From that point, the AI reads the uploaded file using the saved profile and builds the consultant’s record with the content placed exactly as configured, while producing a finished CV in the target template in the same step.
Do I need a new profile for every consultant?
No. A profile is built once per case, then reused for every consultant who fits it.
If a team is onboarding twenty consultants who all bring the same source CV format, one profile covers all twenty. The same applies to any recurring case, including a large framework contract win where every incoming consultant arrives with an identical template.
What This Means for Onboarding Speed and Consistency
For a bid or tender manager, the value shows up the moment a large contract is won and a batch of consultant CVs needs to be submission-ready fast. For a Head of Delivery, it shows up every time a new hire or subcontractor joins a project that runs on a fixed CV template. Either way, the gap between “consultant sends CV” and “CV is ready to submit” gets compressed into one upload against the right profile.
None of this replaces judgment. A recruiter still decides which consultant goes forward, and a delivery lead still reviews the final CV before it reaches a client. What changes is how much formatting work sits between that decision and a submission-ready document, and how much control the team has over what the AI is allowed to touch.
Frequently Asked Questions
What is an AI Prompt Profile in Sprint CV?
It is a saved configuration that controls how the AI reviews a CV for a specific case, defining what to extract from each section and where it belongs, instead of applying one fixed behavior to every document.
How do I create an AI Prompt Profile?
Go to Company Settings, open AI Review, and click Add AI Prompt Profile. Name it, fill in the prompt fields describing what to extract from each section of the source CV and where it should go, then save it. It appears as a selectable option whenever you onboard a consultant.
Will using a profile change the wording on my consultants’ CVs?
Only if the profile is built to. A parsing profile copies text section by section without rephrasing it. A different profile can be configured to edit more heavily if that is what a specific case actually needs.
Can a profile prepare interview notes or tailor a CV to a specific job?
Yes. Alongside parsing, these are the other two use cases teams build profiles for: one that turns an existing CV into structured interview notes, and one that adjusts a CV’s emphasis and content to match a specific job or tender without discarding what already works in it.
Is there a profile for converting DIGIT-TM II CVs to DIGIT-TM III?
Yes. It is one of the parsing profiles teams are already using: it maps summary, project description, and tasks and responsibilities from a DIGIT-TM II document straight into DIGIT-TM III fields, preserving the original wording. The same approach works for ITS onboarding or any other framework contract or client template where consultants arrive with a consistent CV format.
Do I need a different profile for every onboarding scenario?
Only where the underlying task is genuinely different. One profile per recurring case is typically enough, whether that is a specific framework contract, preparing interview notes, or tailoring CVs to a type of job.
Final Thought
The friction in most onboarding was never a lack of automation. It was automation that could not tell the difference between a CV that needed rebuilding and one that needed to be left alone.
AI Prompt Profiles fix that by putting the configuration in your hands. Parsing a DIGIT-TM II CV into DIGIT-TM III format is one profile built on top of it. Preparing interview notes and tailoring a CV to a specific job are two more. The same approach is available for whatever recurring case your team handles next.
Curious what an AI Prompt Profile built for your own CV formats and framework contracts would look like? Book a demo with Marco Pincho to walk through your specific case.
About the Author
Seven years of watching recruiters format the same CV three different ways for three different clients led Marco Pincho to build Sprint CV, an enterprise CV manager used by companies including VASS, Fujitsu, Sword Group, and Expleo to standardize CV creation and submission. He holds an Executive Master in IT Management from Solvay Brussels School and spends most weeks on calls with recruitment leaders and HR directors, working through documentation problems like the one covered in this article. Connect with Marco on LinkedIn
