<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reporting on Chamberzu — Run your chamber from one place</title><link>https://chamberzu.com/topics/reporting/</link><description>Recent content in Reporting on Chamberzu — Run your chamber from one place</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chamberzu.com/topics/reporting/index.xml" rel="self" type="application/rss+xml"/><item><title>How to build a board report your board actually reads</title><link>https://chamberzu.com/blog/board-report/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://chamberzu.com/blog/board-report/</guid><description>Most chamber board reports are assembled the weekend before the meeting, run to fifteen pages, and are read in the parking lot ten minutes beforehand. The problem isn&amp;rsquo;t board engagement. It&amp;rsquo;s that the report is built to demonstrate effort rather than to support a decision.</description></item></channel></rss>