Skip to main content
Out of Scope

is adding motion to a static design out of scope?

Yes — turning a static deliverable into an animated one is a different craft and a different output, so it sits outside a contract scoped for static work. The rare exception is a contract that explicitly bundled motion or named animated formats from the start.

Why this answer

Animation isn't a finishing touch on a static deliverable — it's a separate discipline with its own tools, its own time cost, and its own skill set. A static design or graphic is built to be looked at; an animated version has to be built to move, which means timing, easing, sequencing, and often rebuilding the asset entirely so its parts can be controlled independently. So when a client asks you to 'just add a little motion' to something you delivered flat, they're not asking for a revision of the existing work — they're asking for a new deliverable in a different medium that happens to start from the same visual. The reason this trips people up is that the source looks finished, so adding movement feels incremental. It isn't. Producing motion can easily exceed the time the static piece took, because you're not editing the deliverable, you're authoring a new one on top of it. A contract scoped for static outputs priced static effort; motion is effort that was never in that number.

When the answer flips

The verdict softens only when motion was genuinely part of the deal from the outset. If your contract named animated deliverables, listed motion formats, or scoped the project as including movement, then producing it is owed — and any dispute is really about how much, not whether. It also bends toward Ambiguous if the original brief was vague enough that 'the asset' could reasonably have meant a moving version, though that's uncommon for work delivered and accepted as static. The flip stays firmly Out of Scope for the usual case: a deliverable scoped, produced, and accepted as a still, now being asked to move. The more the request involves rebuilding the asset for animation, syncing it to audio, or producing multiple motion variants, the more clearly it's a fresh commission rather than an extension of the old one.

What to do next

Frame motion as the new deliverable it is, and make commissioning it feel like an exciting next step rather than a denied request. Acknowledge the static work as complete and accepted, then position animation as its own piece: 'The static version is wrapped — bringing it to life in motion is a separate production I'd love to scope for you.' Price it on the real effort, which clients routinely underestimate, so quote it as standalone production with its own fee and timeline rather than a small add-on to the static number. If it helps the client understand the gap, name what motion actually requires — rebuilding the asset to move, timing, rendering — so 'just add motion' lands as the substantial work it is. Put it in a fresh scope or change order. And going forward, make your deliverables clause specify the medium explicitly, because 'the graphic' or 'the design' without a stated format is what lets a client assume motion was always on the table.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

The client thinks adding motion is a quick effect on the file I already made. How do I explain it?+

Show them what motion actually involves underneath the surface. Explain that animating means rebuilding the asset so its parts can move independently, then authoring the timing, easing, and sequencing that make movement feel intentional — work that often takes longer than the static piece did. Most clients picture a one-click effect because the source looks finished; the gap is invisible to them until you describe it. Once they understand they're commissioning a new production rather than tweaking a file, the price stops feeling surprising and starts feeling fair.

I delivered a static logo and now they want an animated version for video. Same project or new?+

New. An animated logo is a distinct deliverable in a distinct medium, even though it starts from the static mark you already provided. The static logo was built to be placed; the animated one has to be built to move and to read in motion against video, which means rebuilding and authoring movement from scratch. Treat it as a fresh commission with its own scope and fee. The shared starting point saves a little setup, but the animation itself is new production that was never inside the static logo's price.

Can I reuse the static files, so shouldn't the animation be cheaper?+

The static files give you a starting visual, not a finished basis for motion, so the savings are smaller than clients expect. Often the asset has to be rebuilt — separated into movable parts, re-prepared for animation — before any movement can happen at all. You can reflect the modest head start of having the visual already designed, but don't let 'you already have the files' pull the price toward a discount on the real production work. Quote the animation on the effort it genuinely takes, with the existing design as a contributor to that effort, not a replacement for it.

What if my contract just said 'the graphic' without specifying static or animated?+

Then honor the reasonable reading and fix the ambiguity going forward. If the work was briefed, produced, and accepted as a static graphic, that shared understanding is the scope, regardless of the loose wording — a vague noun doesn't retroactively include a whole second medium. Deliver against what was actually agreed and made, and treat animation as new. Then tighten your deliverables clause to state the medium and format explicitly, so 'the graphic' can never again be stretched to imply movement that was never priced or planned.

They want a few motion variations to test. Does that change the scope conversation?+

It enlarges it. Multiple motion variants mean multiple authored animations, each with its own timing and rendering, so a request for variations is a request for several deliverables, not one. Scope it as such: a base animation plus additional variants, each priced for the production it requires. Be clear that testing variations is a normal, worthwhile thing to do and also genuinely more work than a single motion piece. Pricing the set honestly up front prevents the client from assuming 'a few options' is free iteration on one animation.

How do I scope contracts so motion versus static is never ambiguous?+

Name the medium and format for every deliverable, and state plainly whether animation is included. A deliverables clause that says 'static graphic, delivered as [format]' draws the line before anyone can blur it, and if motion is in the deal, it should appear as its own listed item with its own scope. The single most common cause of these disputes is a clause that names a visual without naming whether it moves. One specific phrase per deliverable closes that gap and turns 'can you just animate it' into a clean new-commission conversation.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide