Support

warranty team

Revision cover logs each agreed fix after delivery with its timecode, the person who asked and the date it was done.

How revision cover works in a real week

Warranty Desk covers agreed fixes after delivery, so revisions are logged properly and tied to what was actually approved. Changes are captured clearly, with no confusion about what sits inside the original brief.

State which delivered cut is under review, who approved it, and what part now needs correction. Warranty team requests usually involve swapped logos, outdated pricing, missing legal lines, or a scene exported from the wrong approved timeline. Teams in Johannesburg, Durban, Cape Town, and regional branches need that record tied to the exact version that went out.

Send the first evidence with the request, not later in the thread. A frame grab, timecode range, approval mail, and the final exported file give the revision desk something measurable to assess. That usually prevents opinion-based changes from being mixed up with genuine post-delivery fixes.

Fixes tied to approved cuts

The output is a logged revision request with the issue, source file, and affected runtime written down clearly. You also leave a paper trail that shows whether the change belongs under warranty team cover or sits outside the original sign-off. For internal teams, that matters when marketing, procurement, and operations each remember the brief differently.

Link the warranty team request to the approved brief, the delivery file, and any prior correction notes before scope expands. For multi-branch rollouts, check the same error across each exported variant before anyone resends assets. Film briefs need the venue, the people on camera and where the finished cut will be shown.

  • Approved version listed before changes begin
  • Timestamped fault noted against delivered file
  • Correction request stored with project trail

Revision cover under local conditions

South African teams often juggle branch managers, procurement sign-off, agency comments, and supplier approvals on one job. That makes version control more important after delivery, especially where one mistaken export is forwarded between WhatsApp groups and internal mail chains. Warranty team logging works best when each requested change is matched to the file name people actually circulated.

Regional conditions also affect what counts as a valid correction. Packaging law updates, bilingual text swaps, retailer compliance copy, and pricing changes for different provinces need to be identified properly rather than folded into a vague rewrite request. Load-shedding, remote approvals, and patchy mobile review links can all muddy who signed off which cut.

Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.

What to send with defects

Brief the revision with links, timing, and what has already gone wrong. Keep the subject line specific.

Include the exported file name, the approval reference, the exact timecode, and a note on what appears incorrectly on screen. Where audio is affected, mention whether the fault sits in voice-over, music level, subtitle timing, or the final mix. That gives warranty team checks a clear basis without reopening the entire production brief.