Review a presentation before handoff

Start from the saved revision#

Complete or cancel active edits first. Confirm the project and revision you intend to review. Reopen the project to make sure the intended text, media and slide structure were saved.

A proposal, direct-edit canvas, compiled browser build and native delivery package are different artifacts. State which one your team is reviewing.

Review content and behavior#

• Read claims and numerical values against the selected sources.
• Check labels, units, citations and scientific context.
• Review every slide and every intended presentation path.
• Operate tabs, overlays, controls and navigation.
• Check image crops, text wrapping and content outside slide bounds.
• Play media and inspect its controls, return behavior and text alternatives.
• Check that illustrative content is recognizable as illustrative.

Use the presentation check#

Open Export and inspect Check presentation where available. Use a finding’s Go to action to locate the affected content. Save fixes before choosing Run check again.

The check can identify authoring or asset readiness issues. It does not establish scientific approval, native client acceptance or that a file has been uploaded to a destination.

Choose the appropriate handoff#

For browser review, use the saved HTML5 workflow when an appropriate build is available. For a native target, follow CLM export and Veeva handoff and verify the intended profile and saved revision.

Give reviewers the project or artifact identity and tell them what to inspect. Keep a record of your team’s review outcome in your normal review system. Studio does not turn a download into a recorded Vault approval.