Demonstrate a form without showing every keystroke

Separate consequential choices, straightforward values and repeated entries. A permission level or destination needs explanation because the selected value changes behavior. A fictional display name may need only a readable completed field. Repeated address lines rarely need individual animation unless formatting is the lesson.

List required and optional fields using the real interface. Do not hide a required field beneath a crop and then imply the displayed entries alone permit submission. If the form begins partly completed, label that starting condition.

The fictional form contains Subject, Reviewer, Due date and Note. The sample task is to submit “Sample booklet” to Example reviewer. Use a configured account and actual screenshots of the form behavior.

• Subject: show the completed illustrative value “Sample booklet”; no character-by-character typing is needed.
• Reviewer: show the selection and explain that it determines who receives this request. Keep the chosen identity visible afterward.
• Due date: show the product’s accepted format and one valid example. If the date is optional, preserve that label.
• Note: reveal a short completed sentence, “Please check the sample heading.” Avoid a long text animation that distracts from routing.
• Submit: show the real action and resulting request identifier. A filled form is not proof that a request was created.

For a training version, intentionally leave Reviewer unselected if the supplied product actually validates that condition. Hold the real message, “Choose a reviewer,” then select the correct role and retry. Identify this as an illustrative recovery path rather than an unexplained failure.

Do not invent red borders or validation wording to make the film more dramatic. If the real form validates on blur, show that trigger. If it validates only on submission, preserve the submit attempt so the feedback has a cause.

End with the created request and its selected reviewer. If submission is asynchronous, show the distinction between pending and accepted states. Avoid replacing product confirmation with a celebratory graphic that hides the actual result.

For a shorter version, remove the recovery branch and link it from training material. Keep all consequential field choices. For a longer version, explain one optional field’s effect rather than adding more decorative typing.