ITS26-DEV Framework Contract: Lot Rules, SLAs and CV Compliance

Este artículo se publica en su idioma original.

European Market & Institutions

Winning a position on the ITS26-DEV framework contract is only the start. Each request for offer then gives a contractor 3 working days to confirm intent, candidates must be available for interview on time or incur €100 per day in liquidated damages, and a replacement consultant has to take over within 20 working days.

The framework serves eight EU institutions across four lots, four locations and up to 48 months, under rules that reward administrative precision as much as technical quality. This article sets out how the lots are built, how the two-lot award cascade works, which SLA and profile rules apply and what a compliant bid package looks like, so delivery and bid teams can plan around them.

TL;DR
  • ITS26-DEV (EP-ITEC/LUX/2025/OP/0003) is the European Parliament’s open procedure for the development and maintenance of information systems, led by DG ITEC under Regulation (EU, Euratom) 2024/2509.
  • It serves eight EU institutions and bodies for up to 48 months (24 months plus two 12-month extensions), as a multi-vendor framework without reopening of competition and with up to three contractors per lot.
  • Four lots separate core business systems from supporting and steering systems, and Brussels, Strasbourg and Lisbon from Luxembourg.
  • A tenderer can bid on all four lots but win a maximum of two, and the lots are awarded in the order Lot 4, Lot 2, Lot 3, Lot 1.
  • Delivery risk is specific: €100 per day for interview delays (TM-1), 3 working days to declare intent on a request for offer, 20 working days to replace a consultant, and partial termination under TM-7.
  • Total contractor liability is capped at three times the value of the framework contract, as an absolute aggregate cap.
  • Profile rules include PM², PMI-PMP or Prince2 for project managers, intermediate or expert cloud certifications, experience in decimal years with a last-updated date, and freelancers declared as subcontractors.
  • Word-count limits include table text, figures and single-letter RACI entries (Q&A 82591).

What Is the ITS26-DEV Framework Contract and Who Buys Through It?

The ITS26-DEV framework contract procurement (EP-ITEC/LUX/2025/OP/0003) is titled “Development and maintenance of information systems”. It is a multi-buyer purchasing structure led by the European Parliament’s Directorate-General for Innovation and Technological Support (DG ITEC).

It spans the complete software lifecycle, from initial architectural consultancy and custom development to system deployment, application tailoring, integration and long-term maintenance. The procurement establishes the software engineering supply chain for the European Parliament and seven partner institutions over a four-year period.

The operational perimeter covers all administrative, supporting and core legislative software systems, including public Internet portals and internal Intranets. The only explicit exclusion is new software development executed in fixed-price off-site delivery mode.

ITS26-DEV is an Open Procedure governed by Regulation (EU, Euratom) 2024/2509, the EU Financial Regulation. It consolidates institutional purchasing power to drive digital modernisation and sets a standardised, highly regulated mechanism for IT professional services.

Which institutions can order under the ITS26-DEV framework contract?

Eight institutions, bodies and agencies, with the European Parliament as lead Contracting Authority and Group Leader.

DG ITEC acts as the central purchasing body, managing the procurement out of Luxembourg under registration EP. The resulting framework agreements serve:

  • European Parliament (EP): Lead Contracting Authority and Group Leader (Luxembourg)
  • European Data Protection Supervisor (EDPS): Participating Buyer (Brussels, Belgium)
  • European Court of Auditors (ECA): Participating Buyer (Luxembourg)
  • European Ombudsman (OMBUDSMAN): Participating Buyer (Strasbourg, France)
  • European Union Drugs Agency (EUDA): Participating Buyer (administrative contact in Luxembourg, operations and primary technical infrastructure in Lisbon, Portugal)
  • Translation Centre for the Bodies of the European Union (CdT): Participating Buyer (Luxembourg)
  • Committee of the Regions of the European Union (CoR): Participating Buyer (Brussels, Belgium)
  • European Economic and Social Committee (EESC): Participating Buyer (Brussels, Belgium)

