Rules of work
One page of rules, one line each, with the reason. This is what a new person is trained on and what an old hand is held to. Everything else in the handbook explains a rule here in more depth. Alex, 20 Sep 2026: "make our SOPs granular to sort each scenario, so we have a legitimate agency and when I train them it makes sense."
A. Tasks
- Every piece of work is a task in ClickUp before it starts. If it is not in ClickUp, it did not happen and will not be paid for or counted. Because the task is how work reaches cost, the client sheet and your record.
- You do not create deliverable tasks. The portal creates them from the invoice. If a piece you are asked to make has no task, tell the AM; do not start. Because a piece with no task has no package, and nobody can say who is paying for it.
- One task per piece. No subtasks, ever. A second version is a Frame.io version, a step is a checklist item, a second piece is a second task. Because subtasks vanish from every count.
- The title is the key.
HOFT-B03-07 Reel The Same Home. Never rename a task. Because the key is what ties ClickUp, Frame.io, Drive and the ad together. - Status is the only signal. Move it when the truth changes: In progress when you start, Internal review when the first version is up, Client review when the AM sends it, Done when it is live. Never write "ready for review" as a comment. Because reviewers work from a view of statuses, not from their inbox.
- Every task has a due date and an assignee. If yours has neither, say so to the AM the same day. Because a task without a date cannot be late, and one that cannot be late is not work.
- Links go in fields, never in the description or a comment. Script, footage, Frame.io, references. Because the table shows fields; nobody opens a task to find a link.
- The description is written by the portal and is not edited. A brief that changes is a change request task. Because an edited brief erases what was agreed.
- Tick the checklist as you go. For the month tasks, the tick is the record of your time. Because nobody uses timers and the minutes have to come from somewhere true.
- Ad hoc requests get a task in the client's Account list,
CODE Ad hoc: what, with the package it belongs to or the tagunbilled. Because unbilled work must be counted before it can be priced.
B. Where to talk
- About a version, comment on the video or design in Frame.io. Timestamped, pinned. This includes graphics: statics and carousels are reviewed on Frame.io as image assets, not as PNGs in ClickUp comments. Because a note on the pixel is the only note an editor or designer can act on without asking.
- About a task but not the version, comment on the task, one comment, @ one person, ending in a question or a decision. Because a comment that asks nothing needs no answer and is noise.
- About a client but no task, make the task (rule 10). Because a client channel is a folder with no structure.
- About your day, the Standup channel, one message a day. Team questions in your team's channel. Because seven channels are enough, and none of them is for a client.
- Anything a client must hear goes through the AM, in the client's WhatsApp group. Never from an editor, never from ClickUp. Because one voice per client.
- Never DM Alex or Junkai about work. Put it where it lives. Because if it is not on the task, the record does not have it.
C. Files and naming
- Frame.io: one asset per piece, named with the key only.
HOFT-B03-07. Every new version is a new version on that asset. Never a second file, neverv2in a name. Upload from your own login. Because the version count is the revision count and the login is who did the work. - Drive: footage in
Clients / CODE / Shoots / date / Raw, finals inDeliverables / KEY. Never on a desktop, never in a personal Drive. Because the laptop has filled twice and the folder is what the portal reads. - Ads: every ad name is generated in the portal and pasted. Never typed in Ads Manager. Because the key at the front is what lets the report say which creative did what.
- Calendar: the client code in every client event title.
HOFT Call: Hoft,HOFT Shoot: Hoft. Because that is how meeting time lands on the client.
D. Review and revisions
- One internal review, by Nigel, within one working day of the first version. The AM covers only when Nigel is on a shoot. Nobody else comments on a v1.
- Two client rounds included. The AM relays the client's notes as Frame.io comments in the client's words, one comment per change. Status Needs revision each time.
- A third round is a change request task, opened by the AM, and the piece waits. Because unlimited rounds is how margin disappears without anyone deciding to give it away.
- Alex and Junkai do not comment on videos or designs. They tell Nigel or the AM. Because one voice per round.
- Graphics follow the same rounds as video. Version 1, internal pass, up to two client rounds, then a change request. Because design was where 25-comment tasks came from.
E. Shoots
- A shoot exists when it is on the shoot calendar,
CODE Shoot: Client, place in location, videographer as attendee. Nothing else counts as booked. Because the folders and the task are created from the event. - Footage is in Raw the same evening. Because the edit task's footage field points there and the editor starts tomorrow.
- Videographer and talent are paid with the client code in the memo. Because that is how the cost lands on the shoot instead of on the agency.
F. Media buying
- Every change to a campaign is a logged decision in the portal before or as it is made. The portal judges it at seven days. Because a change nobody recorded cannot be learned from.
- The daily check runs in the order the health page ranks accounts. Because the worst account first is the whole job.
- Escalations are tasks to the AM, never a message. Because the AM must know before the client.
- Once a month, "what worked by format and angle" goes to Nigel as a checklist item on the month task. Because that is the hand-off that stops the buyer writing scripts himself.
G. Reporting
- Monday message by 12:00, monthly deck by cycle day 3, from the Report tab. Numbers are never typed. Because a typed number is a number nobody checked.
- Nothing goes to a client while the tab says the numbers are not trustworthy. Because the client checks Ads Manager and finds it.
- The internal block is never sent. Because it is the unfiltered version.
H. Time, access, money
- Nobody sees another client's folder unless assigned to it. Access follows the Team tab.
- Passwords and card numbers never go in a task, a field or a comment. Ids only.
- Nothing is deleted. Cancel it, archive it, close it. Alex archives; the portal never deletes anything anywhere.
- Salaries and margins are Alex's and Junkai's. They are not in ClickUp and not in channels.
I. When this happens, do this
| Scenario | Do | Do not |
|---|---|---|
| Client asks for a change in WhatsApp | AM writes it as a Frame.io comment on the video or design, status Needs revision | forward the WhatsApp to the editor |
| Client asks for something new in WhatsApp | AM makes an Ad hoc task with package or unbilled | tell the editor in a channel |
| Footage is missing or corrupt | Comment on the task @ Nigel, status stays In progress, checklist "waiting on footage" | email, DM, wait silently |
| You will miss the due date | Change the due date and write one comment: why | let it go overdue |
| A task has no client or no package | Tell the AM; the AM fixes it that day from the Team page list | work on it |
| Editor is sick | Nigel reassigns in the Editor field, one comment naming what is done | leave it |
| Brief changes after v1 | Change request task in Account; the piece waits | edit the description |
| Client has not paid | The portal flags it on the Account month; the AM chases; work on open packages continues, new packages wait | stop mid-package |
| Ad account banned or ads off | Portal posts to Alerts; buyer opens an Escalation task to the AM | message the client |
| Someone comments a PNG in ClickUp for review | Reviewer replies once: "on Frame.io please", and the designer uploads it there | review it in the comment |
| You are asked to do something with no task | Ask the AM for the task; start when it exists | start |
| You are unsure who owns something | The list says: Creatives is the editor or designer in the field, Media buying is Jonathan, Account is the AM, Shoots is Nigel | ask in Standup |
| A client is unhappy | AM tells Alex the same day, in person or by call, and notes it on the Account month | wait for the report |
| A tool is down (Frame.io, ClickUp) | Standup channel, one message; Junkai owns it | DM everyone |
Training order
Day one: A, B, C. Day two: D and the person's own section (E, F or G). Rules 1, 5, 11, 17 and 19 are the five that, kept, make everything else work.
Related: every other SOP in this handbook explains one of these rules.