160 likes | 430 Views
Work Packages. WORK PACKAGES A PART OF THE APPLICATION PACKAGE. Background Experience from INTERREG IIIB Northern Periphery Programme demonstrates a need for a more defined structure in both the application form and activity report templates.
E N D
WORK PACKAGES A PART OF THE APPLICATION PACKAGE Background • Experience from INTERREG IIIB Northern Periphery Programme demonstrates a need for a more defined structure in both the application form and activity report templates. • Aim is to improve project planning because a well planned project: • usually has greater potential to become successful in its implementation • is easier to evaluate and identify expected results and outputs from – facilitating the building of expertise and knowledge in the participating organisations, municipalities, regions, nations and on a transnational level. • is easier to monitor – simpler to identify if implementation is being carried out in accordance with the plan, both for the project partnership and for the JPS.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE New structure • The overall objective of the project should be described in the application form • All projects will be asked to split their activities into a maximum of 5 work packages • In the main application, a description will be given of how the work packages all contribute to the overall objective of the project • The section on NPP concepts should describe how the different work packages are connected • The section on NPP core concepts should describe how the different work packages are related and how they are dependant on each other.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE A work package description will contain the following parts: • Title of the Work Package • Strategic focus • Partner assigned responsibility for the work package • List of all project partners participating in the work package • Description of the expected results • Quantification of any output indicators • Overall description of work package • An activity plan for the work package, including activity indicators and output indicators. Note that work package 1 is “Management, coordination and communication”
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Title of the Work Package • All work packages needs to be given an individual title to describe the work that will be carried out in the work package. • The first work package will be “Management, coordination and communication”
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Strategic focus • All work packages should have a strategic focus. • By briefly describing the planned activities in the work package a clear strategic focus should be developed.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Partner assigned responsibility for the work package • Every work package should have one assigned partner organisation designated as responsible for the work package’s activities. • Partners need to consider the most suitable partner to be assigned this task and what the role encompasses. • The Lead Partner principle means that the Lead Partner is responsible for the project’s implementation, so it is vital that all participating partners understand their role and responsibility. REMEMBER: In the Northern Periphery Programme 2007-2013 a signed partnership agreement will be mandatory - probably before receiving the grant offer letter.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE List of all project partners participating in the work package • A list of all project partners participating in the work package activities should be given. • Within each work package it is important that clear responsibilities for activities are assigned to the specific partners • The Lead Partner principle means that the Lead Partner is responsible for the project’s implementation, so it vital that all participating partners understand their roles and responsibilities. REMEMBER: In the Northern Periphery Programme 2007-2013 a signed partnership agreement will be mandatory, probably before receiving a letter of a grant.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Describe the expected results • Details of the results indicators will be provided in the main application form • Purpose of this section is to describe the work package’s contribution to the achievements of the result indicators. A written description should be provided but the results will not be quantified in the work package. • In some projects a single work package may generate result indicators, if so this should of course be described.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Quantify any output indicators • Output indicators are expected partly to be generated on a work package level • Output indicators can also be generated on a project level - this information will be captured in the main application. • Output indicators generated in a work package will be quantified in the work package description.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Overall description of work package • All work packages should contain a detailed description. This will outline the details of the work package and justify the need for the work package and activities to the assessment bodies • The overall description should be no more than 3 000 characters. • The description should answer questions such as • What is being done? • How is it being done? • For what purpose is it being done?
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Activity plan for the work package, including activity indicators • Every work package should be split into six month “stages” - BUT a project launch could be done quarterly with an extended first reporting period of up to 9 months • Each stage should contain an activity plan to demonstrate concrete actions in the project work package and to be used for milestone reporting in progress reports. If applicable, a stage should include output indicators generated through the respective work package. • Work package 1 should cover “management, coordination and communication”. • When reporting progress the project will be asked to demonstrate achieved activity indicators and output indicators on a work package level. • The logic behind this requirement is to simplify the reporting and monitoring procedure, so that the JPS can easily assess a project’s progress in relation to its targets and proposed activities. In future, progress reports will automatically be generated by the new database system using this information.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Reporting periods: Stage 1: 1 October 2007 – 30th of June 2008 Stage 2: 1 July 2008 – 31 December 2008 Stage 3: 1 January 2009 – 30 June 2009 Stage 4: 1 July 2009 – 31 December 2009 Stage 5: 1 January 2010 – 30 of June 2010 Stage 6: 1 July 2010 – 30 of September 2010 If the project starts mid-stage, the first reporting period could be extended to over six months.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Reporting periods: Alternatively: Stage 1: 1 October 2007 – 31 December 2007 Stage 2: 1 January 2008 – 30th of June 2008 Stage 3: 1 July 2008 – 31 December 2008 Stage 4: 1 January 2009 – 30 June 2009 Stage 5: 1 July 2009 – 31 December 2009 Stage 6: 1 January 2010 – 30 of June 2010 Stage 7: 1 July 2010 – 30 of September 2010 Remember: National Controllers need to approve the costs before claiming.
WORK PACKAGES AS PART OF THE APPLICATION PACKAGE Reporting periods: Alternatively: