How to write a methodology section for an EU tender

What evaluators look for in the methodology

Before considering structure, it helps to understand what evaluators are actually doing when they read a methodology section. They are working through the evaluation grid, sub-criterion by sub-criterion, asking: does this offer demonstrate the attribute this sub-criterion describes, and how well? They score on the evidence in front of them, not on assumptions about the organisation's capability.

The sub-criteria for the methodology or technical approach criterion in INTPA and NEAR tenders typically assess some combination of:

• Understanding of context: Does the methodology show that the team understands the specific situation on the ground, the key constraints, and the stakeholder dynamics, rather than applying a generic sector framework?
• Coherence with the ToR: Does the proposed approach address the tasks and deliverables specified in the Terms of Reference, in a sequence and manner that is feasible given the timeline and resources?
• Technical soundness: Is the methodology credible from a technical standpoint? Does it apply appropriate tools, frameworks, and analytical approaches for the type of work required?
• Innovation: Does the approach offer anything substantively better than the standard method? This is not scored for novelty; it is scored for demonstrated improvement in outcome.
• Risk awareness: Does the methodology identify the real risks to delivery and propose credible mitigation measures, or does it present an idealised project scenario?

Generic methodology sections fail because they demonstrate none of these at a specific level. They describe what the team will do (stakeholder consultations, capacity building, monitoring and evaluation) without explaining how, for whom, under what constraints, and with what expected result in this specific contract context. Evaluators read these sections quickly, find no scoreable evidence, and assign the minimum or a score just above it.

How to structure the methodology section

There is no single mandated structure for EU technical proposals, but a proven structure for technical assistance contracts follows the logical progression of project design: from understanding of the problem through technical approach to operational planning. A structure that consistently supports strong scoring:

1. Situation analysis and understanding of context: Analysis of the situation in the specific country, sector, and institutional environment covered by the contract. This section should reference specific data, reports, or contextual factors identified in the ToR or through pre-bid research.
2. Technical approach: The core methodological response to the ToR. Explain the approach taken, why it is the right one for this specific context, and how it compares to or improves on standard approaches. Sub-divide by workstream or phase if the contract has distinct components.
3. Intervention logic: For development cooperation contracts under INTPA and NEAR, the intervention logic or logframe maps the causal chain from inputs and activities through outputs and outcomes to the intended impact. This section demonstrates results-orientation and is often a specific evaluation sub-criterion.
4. Work plan: A phase-by-phase or work-package description of how the methodology will be implemented. Includes key activities per phase, estimated timelines, and how phases link to the deliverables specified in the ToR. A Gantt chart should follow or complement the narrative.
5. Quality assurance: The internal review and quality control processes that will apply to deliverables. Specific to this contract, not a copy of the organisation's corporate QA policy.
6. Risk identification and mitigation: The main risks to delivery, assessed by likelihood and impact, with specific mitigation measures. Risks should be genuine, not generic (not "risk of delays" without specifying what kind of delay, why it is a risk in this context, and what would be done).

The section headings should use language from the evaluation grid where possible. If the evaluation grid labels a sub-criterion "coherence of technical approach with the objectives of the ToR", a section heading that includes those words or near-equivalents helps evaluators locate the relevant content quickly. This is not gaming the system; it is making the evaluator's job straightforward, which is what the strongest bids do.

Writing to the evaluation sub-criteria

Writing to the evaluation criteria means more than organising the document to match the grid structure. It means ensuring that within each section, the text provides explicit evidence of the attribute being scored, not implied evidence. Evaluators cannot add points for what they infer; they can only score on what is stated.

A practical discipline: before finalising each section, open the evaluation grid and read the sub-criterion it corresponds to. Ask: if I am an evaluator scoring this sub-criterion, does this paragraph give me enough specific, verifiable content to award a high score? If the answer is "probably", revise until it is "yes".

Three specific writing practices that consistently improve scores:

Reference the ToR explicitly

When your methodology addresses a specific requirement from the Terms of Reference, say so. "As specified in section 3.2 of the ToR, the capacity needs assessment will cover all five directorates identified by the contracting authority" is more scoreable than the same assertion without the ToR reference. It demonstrates that the team has read the ToR and is responding to it, not writing a general proposal and mapping it to the contract description later.

Use numbers and specifics

Methodology sections that use specific numbers, names, tools, and timeframes are consistently scored higher than those that rely on qualitative descriptions. "We will conduct stakeholder consultations" leaves the evaluator with nothing concrete to assess. "We will conduct structured key informant interviews with approximately 30 stakeholders across four categories, using the semi-structured interview protocol described in Annex 2, during the first six weeks of implementation" gives the evaluator verifiable specifics on scope, method, and timeline that they can score against the sub-criteria.

