An Upload Schedule Experiment on a Small Channel: Open Case Brief
Publishing rhythm is one of the few variables a small channel fully controls. This is the comparison we will document and how to run it yourself.
Evidence status
This case is not complete. No schedule data, audience figures, or outcomes have been submitted, verified, or published for this page.
See our editorial policy for how submissions are verified.
Upload frequency is the advice new creators hear most and can verify least. Post more, the reasoning goes, and the algorithm rewards you. Sometimes the channel grows; sometimes the creator burns out and the quality drops. This brief describes the schedule comparison we want to document properly, with the working conditions stated up front instead of buried.
Why publishing rhythm is a testable variable
Unlike thumbnails or topics, a schedule is entirely under the creator's control. It can be planned in advance, held constant for a defined period, and recorded without guessing. That makes it a good candidate for a case study, provided the test keeps production quality roughly stable. A schedule that doubles output by halving the effort per video is not a schedule test; it is a quality test wearing a calendar.
The interesting question is not simply whether more uploads produce more views. It is what happens to retention, returning viewers, and the creator's ability to keep going when the pace changes. A pace that grows an audience for six weeks and then collapses is not a strategy.
The comparison we will document
The contributor we are looking for has a small channel with a short but consistent history, so a baseline exists. The case compares two periods of equal length, each with a fixed number of uploads per week and a fixed day and hour. Everything else, including format, length band, and thumbnail template, stays the same. Between the periods the creator takes a short break rather than switching overnight, so the change is deliberate and the reason is recorded.
- Period A. The lower or current frequency, documented for four to six weeks.
- Period B. The higher frequency over the same number of weeks, at the same times.
- Quality guard. Average production hours per video, tracked so a hidden effort drop is visible.
- Creator load. A simple weekly note on how sustainable the pace felt, written at the time rather than recalled later.
How to run a schedule experiment without burning out
- Choose a pace you can hold for six weeks, not six days. The higher period should be a stretch, not a fantasy.
- Batch before you begin. Record and edit a buffer of videos so the new pace does not immediately eat your weekends.
- Keep the day and hour fixed. Moving uploads around introduces a second variable and makes the result unreadable.
- Cap the effort per video. If a video needs more time, publish it later rather than shortening the test.
- Record weekly numbers, review at the end. Weekly notes catch a collapse; weekly decisions destroy the comparison.
- Decide the exit condition in advance. For example, if retention falls sharply for two consecutive weeks, stop and record why.
Map the plan with the upload schedule planner so both periods are visible on one page. For background on how frequency is usually discussed, see how often you should upload, and read it as guidance rather than a rule.
Record numbers per upload as well as per week. Weekly totals are dominated by whichever video happened to receive a recommendation, while a per-upload view of impressions and average view duration shows whether the audience is responding to the cadence or to one lucky video. Both views belong in the log; neither one alone tells the story.
What we count as evidence
We will require the upload calendar with dates and times, the production-hours log, a continuous analytics export for both periods, and the creator's written reason for choosing the two frequencies. Screenshots of weekly views are not sufficient on their own, because they hide the impression volume and the traffic mix that explain them. We also ask for a short statement about whether the creator would repeat the schedule, since sustainability is part of the result. Until a contributor supplies this material with permission, the page stays a brief.
Limits of this case
Two periods on one channel is a weak design by research standards. Seasonality, one unusually successful video, or a single recommendation burst can outweigh the schedule entirely. Audience growth during period A also changes the starting point for period B. We will report those pressures instead of correcting for them silently, and we will not publish a recommended posting frequency as a conclusion. A documented case can show what happened once; it cannot tell you what your channel needs. For a related question about mixing formats, see the Shorts and long-form brief.