Animation and Motion Graphics

01Purpose and scope

• This manual describes how animation and motion graphics work is planned, produced, reviewed and delivered in professional settings. It covers explainer videos, kinetic typography, title sequences, interface motion, product demonstrations and short branded clips for social platforms. Feature film pipelines and full character rigging for games are outside the scope, although many of the timing and review habits here carry over to those areas.
• The guidance is general practice, not legal advice. Music licensing, trademark use, font licenses, medical or financial claims in advertising, and disclosure rules for paid promotion all depend on jurisdiction, distribution channel and the specific content. Check the current authoritative source for each rule and involve the client's legal or compliance reviewer where the material is regulated. This manual does not replace qualified professional judgment, approved procedures or any required authorization.

02Core principles

• Every movement should answer a question the viewer has. A element that moves because it can move usually adds noise. Before animating, write down what the viewer should notice first, second and last, then design the motion to support that order.
• Timing is the main tool. The same position change feels abrupt, soft, playful or heavy depending on duration and easing. Judge timing by playing the piece at real speed on the target device, not by scrubbing a timeline, because scrubbing hides rhythm and pauses.
• Readability comes before decoration. Text on screen must stay long enough for a typical viewer to read it, and it must remain legible at the smallest size it will be shown. Many teams pad reading time generously and confirm the final value with the client, since no single fixed rule covers every audience.
• A motion system keeps a project coherent. Define a short set of durations, easing curves, entrance and exit directions and color roles, then reuse them. A system also makes later revisions faster because changes propagate from a few controls rather than from dozens of hand adjusted keyframes.

03Planning and preparation

• Start with a brief that names the audience, the platform, the duration, the deliverable formats, the required brand elements and the approval path. Ask for the final or near final script before animation begins. Late copy changes are the most common cause of schedule loss in motion work, because text timing, layout and sometimes entire scenes depend on the words.
• Confirm the technical specifications early. Common deliverables include 16:9 for video players, 9:16 for vertical feeds and 1:1 for some social placements. Record the frame rate, resolution, color space, audio sample rate, safe areas and file container the platform requires. If the output is interface motion for a web or mobile product, ask the developer which export format and file size limits apply, since a clip that looks right in a compositing application may be too heavy for the product.
• Identify stakeholders and their roles. The client usually owns the message and brand decisions. A copywriter or subject expert checks accuracy. A brand owner or designer supplies logos, colors and typefaces. A voice talent or composer may need separate contracts. A developer may need to integrate the motion. A legal or compliance reviewer checks claims in regulated categories. Write these names into the plan so approvals do not stall.
• Choose tools by the output, not by habit. A layer based compositing application suits most explainer and title work. A 3D package is useful when perspective, lighting or camera movement carries the concept. Vector animation tools with JSON based export suit lightweight interface motion. The tool matters less than the discipline of keeping assets organized, naming layers clearly and keeping a stable project template for the team.

04Recommended workflow

1. 1
   : Write the brief and confirm the deliverables. List every output file, its aspect ratio, duration, frame rate and destination. Get sign off on the list before any production begins, because format changes later can force rework across every scene.
2. 2
   : Build the script and storyboard. Break the script into scenes with a rough time budget for each. Sketch key frames for each scene and note the motion intent in one or two sentences, such as the title drops in with a short overshoot and settles. Storyboards can be rough, but they must show composition, sequence and the text that appears on screen.
3. 3
   : Create the style frames and motion rules. Produce one or two finished still frames that show color, type, texture and layout. Then write a short motion guide with durations, easing choices, entrance and exit rules and any signature moves. Circulate this guide for approval so the team animates from the same rules.
4. 4
   : Set up the project template. Create a project file with the correct resolution, frame rate, color settings, folder structure and expression or script libraries the team uses. Import the approved assets, check their licenses and convert vector art or photos to the form the project needs. Keep raw assets separate from working comps.
5. 5
   : Block the timing. Before refining shapes or textures, lay out the position, scale and opacity changes with simple keyframes or a timeline sketch. Play the block at real speed. Adjust durations until each scene has enough hold time for reading and comprehension, then refine easing curves.
6. 6
   : Refine motion and detail. Add secondary motion, overlap, texture and sound cues only after the primary timing is locked. Check that secondary motion supports the main action instead of competing with it. Keep layer names and comp structure clean as you go, since they determine how easily the piece can be revised.
7. 7
   : Render test and final outputs. Render short test clips at the target codec and bitrate to check compression, banding and text sharpness. Then render final outputs for each deliverable format from the same master comp. Where the same piece must appear in several sizes, use separate comps with shared controls rather than duplicating the timeline.
8. 8
   : Deliver the package and close the project. Provide the final files, source project, fonts or license records, an asset list, a short readme with revision notes and any export settings. Archive the project with a version label. Confirm with the client that the files were received and that the approval record is complete.

05Quality checks, risk controls and compliance

