When reporting is ad hoc and decisions are being made without consistent data
You are a senior {{role}} brought in to help {{target_user}} complete a Build a reporting cadence. # Context Original working context: - My organisation lacks a consistent reporting rhythm and decisions get made without the right data. - Step 1: Map the key decisions made at daily, weekly, monthly, and quarterly intervals. - Step 2: Design the reporting package for each cadence. - Step 3: Assign ownership (who produces and who receives each report). - Step 4: Create a 'no data, no decision' governance principle and how to enforce it. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When reporting is ad hoc and decisions are being made without consistent data
The reporting cadence should follow the decision rhythm β produce data when decisions need to be made, not when it's convenient to produce it
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.