EU Tenders
The DIGIT-TM III Mini-Competition Playbook for Staffing Agencies
Under DIGIT-TM III, work arrives as mini-competitions with response windows measured in working days, not weeks. This playbook covers the go/no-go decision, the CV pack that sits on the critical path, and how to submit a compliant response before the clock runs out.
Written by: Saply Team
A DIGIT-TM III mini-competition playbook is the repeatable operating procedure an agency runs each time a Service Request lands under the framework: triage the request, make a go/no-go call, staff the response, assemble a compliant CV pack, and submit before a deadline usually set in working days rather than weeks. It is a project management problem, not a writing problem. The winner is rarely the agency with the strongest consultants. It is the agency that can prove they qualify, on the right template, before the window closes.
DIGIT-TM III was awarded in mid-2026 at roughly 3.97 billion euros over 48 months across three lots, under notice EC-DIGIT/2025/OP/0014, with the first Service Requests expected in autumn 2026. For four years after that, work will not arrive as one big tender. It will arrive as a stream of mini-competitions, each with its own profile mix, its own deadline, and its own CV pack. An agency that treats each one as a fresh fire drill will lose the early ones. This playbook is how you make the response boring and fast.
What a DIGIT-TM III mini-competition actually is
Once a framework agreement is signed, the contracting authority does not run a full tender again for each piece of work. It either awards a specific contract directly under the framework’s pre-set terms, or, where the framework allows it, reopens competition among the signed suppliers. That reopened competition is the mini-competition, and it is governed by the EU public procurement rules in Directive 2014/24/EU on framework agreements.
Two facts from that Directive shape the whole playbook. First, a framework agreement may not run longer than four years except in duly justified cases, which is why DIGIT-TM III is a 48 month commitment and why the mini-competition rhythm repeats for that entire period. Second, the authority must set a response deadline that is “sufficiently long” for the complexity of the work. The Directive deliberately does not fix a number of days.
The “5 to 10 working days” figure you will hear quoted is EC practice, not a legal rule. Comparable Commission framework mini-competitions commonly run five to ten working days for the full response, and DIGIT-TM II consortium arrangements showed windows as tight as three business days per consortium member. Plan for the short end. The Directive lets the authority choose, and complexity is judged from their side, not yours.
Map the days before you touch a template
The instinct on day one is to start formatting CVs. That is how agencies lose. The response has three workstreams that must run in parallel, and only one of them sits on the critical path. Draw the timeline first, then staff it.
The CV pack is on the critical path because it depends on people, not documents. You cannot format a consultant into the template until you have confirmed that consultant is available, willing to be named, and actually meets the profile. Chase availability on day one, in parallel with everything else, or you will discover on day five that your lead expert took another contract and the whole pack unravels.
Day one: triage and the go/no-go decision
Not every Service Request is worth answering. Responding costs real hours from your best people, and a thin bid you cannot staff wastes them for nothing. Make the go/no-go call in the first hours, before the team invests a day.
| Question | Go signal | No-go signal |
|---|---|---|
| Named experts available | You can name and confirm every required profile | You are one senior expert short and cannot source in time |
| Profile match | Consultants clear the experience thresholds on dates | You would be stretching a claim you cannot evidence |
| Template and format known | You have the exact template and file rules in hand | Instructions are unclear and the clarification window is closing |
| Deadline realistic | The window fits your capacity this week | Two other Service Requests are due the same day |
| Strategic value | The lot and client matter to your four-year plan | Marginal work that blocks a better bid next week |
The experience thresholds are the fastest way to disqualify yourself, so check them at triage rather than on submission day. For a DIGIT-TM III expert profile the minimum years scale with education: roughly five years of IT experience with a master’s degree, seven with a bachelor’s, and twelve with no degree. Confirm the exact figures in the annexes for your lot, because they differ by profile and by framework generation. If a named consultant cannot prove the threshold from dated roles, that is a no-go on that profile before any formatting begins. The mechanics of proving it live in our guide to preparing CVs for European Commission framework contracts.
Staff the response so nobody waits on one person
A mini-competition fails when three people all need the same colleague at the same time. Assign owners on day one and let the workstreams run independently.
| Workstream | Owner | Does | Waits on |
|---|---|---|---|
| Bid management | Bid lead | Reads the SR, methodology, compliance checklist, final assembly | Nothing, starts immediately |
| CV pack | Resourcing / delivery | Confirms availability, gathers evidence, renders each template | Consultant replies (chase day one) |
| Pricing | Commercial / finance | Rate build, margin, financial offer in the required form | Confirmed named experts |
| Sign-off | Account owner | Compliance read, one final quality gate, submission | The other three, only at the end |
The single most common failure is the bid lead also owning the CV pack. Those are different skills on different clocks. The bid lead is writing prose that persuades. The resourcing owner is assembling evidence that scores. Splitting them is what lets the pack proceed while the methodology is still being drafted.
The CV pack is where the days actually go
Formatting one consultant CV into a mandatory template takes an experienced recruiter 15 to 30 minutes when the source data is clean, and considerably longer when it is a five-year-old Word file with gaps. A pack of ten named experts is most of a working day of copy, paste, and reconciliation, landing in the same week the bid team is writing the technical offer. With an estimated 2,000 to 3,000 consultants needing re-placement around the DIGIT-TM III transition, agencies bidding into the first wave will hit this every few days rather than once.
The consistency trap. Ten experts who each worked on the same programme, described ten slightly different ways, reads as carelessness to an evaluator and can trigger a clarification request you have no time to answer. The same project must carry the same title, client, and dates on every CV in the pack. This is exactly the error that scales badly under repeated mini-competitions, because each fresh fire drill reintroduces it.
The structural answer is to stop treating each CV as a document you write and start treating it as a rendering of one maintained profile. Keep a master record per consultant with every assignment, client, country, exact dates, funding source, role, technologies, and deliverables. When a Service Request lands, you select the relevant subset and render it into the required template, which is a minutes-per-CV job rather than a rewrite. Remember that the DIGIT-TM template is not Europass; a Europass export is a fine master record and never a substitute for the mandated template.
This is the workflow Saply’s EU institutions setup is built around: parse each consultant’s existing CV once, hold it as structured data, then format it into the mandatory template on demand and score the profile against the Service Request before a name is committed to the bid. Everything is processed in the EU, which matters when consultant CVs are personal data and your client is a Commission DG (see our security overview).
The honest limitation: automation fixes formatting, consistency, and speed. It does not fix judgement. It cannot decide whether a consultant genuinely clears a twelve-year threshold, and it cannot conjure a missing certificate. Someone on the bid team still reads the Terms of Reference and signs off on the final pack. What changes is that they spend that hour on compliance, not on retyping dates at 16:00 on deadline day.
The quality gate before you submit
Reserve the final half day for one compliance read against the instructions, not the CV content. These are the failures that reject an otherwise strong response, and every one of them is a process check rather than a writing task.
- One CV per named expert, in the exact template the SR specifies, no house format.
- The requested file type, since some frameworks still require .doc and forbid PDF.
- No headers, footers, logos, or photographs unless explicitly permitted.
- Section names and order unchanged from the template, empty sections kept.
- Dates written as month and year so an evaluator can add up the years.
- Languages in CEFR levels, never “fluent” or “good working knowledge”.
- Every requested annex, signature, and availability declaration present.
- Submission through the correct portal, well before the stated hour.
How to make the next mini-competition faster than this one
The first Service Request you answer is the expensive one. The playbook only pays off if each subsequent response is cheaper, so close every mini-competition by updating the master profiles you touched: add the new assignment, correct any date you had to reconstruct, file the certificate you had to chase. Done consistently, the response window stops being a fire drill and becomes a selection task. That is the difference between the agencies that win the early Service Requests and the ones still training recruiters on a template while the clock runs. Our guide to what changed in the DIGIT-TM III templates covers the format shifts you should encode into that master-profile workflow now, before autumn.
Frequently asked questions
How long is a DIGIT-TM III mini-competition deadline?
There is no fixed legal number. Directive 2014/24/EU requires only that the authority set a deadline “sufficiently long” for the complexity of the work. In practice, comparable Commission framework mini-competitions commonly run five to ten working days for the full response, and some consortium arrangements have compressed that to as little as three business days per member. Plan your process around the short end.
What is the difference between a direct award and a mini-competition under a framework?
A direct award is used when the framework already fixes all the terms for that piece of work, so no new bid is needed. A mini-competition, also called reopening of competition, happens when the framework allows it and the authority invites the signed suppliers to compete again for a specific Service Request. Under DIGIT-TM III, the work that requires a CV pack and a fresh bid is the mini-competition path.
Who should own the CV pack during a mini-competition?
A resourcing or delivery owner, not the bid lead. The bid lead is writing the technical methodology, which is persuasive prose on its own clock. The CV pack is evidence assembly that must run in parallel and sits on the critical path because it depends on confirming real people are available and qualified. Splitting the two roles is what keeps both workstreams moving at once.
How many years of experience does a DIGIT-TM III expert CV need?
The threshold scales with education rather than being a single figure: approximately five years of IT experience with a master’s degree, seven with a bachelor’s, and twelve with no degree. These vary by profile and lot, so confirm them in the annexes for the specific Service Request. Check them at triage, because a consultant who cannot evidence the threshold from dated roles is a no-go before any formatting begins.
Can we reuse a CV pack from a previous mini-competition?
Only where the template and the required profile are genuinely identical, which is rare for long. Reusing a pack unchanged is how stale dates, missing recent projects, and mismatched terminology enter a live bid. Maintain a master profile per consultant and render a fresh, template-correct version each time, which keeps the pack internally consistent and turns the next response into a rendering job rather than a rewrite.