Plan the week's reels without losing the chat

If you manage content for more than one person, this scene will be familiar. It is Thursday and somebody asks: “which one was the one to record with the rear camera?” And you scroll back up to Tuesday, find the link, and explain again what you already explained.

It is not a problem of being more organised. It is that a chat is not built for this, and no amount of discipline fixes it.

Why chat fails, structurally

Three reasons, and none of them yields to trying harder:

It is chronological, not organised by task. Messages are ordered by when they were sent, not by which reel they belong to. Directions for the same reel end up split between Tuesday and Thursday with twenty unrelated messages in between.

It holds no state. A chat does not know what is recorded and what isn’t. That information lives in two people’s heads, and the moment one loses track somebody has to ask — which is the single most repeated message in any working group.

Directions get separated from their reference. You send the link, and three messages later the notes. A week on, the link and its notes are two separate things somebody has to put back together by hand.

What a brief actually needs

Surprisingly little, but together:

• The reference: which reel, with its link, so it can be watched.
• What to copy: the hook, the format, the pacing, whatever worked.
• What to change: the parts not to replicate as-is.
• A state: to do, recorded, skipped.

What matters is not the list, it is that all four sit attached to each other. A link without notes does not say what to do. Notes without the link do not say what they refer to. And with no state, nobody knows where the week stands without asking.

What applies to everything, said once

Some directions apply to all five reels of the week: “record everything with the rear camera”, “no on-screen text this week”, “remember to keep the original audio”.

Repeat them on every reel and they take up so much room they bury what is specific to each one. Say them once in the chat and they are gone the moment five more messages arrive.

They belong in one place: at the top, once, always visible. It is the kind of thing that looks like a detail and shows up in how many questions you get.

State has to be visible both ways

This is the part that saves the most time and gets thought about least.

When whoever records marks a reel as done, whoever prepared it should see that without asking. It is not surveillance: it is that the question “how is it going?” stops being necessary, and that question gets asked several times a week per person.

The same in reverse: whoever records needs to see how many are left without counting backwards through messages.

A format that works

Even with no tooling involved, this alone helps a lot:

1. One list per week, per person. Not one for the whole team: each person opens theirs and does not wade through anyone else’s.
2. One entry per reel, with its link and its notes inside the same entry.
3. The general notice at the top, separate from the per-reel notes.
4. A state per entry, even if it is just a tick.
5. A permanent link, not a fresh document every week. A link that changes every Monday gets lost; one that is always the same gets saved to the phone.

You can build this in any shared notes tool. We made it part of Iloo Pro because, once you are already measuring which reels work, it makes sense for the brief to come from the same place as the data — but the format works just as well elsewhere.

What no tool fixes

A vague brief.

If the note says “make it nice” or “something like this but yours”, no format, template or app is going to save it. Whoever records will have to guess, and will guess wrong half the time.

What a good format does do is make a vague direction obvious. In a chat, “make it nice” slips by among twenty other messages. In a card with a field labelled “what to do”, it stands there on its own — and whoever wrote it usually ends up writing something better.