Rivya Commercial Asset Review Checklist

Use this checklist when choosing a Rivya result for a product page, advertisement, client project, or other public use. Review the exact file or text you will deliver, including any edits made after generation. A successful task is not approval to publish.

Define the Intended Use

Write down where the asset will appear, its audience and language, the product or offer it represents, and who can approve it. A draft for internal discussion and a paid advertisement need different review decisions.

List the details that must stay unchanged: for example, the product's shape, packaging text, price, or spoken script. Use the actual product information and approved brief as your reference, not an earlier generated variation.

Check Facts, Claims, and Language

Compare the result with the approved source material:

• Check shape, color, packaging, labels, accessories, and visible features. Remove or correct features the product does not have.

• Verify names, numbers, prices, discounts, dates, and offer conditions in visible text and speech.

• Check implied claims as well as written ones. A before-and-after image, demonstration, or testimonial-style voice can suggest a result that needs supporting evidence.

• For each language, preserve the same facts and offer while checking natural wording, pronunciation, units, and reading order. Do not let localization introduce a new promise or discount.

For claims that require specialist or legal review in your project, obtain that review before publication. A polished image or fluent script is not evidence for the claim. See Content Localization for preparing and checking language versions.

Review Inputs and Usage Rights

Check the materials used in the request: product photos, reference images, audio, text, logos, people's likenesses, and client or third-party files. Confirm permission covers the intended upload and use; receiving a file from a client does not by itself explain the scope of permission. Use Safe Upload Guidelines when deciding what to submit.

Check the model used and the applicable provider conditions. A model's public page does not establish which service processed an older result or what rights apply to it. Keep the model name and task information available; if the applicable conditions are unclear, resolve that before publishing. The Provider and Commercial-Use Matrix is a starting point for that review.

Rivya's Terms of Service describe output ownership between you and Rivya to the extent permitted by law. They do not guarantee uniqueness, freedom from third-party claims, or suitability for every commercial use. See Ownership and Commercial Use for the distinction. This checklist does not grant additional rights.

Inspect the Actual Delivery File

Save the chosen result and inspect the saved copy:

• Images: inspect the full image and the intended crop, dimensions, small text, logos, product details, and visible artifacts.

• Video: watch the entire clip, including its ending. Check motion, product consistency, framing, duration, and audio when present.

• Audio: listen from start to finish. Check wording, pronunciation, pace, unwanted sound, and missing or cut-off passages.

• Text: read the final copy in its destination layout. Check factual accuracy, formatting, links, and any text altered during editing.

Compare tone and presentation with the brand's existing materials. Make required corrections in an appropriate editor, then review the exported file again. Checking a thumbnail or an earlier version is not enough.

Follow Downloading Outputs to save your own copy. A history record is not permanent file storage. Keep the original separately from the edited delivery version.

Record Approval and Handoff

Keep a short review record in your own project files:

1. Identify the exact approved filename or text version, language, and intended placement.

2. Record the source materials, model, prompt, relevant settings, and task ID where available. Keep permission records and evidence for claims with them.

3. Note any outstanding edits or restrictions. If these affect the planned use, keep the asset as a draft until resolved.

4. Record who approved the final version and when, then hand over that version with the agreed usage notes.

These are records you maintain for the project; this checklist does not describe an approval workflow built into Studio. Recheck after changing the asset, translation, claim, offer, audience, or placement. Approval of one version does not automatically cover a different use.

For coordinating the wider production process, use the AI Content Production Checklist.