Required reports 2 Aug 2010 1 Oct 2010 6 May 2011 30 Jun 2011 Project Plan & Budget Consortium Agreement (where applicable) Draft Final Report Final, Completion reports & Budget 30 Dec 2010 Interim Report & Budget Very much encouraged: blogs / wiki / news feed (rss), etc. 27/08/10 | slide
Budget reporting – you should forecast whether you have over- or under- spent in each reporting period and agree any changes to your budget with your Programme Manager. Programme Managers would rather see you use resources effectively than be faced with a big budget variance at the end of the project.
Staffing – you should always report on any changes in staffing, or significant periods of absence.
Issues and Achievements – if things aren’t going to plan, say so, say why, and say how you are handling it. If you need help, say so, it is not failure, its just truthful reporting! Likewise where things are ahead of schedule, or working really well, say so, or your programme manager might not know about it.
Reporting (ii) 27/08/10 | slide
What works well in interim & final reports? 27/08/10 | slide
telling the story of your project/progress
describing how any of your initial assumptions were/have been challenged
sharing details of anything that didn’t work and how you addressed this
insert chunks of your project plan
just refer to work package numbers – name them!
make the reports “difficult” to read without prior knowledge
Programme & project websites - overview of project - project proposal - project plan (when available) - final reports (when available) - link to project website - JISC branded & link back to programme - managed by project team - materials and reports - news and events (rss feed please) - project aims and objectives - methodology - planned outcomes - project partners - contact details jisc.ac.uk 27/08/10 | slide Remember: All outputs and deliverables need to be made available on or via your website which must be maintained for at least 3 years following project completion. project website