Legal oversight and dispute resolution fall under the exclusive jurisdiction of the General Court of the Court of Justice of the European Union (CURIA, located in Luxembourg).

The procurement is a multi-vendor Framework Contract without reopening of competition, awarding positions to a maximum of three economic operators per lot. Specific contracts, issued as cascade task orders, go directly to the awarded contractors based on their final ranking.

The framework runs for a maximum of 48 months: an initial 24-month operational period, with provisions for up to two consecutive 12-month extension renewals. Under standard Financial Regulation provisions, the Contracting Authority may run negotiated procedures without prior publication for repetitive or similar services. These are capped at 50% of the initial contract value and must strictly conform to the baseline project specifications.

Multi-tenant delivery capacity

Aggregating demand across eight EU entities shifts the requirement from single-client support to multi-tenant service delivery. Prime contractors must run operational infrastructure that handles distinct institutional mandates, regulatory frameworks and governance rhythms at the same time, across four primary locations: Brussels, Luxembourg, Strasbourg and Lisbon.

  • Brussels hub: EP, EDPS, CoR, EESC.
  • Luxembourg hub: EP, ECA, CdT, EUDA.
  • Strasbourg hub: EP, OMBUDSMAN.
  • Lisbon hub: EUDA operations.

Consortia must set up flexible governance that accommodates the varying administrative processes of the participating bodies while keeping profile qualifications, security standards and Service Level Agreements (SLAs) uniform. The consortium delivery model rests on a shared resource bench and governance, multi-site near-premises infrastructure, and cross-institutional SLA and quality management.

Incumbent market benchmarks

Historical data from similar large-scale EU public sector IT frameworks shows market share concentrated in a select tier of established prime contractors and large joint ventures.

ContractorTotal award valueAwarded contracts
Cronos€429 million19
Netcompany Intrasoft€286 million16
NTT DATA€198 million16
Atos€169 million16
Capgemini€145 million19

These figures show that top-tier incumbents bring deep institutional knowledge, pre-established local bench capacity and complex subcontracting ecosystems. For new entrants and challenger consortia, competing against them takes rigorous commercial pricing, strong local delivery capabilities across all institutional sites, and flawless administrative compliance.

How Is the ITS26-DEV Framework Contract Divided Into Four Lots?

DG ITEC divided the procurement into four lots to balance operational delivery footprints against domain-specific application architectures. The structure separates core legislative and political systems from supporting corporate administrative software, and sets a geographic boundary between Luxembourg-based operations and work executed in Brussels, Strasbourg and Lisbon.

DimensionLot 1: Core Business Systems (Brussels and Other)Lot 2: Core Business Systems (Luxembourg)Lot 3: Supporting and Steering Systems (Brussels and Other)Lot 4: Supporting and Steering Systems (Luxembourg)
Internal identifierEP-ITEC/LUX/2025/OP/0003-LOT-1EP-ITEC/LUX/2025/OP/0003-LOT-2EP-ITEC/LUX/2025/OP/0003-LOT-3EP-ITEC/LUX/2025/OP/0003-LOT-4
Primary geographic locationsBrussels, Strasbourg, Lisbon (excluding Luxembourg)LuxembourgBrussels, Strasbourg, Lisbon (excluding Luxembourg)Luxembourg
Core functional domainCore business (legislative, budgetary, parliamentary work, political engagement)Core business (legislative, budgetary, parliamentary work, political engagement)Supporting and steering (HR, finance, logistics, governance, security, IT and more)Supporting and steering (HR, finance, logistics, governance, security, IT and more)
Maximum awarded contractorsUp to 3Up to 3Up to 3Up to 3
Contract duration model48 months (24 months initial plus 2 x 12-month renewals)48 months (24 months initial plus 2 x 12-month renewals)48 months (24 months initial plus 2 x 12-month renewals)48 months (24 months initial plus 2 x 12-month renewals)
Procedure typeOpen (without reopening of competition)Open (without reopening of competition)Open (without reopening of competition)Open (without reopening of competition)