Explain the reasoning, not just the activity

Evaluators score technical approach on the quality of thinking behind it, not just on the description of activities. For each significant methodological choice, include a brief explanation of why that choice is appropriate for this specific context. "The phased training design, with consolidation workshops between cycles, is based on evidence from comparable public financial management reform programmes in the region, where single-cycle training showed low retention rates at the six-month mark. The multi-cycle approach has demonstrated higher competency transfer in contexts with high staff turnover in the beneficiary institution." This is scored differently from "we will use a phased training approach".

Before and after: weak versus strong methodology paragraphs

The contrast between generic and specific methodology writing is more visible at the paragraph level than in any description. The examples below show the same content area handled weakly and strongly for a public administration reform technical assistance contract.

Example 1: Stakeholder engagement approach

Example 2: Capacity assessment approach

The weak examples describe intent. The strong examples describe the specific method, the specific scope, the specific tools, and the link to ToR deliverables. An evaluator scoring "comprehensiveness of the capacity assessment approach" has concrete, verifiable evidence in the strong example and almost nothing in the weak one.

Intervention logic and logical frameworks in development cooperation tenders

For contracts funded under INTPA and NEAR development cooperation instruments, familiarity with results-based management frameworks is expected. The logical framework (logframe) is the standard planning tool used by the European Commission to design, monitor, and evaluate programmes. Many INTPA and NEAR tender dossiers either require a logframe or an intervention logic narrative as part of the technical offer, or include it as a specific scoring sub-criterion.

The logframe maps a causal chain:

• Inputs: resources the project brings (expert days, budget, tools)
• Activities: what the team does with those inputs (consultations, training, technical support)
• Outputs: direct, verifiable products of the activities (reports, trained staff, approved legislation)
• Outcomes: medium-term changes in behaviour, capacity, or systems attributable to the outputs
• Impact: the long-term development change to which the contract contributes, typically shared with other interventions

At each level, a well-constructed logframe identifies assumptions (conditions outside the project's control that must hold for the causal link to work) and risks (factors that could prevent the link from holding). The assumptions and risks section of the methodology, when it reflects this framework, demonstrates to evaluators that the team is thinking about delivery realistically, not optimistically.

Even when a formal logframe is not required, presenting the intervention logic in a structured way, showing the chain of change from activities to outputs to outcomes, strengthens the methodology score for the "coherence of approach" and "results orientation" sub-criteria. INTPA programme managers who serve as evaluators or technical assessors are trained to think in logframe terms; a methodology that speaks that language will be read more easily and scored more generously than one that does not.

Work plan formats and managing page limits

The work plan translates the methodology into an operational schedule. It should show, for each phase or work package, the key activities, the expected timeline, the responsible team member or role, and the link to the ToR deliverables. A work plan that maps to the deliverable structure in the ToR is more useful to evaluators than one organised around the bidder's internal phases, which may not align with the ToR's delivery milestones.

Gantt charts

A Gantt chart communicates timeline and dependencies visually and concisely. For contracts over 12 months, a Gantt is almost always necessary: narrative descriptions of a 24-month implementation sequence are difficult to read and verify. A well-structured Gantt should show activities per work package, key deliverable milestones, and any dependencies between workstreams. Keep the Gantt at a level of detail that is legible at A4 or letter size; a chart with 50 activity rows in 8-point font communicates nothing and will be ignored.

Narrative work plans

A narrative work plan explains the sequencing rationale, the assumptions behind the timing, and how the phases connect. For contracts with complex inter-dependencies between workstreams, or where the sequencing of activities is a substantive methodological choice, the narrative work plan is where that reasoning is made explicit. In most strong bids, the narrative work plan and the Gantt complement each other: the narrative explains the logic, the Gantt summarises the timeline.

Managing page limits

Most INTPA and NEAR technical offers have a total page limit of 30 to 80 pages, with the methodology and approach section typically accounting for 15 to 25 pages. When the page allocation is tight, prioritise depth on the highest-weighted sub-criteria. If methodology and approach carries 40 points and quality assurance carries 10, the allocation of page space should roughly reflect that ratio. Distributing pages equally across a low-value section that cannot be meaningfully differentiated and a high-value section that can be is a common structural mistake in EU proposal writing.

Where a page or word limit forces cuts, cut from sections that are unlikely to differentiate the score: general background context that the evaluator already knows, corporate capability statements that belong in the cover letter rather than the methodology, and generic risk matrices with risks that apply to every contract in the sector. Every page and paragraph in the methodology should be there because it adds to the score, not because it adds to the sense of completeness.

Frequently asked questions