In consulting , CV experience calculation for tenders is what determines how many points a candidate actually scores. When years of experience are missing, miscalculated, or poorly structured, strong profiles are submitted at the wrong level and lose against weaker but better-documented competitors.
A Java developer with 21 years of experience sends you his CV. You read it carefully. It lists nine months of Agile, nine months of Scrum, no Angular at all. So you submit him as a mid-level back-end profile. He gets dropped from the shortlist. The framework contract goes to a competitor.
The problem was never the candidate. He had eight years of Angular and seventeen years of Agile. None of it was on the page. This is how 99% of consulting tender submissions lose level points before they even reach the evaluator. The CV is not lying on purpose. It is lying by omission. And the recruiter’s real job is to fix that gap before the document leaves the building.
TL;DR
- Most CVs underreport experience by years on the technologies that matter most for tender scoring.
- Submitting the CV “as received” is the single fastest way to lose level points and lose tenders.
- A two-minute WhatsApp exchange with the candidate often reveals 5 to 15 missing years of stack experience.
- The recruiter’s role is not to convert what is on the CV. It is to surface what is missing from it.
- Software handles parsing, calculation, formatting, and overlap deduplication. It does not replace judgement on what to ask the candidate.
- For DIGIT-TM II and similar frameworks, even a single missed certification can be the difference.
- Centralising stack data per consultant once means every future tender benefits from the work you did today.
What’s in this article
- The omission problem in candidate CVs
- A real example: 21 years of Java, nine months of Agile
- The two-minute WhatsApp method
- What software handles, and what it does not
- Overlapping experience and the academic penalty
- Why this is the difference between Level 8 and Level 9
- An operational checklist for tender submissions
- Frequently asked questions
The omission problem in candidate CVs
Candidates do not write CVs for tenders. They write them for themselves. They list what they remember, what they consider important, and what fits on two or three pages. Years of cumulative experience with specific technologies disappear into project descriptions or get omitted entirely.
For a recruitment team replying to a public tender or a framework contract, this is a structural problem. The evaluation grid does not reward “great developer”. It rewards documented years of experience on a specific technology stack, certifications, and academic level. Each one converts into points. Points convert into level. Level converts into daily rate or whether the candidate is admissible at all.
This is where CV experience calculation for tenders breaks down: the data exists in the candidate’s career, but not in the document used for evaluation.
Why do candidates underreport their own experience?
Because they write CVs for jobs, not for evaluation grids.
A back-end developer with eight years of Angular thinks of himself as a back-end developer. He mentions Angular in passing on one project, or not at all. The recruiter, working from the document alone, has no way to know that the candidate could legitimately claim full-stack experience. The information exists. It just was never written down.
A real example: 21 years of Java, nine months of Agile
Take a real Java developer profile. The CV is short. It mentions Java in a few project descriptions. It lists nine months of Agile and nine months of Scrum, taken from a single recent project where those words appeared. There is no Angular. There is no Jira or Confluence. The system parses the CV honestly and returns exactly what was written.
Now ask the candidate three direct questions:
“I see that you work with 10 years of Java. Is it correct? No. So I work since 2005 always with Java.”
Suddenly the same person has 21 years of Java instead of 10. Ask about Agile and Scrum: he started in 2008, so 17 years. Ask about Angular: 2018, so eight years. Same career, same person, completely different submission. Nothing has been invented. The career timeline has only been correctly described.
The two-minute WhatsApp method
Most senior candidates do not have time for a coaching call. They are working full days on client projects. The mistake is to assume that this means you cannot get the information. You can. You just have to make it cost the candidate two minutes, not thirty.
The format that works in practice is a short WhatsApp message that lists each missing technology from the tender requirements and asks one question per item: since when have you worked with this? The candidate replies in the format “Java 2005, Angular 2018, AWS 2018, Jira 2008”. You convert those answers into stack assignments inside the profile, run the calculation, and the years update across every relevant project automatically.
“It’s the way that we should do it.”
That is what experienced recruiters confirm when they see the workflow. It is not invention. It is structured verification. The candidate is the source of truth. The CV is just a starting document.
Is it ethical to add experience that was not on the original CV?
Yes, as long as the candidate confirms it directly and you can defend the dates.
Tender evaluators do not require that every claim appear on the original PDF the candidate sent you. They require that the submission be accurate and defensible. If the candidate states he has worked with Angular since 2018, that is a fact about his career, not a fabrication. Your job is to make sure the submission reflects the candidate’s actual experience, not the limitations of his CV writing.
What software handles, and what it does not
It is worth being precise about where automation helps and where it stops. A modern parsing and CV management platform does the heavy structural work. It loads the CV, identifies projects, education, certifications, and stack. Furthermore, it calculates years per skill and per project. It handles formatting for DIGIT-TM, Europass, single resolution board, and other institutional templates. It de-duplicates overlapping months automatically.
What it does not do is invent the questions you need to ask the candidate. That part is operational judgement. This is the boundary I described in why recruitment teams are moving beyond CV parsing tools in 2026: parsing is solved, but the commercial layer above it, the verification, the coaching, the level optimisation, that is still recruiter work.
| Task | Software handles | Recruiter handles |
|---|---|---|
| CV parsing into structured fields | Yes | Spot check |
| Years of experience calculation | Yes | Validate dates |
| Overlap deduplication | Yes | No |
| DIGIT-TM or Europass formatting | Yes | No |
| Identifying missing stack from CV | Partially (via job description match) | Confirm with candidate |
| Asking candidate “since when did you work with X” | No | Yes |
| Simplifying education to optimise level | No | Yes |
| Cross-checking certifications on LinkedIn | No | Yes |
Accurate CV experience calculation for tenders depends on structured data, not on raw CV text.
Overlapping experience and the academic penalty
There are two technical points that matter for tender accuracy and that most teams calculate by hand.
The first is overlap. If a consultant worked two full-time projects in parallel, you cannot count 80 hours per week of experience. The maximum is 40. So the system splits the weight: 50 percent to each project. If one project is full-time and the other is 20 hours, the split is 66 percent and 33 percent. This is computed per month and then assigned back to the projects and the stacks attached to them. Done by hand, this takes thirty minutes per CV and introduces errors. Done correctly by software, it takes seconds and is defensible.
The second is the academic penalty. When a candidate studied while working, you cannot double-count those years toward total professional experience. But there is a fairness ceiling. The maximum academic penalty applied is five years, even if the candidate completed three masters back to back. Otherwise people who worked through their education would be punished for ambition.
Why does the academic penalty matter for daily rate?
Because total years of experience determines level, and level determines daily rate.
A candidate arriving with what looks like ten years of experience, but who studied for five of those, will be evaluated at five years for total professional experience. That can move them from senior to mid-level on the framework grid. On individual skills, however, the years are not discounted: if you used Java while studying, you used Java. So total experience and per-skill experience are calculated on different rules, and both have to be right.
Why this is the difference between Level 8 and Level 9
On most EU framework contracts, the gap between two levels is a few points. A missing certification can be three points. A correctly described academic timeline can be two points. A stack that reflects 17 years of Agile instead of nine months can be the difference that pushes the total over the threshold.
This is why the work of going CV by CV, asking the right questions, and editing the structured profile matters more than any other step in the submission process. A team that treats CVs as documents to forward will lose tenders to a team that treats CVs as structured data to verify. We covered the operational side of this for consulting firms in how SWORD Group improved tender response and in reducing time-to-submission by 10x.
“You can see that you can already save a lot of time doing those calculations manually to add the stack easily. So instead of losing one hour per CV, you lose 10 minutes, but you focus on really what matters: to maximise the chances of the candidate being called to the interview.”
An operational checklist for tender submissions
If you are responsible for tender response in a consulting or staffing firm, this is the minimum verification routine that should run on every CV before submission.
- Run the CV through structured parsing so you have years of experience per skill, not just per project.
- Compare the parsed stack against the tender’s required technical profile.
- List every required technology that has zero or very few months on the parsed CV.
- Send the candidate a single WhatsApp message: “Since when do you work with X, Y, Z?”
- Apply the candidate’s answers to the structured profile, attaching stack to the relevant projects.
- Run auto-rating so the most experienced skills appear at the top of the technical expertise section.
- Check certifications. Cross-reference with LinkedIn if the CV does not list them. Each one can be three points.
- Simplify the education timeline to avoid unnecessary academic penalties when overlapping degrees exist.
- Generate the final document in the required format (DIGIT, Europass, SRB) only after all the above is done.
- Save the enriched profile centrally so the next tender starts from a complete, verified record.
This is also the reason centralisation matters. A consultant who is fully verified once, with stack, certifications, diplomas, and accurate dates, becomes a reusable asset for every future tender. That is the structural advantage of treating CVs as data and not as documents, which is the core argument behind CV database management for consulting firms at scale.
Final thoughts
The recruiter’s job in a tender response is not to type faster. It is not to convert PDFs into Word documents. It is to surface what the candidate forgot to write down, verify it, structure it, and submit a profile that reflects the actual career rather than the document. Software does the calculation, the formatting, the overlap maths, and the AI rewriting. The recruiter does the questions. That is the part that wins or loses the tender.
At its core, CV experience calculation for tenders is about representing reality correctly, not rewriting it.
If you want to see how this is handled inside a structured platform, including the per-skill calculations and the format generation, you can book a working session with Sprint CV or read more about the enterprise CV management approach used by consulting companies.
Frequently Asked Questions
If the recruiter sends a single structured WhatsApp message listing each technology and asking “since when”, most senior candidates reply within a few hours and the exchange takes them under two minutes. The recruiter then needs about ten minutes to apply the answers to the structured profile.
The total professional duration is reduced because no one can work more than 40 hours per week. The system distributes weight per month: two parallel full-time projects each count for 50 percent, while one full-time and one 20-hour project split 66 percent and 33 percent. This is calculated automatically and applied per skill
Yes, within the truth. If a candidate completed two overlapping degrees and the system applies a heavier academic penalty than necessary, the recruiter can simplify the timeline to one degree without falsifying anything. The goal is fair representation under the framework rules, not maximisation by invention.
Five years. Even if a candidate completed multiple degrees while working, the cumulative academic penalty deducted from total professional experience is capped at five years. This prevents punishing candidates who worked through their education from being penalised multiple times for the same period.
No. Total professional experience is reduced when academic years overlap with work, but per-skill experience is not. If a candidate used Java while studying, the Java months are counted in full. Only the global “years of professional experience” figure is adjusted for academic overlap.
Yes. Once the recruiter has added the verified stack to the relevant projects, an AI revision pass rewrites the project descriptions to incorporate that stack consistently. This is what turns a sparse two-page CV into a complete tender-ready profile in minutes rather than hours.
About the Author
Marco Pincho – Founder & CEO, Sprint CV
Marco has spent over seven years working with recruitment leaders and consulting executives on the same operational problem: how to turn unstructured CVs into governed, reusable data that wins tenders. The patterns in this article come from real conversations with bid managers, HR directors, and delivery leads across enterprise groups including VASS, Fujitsu, Sword Group, among others. He built Sprint CV in 2018 to fix the structural CV problem most consulting firms accept as normal. Connect with Marco on LinkedIn.