• Run a technical check on every final render. Confirm frame rate, resolution, aspect ratio, audio levels and loudness against the platform spec. Scrub through the file and look for dropped frames, color shifts, banding in gradients, halos around text and clipped audio. Check that loops start and end on matching frames if the piece is meant to repeat.
• Check legibility on the smallest intended screen. Keep key text inside the platform safe area, which is the region that will not be covered by interface elements or cropped in a different aspect ratio. View the piece on a phone or a low resolution monitor, since problems at small sizes are easy to miss on a large display.
• Assess flashing and motion risk. The Web Content Accessibility Guidelines, guideline 2.3.1 in version 2.x, limit content that flashes more than three times in any one second period. Strobing effects and rapid high contrast alternation can trigger photosensitive seizures, so review any rapid flashing against that rule. Large parallax or continuous motion may also affect viewers with vestibular disorders, so provide a reduced motion version where the platform allows it.
• Verify rights and claims. Keep license records for music, sound effects, fonts, stock footage and images. Confirm that every product claim, testimonial or statistic shown on screen is approved by the client and supported by documentation. Where advertising rules apply, the rules vary by jurisdiction and medium, so check the current requirements with the client's compliance reviewer rather than assuming that a general practice is sufficient.
• Add captions or on screen text alternatives where the piece carries essential information in speech. Confirm that caption timing matches the animation and that captions do not cover key graphics. This is a practical habit even where no formal requirement applies.

06Collaboration and documentation

• Use a clear review loop. Share review links with timestamped comments, and ask reviewers to use one consolidated comment document or tool. Group feedback by category, such as message, timing, text, brand, technical and legal. Ask the client to approve each round in writing so that later changes can be tracked against a known version.
• Name files and comps consistently. A simple pattern such as project, scene number, version and date stamp works for most teams, though the date stamp should follow the internal convention rather than any external rule. Keep a changelog that records what changed in each version and who requested it. This record protects the team when a client asks why a scene now runs longer than the approved version.
• Document the motion guide, asset register and export settings. A new animator or developer should be able to open the project and understand the structure within an hour. Include notes on any expressions, scripts or plugins used, because a missing plugin can make a project unopenable months later.
• Coordinate closely with developers when motion is part of a product. Agree on the export format, file size budget, playback frame rate, reduced motion behavior and how the motion will be triggered. Share a short test build early so the developer can report performance problems before the timeline is locked.

07Measures and continuous improvement

• Track indicators that describe how the work actually runs. Useful measures include the number of review rounds per deliverable, the share of revision requests that change the message rather than the polish, the time between brief approval and first draft, the number of late script changes, and the number of technical rejections from platforms or developers. Compare these across projects of similar size rather than against a fixed external benchmark.
• For delivered pieces, collect whatever the platform or client already reports, such as completion rate, watch time or click through, and read them with care. Audience data reflects distribution, audience and placement as well as motion quality, so it cannot isolate the effect of one animation choice. Use it to form hypotheses for the next project rather than as proof.
• Run a short retrospective after each project. Ask what slowed the schedule, which tools or templates helped, which motion rules were unclear and which review steps added little value. Update the motion guide and project template with the lessons. Small changes made consistently tend to pay back more than occasional large overhauls.

08Common mistakes and how to prevent them

• Overanimating is the most frequent problem. When every element moves, the viewer cannot tell which idea matters. Limit primary motion to one or two elements per beat and let the rest hold. Review each scene by asking whether removing a movement would weaken the message.
• Using default easing creates a generic feel. Linear motion looks mechanical for most organic subjects, and default ease curves can look like a template. Shape curves deliberately and compare two or three options at real speed.
• Designing at the wrong frame rate or aspect ratio causes rework. A piece built at one rate and delivered at another can show judder or timing drift. Fix the project specification at the start and confirm it again when the deliverable list changes.
• Placing text too close to the edges or too briefly loses information. Keep text inside the safe area, check the smallest viewing size and hold each line long enough to read at a relaxed pace.
• Baking compression artifacts into source files creates problems later. Keep a lossless or high quality master and render compressed versions from it. Never edit a compressed file to make a new version.
• Forgetting licenses and claim approvals creates legal exposure. Build a license register at the start and make the claim approval step part of the review loop, not an afterthought.
• Delivering only the rendered video leaves the client stranded. Always include the source project, font and license records, and a readme so revisions can happen without rebuilding the piece from memory.

09Practical checklist

• Confirm the brief, script, deliverable list, frame rate, aspect ratio and approval path in writing before animation starts.
• Build a motion guide with durations, easing rules, entrance and exit directions and color roles, and get it approved.
• Block the timing at real speed and confirm that every text element stays on screen long enough to read.
• Check each final render for technical specification, banding, loop seams, audio levels and safe area placement.
• Review rapid flashing against the accessibility guideline limit and provide a reduced motion version where the platform allows it.
• Verify licenses for music, fonts, stock and images, and confirm that every claim shown on screen has documented approval.
• Record every version in a changelog and label each delivered file with its version number.
• Deliver the final files, source project, asset register, export settings and readme, then run a short retrospective.

★Learning sources

• Micro Degree: Animation and Motion Graphics
• Micro Degree: 2D Animation Fundamentals
• Micro Degree: 3D Animation Techniques
• Micro Degree: Illustration Fundamentals