Prompt Mode vs Script Mode in ToMotion AI

Look at the material you have before opening the create screen. A topic, outline or collection of notes still needs to become spoken language. A finished voiceover script has already gone through that writing process.

Prompt mode suits the first situation: describe the explanation you need and let ToMotion develop the narration. Script mode suits the second: enable Use own script and supply the narration yourself. Both workflows also need a clear idea of what the viewer should see and learn.

In the create screen, Use own script is the switch between these inputs. When enabled, the form separates Video instructions from Script. Treat those fields as different parts of the same brief.

Leave Use own script off. In the main input, explain the subject and the viewer's starting knowledge. A video for someone learning a process needs different language from a refresher for an experienced colleague.

Describe what the viewer should be able to explain or do afterward. Add the facts, terminology and examples that belong in the video. Paste relevant source notes into the brief instead of assuming the system knows your organization's process.

Give the explanation a useful direction: introduce the problem, show how it works, then finish with the action you want the viewer to take. If a detail is unknown, say so. Ask for unsupported promises and invented product features to be left out.

Use the available controls to choose the voice, language, visual style, orientation and intended length. Read the brief again after choosing those settings; a compact social video and a detailed lesson need different amounts of material.

The public example below starts from the short prompt "Newton second law". Its narration expands that topic into an explanation of force, mass and acceleration, with skateboard and shopping-cart examples. Open the source page to compare the input with the full narration and finished video.

This illustrates the writing work you delegate when you start from a topic. If a lesson must use your approved wording, prepare that narration for Use own script and review the generated voiceover against it. This example does not test script fidelity or compare the two modes side by side.

The public page records a requested length of 60 seconds and a finished duration of 1 minute 4 seconds. Check the actual exported runtime when a lesson or publishing slot has a strict limit. The public record does not establish generation time, attempt count or billed credits, so those are not claimed here.

Enable Use own script. Add the intended audience and visual direction to Video instructions, then paste the spoken copy into Script. Complete both fields before starting generation.

Write the script as something a person would say aloud. Replace slide fragments with complete thoughts, explain unfamiliar terms, and make the transitions between ideas easy to follow. Keep a copy of the approved draft so you can compare it with the finished voiceover.

Remove editing comments and production directions from the narration. For example, a note asking for a diagram belongs in Video instructions. Keep a heading in Script only if hearing that heading helps the explanation.

Read the narration at a comfortable speaking pace. If it feels crowded for the intended length, simplify the explanation or choose a more suitable length in the interface. Leave room for a listener to absorb unfamiliar ideas.

Video instructions can describe the scene treatment, audience, mood and visual relationships. Instead of asking for an impressive animation, explain which objects should be connected, what changes, and what the viewer needs to notice.

For a process explanation, describe how information moves between people or stages. For a concept, suggest a diagram or a familiar analogy. Keep the direction consistent with the spoken script so the visuals help the viewer follow it.

If particular labels matter, name them in the instructions and inspect the rendered result. Supplying narration does not by itself approve every label, diagram or visual interpretation in the finished video.

The following examples are sample inputs you can adapt. They are not recordings or claims about a generated result.

Prompt: Create an animated explainer for colleagues who are taking over an active project. Explain how a useful handoff connects the project's purpose, current work and next action. Use a shared project notebook as the visual idea. Show how scattered messages leave a new owner guessing, then show a clear handoff note that makes the next action easy to find. Keep the tone calm and practical. Do not invent company rules or deadlines. End by inviting the viewer to prepare a handoff note before transferring responsibility.

This brief gives ToMotion a topic, an audience, a visual idea and an outcome. It leaves the spoken phrasing open. Adapt the process details to match how your team actually works before generating a training video.

Script: A project handoff should help the next person continue with confidence. Start by explaining what the work is meant to achieve. Describe what is already complete and what still needs attention. Point to the current files, record any open questions, and make the next action clear. Imagine arriving at a desk covered in loose notes. The information may be there, but finding the way forward takes effort. A useful handoff brings those notes into a shared story. Before you pass the work on, read your handoff from the next person's perspective. Can they understand where things stand and what to do next?

Video instructions: Create a clear workplace explainer for colleagues taking over an active project. Begin with scattered notes around a project notebook, then organize the notes into a readable flow. Use simple diagrams to connect completed work, open questions and the next action. Keep the mood reassuring and avoid adding fictional company branding or policy claims.

Here, the script supplies the spoken explanation while the instructions describe its visual treatment. You can revise the visual brief without putting those production notes into the voiceover text.

Before generating from your own script, compare the copy with the source material. Check names, specialized terminology and any product or process claims. Have the person responsible for the material approve the wording when your workflow calls for approval.

After generation, listen to the voiceover and watch the visuals together. Check pronunciation, the relationship between labels and narration, and whether the ending delivers the intended takeaway. A correct sentence can still be illustrated in a confusing way.

When revising, identify where the problem started. Change the brief if the explanation chose the wrong focus. Edit the script if the wording is unclear. Adjust the visual instructions if the narration is useful but the scenes distract from it.

For internal material, turn off Publish to Public Gallery before generating. It is selected by default on a fresh create form. Check the setting on every project; public watch pages can expose the prompt and narration as well as the video.

A topic title is not a finished script. If you need the subject developed into an explanation, start with a prompt. If you already have approved narration, choose Use own script rather than relying on a general brief to preserve it.

Avoid conflicting instructions. A script that explains a workplace process will be harder to follow if the visual brief asks for unrelated imagery. Read both fields together and remove requests that pull the video away from its purpose.

Save the brief, script and settings that produced a useful result. For a related video, update the actual subject and source facts instead of carrying over details that no longer apply.