A graphic package has arrived in production, the files open, and the visual identity has received approval. It still remains to check what happens when these materials appear in the broadcast composition. A strip may cover important match information; an animation may end in a different position than predicted by the operation.

To accept materials from an esports broadcast, combine checks that link each file to its use. The team needs to know which conditions will be tested, who checks each result, and how to record a correction. This prevents simple receipt from being used as evidence that the entire package is cleared.

In this article, the example is hypothetical: a package for a fictional broadcast contains participant identification, a break slate, and a brand animation. There are no universal technical specifications. Parameters must be defined by the people who know the environment and the project operation.

Choose the delivery and delimit the composition

Start with the list of items included in the package. Inform which versions are expected and which elements need to be editable, when this is part of the scope. Also identify the visual reference and the approved content used to produce each piece.

Then, describe in what situation each material will be displayed. With which scene does the participant identification appear? Does the lower third occupy the entire screen or coexist with other elements? Does the animation enter over the match image or in a separate block? These answers guide both creation and checking.

When the composition is still undefined, record the dependency. The team can approve aspects of the file that are already verifiable, but must keep the test that requires the final scene pending. An unknown condition cannot be treated as met.

Transform expectations into observable checks

“Working in the live stream” is too broad to guide a review. For participant identification, a possible criterion is to present the full approved names, without overlapping with the elements that must remain visible in the combined scene. The test must indicate which composition and which situation will be used.

With the break slate, the check can compare the text with the approved reference and observe its display on the agreed test output. For the animation, it can verify if entry, hold, and exit correspond to the behavior requested from creation. Each criterion depends on what was contracted and discussed with the operation.

Avoid turning an aesthetic preference into an objective measure without explanation. If a decision regarding appearance depends on art direction or branding, indicate that responsibility and the reference that guides the evaluation.

Agree on the demonstration before producing

Decide how each requirement will be demonstrated. Opening a file confirms something different from inserting it into the scene and going through the intended use. A screenshot can record the static composition; a test recording can document the sequence of an animation, when such a record is possible and authorized.

Define with operations which situations merit checking. If the package includes variable fields, for example, choose content representative of the agreed uses. Do not create requirements after delivery without evaluating the change with those executing. The goal is to verify what was agreed upon, not to silently expand the scope.

Record the version of the material and the condition used in the test. Evidence without this identification can become useless when there is a correction, because no one knows which file the result refers to.

Separate the delivery states

Use states that allow understanding what occurred: received, awaiting test, needs adjustment, and accepted for the agreed use. If one piece passes the check and another remains pending, record each item. A partial visual approval does not need to disappear, but it also does not automatically clear the entire package.

In the hypothetical example, the break slate meets the criteria. The participant identification needs to be repositioned in the composition. The animation is still awaiting testing with the operation. The description shows different actions: preserve the accepted item, correct the second, and perform the verification of the third.

Indicate who receives the correction, who checks the new version, and who gathers the validations for acceptance. These responsibilities must be agreed upon between the parties, including the scope of release for each material.

Acceptance sheet to adapt to the graphic package

Item and version: [Package file and identification]. Agreed condition of use: [Scene, composition, and script reference].

Observable criterion: [What should appear or happen]. Avoid expressions such as “good”, “impactful” or “ready” without explaining what will be checked.

How to test: [Combined environment, sequence of actions, and content used]. Who checks: [Person or role that accepted this responsibility].

Evidence: [Authorized record of the test, its date, and the version checked]. Describe the result even when it is not necessary to keep an image or recording.

Status and adjustment: [Meets, needs correction, or not yet checked]. If there is a problem, indicate the observed behavior and the change to be discussed.

Revalidation: [Corrected version, criterion to be repeated, and responsible person]. Acceptance: [Confirmation, reference, and use that has been cleared].

Fill out one form per item or group records with the same fields. The instrument should allow locating a pending issue without rereading the entire project conversation.

Check the correction in the affected context

After repositioning the participant identification, repeat the test in the corresponding composition. Opening the corrected file does not prove that the visual conflict has been resolved. If the adjustment affects other intended states of the piece, agree on which ones will also need to be reviewed.

Keep the previous version identified as replaced and report who prepares the materials for the broadcast. Update the acceptance reference so that the operation does not use a copy that was left out of the last check.

Evaluate the broadcast result in another conversation

Audience, public participation, and activation results can be monitored according to project objectives. These indicators do not, on their own, demonstrate whether the graphic package met the delivery criteria. Preserve the distinction between verifying the material and analyzing its performance after use.

At Tessli, professionals can meet potential collaborators through profiles and chat using the contacts they provide. When the connection evolves into a project, those involved agree on scope, testing, and acceptance using the tools they choose.

Request participation for free at tessli.com.br. The team performs human curation, and access depends on approval. After being approved, prepare your profile and choose the contacts you wish to make available. Use of the network is free after approval.

Get to know Tessli and request participation. Access to the network depends on human curation and approval.