Drafting Board · single piece

How one piece moves from draft to release

This page explains how a single deliverable — a film cut, a long article, a partner kit — is drafted, marked, revised and released on the Lorong floor. It is not a software tutorial; it is the sequence we use so anyone opening the handover folder understands what happened.

Who checks what, and in which order

The project editor checks completeness against the brief — nothing more. The production lead checks timing and dependencies. Brand or legal checks only when the intake mark flagged their lane. Creative direction checks visual work before the review mark is applied. No step is skipped by chat message; the mark on the schedule is the record.

What the final handover contains

The handover folder carries five items: the approved asset at final version, a one-page release note, the margin sheet with approver initials, a copy of the schedule row as PDF and a short note on what was held back and why. If partner materials were involved, we include contact names and expiry dates for co-branded assets.

When your team already versions files but lacks a shared mark language, we can document yours into the margin ledger above during the first fortnight. When a piece fails review, the card returns to draft column with a written reason — never an empty rejection.

Revision rounds are counted on the schedule, not in email threads. Each round receives a version mark; approvers initial the margin sheet against that mark so nobody confuses Tuesday's draft with Thursday's. Held items stay on the board in a grey column with a plain sentence explaining the hold — legal query, missing asset, dependency on another team's release.

When work leaves the floor, the handover folder is the authority: if it is not in the folder, it did not release. That rule saves arguments later. Partners receive the same folder structure so co-branded assets never sit in an unnamed attachment.