Core business systems (Lots 1 and 2)

Lots 1 and 2 cover core statutory, legislative and regulatory applications. For the European Parliament, this means applications that directly support:

  • Legislative, budgetary and non-legislative Treaty powers.
  • Parliamentary and plenary session workflows, committee business and agenda management.
  • Political engagement, member support and external stakeholder relationship management.

For the partner bodies (EDPS, ECA, OMBUDSMAN, EUDA, CdT, CoR, EESC), core business means specialised operational software tied directly to their primary statutory mandates under the EU Treaties and governing regulations.

Supporting and steering business systems (Lots 3 and 4)

Lots 3 and 4 cover corporate administrative software, institutional steering applications and internal IT operational tooling across fifteen functional domains:

  1. Planning
  2. Monitoring and Reporting
  3. Governance
  4. Compliance and Transparency
  5. Human Capital Management (HR)
  6. Facilities and Auxiliary Services
  7. Financial and Accounting Services
  8. Infrastructure Management
  9. Information Technology and IT Service Management
  10. Logistics and Inventory
  11. Conferences, Interpretation and Meetings Management
  12. Security and Building Access Control
  13. Corporate Communication and PR Tools
  14. Publication and Information Dissemination
  15. Enterprise Collaboration and Knowledge Management

Geographic allocation and the Lisbon clarification

The lot architecture enforces a geographic boundary. Lots 1 and 3 (Brussels and Other Locations) cover service execution in Brussels (Belgium), Strasbourg (France) and Lisbon (Portugal), explicitly excluding Luxembourg. Lots 2 and 4 cover service performance delivered within Luxembourg-based institutional facilities and local near-premises sites.

Lisbon is included because of the operational footprint of the European Union Drugs Agency (EUDA). Its administrative purchasing address is listed under DG ITEC in Luxembourg, but its core technical environment and operational teams are in Lisbon.

Geographic separation and sourcing strategy

The division between Brussels, Strasbourg and Lisbon on one side and Luxembourg on the other forces tenderers to build tailored recruitment, pricing and infrastructure strategies. The Luxembourg labour market has higher local labour rates, specialised cross-border commuting patterns and competitive sourcing dynamics compared with Brussels or Lisbon.

Consortia must therefore build delivery models that use near-premises delivery centres in both Brussels and Luxembourg, and secure local candidate pipelines in Lisbon to support EUDA systems without driving up overall cost.

How Does the Two-Lot Award Cascade Work?

To prevent vendor lock-in, preserve competition and keep operational redundancy, DG ITEC set explicit bidding limits. Economic operators, whether sole bidders or consortia, may submit bids for all four lots. A single tenderer can be awarded a maximum of two.

Because of that ceiling, the Contracting Authority set a mandatory, chronological evaluation sequence for awarding contracts:

  1. Step 1: Lot 4 (Supporting and Steering Business Systems, Luxembourg) is awarded first.
  2. Step 2: Lot 2 (Core Business Systems, Luxembourg) is awarded second.
  3. Step 3: Lot 3 (Supporting and Steering Business Systems, Brussels and Other) is awarded third.
  4. Step 4: Lot 1 (Core Business Systems, Brussels and Other) is awarded fourth.

How many lots can one tenderer win in ITS26-DEV?

A maximum of two, even though a tenderer can submit bids for all four.

Lots are awarded in a fixed sequence: Lot 4, Lot 2, Lot 3, Lot 1. If a tenderer ranks among the top three winning bids in both Lot 4 and Lot 2, it reaches the two-lot ceiling. Even with the highest overall score in Lot 3 or Lot 1, it is then legally disqualified from those lots, and the contract cascades to the next highest-ranked eligible bidder.

When a bidder reaches the two-lot ceiling in earlier steps, it is automatically eliminated from winning the lots that follow in the sequence.

Strategic bidding scenarios

