Use this only when the file is valid, the destination is correct, and nothing else should stop launch.
Creative review
Clear it or send it back fast. This guide is for the publisher-side review flow only – approve the asset, request changes clearly, and keep launch context attached to the booking.
What every creative row must show
The row should let a publisher make a decision without opening five other tools first.
- Buyer, booking item, publication, format, and upload time.
- Dimensions or duration, destination URL, file status, and the latest validation result.
- Current owner, latest note, and whether launch is blocked or still on track.
Decision rules
Use this when the buyer can fix the issue. Give one concrete reason, not a vague rejection.
Do not treat approval as the end of ops. If timing, proof expectations, or serving context are still unclear, keep the row visibly blocked.
Before launch
- Keep the approval state, launch date, and proof expectation in one visible timeline.
- Do not split the decision across messages, spreadsheets, and ops notes.
- After approval, the booking should move clearly toward
readyand thenlivewithout losing the approved asset.
Keep this attached after approval
Approval is not the end of the record. The publisher should still be able to see what will run and what proof is expected.
- The exact asset that was approved.
- The most recent buyer-facing note and any change-request reason.
- The launch date, live owner, and proof expectation.
- Any discrepancy or help case tied to the same booking item.
Next: live delivery. Move to live delivery once the asset is approved and the booking is ready to pace against its goal.