8 min read

Work packages are both the backbone and building blocks of any Horizon 2020 project. The work package structure is the means through which the concept presented in the project proposal is realized. In other words – first we explain what it is that we want to achieve by outlining the project objectives and the suggested concept. Once this is established, we turn to explaining how we are going to achieve this by planning a tangible work-plan, in the form of work packages that breakdown the different tasks, deliverables, and milestones. So how can you ensure your work packages in Horizon 2020 are both impressive for the evaluation phase and feasible for execution? In this article we will define the role of the Work Package and offer our top tips for constructing a solid work packages plan.

The roles of work packages in Horizon 2020 proposals 

Before we dive deep into our top tips for successful structuring of work packages, let us first thoroughly understand their role in the Horizon 2020 project and its proposal.

The work packages (WP) structure in Horizon 2020 project proposals has two very important roles:

  1. During the evaluation phase: The WPs structure enables the experts reviewing the application to assess the work involved in the project in terms of logic, relevance, collaboration, coherence, effectiveness, competitiveness, innovation, etc. Importantly – the WPs presentation is in fact a primary justification for the requested grant. Therefore it is of utmost importance to make it as competitive as possible (while still possible for execution).
  2. During the execution phase: Once a project proposal is selected for funding, the proposal text becomes an annex to the Grant Agreement, as the plan for execution. The tangible work packages, tasks, deliverables, and milestones turn to be contractual obligations of the partners (the beneficiaries to the grant). This means that it’s crucial to have a good work packages structure in place. It is in the best interest of the Horizon 2020 project that the work plan will be logical and easy to manage during the project’s lifetime.

**Important note – many applicants, during the proposal development phase, are so keen on presenting the most competitive project structure that they tend to neglect the fact that this work-plan must actually be executed. Read all about how to “Ensure competitiveness and feasibility” for the Horizon 2020 project for more information.

Having understood the roles of the work packages in Horizon 2020, let us turn to our top tips for structuring them successfully.

Tip #1: Work package(s) in Horizon 2020 derive from the project’s Concept

The WPs are used to realize the concept of the project, and not the other way around. The typical mistake that we see in many applications is the natural attempt to first develop the WPs before establishing the proposed project’s concept. This happens due to various, yet common reasons:

  • Many times, the big picture (the project’s Concept) does not exist (or it is only half-baked) at the beginning of the project development process. In severe cases, this big picture is not fully developed even at the later stages of the proposal development.
  • Even when there is a big picture – many project partners usually tend to see and focus only on their part of the project, and not the entire picture.
  • Many applicants “play it by ear”, meaning – they are working to recruit new partners and then adjust the proposal according to the inputs from these new partners, even at the cost of significant deviation from the original big picture (assuming there is one). Generally, this practice is not recommended as it will not yield the best results (read more on this issue in “Don’t bring your friends to Horizon 2020 projects”)

To summarize –  developing a Horizon 2020 project from the work packages up is not a recommended practice. While it is a much more demanding task to work from one holistic, comprehensive project’s concept to the detailed and tangible work packages, it is by far the recommended option. Therefore, as a rule of thumb, make sure to follow the inner logic by addressing and establishing the project’s Concept first (in section 3.1), and only based on that develop the work packages.

Tip #2: Linking the work packages back to the project’s objectives and concept

As we stressed earlier, the work packages should be derived from the project’s concept, which in turn is derived from the project’s objectives.

When comes the time to construct the project plan and lay down the work packages structure, it is important to also make it clear to the reviewer how this work plan is actually serving the project’s concept and objectives. For that matter we should illustrate a clear link back to section 1.1 (Objectives) and section 1.3 (Concept and approach).

The best place to address this is in the work plan overview, at the beginning of section 3.1. The way to do that is by adding a table or any kind of efficient illustration (e.g. PERT diagram) that links each work package (or a combination of work packages) to the relevant objective(s) (listed in section 1.1) and/or any main conceptual aspect(s) (presented in section 1.3). The links can be one-to-one, or one-to-many, or many-to-one, or many-to-many, as needed. This table or illustration should be accompanied by text that will explain these links.

When doing so, make sure that the work plan presentation is clear and smooth with no gaps or unwanted overlaps. This will convey a very powerful message to the reviewer about your project, and will leave a very positive impression.

Tip #3: Work packages in Horizon 2020 to be prepared by one scientific leader 

Horizon 2020 requires collaborative work on funded Horizon 2020 projects. Such method of work is truly productive as it can certainly expand on the capabilities of just one researcher working on the project. However, the same cannot be said about collaborative management. Experience shows that this type of management is inefficient and generally not as successful as ‘traditional’ management.

In the context of structuring the project’s concept and, as a result, its work-packages – the following needs to be considered:

If the project’s concept is a result of collaborative thinking and the work of the partners, but only one scientific leader then turns the products into a unified & comprehensive concept (which then becomes a detailed work plan and work packages), this is fine.