The forced sequential order creates decision points. Consortia must decide whether to bid across all lots or to target specific opportunities, so that they do not use up their two-lot capacity on lower-priority contracts. The tactical question starts with the primary contract target: the Brussels and Lisbon hub (Lots 1 and 3) or the Luxembourg hub (Lots 2 and 4).

ScenarioLots bidApproachReasoning
A: Direct targeting of Brussels systemsLots 1 and 3 onlyDecline to submit offers for Lots 4 and 2, and bid exclusively on Lots 3 and 1.A tenderer bidding on all four lots that wins Lot 4 and Lot 2 in Steps 1 and 2 is legally eliminated from Lot 3 and Lot 1 at Steps 3 and 4. Bidding only on Lots 1 and 3 carries zero risk of using the two-lot limit in the earlier Luxembourg steps.
B: Luxembourg hub dominanceLots 4 and 2Submit aggressive technical and financial proposals for Lot 4 and Lot 2.These lots are evaluated first and second, so a winning score secures both contracts immediately and uses the tenderer’s maximum two-lot capacity early in the award process.
C: All-lot hedging with calibrated financial proposalsAll four lotsBid on every lot, with highly competitive pricing on target lots and higher margins on non-target lots evaluated earlier in the cascade.Participation is preserved while the probability of an unwanted early award is lowered.

How Are Contracts Awarded, and What Changed During the Tender?

Contracts are awarded on the best price-quality ratio, combining technical quality scores and evaluated financial prices.

On 27 November 2025, DG ITEC issued an official corrigendum correcting two errors in the tender specifications:

  1. Award criteria text (p. 14). The wording was clarified to confirm that contracts are awarded to the tenderer offering the “best price-quality tender, based on the formula of paragraph 16.3.”
  2. Evaluation calculation multiplier (p. 15). A formula error had multiplied estimated person-hours over a 5-year period. The text was updated to 4 years, which aligns the financial evaluation model with the maximum 48-month contract duration.

The procurement timeline ran as follows:

MilestoneDate
Official publication17 November 2025
Corrigendum 1 (formula and wording updates)27 November 2025
Corrigendum 2 and deadline extension notice4 December 2025
Deadline for clarification requests16 December 2025 (portal closed 16 January 2026)
Final submission deadline26 January 2026 at 16:00 CET
Public opening session28 January 2026 at 10:00 CET
Tender validity requirement9 months from the submission deadline

Which Delivery Modes, Security Checks and Profile Standards Apply?

The framework sets operational execution parameters across service delivery modes, technical profile baselines, security clearances and SLA penalties. Services are requested in three execution modes:

  • Time and Means (T&M): technical profiles reimbursed on actual daily or hourly effort.
  • Quoted Time and Means (QTM): deliverable-based task orders executed against pre-agreed time and cost estimates.
  • Fixed-Price / SLA mode: outcome-based project deliverables bound by strict acceptance criteria, excluding off-site fixed-price new development.

Work happens in three contexts: on-premises (direct site access, with Belgian MoU clearance), near-premises (external facilities near the institutional hubs) and off-premises (remote contractor facilities, where the MoU applies).

Baseline work contexts

The technical evaluation specifications set baseline team models (Q&A 83074, 83077, 83078). Work Context 1 has a baseline capacity of 4 FTEs split 50% on-premises and 50% near-premises under QTM mode for application maintenance. Tenderers must show how they would transition this team to a 100% near-premises or 100% off-premises model. Work Context 2 has a baseline application maintenance team of 4 FTEs working full-time under T&M mode.

Security verifications and the Belgian MoU

Under Service Requirements (SR) Section 5.7 and Q&A 83086, security verification protocols apply to all on-site personnel. Under the Memorandum of Understanding between the European Institutions and the Belgian Government, off-premises consultants who access institutional infrastructure, staging environments or internal applications are also subject to formal background security checks.

Profile standards and certification baseline

Project management profiles must hold recognised professional certifications. Q&A 80743 confirms that PM², the European Commission’s project management methodology, is accepted alongside PMI-PMP and Prince2.

Which cloud certifications are accepted for ITS26-DEV cloud engineer profiles?

