# Rubrics, rhythm and the content plan

A channel that publishes the same kind of post every day soon turns into a monotonous feed. Rubrics bring variety, rhythm brings predictability, and a content plan shows what is missing before the audience notices.

**What you leave with:** A list of your rubrics, a day's rhythm on the GEO's local time, and a week's content plan loaded into scheduled posting.

## 01. Rubrics: what the feed is made of

You do not need them all at once. Each rubric does one of five jobs, and a week should have a little of each.

| Job | Rubrics |
| --- | --- |
| Personality and warm-up | Welcome post · personal posts · round videos · voice messages · evening recap |
| Value | Useful content · education · information posts · news |
| Engagement | Polls · entertainment · contest announcements |
| Streams and events | Stream announcements · trading session announcements · YouTube announcements · marathon warm-up · trading session warm-up |
| Product and trust | VIP seats opening · reviews |

There is no need to use everything every day. The job is rhythm and variety: a feed that runs nothing but news for three days reads as an aggregator, not a channel. The more varied the rubrics, the more interesting the channel is to follow — and the more profitable it is.

Two rubrics hold trust better than the rest — round life videos and voice messages: they go out regularly, not now and then. And the feed's main rule: the channel is never abandoned — the strategy is thought through in advance, the posts are written strong, and the rubrics are mixed.

## 02. The basic rhythm of a day

Not a KPI but a starting structure that is easy to work from. Every time here is the GEO's local time, not yours.

| When | What goes out |
| --- | --- |
| Morning | A personal or contextual post, the day's plan, news, a learning post |
| Daytime | A useful post, interaction, explaining the product, a stream announcement |
| 30–60 minutes before a stream or a trading session | A reminder in the main channel |
| 2–3 times a day | A call to join VIP — this is what raises conversion to a lead |
| After the stream | A recap, reactions, proof, the next CTA |
| Evening | Life content, the day's recap, a preview of tomorrow |

## 03. An example week

Three days made of the same nineteen rubrics. There is no need to copy them one to one — what matters is that each day has something personal, something useful, and no more than one or two calls to action.

**Monday:** Morning round video (Personal and life) · Market and news (Value and education) · Education (Value and education) · Poll (Interaction) · VIP CTA (CTA) · Session reminder (Streams and sessions) · Evening recap (Personal and life)

**Tuesday:** Personal post (Personal and life) · Common questions answered (Value and education) · Review or case (Reviews and community) · Short tutorial (Value and education) · Q&A (Interaction) · VIP CTA (CTA)

**Wednesday:** Stream announcement (Streams and sessions) · Useful post (Value and education) · Quiz (Interaction) · Live (Streams and sessions) · Stream recap (Streams and sessions) · Community feedback (Reviews and community)

**Watch out:** What matters most is that the channel does not look like an automated ad feed. A week with more calls to action than personal posts reads exactly like one.

## 04. The content plan

Working entirely in the moment is awkward and does not scale. A content plan shows what has already gone out, which rubrics repeat too often, where personal content is missing, when the next CTA is due, which posts to rewrite and what to schedule.

| Date | Time | Rubric | Topic | Format | CTA | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Mon 12 Oct | 09:00 | Personal | Morning before the session | Round video | — | Recorded |
| Mon 12 Oct | 13:30 | Value | How to read a level | Post with a picture | — | Ready |
| Mon 12 Oct | 18:30 | Streams | Session reminder | Post | To VIP | Scheduled |

A content plan is a draft and a report at once. Once a week it shows which rubric took over the feed and which days had no personal post at all — and that gets fixed before the views drop.

## 05. Posting times follow the GEO

You cannot run the US on a Moscow schedule just because the SMM works from Moscow. If posts go out from 9 a.m. to 9 p.m. Moscow time and the GEO is the US, most of them land in the subscriber's night, and they simply mute notifications.

**Time zone**

Every time in the content plan is local to the GEO.

**Waking up**

When the audience first picks up their phone.

**Working hours**

When people read in snatches — the time for short posts.

**Evening**

When there is time for something long, and for a stream.

**Stream times**

Set to the GEO's evening, not to a window that suits you.

**Notification frequency**

Every post is a notification, and too many get muted.

**Watch out:** Muted notifications do not show in the subscriber count: the person stays in the channel but stops seeing the posts. The views show it first.

## 06. Scheduled posting

A content plan without scheduled posting depends on somebody pressing Send on time. Three ways to take that off a person.

**Scheduling in Telegram** (Built in)

A long press on the send button, and the post goes out at the time you set. Enough for text and media.

**@posted** (Bot)

Scheduled posts with buttons under them, extra formatting, and custom and animated emoji.

**Third-party schedulers** (Services)

For when there are several channels and a team prepares the posts.

## 07. Mini-task: a week on schedule

- [ ] Sorted my rubrics by the five jobs
- [ ] Wrote out a day's rhythm on the GEO's local time
- [ ] Built a week's content plan: date, time, rubric, topic, format, CTA, status
- [ ] Checked the week: every day has something personal and something useful
- [ ] Scheduled the week's posts

Checking a week takes a minute when the rubrics in the plan are colour-coded: a day with no personal post stands out at once.

---

[Back to the programme](https://gamechange.partners/en/academy/telegram/)
