60 likes | 173 Vues
This technical session focuses on the role of local coordination in project management, emphasizing the importance of effective financial oversight and communication among partners. Participants will gain insights into project implementation status, achievements, and areas needing attention. Key elements include administration, financial management, and the necessity of providing partners with guidance and support. Attendees will learn how to navigate the reporting process, ensure compliance with budgets, and maintain a common format for successful collaboration within the community.
E N D
technical session WP0 State of implementation - April 2008 : half of the project ! • Role of local coordination (overview/management) • Read Annex I (full project) - to get an overview of what your community has planned to achieve • What has been achieved ? What is missing ? Read next 18 month Report, to get an overview of where partners stand- what they have planned • Foreseeing progress and identifying potential problems • Report to Project coordinator /PSG when necessary (progress/difficulties) Key element : the success of this project = your partners’ success
Technical session WP0tasks of local coordinator • Administration/Financial management : • Management of your community on a everyday basis • Provide guidelines and assistance to your partners, that they are able to deliver work in time and/or to let you know if they have problems • Supervision of EACH of your partner budget - cf xls document- declared/foreseen/Final result- • Financial key documents are A3.1 (full budget) - A.3.3 (next 18 months) in the end of the Annex 1 • Provide overview/assistance on “financial forecasting” : Make sure that financial forecasting “stick” to what is planned (closest to reality).
Example : Calendar for the Reporting Period 2 • How & what ? The need of having one and single common format for each partner : • fulfilment of xls document by partners (Description activities + Financial declaration) + Mandatory Language : English • ForAnnual Report progress : WP leader • Who? List of main authors (responsible) : • WP0 : WP0.1 : Renaissance coordinator (Hespul/GL) + WP0.2 : local coordinator (GL/Hespul + Ayto./UB) • WP1: Renaissance leader by sub-WP, i.e.: WP1.1 (GL), WP1.2 (INSA ), WP1.3 (LoM), WP1.4 (Urbic), WP1.5 (Ecodes) !!!???- • WP2 : Renaissance leader (UdZ) - separated for WP2.1/2.2 but common for WP2.3 • WP3 : local Leader (SEM Lyon confluence + SMRUZ): annual report per community • WP4 : Renaissance leader (Hespul) • WP5 : Renaissance leader (Ayto.Zaragoza) • Deadline : mid- October 2007 : To be sent to the Renaissance Coordinator
How to handle reporting process ? Suggestions • List of documents (sent by project coordinator) : • Deliverables summary: what ? Who’s involved ? Additional information needed ? • Template of annual report (caution : all partners covered ? major cost items covered ? next 18 months description ?) • Updated financial sheet of xls doc/ Year 2 DG TREN validation ? • Local coordination (close collaboration needed with each partner/ local leaders) : • Preparation of their xls doc (description + financial declaration) ? + visit each partner ? • Adequate fulfilment of xls doc (description activities + financial sheet) • Precise consistence between xls doc & Form C & Audit certificate (flexibility : Clause 39) • Assistance to WP Leader on Annual report production (clearly identify what is asked from them + others involved partners/ locally-internationally). • FINAL CHECKING : comparaison xls/Form C/Audit certif