Process flow
How one request moves from brief to platform. Every adaptation on this site went through these seven steps, and the medium rectangle went round steps 4 and 5 twice.
Step 1: Account and brand brief
Owner Account lead, Brand
Output Intake ticket with deliverables, dates and mandatories
Step 2: Production review and vetting
Owner Production
Output Gaps flagged, specs confirmed, dates agreed or pushed back
Step 3: Design build and adaptation
Owner Production
Output Every size built from the master, versioned v1
Step 4: Internal QA
Owner Production
Output Checklist run per file, fails fixed before anyone else sees it
Step 5: Stakeholder revision round
Owner Brand, Legal
Output One consolidated feedback list, revisions versioned up
Step 6: Final approval
Owner Brand lead
Output Written sign-off recorded on the ticket, not in the filename
Step 7: Delivery to platform
Owner Production, Media
Output Files trafficked, delivery logged, folder moved to 06_Delivered
If a stakeholder round brings changes, the file goes back to step 3 as the next version and runs through internal QA again before anyone else sees it.
Where the evidence lives
- The brief is step 1, the intake ticket.
- The adaptation gallery is the output of step 3.
- Creative QA is step 4, including the v1 to v2 loop through step 5.
- The workload board tracks every request across steps 3 to 7 at once.
- Asset management is where each step’s files land, ending in 06_Delivered.