However, what we often come across is the case where the project is developed from the work packages up, based mainly (or solely) on the inputs and interests of each of the partners. In such cases, little to no significant management or leadership was present. This is clearly not the recommended practice.

Therefore, our advice is to nominate a scientific leader (or a small leading team of up to 3 individuals), which will lead the process of developing the project’s concept and application. In that sense, the collaborative work is limited. The partners will contribute and provide input, but it is the scientific leader that is going to make decisions and manage the process. Experience shows that the results of such process are much better than the alternative.

Tip #4: Representing collaborative work in the work packages in Horizon 2020

The work packages reflect the collaborative work expected in the project and the work package table structure requires listing the participating partners in the work package. It is necessary to detail how many person-months they plan to invest in the work package, and to which tasks they are assigned for participation within the given work package.

Therefore, when preparing the work packages in Horizon 2020 – the scientific leader must collect such input from each of the partners. Additionally, the scientific leader must also make sure they fully understand what is expected from them in that sense and in light of the project’s “big picture”. It is important to ask all partners to provide as many details as possible, while keeping in mind that each of the partners is following a certain agenda and interests. These interests might not be fully in line with the interests of the project, and for that matter the input from the partners must be well assessed and adjusted before including it in the work package description.

During this process, keep in mind the following guidelines:

  • The work plan and work package structure must make perfect sense to the reviewers (and to you, for the execution phase that proceeds).
  • Avoid redundancies, overlaps and gaps between the tasks within a given work package, and across the various work packages.
  • Avoid “patch work” which simply makes use of the text provided by the partners. Make sure to consolidate the various inputs from the partners and ensure that the text has a unified single “voice” (style) across the application.
  • The collaboration between partners is an important added value of these kind of projects. This added value should be present in the way the collaboration is presented. Keep in mind that this reflection of the collaboration’s added value should also be presented in section 3.3 (“Consortium as a whole”).

On top of this, mind the following rules of thumb when referring to the distribution of work between the work packages: 

  • Avoid a presentation of a single partner in a work package. Aim to demonstrate that collaborative work is present in each work package.
  • Avoid a presentation of all partners in all the work packages. The aim is to show the diversity of work in these projects. If all partners are included in all work packages, it may not make sense in the eyes of the reviewers. As an exception to that, it might be relevant to put all partners in “horizontal” work packages (e.g. the work package that deals with dissemination and exploitation of results).
  • Use the work packages and assignments of tasks to partners within the work packages to express the work flow and the collaborative work (e.g. Task 3 done by partner #7 in WP2 will feed the work of partners #2 and #5 in Task 1 in WP4, and so on). Use it wisely and clearly in a way that will allow the reviewers to follow your logic.

Tip #5: Link the work-plan to the profiles of the partners

The full profile description of the partners is available on section 4.1 of the application file.

These partner profiles include general information alongside relevant skills and expertise, main tasks of involvement, CVs & track record of key personnel involved in the project, and relevant infrastructure or technical equipment.

This information is essential for the reviewers when assessing the feasibility of the work-plan, the personnel involved in the execution of the project and the added-value of the collaborative work.

Therefore, when drafting the work packages and work plans, we’d recommend to attend and update section 4.1 accordingly:

  • Make sure that the main tasks of involvement of each of the partners is in line with the work plan in each of the work packages.
  • Verify that the CVs and track record of the personnel involved in the project correlate to the expected tasks. Avoid a presentation of personnel that might not be the right one for performing the action.
  • In case there is a need in infrastructure or technical equipment, make sure to elaborate on that in the profile of the relevant partner, while referring to that also in the work packages (and maybe also in section 1.3, as needed).

Tip #6: Work packages in Horizon 2020 are the primary budget justification

The work presented in the work package is the primary justification to the requested budget (in section 3.4). It is imperative that the work-plan will be well designed in order for the reviewers to properly assess the budget request. Investing in this properly will also be beneficial to you and your partners during the execution phase.

The basic (and mandatory) information provided in the work packages about the budget request is the person-months allocation per partner in each of the work packages.

To begin with, this person-months allocation must be well correlated to the work presented in the work package and it must make sense to the reviewers.

We would recommend enhancing this presentation by providing a higher resolution of information to the reviewers. We recommend indicating the person-months allocation at the level of tasks, on top of the basic requirement of presenting this information solely at the level of the work package.

If this is done, higher resolution of details for the work plan will be achieved. In turn, the reviewers will have a better picture that will enable them to better assess the plan. We know from experience that this will probably leave a better impression on the reviewers. They will respect your efforts in producing such higher resolution planning.

Doing this right ensures the budget estimations of the partners and the overall work-plan will be more accurate. Needless to say that this is good, both for the evaluation and execution purposes.

Conclusion

To conclude, work packages are the backbone for any Horizon 2020 project. As such, they must be regarded with great importance and prepared with attention and detail. A successful work packages structure will not only prove helpful during the evaluation stage, but also serve as the guiding path during the project’s execution. Follow our tips above as you curate the work packages structure for your upcoming Horizon 2020 grant application. As always, should any questions come up, we’re here to help!