Who You Work For on an EU Assignment—and Why It Matters

23 september 2026· Uncategorized

The institution may direct the work. It does not become your employer.

An EU-institution assignment can feel straightforward on day one: a project manager sets priorities, a team includes institutional staff, timesheets require their approval, and the work is delivered inside the institution’s environment. That operational reality leads to one expensive misunderstanding: assuming that the institution is the party you work for in the contractual sense.

Usually, it is not. The contractual chain runs from the contracting authority to the framework contractor, then potentially through a subcontractor or staffing partner, and finally to the consultant delivering the IT or AV work. Each link has a different responsibility. If you do not map those links before signing, routine matters such as time reporting, scope changes, replacement, onboarding issues and assignment continuity can become needlessly unclear.

The right approach is to separate who receives and assesses the work from who holds authority over your engagement. The first may be an EU project manager. The second sits within the contractor chain. That distinction is not administrative trivia; it is the foundation for handling the assignment correctly.

Map the chain → identify authority → confirm reporting rules → avoid working outside the contract

The assignment chain: four parties, four different roles

For a prime contractor, subcontractor, EU institutions consultant arrangement, the names of the organisations may vary, but the logic remains consistent. The institution procures services. The prime contractor is accountable for providing them. Other businesses may perform part of the work under a subcontracting or staffing arrangement. You deliver the work within that approved structure.

Party	Primary role in the assignment	What that role does not automatically mean
Contracting authority or EU institution	Defines the requirement, manages the assignment and may approve work or monthly timesheets through an authorised project contact.	It does not automatically become the consultant’s employer or contractual counterparty.
Prime contractor	Holds the framework-contract relationship and remains responsible for the personnel performing the services.	It may not be the business that signed the consultant’s individual employment or service agreement.
Subcontractor or staffing partner	May have a legal commitment with the prime contractor to perform part of the assignment and may be the consultant’s direct contractual counterparty.	Its involvement cannot be treated as informal if the contract requires declared or authorised subcontracting.
Consultant or consultant’s staff	Delivers the agreed IT or AV services, records time where required and works within the approved staffing arrangement.	Working on-site or inside institutional systems does not create an employment or contractual relationship with the institution.

The key point is simple: the party whose badge, systems, project meetings and approvals dominate your day is not necessarily the party that manages your contractual relationship. The European Commission’s model framework service contract places responsibility for personnel with the contractor and states that the contractor exercises authority over that personnel without interference from the contracting authority.

That is why the question “who employs an EU IT consultant?” needs a more precise answer than “the institution” or even “the prime contractor.” Your direct contractual counterparty may be the prime contractor, a declared subcontractor or a staffing partner. The institution is the contracting authority for the service, not automatically the employer of the individual consultant.

Start with the documents, not the organisation chart

The mistake I see most often is trying to understand an assignment from titles alone: “client,” “manager,” “supplier,” “team lead” and “consultant.” Those labels are useful operationally, but they do not settle the contractual position. The documents do.

Before committing to an assignment, establish which documents govern the role and how they connect. The framework contract sets the wider relationship. The specific contract defines the work for the assignment. Tender specifications can set the required expertise and staffing conditions. Special conditions may add assignment-specific rules. Your own employment, consultancy or service agreement identifies the company with which you personally contract.

Your direct agreement: identify the legal entity that engages you and handles your contractual relationship.
The framework and specific contract position: identify the prime contractor and the assignment that sits under the framework.
The staffing route: establish whether a subcontractor or staffing partner stands between the prime contractor and you.
The approved role: confirm whether you are named as key personnel, listed in the budget or staffing plan, or added as other staff used for the tasks.
The reporting route: identify the institutional contact who accepts deliverables or approves time, alongside the contractor contact responsible for staffing and administration.

Do not rely on verbal shorthand such as “you will report directly to the institution.” It may describe the working environment, but it does not replace the formal chain. A strong staffing arrangement makes the formal chain easy to explain in one sentence: “I contract with this entity; it supports this prime contractor; the institution’s project manager approves this work under this specific contract.”

Step 1: Identify your contractual counterparty

Why this matters: The entity named in your agreement is the first point of reference for engagement matters. It is the organisation that should explain the terms of the role, administer the consultant relationship and coordinate issues up the delivery chain. If a staffing partner employs or contracts you, the fact that the prime contractor holds the framework does not erase that direct relationship.

Subcontracting has a specific meaning in a framework-contract context: the contractor enters legal commitments with another entity to perform part of the contract. This is more than introducing a candidate or passing on a CV. It is a defined delivery relationship. In relevant EU external-action framework arrangements, subcontracting must be declared, and subcontractors involved in the assignment must meet the eligibility rules applicable to that contract.

What to do: Ask for the contractual route in plain language and record the answer alongside the entity named in your own agreement. The most useful result is not a long corporate explanation. It is a clear map showing who contracts with whom and who is responsible for each level.

