8 Steps for Revit Legends: Trainer Backed Sheet Ready Templates
A legend in Revit is a dedicated view that displays symbols, components, and text to explain what the drawings mean, and the fastest way to build one is View tab, Create panel, Legends, Legend, then name it and set a scale before clicking OK. This guide walks through that process and covers the main legend types: material, family, room number, column, and keynote legends, with practical tips on drawing symbols for takeoff to ensure consistent annotation.
TL;DR:
Use the Create panel to quickly build legends matching their intended sheet scale and purpose, such as material, family, or keynote legends.
Adjust detail level and subcategory visibility to ensure clarity, hiding unnecessary elements for legibility at the printed size.
Place legends on sheets with proper alignment and test print accuracy by exporting PDFs at 100% zoom to confirm readability.
Reuse legends efficiently by transferring project standards or saving them in office templates, but verify family and style consistency after transfer.
Avoid placing legend components in drafting views, as they are linked to model families and only work correctly in model-based views or callouts.
Table of Contents
What legends do and which legend types to use
A legend exists to explain the drawing set, not to model anything new. Unlike a schedule, which pulls live data from the project, a legend only displays representative symbols and text that you control directly. Choosing the right type before you start saves rework later.
Material legends show finish or material swatches and are typically placed near floor plans or finish schedules.
Family or component legends display door, window, or furniture types and usually sit on general notes or typical details sheets.
Room number legends explain numbering logic and pair well with floor plan sheets.
Column legends clarify grid and structural naming, often placed alongside structural plans.
Keynote legends list keynote text and numbers and commonly appear on detail or specification sheets.
Reach for a drafting view instead when you need generic, non-model annotation that has nothing to do with legend components, a distinction covered in more depth in our piece on drafting views.
Step-by-step: create a legend view and build a basic legend
Autodesk’s own guidance on creating a legend lays out the exact path, and it is worth following in order rather than improvising.
Go to the View tab, open the Create panel, and select Legends, then Legend.
Name the view something specific, such as “Door Legend” or “Finish Legend,” and choose a scale that matches where it will sit on sheets.
Click OK to open the new legend view, which starts blank.
Add model-based items with Annotate tab, Component, Legend Component, then pick the family and type from the dropdown.
Add non-model symbols, such as north arrows or revision triangles, through Annotate tab, Symbol.
Add explanatory text with the Text tool, keeping phrasing short and consistent.
Check detail level and subcategory visibility so each component displays only what the legend needs to communicate.
Place the finished legend on a sheet and zoom to 100% to confirm it reads correctly at print scale.
Run through a short checklist before moving on: confirm the legend’s purpose, lock in scale and detail level, adjust subcategory visibility, align components neatly, and test the view on an actual sheet rather than just in the view window.
Pro Tip: Build your legend at the exact scale it will be printed at, not a convenient round number, so you catch sizing problems before they hit the sheet.
Adding and customizing legend components and annotations
Detail level and view scale directly affect how a legend component looks, since a component drawn at Fine detail can show far more than the same family at Coarse. Subcategory visibility is the main lever for simplifying a cluttered legend component. For a door and frame legend, for example, you can hide everything except the Frame and Mullion subcategories so the legend stays readable rather than showing every embedded line of the family, a point Autodesk’s support documentation confirms directly.
Switch the legend component’s type selector to show a different size or style without rebuilding the whole legend.
Use Visibility/Graphics overrides on the legend view to hide subcategories that add visual noise.
Apply consistent text styles, filled regions, and line weights across every legend in the project so they read as one family of drawings.
Detail level choices ripple through every legend component on the sheet, and our guide to Revit detail level breaks down how that setting changes what gets drawn.
Pro Tip: Save a custom line weight and text style combination as a view template parameter so every new legend starts with the same look.
Placing legend views on sheets and print or readability checks
A legend view drops onto a sheet the same way any other view does: drag it from the Project Browser, then set the viewport scale to match the legend’s own scale so nothing stretches or shrinks unexpectedly. Align it with the title block grid so spacing looks intentional rather than accidental.
Confirm font sizes are legible at the sheet’s intended print size, not just on screen.
Check line weights print clearly at both full size and half size PDF exports.
Leave consistent spacing between legend rows so the eye can scan quickly.
Export a test PDF and zoom to 100% before issuing anything to a client or contractor.
If text looks too small or crowded once printed, the fix is almost always to revisit the legend’s own scale rather than resizing text after the fact, since inconsistent text sizes across legends create a messier drawing set than a slightly larger legend view.
Copying and reusing legends across projects
Reusing a legend you already built saves real time, but the method you choose matters. Three options exist, each with different risk levels.
Transfer Project Standards moves families, line styles, and object styles between open projects, which works well when both files share a similar setup.
Copy and paste a legend view directly between two open projects is faster for a single legend but can bring along unexpected dependencies.
Saving a legend inside an office template is the most reliable long-term method, since every new project starts with the legend already built and standardized.
After any transfer, check that families loaded correctly, that types match what the legend expects, and that text styles and view templates carried over as intended. When a transfer introduces more missing elements than it saves in time, rebuilding the legend from scratch in the new project is often faster than chasing down every broken reference.
Common pitfalls and troubleshooting
The most common confusion is expecting legend components to work inside a drafting view. They do not: Autodesk Community discussion on legend components in drafting views confirms this limitation and points toward callouts or model-based views as the correct alternative when model-linked geometry is required.
If a legend component looks blank or shows an error after copying between projects, the linked family likely failed to load. Reload it manually from the Project Browser.
If symbols display inconsistently, check that the view’s Visibility/Graphics settings and any applied view template are not overriding subcategory visibility.
If a legend component shows the wrong type, confirm the family’s type parameters match the version loaded in the current project.
One frequent anti-pattern shows up repeatedly in Autodesk Community threads: users try to fake legend components inside drafting views, then wonder why nothing updates. Switching to a dedicated legend view or a model-based callout solves it outright.
Trainer tips from S15Studio: templates, naming conventions and time-saving habits
We build a starter legend view directly into our office template, complete with a preset title block reference and locked text styles, so nobody rebuilds the basics from zero. Applying a view template to every legend locks scale and appearance in one move. Consistent naming across legend views, short demo clips for new team members, and a quick QA pass before issuing drawings round out the habits that save the most time.
Pro Tip: Name every legend view with its content and intended sheet together, such as “Door Legend, A-601,” so anyone browsing the project tree knows exactly where it belongs.
Handling legends in workshared and team environments
Legends can cause quiet conflicts in a workshared model because multiple team members may edit the same legend view without realizing someone else already changed a component or text style. The safest approach is to assign ownership: one person maintains the master legend views for a project, and everyone else requests changes rather than editing directly. This avoids the common scenario where two people adjust the same door legend in parallel and one set of edits silently overwrites the other on synchronize.
Borrowing elements inside a legend view works the same way as borrowing anywhere else in a workshared file: Revit requests ownership of the elements you touch, and another user editing the same legend at the same time triggers a conflict warning. Keeping legend views on a short, well-communicated editing schedule reduces how often that happens.
Worksharing display settings also matter here. A legend component tied to a family that someone else is actively editing can show as grayed out or unavailable until that element is relinquished. Running a regular synchronize with central and relinquishing unused elements keeps legend views current for the whole team rather than stuck on stale data.
Teams that formalize these habits, rather than leaving legend edits to whoever opens the file first, tend to spend far less time untangling conflicting legend versions before issue. Our Worksharing Course goes deeper into collaborative workflows like this one for teams working across the same central model.
A trainer’s perspective: why clean legends matter for coordination
Clean, consistent legends cut down on site questions because nobody has to guess what a symbol means. Standardize them across a practice once you notice the same clarification question coming up more than once.
— Steve
S15Studio courses that teach these skills
Learning these workflows alongside a structured course beats piecing it together from scattered tutorials, especially once views, sheets, and legends all need to work together consistently. Our Revit Introduction course covers the fundamentals that make legend creation straightforward, while our Revit Course Only takes you from those basics through full project documentation, with templates, trainer feedback, and lifetime access to materials included.
Start with whichever course matches where you are, and build legend habits that carry into every project afterward.
FAQ
How do I create a legend in Revit?
Open the View tab, select Create, then Legends, then Legend, name the view, and choose a scale before clicking OK. From there, add model components through Annotate, Component, Legend Component, and annotation symbols through Annotate, Symbol.
Can I learn Revit in four days?
A focused four-day introduction can cover essential navigation and basic tools, but Autodesk’s own 90-minute course shows that even a short overview still requires additional practice time beyond the video runtime. Reliable, project-ready skill takes longer than four days for most learners.
Can I copy a legend from one Revit file to another?
Yes, through Transfer Project Standards, direct copy and paste between two open projects, or by building the legend into a shared office template. Always verify that families, types, and text styles carried over correctly, since missing families are a common cause of broken legend components after a transfer.
What is the best way to learn Revit?
A progressive path works best: start with navigation and basic element behavior, then move into modeling, annotation, schedules, and sheets, as outlined in Autodesk’s Foundations of Revit material. Pairing that sequence with project-based practice, like the structure in our Getting Started with Revit guide, builds skills that transfer directly to real documentation work including legends.
Why don’t legend components show up in drafting views?
Legend components are tied to live model families and simply are not supported inside drafting views, which are meant for generic, non-model annotation. Use a callout or a model-based view instead when you need model-linked geometry, a workaround confirmed in Autodesk Community discussion on the topic.
Sources
Recommended
Comments