Intermediate and expert-level vendor certifications. Entry-level foundation certifications are rejected.

Cloud Engineers (PCLE) need expert-level certifications issued by major public cloud vendors. Under Q&A 81275, expired certifications remain valid if the tenderer submits concrete proof of continuous, uninterrupted practical experience with the relevant technology.

Subcontractor and freelancer status. Tenderers may add operational capacity through external experts, but freelancers are classified as subcontractors and have to be declared as such.

Are freelancers treated as subcontractors in ITS26-DEV?

Yes. Freelancers operating as self-employed corporate entities are legally classified as subcontractors under the Financial Regulation.

They must be formally declared in the tender submission, and their parent legal entities must submit the required compliance documentation, such as the ESPD and administrative declarations (Q&A 81767, 83081). A signed Assurance of Undertaking must also be submitted for every declared subcontractor contributing to the tender (Q&A 80986).

What SLA Penalties and Liability Limits Apply Under the ITS26-DEV Framework Contract?

Contract performance is monitored through Service Level Agreements enforced via daily liquidated damages and specific order default mechanisms. The table sets out each indicator, what triggers it and what follows.

IndicatorTriggerConsequenceQ&A ref.
TM-1: interview availabilityA proposed candidate is not available for interview within the established timelines.Liquidated damages of €100 per day of delay. TM-1 cannot be applied retroactively if a candidate is requested after the initial 5-day administrative window expires.83084
TM-2 and TM-4: candidate suitability and unavailabilityA proposed candidate is rejected for non-suitability (TM-2), or becomes completely unavailable during order processing (TM-4).The Contracting Authority may declare an ordering default, and the order can move to the next contractor in the cascade.83085
TM-7: position incident resolutionThe contractor fails to resolve a position performance incident by the specified target date.The Contracting Authority may partially terminate the specific contract.83087
SM-1 and SM-3: request for offer intentionA Request for Offer is issued under QTM or Fixed-Price mode.The contractor must declare its intention to submit an offer within 3 working days, or the order can go to the next cascade contractor.83079 / 83080
Position replacement and handoverA replacement consultant is needed under T&M.The replacement must assume duties within 20 working days. The Contracting Authority’s internal processing window for reviewing replacements and issuing amendments is fixed at 5 working days. The contractor keeps full operational responsibility and covers the cost of structured handover periods.83088 / 83089 / 83090
Framework liability limitationArticle I.10.1 of the Draft Framework Contract.Total accumulated contractor liability is capped at three times the total value of the Framework Contract, as an absolute aggregate cap across the multi-year lifecycle and not a recurring limit per specific contract.81483 / 81766

What happens if a contractor does not confirm intent on a request for offer within 3 working days?

The Contracting Authority can immediately issue the order to the next contractor in the cascade.

Under indicators SM-1 and SM-3, once a Request for Offer is issued under Quoted Time and Means or Fixed-Price modes, the contractor must formally declare its intention to submit an offer within 3 working days (Q&A 83079). If it does not, the order can pass straight to the next cascade contractor (Q&A 83080).

Operational risk mitigation

Daily liquidated damages under TM-1, strict candidate suitability assessments under TM-2, 3-day offer intention deadlines under SM-1, partial termination risk under TM-7 and a liability cap of three times the framework value add up to tangible operational exposure. Consortia need active bench management protocols to prevent candidates dropping out during the ordering stages.

Bidders must also verify freelancer legal classifications, ensure diploma equivalencies (or obtain formal university declarations where original diplomas are unavailable), and keep active track of vendor certifications to prevent disqualifications during task order execution.

How Is the Financial Price Evaluated?

Financial scoring converts proposed maximum hourly rates into a single evaluated financial price, which feeds directly into the final award ranking. The model in Section 16.3 of the Tender Specifications is:

