Two consultants who each worked six months on two different assignments at the same time do not have twelve months of combined experience between them. Yet that is exactly what happens when a CV is built by hand: every project gets counted in full, overlaps and all, and the total experience shown to an evaluator ends up inflated before anyone notices. Sprint CV runs into this pattern constantly with consulting companies preparing consultant profiles for tenders. Overlapping project experience on a CV has to be split, not summed, and a handful of small data errors around it, duplicate entries, missing dates, unvalidated team sizes, quietly undo weeks of proposal work. This piece walks through how the calculation should work and where it usually breaks.
TL;DR
- Overlapping project experience on a CV must be split, not added. The standard rule is a 50/50 split when two projects run at the same time, and a one-third split each when three run concurrently.
- Skipping the split inflates total experience, sometimes by months, and evaluators who know the rule will catch the discrepancy.
- Missing end dates commonly default to today’s date, silently stretching a project’s duration until someone corrects it manually.
- One real assignment often gets recorded as two duplicate CV entries instead of a single entry with an internal split, which compounds the overlap problem.
- Team size fields left blank get flagged in review. Evaluators expect a validated number, not an empty field.
- AI-assisted skill extraction occasionally tags stray text as a skill, so a periodic manual check of the skills section is still necessary.
- A “tasks and responsibilities” label that goes missing breaks the project description into unstructured text, exactly where evaluators are scoring.
- Configurable reminder cycles and consultant self-service access keep this data current between tenders, rather than reconstructed under deadline pressure.
In this article
- Why overlapping assignments are the hardest thing to get right on a CV
- The European Commission rule for splitting overlapping experience
- The small data errors that quietly cost tender points
- Why a stripped “tasks and responsibilities” label breaks more than formatting
- Keeping consultant data current without manual chasing
- Frequently asked questions
- Final thought
Why overlapping assignments are the hardest thing to get right on a CV
Consultants in staffing and consulting rarely work on one thing at a time. It is common for someone to be allocated part time to two, sometimes three, engagements over the same period, moving between a delivery role and an advisory one, or splitting a quarter between two clients.
A CV built by hand tends to list the full duration of each project independently, because that is how the consultant remembers it and how the source documents describe it. The result is a total experience figure that is technically wrong, and under evaluation frameworks that calculate expertise level from months of experience, that overstatement changes the score, not just the presentation.
How is experience calculated when a consultant works on two projects at once?
By splitting the overlapping period between the two projects, not by counting the full duration twice.
Manually built CVs fail this constantly, because nobody sits down to recalculate months every time a project is added. A system that recalculates automatically whenever a new project or end date is entered removes that manual step, but a bid team working from a static CV template still needs to apply the same logic by hand.
The European Commission rule for splitting overlapping experience
The convention most consulting companies operating on EU framework contracts follow is the same one used to calculate overlapping project experience on a CV under European Commission evaluation rules: when two projects run at the same time, each is credited with half the overlapping period. When three run concurrently, each gets a third.
When you have overlaps, we split. If two projects run at the same time, it is fifty-fifty. If there are three, it is one-third each. That is the rule of the commission. Marco Pincho, Founder & CEO, Sprint CV
What happens if a consultant has three overlapping projects at once?
Each of the three projects is credited with one third of the overlapping period, unless the real allocation is known and documented.
An even split is the default, but it is only an approximation. If the actual allocation was closer to ninety percent on one project and ten percent on another, that needs to be confirmed directly with the consultant rather than left as an even split, otherwise a minor role risks being padded into something it was not, and a major one risks being understated.
The small data errors that quietly cost tender points
Overlap calculation gets most of the attention because it changes a number evaluators can check. The errors below are smaller, and precisely because they look cosmetic, they are the ones bid teams skip reviewing before submission.
- ✓End dates left blank default to today’s date, inflating the current project’s length until corrected manually
- ✓One real assignment recorded as two separate CV entries instead of a single entry with an internal split
- ✓Team size fields left blank instead of a validated, confirmed number
- ✓Contract type labels left visible on the CV, adding clutter an evaluator does not need
- ✓Skills that are not actually skills, a stray phrase pulled from a document, sitting in the skills section
- ✓Nationality field left blank on the consultant profile
- ✓A CV built on an outdated template version instead of the current one
- ✓The “tasks and responsibilities” label missing, so description and responsibilities run together as one block
None of these individually derail a proposal. Together, on a team of ten or fifteen consultant profiles, they are enough to make a technical proposal look rushed, and evaluators score for that impression as much as for the content itself.
Why a stripped “tasks and responsibilities” label breaks more than formatting
When a project entry loses its “tasks and responsibilities” label, whether through a parsing error or a manual formatting slip, the description and the responsibilities merge into a single undifferentiated block of text. The information is technically still there. It is just no longer structured the way an evaluator is scanning for it.
Why does a missing label matter if the content is still on the CV?
Evaluators score against a structure, not just for the presence of information somewhere on the page.
A tender scoring grid usually checks for a named responsibility under a specific heading. If that heading has disappeared, the same sentence that would have scored cleanly now reads as unstructured narrative, and there is no guarantee it gets credited the same way. Fixing this is as much about defending the score as it is about formatting.
Keeping consultant data current without manual chasing
The pattern behind almost every error above is the same: the data was correct once, and nobody went back to confirm it before the tender needed it. There are a few practical ways consulting companies close that gap without turning it into a full-time job.
Giving consultants direct access to their own profile removes the step of a coordinator chasing updates by email. Pairing that with a configurable reminder cycle, prompting consultants to review their own profile every ninety days for example, keeps small changes from piling up unnoticed. A self-rating step where consultants confirm or correct their expertise level also catches cases where raw months of experience do not reflect how deep someone’s knowledge of a technology actually is. Customisable CV summary prompts keep wording consistent across profiles, so a proposal writer is not rebuilding phrasing from scratch for every consultant.
| Reactive upkeep | Structured upkeep |
|---|---|
| Data corrected only when a tender surfaces the gap | Consultants review and confirm their own profile on a set cycle |
| Overlapping projects summed manually, or missed entirely | Overlap calculation applied automatically whenever dates change |
| Expertise level inferred purely from months of experience | Consultants self-rate and confirm their own expertise level |
| Summary wording rewritten from scratch for each CV | Consistent summary prompts applied across all profiles |
None of this replaces the judgement a bid team brings to a proposal. It does mean the underlying data is accurate before the writing starts, rather than corrected in a rush the night before submission. This is the same problem Sprint CV’s work on CV experience calculation for tenders looks at from the scoring side, and it is why an AI CV parser built specifically for this structure matters more than a generic document parser.
Frequently Asked Questions
How is overlapping project experience calculated on a CV?
The overlapping period between two projects running at the same time is split evenly between them by default, fifty percent each, unless the real allocation is known and documented differently.
What happens if a consultant works on three projects at the same time?
Each of the three overlapping projects is credited with one third of the overlapping period by default, following the same logic used for two concurrent projects.
Why do missing end dates cause problems on a CV?
A blank end date commonly defaults to today’s date, which silently extends the project’s duration and inflates total experience until someone manually enters the correct end date.
Why does a CV need a validated team size field?
Tender evaluators often check team size as part of scoring a consultant’s seniority and scope of responsibility. A blank field reads as missing information, not as irrelevant detail.
How often should consultant CVs be updated?
A recurring cycle, commonly every ninety days, works well for most consulting companies. It keeps profiles current without waiting for a tender deadline to surface data gaps.
Why do evaluators care about a labelled “tasks and responsibilities” section?
Because scoring is done against a structure. A responsibility described in unlabelled narrative text is not guaranteed to be credited the same way as one presented under the heading an evaluator is scanning for.
Final Thought
Overlapping project experience on a CV is not a formatting detail. It is a calculation, and getting it wrong changes the number an evaluator sees. The same is true of the smaller errors around it: a blank date, an unvalidated team size, a missing label. None of them look urgent on their own.
The consulting companies that submit consistently strong technical proposals are the ones that treat this as data hygiene, checked on a cycle, rather than a correction exercise squeezed into the days before a deadline.
Where to go next
|
About the AuthorMarco Pincho has spent eight years building the systems recruitment and consulting companies use to manage CVs, technical competences, and candidate data at scale. As founder and CEO of Sprint CV, he works directly with enterprise clients including VASS, Fujitsu, Prime Group, Sword Group, Expleo, and Almaviva, and holds an Executive Master in IT Management from Solvay Brussels School. Connect with Marco on LinkedIn. |