Where this goes wrong: A consultant assumes the prime contractor is their employer because it appears on project documents, while a staffing partner is actually the direct contractual counterparty. The reverse also happens: a consultant treats the staffing partner as the only relevant party and does not understand that their role must fit the prime contractor’s approved staffing commitment.

The judgment call: Treat the institution as the project environment, the prime contractor as the accountable service provider, and your direct contracting entity as the party handling your individual engagement. Keep all three distinct unless the paperwork shows that one entity fills more than one role.

Step 2: Separate project reporting from personnel authority

Why this matters: IT and AV consultants need practical direction to deliver useful work. There will be project priorities, technical constraints, access requirements, deliverables and acceptance discussions. None of that changes the contractor’s responsibility for its personnel.

The framework service contract model is explicit on the principle: contractor personnel must be informed that they may not accept direct instructions from the contracting authority, and their work does not create an employment or contractual relationship with that authority. This is where people tend to oversimplify. It does not mean the consultant ignores the project manager. It means the institutional project manager’s role in managing the assignment must not be confused with authority over the consultant’s employment or contractual engagement.

In practice, project-level direction and approval should sit alongside a contractor-managed route for staffing, contractual changes, absence, replacement, performance concerns and matters that affect the consultant’s engagement. If an institutional contact asks for something that changes the agreed role, staffing level, delivery scope or assignment period, the contractor chain needs to be involved rather than leaving the consultant to negotiate the change alone.

Project manager or authorised institutional contact: confirms what has been delivered, may validate reported time and manages the assignment from the contracting authority’s side.
Prime contractor delivery contact: remains accountable for delivery and should manage the relationship with the contracting authority.
Direct employer or contracting entity: manages the consultant’s individual contractual relationship where it is not the same as the prime contractor.
Consultant: delivers the agreed services, keeps records accurately and escalates engagement changes through the contractor route.

Do not do this: treat an institutional request as a private instruction that bypasses the contractor. That shortcut can create confusion about authorisation, scope and accountability. The better move is to keep the contractor contact informed whenever a request affects more than ordinary delivery coordination.

Step 3: Understand what timesheet approval proves — and what it does not

Timesheets are often the moment when reporting lines look most like employment. A consultant completes time records, an institutional project manager approves them and the record supports the contractor’s charge for work delivered. It is easy to read that approval as proof that the approver is the consultant’s manager in every sense. It is not.

Under the model framework service contract, the contractor maintains timesheets for its personnel. Timesheets are approved monthly by the project manager, another person authorised by the contracting authority, or the contracting authority itself. Fee-based contract guidance also expects staff to complete and sign their own timesheets, acknowledging responsibility for the entries, before approval takes place.

That creates a three-part control:

The consultant records and signs the time because the consultant is responsible for the accuracy of the entry.
The contractor keeps the timesheet record because it is responsible for the personnel and for charging time under the contract.
The project manager or authorised institutional person approves the time monthly because the contracting authority needs to confirm time connected to the assignment.

The approval is an administrative control on reported effort. It confirms neither an employment relationship nor a direct contract between the consultant and the institution. The same distinction applies even where the project manager has close visibility of the work.

Accuracy matters. The model contract ties chargeable time to the implementation period of the specific contract, requires it to relate to personnel named in the specific contract budget and prohibits double charging in earlier financial reports or invoices. A timesheet cannot repair a staffing mismatch after the fact.

Practical safeguard: confirm the full approval sequence before work begins. The governing documents may require monthly institutional approval, while the contractor may also operate an internal review before submission. There is no single universal EU timesheet platform or identical workflow across every institution and programme. The applicable specific contract controls the route.

Step 4: Establish whether the assignment is fee-based or global price

Why this matters: Not every framework arrangement uses timesheets in the same way. In the external-action framework guidance, fee-based contracts involve staff-time records and monthly approval. Global-price specific contracts operate differently: the cited rules state that there is no expenditure verification, no timesheet verification and no verification of incidental expenditure.

This does not make time records irrelevant to a consultant’s own organisation. It means the contract’s external verification logic differs. The common mistake is applying fee-based timesheet assumptions to a global-price assignment, or assuming that every EU assignment has the same monthly sign-off mechanism.

Confirm the commercial structure only to understand reporting and staffing controls. The important operational question is whether the assignment is measured through verified staff time, agreed deliverables, or another contract-specific mechanism. That answer affects how the consultant documents work and how the contractor demonstrates performance.

Step 5: Treat key-personnel status as a contractual commitment

“Key personnel” is frequently misunderstood as a flattering title or an internal seniority label. In EU consultancy and framework-contract language, it is more consequential than that. A key expert or key person is named in the contract or approved staffing setup. Their identity, qualifications and role form part of the basis on which the assignment is delivered.

Specific contracts can stipulate the tasks, timetable, estimated budget, human resources allocated, list of experts and, where needed, required reports. The contractor must ensure that personnel implementing the framework contract, including replacement personnel, have the qualifications and experience required by the tender specifications.

