A channel report is read by people with limited time and limited context. A youtube monthly performance report earns its place by answering, in the first paragraph, whether things are working and what changes next.
Summary first, evidence after
Open with three sentences: what happened, why it happened, what will change. Everything below is support for that. Reports that build slowly toward a conclusion lose most readers before reaching it, and the conclusion is the only part that alters behaviour.
Keep the structure identical every month. Consistency lets a reader find what they care about immediately and makes month-to-month comparison possible; a redesigned report is effectively a new document each time.
What the report contains
- Summary: three sentences, no charts.
- Fixed metrics over an identical window length.
- Published versus planned, with reasons for any gap.
- Best and weakest video, each with a sentence of diagnosis.
- Traffic source movements, which explain most sudden swings.
- Decisions for next month, with named owners.
- Limitations — what these figures cannot tell you.
Including output against plan keeps the conversation honest. Many disappointing months are simply months where less was published, and no amount of analysis of the audience will reveal that.
Handle outliers explicitly
One video picked up by recommendation can dominate a month's totals and hide everything else. Name it, and where possible show the month with and without it, so nobody concludes that a general improvement occurred when a single video moved.
Say plainly where you do not know. A report that explains every movement confidently is usually inventing at least one of those explanations, and invented causes get acted on for months. The underlying routine is in the analytics reporting workflow, and diagnosis in the retention analysis guide.
Common questions
How long should the report be?
One page, with detail in an appendix for anyone who wants it. Longer reports get skimmed and their conclusions missed.
Should it include every video?
List them, discuss the outliers. Commentary on each of twelve videos dilutes the two that had something to teach.
Who should write it?
Someone close enough to the work to explain the numbers, which is rarely whoever has the fastest access to the dashboard.
What about a bad month?
Report it with the cause and the response. Reports that are always positive are quickly discounted entirely. See contact.
Should the report compare against targets?
Compare against output and against the previous period. Targets set on views tend to invite explanations rather than decisions, since the team does not control them directly.
How much history should it include?
Enough to show the trend, usually three to six periods. A single month in isolation almost always reads as either a triumph or a crisis.