Learning patterns/Grant reporting for volunteers. Part 1: Report of project activities

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
A learning pattern forreporting
Grant reporting for volunteers. Part 1: Report of project activities
Korganizer-icon.png
problemTips about preparing the report of project activities from the perspective of user groups or individuals
solutionA list of useful advices that can help user groups members or individuals in preparing the report at the end of their funded projects
creatorSpiritia
endorse
created on19:32, 15 April 2017 (UTC)
status:READY


What problem does this solve?[edit]

Grant reporting for volunteers - the building blocks - part 1 - project activities.pdf

The learning pattern discusses questions related to structure and contents of the report, distribution of roles and responsibilities in preparing the report, report timing, tips about making the report easier for writing and reading.

This is the editable (and wiki structured) version of the poster Grant reporting for volunteers - the building blocks - part 1 - project activities.pdf, presented at the Wikimedia Conference 2017.

What is the solution?[edit]

Many of us may have asked ourselves similar questions when applying for WMF funded grant, and when we had it approved and needed to actually prepare the reports for our project activities and the expenditures (see also Grant reporting for volunteers. Part 2: Financial report). Here are the answers to some of the most obvious questions that arise when facing the deadline for the project report. :-)

What is grant reporting?
Reports of WMF funded projects (grants) are public documents ensuring the responsibility and accountability of individuals and affiliates who are transparently spending donated resources for mission aligned purposes. The report is the obligatory concluding part of any project and it covers project activities, outcomes and expenditures.
Is grants reporting really important?
Reporting is usually deemed important for the sponsoring side, as it ensures eligibility and appropriateness of expenditures while collecting information about the project outcomes and impact of the sponsor. Reports are often used as a basis for taking future decisions and framing policies. However, reporting is helpful for beneficiaries, too, as the process requires them to analyze various aspects of their performance, like strengths, weaknesses, opportunities, needs, vulnerabilities, mistakes and lessons learnt, and is a measure of success for the beneficiary.
Who is responsible for preparing the grant report?
This is an internal decision that project teams should take explicitly and before the end of the grant term. Ideally, all team members should feel welcome to contribute, but contact persons have to.
So, is there a magic recipe?
So, the truth is there is no magic recipe for writing a good report – every report is different, there is no “one size fits all” solution. Each report depends on what the project purpose was, what kinds of activities were envisaged, who implemented it, what was the budget, what obstacles appeared along the way, and how were they overcome. The good news is that once you learn writing good reports, the ability will stay with you. :-)
How are reports structured?
Each of the available grant programs has a predefined structure of the report that you should follow. If relevant, add subsections, but don’t remove ones. Colours can help you additionally structure your report.
What to write in our report and how?
A good report is always a complete and self-explanatory document, containing all the evidences needed to support the data provided and statements made about the project implementation and outcomes. Ideally, it not only describes the activities, but also explains the rationales behind them. It shows not only the final *product*, but also the *process* involved and the long-term benefits for the community.
What if our project didn’t meet its goals?
Sometimes, despite all your efforts, some (or all!) of your project goals remain unachieved. This happens all the time in projects run by professional managers, so it will inevitably happen in projects run by volunteers, as well. :-) Don’t be discouraged, and – more importantly – don’t try to sweep the problem under the carpet: show that you learn from it.
We have thirty days to prepare our project report. Is this time enough?
Yes, especially if you started preparing for this moment in advance: collecting and organizing deliverables, statistics, feedbacks, etc. If you objectively need more time, let your WMF officer know.
Again about teamworking and time. What if no one in our project team takes responsibility for the report, or no one likes writing reports?
Well, user groups are informal, and their members are volunteers. But once your project proposal has been approved and funded, it doesn’t matter if you *like* writing reports, because you *have to* and you have a deadline. Unless explicitly agreed otherwise, project proposers and contact persons are *in charge of* this job. They shall schedule their work so that the rest of the team is given enough time for discussions, edits and additions, before the end of the deadline.
What are these “learning patterns” in the report template?
Learning patterns are a way of sharing experience and lessons learned from both success and failure. No two WMF projects are the same, even if they formulate identical goals but are implemented by different user groups, or are repetitively submitted by the same team over the years. We cannot step twice into the same river. We can learn from every new project.
How to make the report more easily digestible? ☺
Bulleted lists, tables, figures and evidence photos are important ingredients of any grant report. Such items, included along the relevant portion of the text, emphasize on key points, remove clutter and repetition, and make the report visually appealing and easy to follow. Figures, graphs, and tables serve as powerful tools for making comparisons, or summarizing content in a way that captures and retains interest. The same information, presented in descriptive sentences, makes the report too lengthy and cumbersome.
What makes our project report unique and worth remembering?
When you are the first / only one to do something (e.g. you invented, coded it, etc.). :-) When you have done something many times and under various conditions / contexts, and can report and explain the differences. :-) When you have performed better than anyone else, and know the reasons why. ☺ When you have failed epically, but learned your lesson and help others not make your mistakes. :-)
Any final comments?
Yes. Many people consider report writing the most boring part of the project and try to avoid it! Write your grant report with the same enthusiasm, which you wrote your proposal with! Don’t half-ass it. :-)

Things to consider[edit]

  • This learning pattern is explicitly written from the point of view of volunteers – individual contributors or user group members. It doesn't aim to reflect the situation of project reporting for chapters.

When to use[edit]

  • If you do not have prior experience with project reporting, consult this learning pattern for the first project reports that you have to prepare (as individual) or as member of your user group (as an informal group of indivuduals).

Endorsements[edit]

  • The information presented here, both on the poster and on this page, is quite useful. GastelEtzwane (talk) 12:49, 30 August 2018 (UTC)

See also[edit]

Related patterns[edit]

External links[edit]

References[edit]