Who this is for: Teams preparing software assets for public demonstrations.
What to prepare
- All source screens including overlays
- Illustrative replacement dataset
- Asset provenance and permission owner
- Final sequence or complete frame plan
Inventory surfaces beyond the main panel
List the areas a capture can reveal: account identity, workspace names, message previews, attachments, browser tabs, notifications, tooltips and open menus. The featured object may be harmless while a sidebar exposes unrelated information.
Use the organization’s actual approval process for material that belongs to customers or colleagues. This checklist helps locate visible content; it does not determine legal permission or replace a privacy review.
Illustrative screen inspection register
A fictional demo shows sample request R-094. The production team chooses a dedicated illustrative workspace and records these checks before capture.
- Queue screen: replace names and subjects in every visible row, not only R-094. Check avatars and any preview text.
- Detail screen: inspect notes, activity history, external links and attachment filenames. A neutral title does not make the underlying conversation safe.
- Account menu: use Example reviewer and a non-sensitive workspace label; avoid opening it if the task does not need it.
- Notification overlay: clear or disable unrelated incoming previews through an approved capture setup; recapture if one appears.
- Exported image: inspect corners and partially cropped panels at full size. Verify any replacement appears consistently in all states.
Choose a replacement method deliberately
Source-level illustrative data keeps the interface natural and can preserve field relationships. Blur may be appropriate for a bounded area, but it can leave enough surrounding context to identify a person or record. Treat it as a technique requiring inspection, not a guarantee.
If an image is edited after capture, record the changed fields and check repeated occurrences. Replacing a requester in the header while leaving the same name in a comment or file path creates an incomplete review.
Repeat inspection after motion and cropping
A camera move can expose regions that were outside the initial crop. A pause or transition may briefly reveal an unreviewed source frame. Inspect the complete sequence, including first and last frames, overlays and thumbnails.
Keep a simple acceptance record: asset, reviewer, replacement performed and unresolved permission question. When an asset cannot be cleared, substitute a fully illustrative screen or remove the scene rather than assuming a short appearance will go unnoticed.
Review checklist
- All visible rows and panels have been inspected.
- Names are checked alongside messages and identifiers.
- Edited values remain consistent across states.
- Camera moves do not reveal unreviewed regions.