Evaluated price = sum, for every profile p from 1 to n, of (hourly rate of p x estimated person-hours of p over the 4-year horizon x global price multiplier of p)

  1. Labour categories and hourly rates. Bidders submit binding maximum hourly rates for all standardised technical profiles and seniority levels (for example Junior, Experienced, Senior, Expert) detailed in the tender documents.
  2. Duration multiplier correction. After the 27 November 2025 corrigendum, the person-hours multiplier is fixed to a 4-year horizon (48 months), correcting the initial 5-year calculation error.
  3. Global price multipliers. Weighting multipliers apply across profile categories and delivery modes (T&M, QTM, Fixed-Price) so that the price evaluation reflects projected institutional demand over the framework lifecycle.

Financial engineering against operational risk

Lower hourly rates raise the financial evaluation score, but margin compression that cannot be managed creates operational risk over a 48-month contract.

Aggressive rate discountingBalanced commercial pricing
Higher financial evaluation score.Competitive financial score.
Risk of unviable delivery margins in high-cost labour markets.Preserves operational margin for local recruitment.
Vulnerable to SLA penalties, for example €100 per day under TM-1.Absorbs handover costs and SLA liquidated damages.
High turnover risk under the 20-day replacement rules.Maintains a stable resource bench over the 48-month lifecycle.

Aggressive rate discounting removes the commercial room needed to absorb mandatory handover costs, 20-day replacement timelines and daily SLA penalties. Because total liability is capped at three times the aggregate framework contract value, proposed hourly rates need to be calibrated against local labour market realities in Brussels, Luxembourg and Lisbon, so that the contract stays commercially viable across the full four-year term.

What Does a Compliant ITS26-DEV Bid Package Look Like?

Securing a position takes careful administrative execution, precise consortium structuring and strict adherence to the submission guidelines.

Consortium structuring and financial forms

  • Consortia without a dedicated corporate structure must select “Group of Economic Operators WITHOUT Legal Entity” in Form 7a and enter the consortium name in the Organization field (Q&A 80804).
  • For Form 8 (Financial Data Sheet), Option C, a consolidated framework summary, is formally sufficient for the entire group, and all members sign it (Q&A 81044).
  • All members of a group of economic operators assume joint and several liability for contract execution.

Capacity providers and technology vendor alliances

If a tenderer relies on technology vendor alliances, such as public cloud provider partner tiers, to meet the selection criteria, those external entities must be formally declared as Capacity Providers (Q&A 82246). Bidders must submit formal Capacity Provider Declarations together with signed Letters of Intent (Form 4). Listing commercial alliance tiers without formal capacity declarations results in technical non-compliance.

Freelancer, subcontractor and CV rules

  • External consultants, independent contractors and freelancers are legally classified as subcontractors (Q&A 81767).
  • A signed Assurance of Undertaking must be submitted for every declared subcontractor contributing to the tender (Q&A 80986).
  • Profile CVs must express software experience in decimal values, such as 3.5 years, and state the date of the last experience update (Q&A 80847, 80848).
  • Physical copies of training attendance certificates are not required at submission unless a certification is explicitly mandatory for the profile, as with Cloud Engineers or Project Managers (Q&A 80846).

Pre-submission readiness checklist

Before uploading the final bid package to the eSubmission portal, tenderers had to complete these compliance audits:

  • ✓Active EU Login credentials and eSubmission portal access are confirmed well before the deadline (cftUuid: 4c735404-7ba5-4728-861a-7ec89d4b7e88).
  • ✓Submission is executed before 26 January 2026 at 16:00 CET.
  • ✓Completed ESPDs are in place for all consortium partners, declared subcontractors and capacity providers.
  • ✓Form 4 (Letter of Intent) shows the exact legal name of the tenderer or group of economic operators, and Form 7a accurately specifies the joint bidding structure (Q&A 80874).
  • ✓Mandatory certifications are verified (PCLE Cloud Expert, PM², PMP or Prince2). Where a physical diploma is unavailable, an official confirmation declaration from the degree-granting university is attached (Q&A 82555).
  • ✓Technical response documents observe the word-count limits, counting all text in embedded tables, graphs and diagrams, numerical figures and single-letter RACI entries (Q&A 82591).
  • ✓Every freelancer is classified as a subcontractor, with complete CVs, diplomas and a signed Assurance of Undertaking collected.
  • ✓Profile CVs express software experience in decimal values, such as 3.5 years, and state the date of the last experience update (Q&A 80847, 80848).

