> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-circle-stewards/section-4-post-circle/post-event-reporting.md). # Post-event reporting After your event, be sure to share an update on the [**Logos Forum**](https://forum.logos.co/) so the rest of the community can stay informed. Use the template below to help structure your feedback. Once your update is posted on the Forum, share the link in the Discord #circle-discussions channel so others can easily read it. Post-event reporting is a core part of how Circles learn, improve, and coordinate across the network. It ensures that activity in local Circles translates into shared knowledge and measurable progress around winnable issues. #### Why this matters Without consistent reporting, it becomes difficult to: * Track progress on winnable issues * Understand what is working across Circles * Justify ongoing funding and resourcing decisions **Please note!** If a Circle does not share their post-event updates, we will not be able to approve further funding for subsequent Circle activities in that location. This is not intended as a punitive measure, but as a requirement for maintaining transparency, accountability, and effective resource allocation across the network. Funding should directly correlate with the visibility of outcomes. **Privacy Guidelines:** * Any photos of participants should have faces blurred or replaced with emojis before sharing, unless you have their express consent to share the photo. * Avoid including full names in public notes; use first names only or initials. *** ### **Reporting template:** #### **Logos Circle \[location, month]** Date: \ Location: \ Registered on Luma: \ Attended: \[number of participants AND return attendees]\ Languages: #### Participants **Pointers to include:** * Number of attendees and countries represented * Backgrounds: developers, startup founders, crypto enthusiasts, privacy advocates. * Areas of interest or focus #### Topics Discussed **For each topic, include:** * **Topic Name / Theme** * **Key Points & Insights:** * Challenges or open questions * Solutions, ideas, or proposals * Technologies or tools mentioned * **Action Items or Next Steps** #### Winnable issues update **Pointers to include:** * If a winnable issue has been defined, and what is it if so * Any updates on the winnable issue that happened outside of the Circle meeting * Any blockers faced * Planned follow-up actions, including who is taking responsibility of what #### What We Learned / To Improve / New Ideas **Pointers to include:** * Things that worked well * Areas for improvement * New ideas or experiments to try next time --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://circles.logos.co/readme/for-circle-stewards/section-4-post-circle/post-event-reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.