A Motion-Change Request Built Around Start, Transition and End States

Clients often ask an animation studio for a change in words like "make it snappier" or "it feels off." The studio then guesses, produces a revision, and discovers the guess was wrong. This article proposes one small request format as an example workflow. It is not a description of observed results, and a studio can adapt or drop any part that does not suit its work.

The idea is simple. Every motion change request describes three states: where the thing starts, what the change between them should feel like, and where it ends. The client describes them in plain language and points at something visible, such as a timecode label or a named scene, rather than a technical measurement.

Inputs the request should collect

The shot or scene name exactly as it appears in the current review version.
The item that moves, named the way the client sees it (for example "the logo" or "the left character's hand").
Start state: what the viewer sees just before the movement begins.
Transition: one sentence about how the change should behave, chosen from a short list the studio offers, such as "gradual," "sudden," "bouncy," "steady," or "other, described below."
End state: what the viewer sees once the movement has finished and the item rests.
One reference, optional: a sentence about another moment in this same project that already feels right.

The studio should not ask the client for numbers such as speeds or durations. Those belong to the studio's own judgment. The form simply captures intent.

Decision branches

When the request arrives, the studio checks three things in order.

Are all three states present? If the end state is missing, send back one question: "Where should it rest when it stops?" Do not start work.
Does the start state match the current version? If the client describes a start that differs from what the studio sees, reply with a still from the current version and ask whether that is the intended beginning. Work waits for a yes.
Is the transition word clear? If the client writes "other," the studio paraphrases it back in one sentence and asks for a confirmation.

If all three pass, the studio proceeds with a single revision for that item.

Stop conditions

Stop and return to the client, instead of producing a revision, when any of these hold: the request names more than one moving item and the states conflict; the end state of this movement contradicts the start state of the next scene; or the client's description would require changing something outside the named item. In those cases the studio splits the request into separate ones or asks which takes priority. Producing a best-effort revision anyway tends to create a second round of confusion.

Worked example (a proposed illustration)

Suppose a client writes: Scene "Intro", item "the title card". Start: the card is off to the left of the screen, partly hidden. Transition: "gradual, like it is being slid into place." End: the card sits centred and the subtitle is visible beneath it.

The studio compares with the current version and sees the card starts centred and fades in. The start state differs, so the studio replies with a still of the current beginning and asks, "Do you want the card to begin off the left edge instead of fading in?" The client confirms. The studio then produces one revision, labelled with the same three states, so the client can check each against what they asked for.

Not a substitute for judgment

This format does not claim to guarantee that a revision will please everyone. It only makes the disagreement visible earlier. Accessibility considerations, timing choices and technical delivery decisions stay with the studio and should be discussed separately where they matter, rather than assumed from this form.

Practical acceptance test

Before adopting the format, run it on three past change requests that were confusing. For each, rewrite it into the three states, using only what the client originally said or showed.

Pass if:

At least two of the three can be fully filled in without asking the client anything new.
For the third, the missing piece is identifiable as one specific question rather than a vague unease.
A colleague who did not read the original email can describe the intended start and end of each movement back to you accurately.

Fail if a colleague describes a different end state than the one intended. In that case, change the wording of the form's prompts, not the client. Repeat with three fresh requests after changing the prompts.

Conclusion

A motion-change request that names a start, a transition and an end gives both sides something to check. It keeps feeling-based feedback, but anchors it to what is visible. Treat the list of transition words, the optional reference and even the number of states as choices to tune for your studio. The one part worth keeping is the habit of confirming the start and end before any revision begins.