Historical Context & Motivation
Architectural documentation has always demanded a dialogue between drawing and written language. Before the advent of digital tools, architects painstakingly lettered every note, dimension, and specification by hand using Leroy lettering sets or Rapidograph pens, a process that consumed a remarkable portion of a draftsperson's time. The emergence of Computer-Aided Design (CAD) in the 1980s introduced typed text and leaders, but annotations remained largely disconnected from the geometry they described. When Autodesk launched Revit in 2000, the paradigm shifted dramatically: text, keynotes, and detail components became view-specific annotation objects that live inside the Building Information Model, scaling automatically to the view and updating whenever the model changes.
The central question this lesson addresses is deceptively simple: how do you communicate design intent—materials, assemblies, conditions—to contractors and fabricators who will never interact with your 3D model? The answer lies in Revit's triad of annotation tools: text notes, keynotes, and detail components. Understanding when and how to deploy each one is essential for producing documents that are both legible and contractually precise.
Core Principles & Definitions
Before placing a single note, it is important to understand the conceptual framework that governs Revit annotations. All annotations in Revit are view-specific elements—they exist only in the view where they are placed and do not appear in the 3D model. This distinction separates them from model elements like walls and floors. Annotations automatically adopt the scale of their host view, so a text note set to 3/32" will print at that size regardless of whether the view is 1:50 or 1:200. Revit groups its annotation tools into three primary categories, each serving a distinct documentation purpose and carrying different levels of intelligence.
Text Notes
Keynotes
Detail Components
Annotation Scale Independence
Visual Explanation — The Annotation Ecosystem
The diagram above captures the essential spatial and conceptual relationship among the three tools. Notice that the detail component is drawn directly within the section view, living alongside the model geometry it supplements—in this case, the wavy hatch representing batt insulation within a wall cavity. The keynote floats outside the wall but connects via a leader line; its content is not typed by the user but resolved from the keynote table, ensuring that every instance of '07 21 13' on every sheet in the project maps to the exact same description. The text note near the foundation is a unique instruction that no keynote code covers—a reminder to the contractor to cross-reference a geotechnical report. As a visual arts student, you can think of these layers as analogous to the distinction in printmaking between the plate (the model), the ink (detail components), and the marginal annotations (text and keynotes) that guide the viewer.
How It Works — Placement & Data Flow
Text Note Placement
To place a text note, navigate to the Annotate tab on the ribbon and click Text. The options bar presents two fundamental choices: leader (one-segment, two-segment, or curved) and no leader. When you choose a leader, you first click the point on the element you want to annotate, then click to place the elbow, and finally click to set the text box location. Text notes support basic formatting—bold, italic, underline—and can be rotated. The text note type controls font, size, background color, and leader arrowhead style. In practice, a firm's template will pre-define two or three text types (e.g., '3/32" Arial' for general notes, '1/8" Arial Bold' for titles) so that all users produce uniform documents.
Keynote Placement & the Keynote Table
Keynotes operate through a lookup mechanism. Each element or material in the model can have a Keynote parameter—a text string such as '07 21 13'—which corresponds to a row in the project's keynote file (a tab-delimited .txt file). When you click Annotate → Keynote, Revit offers three modes: Element Keynote (reads the keynote assigned to the element's type), Material Keynote (reads the keynote assigned to the specific material face you click), and User Keynote (lets you pick any value from the table without attaching to an element). The keynote tag then displays the code, and a Keynote Legend schedule placed on the sheet automatically lists only the keynotes visible in that view, providing the decoder ring for the reader.
Detail Component Placement
Detail components are loaded from the Revit family library (or custom .rfa files) via Annotate → Detail Component. Because they are 2D families, they appear only in the view in which they are placed—plan, section, or detail. A detail component can include line work, filled regions, and masking regions, making it ideal for representing items like rigid insulation, steel angles, or sealant joints that are too fine-grained to warrant full 3D modeling. Detail components carry subcategory, keynote, and visibility parameters, meaning they can be tagged with keynotes and filtered in schedules just like model elements. Their draw order is controlled through the Arrange tools (Bring to Front, Send to Back), which function much like layer ordering in Adobe Illustrator.
Annotate → Keynoting Settings. In a collaborative project, this file should live on a shared server or BIM 360 so that all team members reference the same descriptions. If the path breaks, Revit will display empty keynote tags until the file is relinked.Detailed Breakdown — When to Use Each Tool
Choosing between text notes, keynotes, and detail components is not arbitrary—it depends on the nature of the information, the need for consistency, and the graphic requirements of the document set. A good rule of thumb is that if a note will appear in more than one location across the project, it belongs in the keynote system rather than as freeform text. If the information is inherently graphic—representing a physical assembly like flashing or blocking—it belongs as a detail component. The table below maps common documentation scenarios to the recommended tool.
| Documentation Scenario | Recommended Tool | Rationale |
|---|---|---|
| Identifying a material in a section (e.g., concrete, gypsum board) | Material Keynote | Draws data from the material's keynote parameter; consistent across all views and sheets automatically. |
| Labeling a wall type in a plan view | Element Keynote | Reads the type's keynote; ensures every instance of that wall type across the project displays the same code. |
| Adding a unique field instruction ('VERIFY DIMENSION IN FIELD') | Text Note | Unique, situational notes that have no place in a specification database are best as free-form text. |
| Annotating a condition not tied to a specific element (e.g., 'SLOPE 1/4" PER FOOT') | Text Note (or User Keynote) | If the note recurs frequently, a User Keynote promotes consistency; if it appears once, a text note suffices. |
| Representing batt insulation, rigid insulation, or blocking in a wall section | Detail Component | These items need graphic representation that hatch patterns alone cannot achieve. 2D families give precise line work and can be keynoted. |
| Sheet-level general notes (e.g., list of construction standards) | Text Note (or Drafting View) | Long-form general notes are typically placed in a drafting view and then dropped onto the sheet as a viewport, preserving scale independence. |
Worked Example — Annotating a Wall Section Detail
Let us walk through the complete process of annotating a typical exterior wall section in Revit. The goal is to label the insulation, sheathing, and cladding with keynotes, add a detail component for a sealant joint at a window head, and place a text note for a unique field instruction.
Fine so that material hatches and thin layers are visible. This scale will govern how large your annotations appear on the printed sheet.Annotate → Detail Component. If the sealant joint family is not loaded, click Load Family and browse to Detail Items → Div 07-Thermal and Moisture → Sealant in the default Revit library. Select the appropriate sealant family, then click on the intersection of the window frame and the exterior sheathing. Use Arrange → Bring to Front if the component is obscured by wall hatch patterns.Annotate → Keynote → Material Keynote. Click the face of the batt insulation within the wall cavity. Revit reads the material's Keynote parameter (e.g., '07 21 13') and places a tag with that code. Repeat for the exterior gypsum sheathing ('09 29 00') and the metal panel cladding ('07 42 13'). If a material's Keynote field is blank, Revit will prompt you to select a code from the keynote table—select the correct CSI division and assign it.Annotate → Text, select the 'Two Segment' leader style, and click the head flashing at the window. Drag the leader elbow to a clear area, then click to place the text box. Type: 'INSTALL SILL PAN FLASHING PER MANUFACTURER'S INSTRUCTIONS. SEE SPEC SECTION 07 62 00.' Format the text to match the project standard (typically 3/32" Arial).View → Legends → Keynote Legend (or create one via View → Schedules → Keynote Legend). Configure the legend to filter by sheet, so it displays only the keynotes visible on that sheet. Drag the legend from the Project Browser onto the sheet, positioning it in the lower-right corner per your title block convention. The legend will automatically list codes 07 21 13, 07 42 13, and 09 29 00 with their full descriptions.Strengths & Limitations of Each Tool
| Criterion | Text Notes | Keynotes | Detail Components |
|---|---|---|---|
| Consistency | Low — each instance is independently typed; prone to spelling and wording variations. | High — all instances pull from the same keynote file; edit once, update everywhere. | High — family-based; changes to the family propagate to all placed instances. |
| Flexibility | Very high — any text can be entered, formatted, and positioned freely. | Moderate — limited to codes in the keynote table; custom entries require editing the .txt file. | Moderate — limited to loaded families; custom assemblies require creating new .rfa files. |
| Model Intelligence | None — text notes are not linked to any element or parameter. | Strong — Element and Material keynotes are parametrically linked to model data. | Partial — detail components can carry parameters and be scheduled, but they are 2D only. |
| Graphic Output | Text only, with optional leader lines. | Code number with leader; descriptions appear only in the legend. | Rich graphic representation — line work, hatches, and masking regions. |
| Best For | One-off instructions, general notes, drawing titles. | Standardized material and product identification per CSI MasterFormat. | Representing building assemblies at fine detail levels in sections and details. |
Connection to Advanced Documentation Workflows
The introductory annotation tools covered in this lesson serve as the foundation for more sophisticated documentation strategies used in professional practice. As projects grow in complexity, firms adopt workflows that extend these basic concepts into automated, data-driven systems. Understanding the trajectory from simple text placement to intelligent annotation helps you appreciate why mastering the fundamentals matters.
| Introductory Concept | Advanced Extension |
|---|---|
| Manually placing text notes for field instructions | Creating shared parameter-driven annotation families that auto-populate from model data (e.g., a wall tag that displays type, fire rating, and STC value). |
| Using the default Revit keynote table | Developing a firm-specific keynote file mapped to the project's specification sections, managed through a BIM Execution Plan and version-controlled on a shared server. |
| Loading detail components from the default library | Building custom detail component families with parametric dimensions, visibility controls, and nested keynotes—enabling a single family to represent multiple sizes of a product. |
| Placing keynote legends manually on each sheet | Using Dynamo scripts or the Revit API to auto-generate keynote legends filtered by sheet, ensuring no legend is ever missing or out of date. |
| Annotating individual detail views | Implementing detail libraries—entire pre-annotated drafting views stored in a template and inserted into projects as needed, dramatically reducing documentation time. |
As you advance in your study of Revit, pay particular attention to shared parameters and tag families, which extend the keynote concept into a fully parametric annotation system. In many firms, the documentation phase accounts for 40–60% of total project hours, so even incremental efficiencies in annotation—such as switching from text notes to keynotes for recurring material labels—can yield significant time savings across a project's lifecycle.
Practice Problems
Lesson Summary
This lesson introduced the three primary annotation tools in Autodesk Revit's documentation workflow. Text notes provide free-form, user-typed annotations with optional leaders—ideal for unique field instructions and general notes that do not recur across sheets. Keynotes offer a database-driven approach: each element or material carries a code that resolves against a centrally managed keynote file, ensuring consistency across all views and sheets. Three keynote modes— Element, Material, and User—serve different tagging scenarios, and a Keynote Legend on the sheet decodes all codes for the reader.
Detail components are 2D annotation families that represent building assemblies—insulation, sealant joints, steel clips—with rich graphic fidelity, visible only in the view where they are placed. All three tools are view-specific and scale-independent, meaning they print at their specified size regardless of view scale. Choosing the right tool depends on whether the information is unique or recurring, whether it needs model intelligence, and whether it requires graphic representation. Mastering this triad is essential for producing construction documents that are clear, consistent, and contractually defensible.