How to brief an architectural animation before production.

Start with the decision the film must help someone make.

A moving camera does not automatically explain architecture better than a still image. A useful film answers a particular question: how a visitor approaches the entrance, how a courtyard connects two buildings, how a home opens to a terrace, or how a proposed development sits in its surroundings. Write that question at the top of the brief. If a still image, plan or interactive floor selector answers it more clearly, use that instead.

Record the intended audience and channel. A film for an internal design review can stop on unresolved details; a public presentation needs clear context and visible qualification of anything provisional. A short social cut and a longer presentation film are not necessarily the same edit at different lengths. They have different reading times, crops and calls to action.

Specify the project revision, the person who can approve architectural accuracy and the person who can approve editorial direction. This separates what is built in the model from how it is shown. The brief should also state which drawings, material schedules and landscape decisions are authoritative.

Choose a film structure before asking for a duration.

“A 60-second fly-through” describes time, not a narrative. Decide whether the film is a continuous route, a sequence of composed camera shots, a phased construction explanation or a set of short spatial studies. A continuous route can establish orientation but may spend too long passing blank walls. A montage can explain several spaces quickly but needs visual anchors so the viewer knows where they are.

Do not confuse a rendered film with an interactive 360° tour. The former has a fixed editorial sequence; the latter lets a visitor choose where to look and requires a different interaction and QA plan.

Turn the architectural story into a shot list with acceptance criteria.

Every shot should have an ID, intended message, location, camera move, approximate duration, design reference and approval status. A storyboard can be a contact sheet of rough renders with arrows and notes. It need not be a polished film. The point is to make the sequence reviewable before expensive frames are rendered.

For each shot, add a “must show” and a “must not imply” line. For example, “show the shared path connecting the two entrances” and “do not imply the private gardens are publicly accessible.” These two lines are often more useful than ten mood references.

Keep camera motion believable and protect the building geometry.

Camera speed should follow the amount of information in the frame. A fast orbit can look energetic while hiding the very proportions a client needs to understand. Avoid extreme lens choices simply to fit the whole building into a narrow crop. Use a calm eye-level view when the experience of a person is the subject; use an elevated view only when the site relationships genuinely require it.

Set a consistent rule for eye height, verticals, horizon, movement speed and the amount of roll or tilt permitted. Check camera paths for collisions with walls, doors, furniture and planting. If a shot travels through glazing, make it clear whether that is an intentional transition rather than a literal human route. A camera should not silently pass through a closed wall or make a room appear wider than the approved plan.

Freeze the architectural model revision and approved camera paths at a defined gate. A later request to move a wall can affect multiple shots, lighting caches and transitions, not just one frame. The BIM/CAD handover guide

Identify what is confirmed, provisional and purely illustrative.

Moving images can make provisional design choices feel more definite because the viewer sees them from several angles. Establish an explicit status for façades, balconies, landscape boundaries, neighbouring buildings, people, vehicles and furniture. Keep the same approved details consistent across every shot. A railing should not change profile between the courtyard and terrace sequences.

For a development film, distinguish verified views from design-stage impressions. Do not create an uninterrupted panorama that suggests a guaranteed view from a specific unit unless the relevant geometry, viewpoint and context have been checked. Avoid showing mature trees as if they were present at handover when only young planting is proposed. The separate landscape accuracy checklist

Put any necessary qualification where the film will be consumed, not only in the producer’s email. If a disclaimer is needed, agree the exact wording, display duration and small-screen readability with the responsible project team. Do not treat this guide as legal advice for marketing or planning disclosures.

Approve an animatic before committing to final frames.

An animatic is a rough timed sequence of stills or low-quality moving previews. It is the right place to test the opening, orientation, transitions and total rhythm. Review it without music first. If the architecture is incomprehensible without a soundtrack, the edit is probably relying on mood to replace information.

At the animatic gate, approve shot order, framing, approximate timing, visible design elements and the main editorial message. Keep material polish and atmospheric effects for later. At the next gate, inspect model accuracy, material direction and lighting in representative frames. Only after those decisions should the team invest in full-resolution sequences and final sound.

A storyboard approval is not approval of unresolved geometry. Maintain a separate issue log for design questions. The rendering feedback guide

Choose light and weather for continuity, not spectacle.

A film can move through multiple spaces, but it should not accidentally jump between incompatible lighting conditions. Record whether the sequence is one continuous time of day, a deliberate change of scene or a collection of separate moments. When a camera turns around a building, shadows should remain consistent with the chosen sun setup unless the edit explicitly changes time.

Do not promise a specific sunlight condition from a cinematic render alone. A planning claim about daylight or overshadowing needs a separately defined method, date, time zone, location and validated model. For technical checks, use the sun and shadow accuracy guide. For an atmospheric film, describe the lighting as illustrative when it has not been verified against a stated solar scenario.

