I received feedback that while we have the report and the weekly tools for teams to see their Error Budgets, that it's hard to during the month if "things are bad overall". Without creating more tools, an option to have this information is to run the Error Budget report generation job more frequently. ### Current State At the start of each month we have a pipeline scheduled to run to create a monthly report issue. We manually update this report with any additional information and then issue this report to the rest of the company on the 4th of the month (or closest working day thereafter). We wait for feedback on the issue and when the next report is generated, we close the previous one. ### Proposal We always have a state where we have one issued report and one in-progress report. The issued report is the Error Budget Report as it stands today. It's a fixed report where the contents of the description are not edited after it is issued. Teams can use this for prioritization decisions and because the content is fixed, teams can refer back to this report in future. The in-progress report would be built using the same tool but updated daily to show the most recent information. Every day, it would be updated to show t-28d worth of data. The report should clearly say that this is a dynamic draft that is updated daily. Then as the 4th of the month approaches, we start to include the manual text as we normally do, before removing the "draft" status and disabling automatic updates for this issue. This report then becomes the issued report and we open a new one for the next month.