Dispatch
Stop habits before the ribbon moves.
By Mr Nazeem Toefy, Technical MD
Wind calls, cable routes, and egress checks shape this note across Cape Town sites and Highveld festival grounds.
AuthorStop habits before the ribbon moves. At Astonishing Studio we write from Woodstock and regional desks, not from a brochure. Fail-safe first is the note we wish producers had before the week turned loud. We keep the language plain, the steps countable, and the next link obvious: an activation path, a venue, or a booked hour with our contact form.
A small production team can lose an hour because one risk was spoken about, but never written down. On festival and retail launch days, Fail-safe first puts the first line in writing before branding goes up, before stock is unpacked, and before public access changes the site. The note works best when it names the main problem, the owner, the time checked, and the proof attached. In South African conditions that often means a wind reading, a ballast count, a mall access restriction, or a photo of a damaged lead.
Write the problem before anyone starts dressing the activation. Then add the exact owner, the affected area, and the evidence, whether that is a gate time, a venue instruction, or a missing item on the truck. Print the note when power supply is uncertain, and tape it where crew, suppliers, and security will all see it.
List the one thing that must still work when a screen freezes, a lamp trips or rain starts. On this kind of activation, that usually means a manual fallback for check-in, product security and a safe shutdown plan for power.
South African sites rarely fail for one dramatic reason. More often it is a chain of small misses such as coastal gusts, red earth in connectors, shopping centre delivery windows, or a generator placed too far from media control. Fail-safe first is written for those conditions, so the note asks for counts, locations, and names instead of vague concern. Load-shedding planning still matters even when the venue has backup, because charging, testing, and screen resets must be timed around what is actually available.
Use /activations when the problem changes the build itself, and /venues when the rule belongs to the site. /builds helps when the team needs to compare how a solved issue looked in practice. If the note is moving between producer, supplier, and venue, keep the first problem line attached so each handover starts with the same fact set.
Move from this dispatch to activations for install formats, venues for site conditions, or the contact form when the problem needs a named owner and a city.
Based in Woodstock, Cape Town, we route booking details through our contact form so venue names, access times and exceptions stay attached to the same note.