Reflections, exposure and white balance also need continuity. A warm interior cut next to a cool exterior can be intentional, but abrupt changes in façade colour or glazing reflectivity often read as modelling mistakes. Compare representative frames side by side before rendering the whole sequence.

Use people and movement to explain scale without inventing use.

People, vehicles, curtains, foliage and water can add scale and life. They also create decisions about movement, realism and what the project appears to offer. Specify where activity is helpful and where a quiet shot communicates more. A crowded courtyard may obscure a route or imply a programme that has not been designed.

Check that people do not intersect furniture or walls, that walking direction matches the path and that visible doors open plausibly. Avoid animated traffic that conflicts with the actual circulation plan. If a scene includes a family on a private terrace or a café in a ground-floor unit, confirm whether those uses are proposed, approved or merely illustrative.

Any identifiable people, stock footage, music, voice recordings or third-party assets require suitable permission for the intended use. Do not infer rights from an asset being downloadable or included in a software library. Record asset origin and licensing responsibilities in the handover.

Plan a film that still works without sound.

Many visitors first encounter an architectural film in a feed, on a muted website or during a presentation with unreliable audio. The visual sequence and any essential on-screen text should carry the message on their own. If narration is used, script it against the approved shots and verify every factual statement about the development.

Decide early whether the output needs music, voice-over, ambient sound, captions, a descriptive transcript or audio description. These are not interchangeable. Captions cover relevant speech and sound information; audio description communicates important visual information that is otherwise inaccessible. The W3C WAI guidance on planning accessible video explains how requirements depend on the type of media and its content.

Keep text away from areas likely to be cropped in vertical edits. Check its contrast and reading time at actual phone size. Record the music track, source, permitted channels, territory and duration of licence where relevant. If rights are unresolved, deliver a silent review cut and do not assume that a temporary soundtrack can be published.

Define outputs as a matrix, not as “one video file”.

Before final rendering, list where the film will appear: website hero, project page, presentation screen, social feed or exhibition display. Agree a master aspect ratio and whether alternative crops need re-composed shots. A vertical cut from a wide architectural frame can remove an entrance or slice off the building; it is not always a simple automated export.

Specify the expected delivery format and playback environment, then test the files there. A presentation screen may expose banding or motion artefacts that were invisible in a small review player. A website may need a separate lightweight version and a static poster. Preserve the approved master separately from compressed derivatives.

Review with timecodes, then sign off the actual exports.

Review comments should reference a version, shot ID and timecode range. “At 00:18, the garden boundary is too far behind the terrace; compare with site plan L-04” is actionable. “The middle feels wrong” is a conversation starter. Nominate one person to consolidate feedback from the architect, developer and marketing team before it reaches the editor.

Use three explicit gates: storyboard/animatic, look and accuracy, and final edit and exports. At the final gate, check the real files, not just a streamed preview. Watch at normal speed, with and without sound, and at the intended screen size. Confirm opening and closing frames, text spelling, crops, playback, captions, credits and any disclosures.

Changes to approved architecture after final render are not automatically minor retouches. Record which shots need re-rendering and which derivatives must be replaced. For a live development campaign, the rendering change-control guide

Make the website version playable, accessible and optional.

A heavy video should not block access to the project information. On a website, give visitors a clear play control, a meaningful poster frame and a visible path to the same core facts in text or still imagery. Avoid forcing audio or continuous motion on someone who came to read a project description. A motion-sensitive visitor should be able to stop animation; an autoplaying hero needs particular care.

Browser video loading is affected by attributes such as poster, preload and playsinline. The MDN reference for the HTML video element explains their behaviour. Test the actual embed on a narrow phone, slower connection and keyboard-only navigation. Do not assume a compressed file is accessible simply because it loads quickly.

Check that the video has an accessible name, usable controls and the appropriate media alternatives for its content. Follow W3C WAI’s accessible audio and video guidance rather than treating auto-generated subtitles as a complete accessibility strategy. Keep a static image and project summary available if playback fails.

A final architectural animation brief checklist.

• The audience, channel and single communication goal are recorded.
• The approved architectural model revision and decision owner are identified.
• The shot list states location, message, camera move, approximate timing and must-show details.
• Provisional design elements and visualisation disclaimers are explicitly listed.
• Camera paths preserve proportions, access routes and relevant context.
• The storyboard or animatic has been reviewed before final frames.
• Lighting, material appearance and landscape status are consistent across shots.
• People, moving objects and third-party assets have appropriate use approval.
• Narration, music, captions, audio description and text alternatives have named owners.
• Master, website, social and presentation deliverables are defined separately.
• Comments use shot IDs, timecodes and a consolidated approval register.
• The exported film has been tested with and without sound on its intended devices.
• The rights register and final approval identify where each version may be published.

A well-structured animation brief does not remove creative freedom. It makes room for it by protecting the architectural decisions, audience needs and delivery constraints before production starts. The result should explain the proposal more clearly, not merely move a camera through a beautiful model.