For the consultant, key-personnel status has three practical consequences:

Your name and profile may be part of the approved delivery arrangement. The role is not simply an internal deployment decision.
Replacement is controlled. A contractor cannot treat a named expert as interchangeable with any available resource, particularly where the contract requires approval or imposes qualification requirements.
Role changes need discipline. Moving a key person to a materially different function, adding staff or substituting personnel may require action through the formal contract structure.

Non-key staff should not assume they sit outside all contractual controls. Guidance requires the consultant to inform the contracting authority of staff used for the tasks beyond the named key experts. The distinction is therefore not “key staff matter, everyone else does not.” It is that named key personnel face a more direct contractual link to the approved staffing package.

There is no single EU-wide definition that applies unchanged across every institution or programme. The role must be read in the tender, framework contract and specific contract governing the assignment. That is the only reliable interpretation.

Step 6: Get these points clarified in writing before signing

A clean answer to the following points prevents most chain-of-command problems. Do not accept vague phrases such as “the client handles that” or “the project will explain it later.” Staffing governance is easiest to fix before the engagement starts.

Who is the direct contractual counterparty? Confirm whether it is the prime contractor, a subcontractor or a staffing partner.
Which organisation holds the framework contract and which specific contract covers the assignment? This identifies the accountable prime contractor and the defined work package.
Is the consultant key personnel or non-key staff? Confirm whether the role, name, qualifications and replacement arrangements are part of the approved contract package.
Is the consultant named in the staffing list or specific-contract budget? Chargeable work time is linked to the personnel named for the specific contract in the model framework rules.
Is the assignment fee-based or global price? This affects the contract’s approach to timesheet and expenditure verification.
Who completes, maintains, reviews and approves time records? Establish the consultant’s signature requirement, the contractor’s record-keeping responsibility and the institutional approval route.
Who is authorised to approve time monthly? Confirm whether that person is the project manager, another authorised person or the contracting authority itself.
Is the subcontracting or staffing route declared and authorised where required? The framework model restricts implementation by third parties beyond those mentioned in the tender without prior written authorisation.
Which contact handles changes to scope, duration, staffing or role? The answer should sit within the contractor chain, not rest solely with the consultant and an institutional project contact.

Troubleshooting the failure points that create real risk

The institution asks for a material change to the role

Do not handle a change in isolation. A request for different responsibilities, additional staffing, replacement or a revised delivery commitment may affect the specific contract and approved personnel arrangement. Inform the contractor delivery contact and your direct contracting entity so the request is handled through the correct chain.

A project manager has approved time, but the contractor disputes the record

Institutional approval is an important control, but the contractor remains the record-keeper for time charged under the framework arrangement. Retain accurate entries, ensure they relate to the correct implementation period and make sure the time is connected to the approved assignment. Approval cannot validate time that is outside the contract period, unrelated to the named staffing setup or already charged elsewhere.

You are described as key personnel only after the assignment begins

Ask for the role’s contract status and the implications for qualifications, named staffing and replacement. Key-personnel status should not remain a loose project label. The relevant tender and contract documents determine whether the consultant is a named expert and what controls apply.

The staffing partner says the prime contractor will deal with everything

The prime contractor is accountable to the contracting authority, but that does not remove the direct contracting entity’s responsibility for its relationship with the consultant. Keep the lines clear: your direct counterparty manages the individual engagement; the prime contractor manages contract delivery; the institution manages the assignment from the contracting authority side.

The advanced move: keep two maps, not one

The most effective consultants maintain two simple maps throughout the assignment.

The contractual map: contracting authority, prime contractor, subcontractor or staffing partner, direct contractual counterparty, specific contract and approved staffing status.
The delivery map: project manager, technical lead, authorised timesheet approver, contractor delivery manager and escalation contact.

These maps may include some of the same people or organisations, but they answer different questions. The contractual map tells you where authority and responsibility sit. The delivery map tells you how work gets done. Conflating them is what turns a normal assignment issue into a chain-of-command problem.

Done well, this approach gives the consultant a professional operating position from the start: the institution receives and assesses the service; the contractor chain remains responsible for the people delivering it; approved staffing and accurate reporting support the contract; and changes are escalated through the party with authority to manage them.

The essential points to carry into the assignment

The EU institution is the contracting authority and project environment; it is not automatically the consultant’s employer or contractual counterparty.
The prime contractor remains responsible for the personnel performing the service under the framework arrangement.
A subcontractor or staffing partner may be the consultant’s direct contractual counterparty, but its role must fit the approved delivery chain.
Project-manager approval of a monthly timesheet validates reported effort for the assignment; it does not create an employment relationship.
Key-personnel status means the consultant is part of the approved contractual staffing setup, not merely a preferred resource.
The framework contract, tender specifications, special conditions and specific contract — not informal project language — determine what the role permits.