A large share of these checks come down to the same data: CVs with decimal experience and an update date, diplomas and certifications on file, freelancer status and legal entity affiliation. Teams that keep this data structured in one place, for example in an Enterprise CV Manager, can answer a request for offer inside a 3-working-day window without rebuilding profiles each time. Consortia that need every consultant to follow one agreed layout can look at standard CV templates, and consulting teams working through several of these requirements at once can read more about CV management for consulting companies.

Frequently Asked Questions

What is the ITS26-DEV framework contract?

ITS26-DEV (EP-ITEC/LUX/2025/OP/0003) is the European Parliament’s open procedure for the development and maintenance of information systems, led by DG ITEC under Regulation (EU, Euratom) 2024/2509. It is a multi-vendor framework contract without reopening of competition that serves eight EU institutions, bodies and agencies for up to 48 months.

How many lots are in ITS26-DEV and how are they split?

There are four lots. Lots 1 and 2 cover core business systems, and Lots 3 and 4 cover supporting and steering systems. Lots 1 and 3 cover service delivery in Brussels, Strasbourg and Lisbon, and Lots 2 and 4 cover Luxembourg. Each lot can have up to three awarded contractors.

How many lots can one company win in ITS26-DEV?

A single tenderer can bid on all four lots but can be awarded a maximum of two. Lots are awarded in the order Lot 4, Lot 2, Lot 3, Lot 1, so a tenderer that wins Lot 4 and Lot 2 is disqualified from Lot 3 and Lot 1.

What are the SLA penalties in ITS26-DEV?

Interview delays under TM-1 incur liquidated damages of €100 per day. Candidate rejection or unavailability under TM-2 and TM-4 can lead to an ordering default, and failing to resolve an incident by the target date under TM-7 allows the Contracting Authority to partially terminate the specific contract. Contractors must also declare intent on a Request for Offer within 3 working days.

Are freelancers subcontractors in ITS26-DEV?

Yes. Freelancers operating as self-employed corporate entities are legally classified as subcontractors under the Financial Regulation. They must be declared in the tender submission, and a signed Assurance of Undertaking is required for every declared subcontractor.

What is the liability cap in the ITS26-DEV framework contract?

Article I.10.1 of the Draft Framework Contract caps total accumulated contractor liability at three times the total value of the Framework Contract. Q&A 81483 and 81766 confirm it is an absolute aggregate cap across the multi-year framework lifecycle, not a recurring limit per specific contract.

Final Thought

A position on the ITS26-DEV framework contract establishes a four-year commercial footprint for software engineering services across eight European institutions. Keeping that footprint depends on how cleanly a consortium answers each order: intent declared within 3 working days, candidates available for interview on time, and replacements in place within 20 working days.

Reading the incumbent trends, managing the sequential award cascade, building SLA controls into the delivery model and keeping the administrative file compliant are the things that put prime contractors in a good position for the long term in European public sector IT.

A request for offer gives you 3 working days to confirm intent, and a replacement consultant has 20 working days to take over.

If your consortium is preparing for the pace of ITS26-DEV task orders, we can walk through how CVs, certifications, diplomas and experience dates can be organised before the clock starts.

Book a demo with Marco Pincho

Marco Pincho

Sobre el autor

Marco Pincho

Founder and CEOLinkedIn

Marco has more than 20 years of experience in the consulting industry, focusing on process automation, data management, and operational efficiency. In 2018, he founded Sprint CV after identifying the challenges consulting companies face in managing employee skills and CVs, and responding to tenders.

Today, Sprint CV helps more than 70 consulting companies across Europe, including VASS Group, Fujitsu, Almaviva, Cronos Europa, and Sword Group, automate and optimise CV management and respond faster to business opportunities.