Chatter Shift Schedule Template: Slots, Cover and Gaps

Most rotas fall apart in the same place. Not because nobody knew who was working, but because nobody wrote down which hours were deliberately empty. The schedule below is a coverage document: it names the blocks, names the people, and names the gaps.

Copy it, change the clock boundaries to fit your creators, and keep the dashes.

What is a chatter shift schedule template for, and who uses it?

It answers one question for every hour of the week: is a live thread going to get a reply, and from whom.

Three people use it, and each reads a different column:

• The agency owner reads coverage: which blocks are staffed, which are not, and whether the staffed ones sit where the money is.
• The chatter reads their own row: the blocks they own, the ones they back up, and what the previous block handed them.
• The creator reads the gaps: the hours where a message will wait, so nothing arrives as a surprise.

It is not a fairness document. Shifts are not equal, and pretending they are is how the peak evening ends up staffed by whoever complained least.

What does the complete schedule template look like?

Here is the grid, filled with a worked five-chatter roster. C1 to C5 are people, n/a is a block you are leaving uncovered on purpose.

Block	Hours	Mon	Tue	Wed	Thu	Fri	Sat	Sun
Night	02:00–06:00	n/a	n/a	n/a	n/a	n/a	n/a	n/a
Morning	06:00–12:00	n/a	n/a	n/a	n/a	n/a	n/a	n/a
Afternoon	12:00–18:00	C5	C5	C5	C5	n/a	n/a	n/a
Evening (peak)	18:00–22:00	C1 C2	C1 C2	C1 C2	C1 C3	C1 C3	C2 C3	C2 C3
Late	22:00–02:00	C3	C4	C4	C4	C4	C4	C5

That is 25 block-days: five chatters at five shifts each. The peak evening is doubled every day of the week, the late block runs single, the afternoon runs Monday to Thursday, and two blocks are empty by decision.

Under the grid, every block carries the same field list:

Block: ____________          Hours: ______–______
Owner: ____________          Backup: ____________
Creators covered: ____________________________
Priority order this block: 1) ______  2) ______  3) ______
Floor price in force: ____________
Scheduled sends landing in this block: ____________
Uncovered after this block until: ____________

Every block also ends with a close-out sheet. This is not the per-fan handover note (that format is settled in handover note examples). It is the block-level cover sheet that says what state the whole shift is leaving behind:

Block close-out | [creator] | [date] | [block] | from ____ to ____
Threads live at handover: ____________________________
Pitched, awaiting reply: ____________________________
Bought this shift (do not re-pitch): ____________________________
Haggles refused, floor held: ____________________________
Anything the next shift must not repeat: ____________________________
Unanswered longer than one block: ____________________________

How do you fill each field?

Start from coverage and work backwards to people. Filling names in first is how the peak block ends up thin.

• Block and hours. Set boundaries from your own account, not from the template. Keep the block names stable across creators so a swap between grids stays readable.
• Owner. One name per cell, never two names sharing a cell without a priority order. A doubled block means two owners with split queues, not two people watching one inbox.
• Backup. A named person, not a pool. The backup owns specific blocks, so a swap is one edit.
• Creators covered. List them. This is the line that catches double-booking before the shift rather than during it.
• Priority order. Which threads get answered first when the block is busy: a live buyer, then a warm thread past the sixth message, then everything else. The rules behind that ordering are in managing fan conversations.
• Uncovered after this block until. The most valuable field in the template. It forces someone to write “nothing until 12:00 tomorrow” rather than assume.

Why does the grid put everyone on evenings?

Because that is where the conversions are. In our corpus of 42,852 conversations, evenings maximise conversion and the 2am-6am window collapses it. So the ordering rule for the grid is not “cover the clock”, it is “cover the peak twice before you cover anything once”.

That is why the worked roster doubles the evening every day of the week before it puts a single name on the late block, and why two blocks stay as dashes. Coverage is bought in that order or it is bought badly. Count it in block-days and the trade is visible in one line: whatever you spend on the night is not being spent on the evening, and the evening is where the sales are.

The full timing picture, including what we did not measure, is in what time fans buy. The coverage ladder (what each level of coverage costs in people) is in how to hire chatters.

What are the three classic mistakes?

Leaving the gaps blank instead of writing dashes. An empty cell reads as an oversight and gets argued about; a dash reads as a decision and gets planned around. The creator should be able to see, at a glance, that nobody is answering between 02:00 and 12:00.

Rotating the peak block “to be fair”. The evening is where your strongest closers belong, every week. Rotating it spreads the weakest coverage across your best hours. Give people the weekend off instead, or pay a premium for the block, but stop moving it.

Treating the block as finished when the clock says so. A block ends when the close-out sheet is written. Without it, the next shift rotation starts blind, re-pitches something already bought, and burns a thread. The per-fan notes that travel with it are only as good as the block-level cover they arrive under.

When do you revise the schedule?

On three triggers, and not on a calendar:

1. The roster changes. Every arrival and every departure re-runs the block-day arithmetic. A leaver does not remove one person, it removes five block-days.
2. A creator’s audience moves. New platform, new geography, a promotion that pulls a different crowd. The peak boundary moves with it.
3. The backlog outlived a block. If threads opened in the evening are still unanswered when the next evening starts, the grid is wrong, not the chatters. Add coverage where the backlog forms, not where it is most comfortable to add.

A schedule that changes every week is not being tuned, it is being avoided.