A report on services can make the work of the common structure understandable if it distinguishes open activities, results and problems. Presenting only completed benefits can leave out significant difficulties for members. The return should make it possible to understand which aspects still require attention.

I propose a comparison with the stated objectives and the resources actually used. Definitions must remain consistent over time. If a service has changed, the variation must be explained before comparing the results; otherwise an apparent increase can only result from a different count.

Let's imagine assistance that has solved many requests but keeps a few recurring problems open. The report can describe both outcomes, without confusing quantity and importance. Subsequent priorities should be linked to these elements and the conditions of the members' activities.

An effective return leaves room for relevant questions and clarifies what information is missing. Its usefulness grows when it feeds the next programming. Making open issues visible allows future work to be discussed with more realistic expectations and a recognizable link to the results achieved.