Autodesk Revit Quiz: Element Schedules
10 questions · exam conditions
0:00
Element SchedulesQuestion 1 of 10

A window schedule must show Type Mark, Width, Height, and Count. It must include only windows whose Comments value is REPLACE, but the Comments column must not appear in the final schedule.

What is the most appropriate workflow?

Add Comments, filter it for REPLACE, and remove Comments from the schedule after applying the filter.
Add Comments, filter it for REPLACE, and mark the Comments field as hidden on the Formatting tab.
Omit Comments, create a text calculated value containing REPLACE, and filter by the calculated value.
Add Comments, sort by it, and reduce the Comments column width until its text is no longer visible.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Element Schedules

Practice Element Schedules in Autodesk Revit with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Element Schedules, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Revit.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A window schedule must show Type Mark, Width, Height, and Count. It must include only windows whose Comments value is REPLACE, but the Comments column must not appear in the final schedule.

What is the most appropriate workflow?

  1. Add Comments, filter it for REPLACE, and remove Comments from the schedule after applying the filter.
  2. Add Comments, filter it for REPLACE, and mark the Comments field as hidden on the Formatting tab. (correct answer)
  3. Omit Comments, create a text calculated value containing REPLACE, and filter by the calculated value.
  4. Add Comments, sort by it, and reduce the Comments column width until its text is no longer visible.
Explanation: When building a Revit schedule that filters by a field without displaying it, you need to understand how the Fields, Filter, and Formatting tabs work together in the Schedule Properties dialog. The key insight is that a field must be added to the schedule (Fields tab) before it can be used as a filter criterion — but adding it doesn't mean it has to be visible to the end user. This is exactly what option B accomplishes. You add Comments on the Fields tab so Revit can reference it, apply a filter on the Filter tab to show only elements where Comments equals REPLACE, and then navigate to the Formatting tab where you can check Hidden Field for the Comments column. The field still drives the filter behind the scenes, but it never appears in the printed or exported schedule. Option A describes removing the Comments field entirely after filtering — but if you delete the field, Revit also removes the filter that depended on it, so all windows would reappear in the schedule. Option C introduces an unnecessary workaround: calculated values are useful for deriving new data, not for hiding a standard built-in parameter like Comments. Option D — shrinking the column width until text disappears — is a cosmetic hack, not a legitimate workflow. The column still exists and would be visible in certain views or exports, making it unreliable and unprofessional. A helpful rule of thumb for the exam: filtering and visibility are independent controls in Revit schedules. Any time a question asks you to filter by a field but hide it, your answer should involve the Hidden Field checkbox on the Formatting tab — that's the purpose it was designed for.

Question 2

A door schedule contains these records: Level 1–Mark 02, Level 2–Mark 01, Level 1–Mark 10, and Level 2–Mark 03. The schedule sorts first by Level in ascending order and then by Mark in descending order.

In what order will the records appear?

  1. Level 1–Mark 02, Level 1–Mark 10, Level 2–Mark 01, Level 2–Mark 03
  2. Level 2–Mark 03, Level 2–Mark 01, Level 1–Mark 10, Level 1–Mark 02
  3. Level 1–Mark 10, Level 1–Mark 02, Level 2–Mark 03, Level 2–Mark 01 (correct answer)
  4. Level 1–Mark 10, Level 2–Mark 03, Level 1–Mark 02, Level 2–Mark 01
Explanation: When working with Revit schedules, multi-level sorting works like a hierarchy: the primary sort field groups records first, and the secondary sort field orders records within each primary group. Keeping that hierarchy clear is the key to answering questions like this one. Here, the primary sort is Level ascending (Level 1 before Level 2), and the secondary sort is Mark descending (higher values first within each level group). Start by separating the records into Level 1 entries — Mark 02 and Mark 10 — and Level 2 entries — Mark 01 and Mark 03. Within Level 1, descending order puts Mark 10 before Mark 02. Within Level 2, descending order puts Mark 03 before Mark 01. That gives you: Level 1–Mark 10, Level 1–Mark 02, Level 2–Mark 03, Level 2–Mark 01 — which is answer C. Answer A applies ascending order to both fields, ignoring the descending instruction for Mark entirely. Answer B reverses everything, treating both fields as descending — it flips the Level sort as well as the Mark sort. Answer D is a common trap: it appears to alternate between levels rather than grouping them, which would only happen if Level were not the primary sort key — it incorrectly interleaves records across levels. As a study tip, always resolve multi-sort questions in strict order: finish grouping by the primary field completely before applying the secondary sort inside each group. Revit schedules work exactly this way, and exam questions will test whether you accidentally apply the secondary sort globally instead of locally.

Question 3

A room schedule includes placed and enclosed rooms, unplaced rooms, and rooms whose boundaries are not enclosed. The schedule should show only rooms that currently have a valid positive area.

Which filter is the most direct way to produce the requested schedule?

  1. Filter Perimeter so it equals zero, retaining rooms whose boundaries have not yet been fully resolved.
  2. Filter Area so it is greater than zero, excluding rooms that do not currently calculate a positive area. (correct answer)
  3. Filter Level so it is not blank, because every room assigned to a level must have a valid area.
  4. Filter Number so it is greater than zero, because numbered rooms are necessarily placed and enclosed.
Explanation: When working with Revit schedules, filters let you control which elements appear based on their parameter values. The key concept here is understanding what parameter actually reflects whether a room is valid — meaning it's placed, enclosed, and actively calculating. A room in Revit falls into one of three states: placed and enclosed (it has a measurable area), unplaced (it exists in the project browser but has no location), or placed but not enclosed (its boundaries aren't fully closed). Only placed and enclosed rooms generate a positive area value. This makes Area the most direct and reliable parameter to filter on. By setting the filter to "Area is greater than 0," you automatically exclude both unplaced rooms (which show no area) and rooms with open boundaries (which also return no calculable area). Answer B targets exactly the property that defines validity. Answer A is backwards — filtering for Perimeter equal to zero would retain problematic rooms, not exclude them, and perimeter alone doesn't fully distinguish valid from invalid rooms anyway. Answer C is flawed because a room can be assigned to a level without being enclosed; Level assignment is a separate action from boundary resolution, so a blank Level does not reliably signal an invalid area. Answer D misunderstands how room numbering works — you can assign a number to any room, including unplaced ones, so a non-blank Number field does not guarantee the room is placed or enclosed. As a study tip: when a Revit question asks you to filter for "valid" or "active" elements, look for the parameter that is directly calculated from the condition you care about — in room questions, that's almost always Area.

Question 4

A project manager needs a schedule containing one record for each wall instance, including wall type, base constraint, length, and total wall area. The manager does not want separate records for paint, finish layers, or other constituent materials.

Which schedule type should be created?

  1. Create a Rooms schedule and add wall-related calculated fields for length and surface area.
  2. Create a Wall Material Takeoff and group all material records by the host wall type.
  3. Create a Multi-Category schedule and filter the Category field for all wall materials.
  4. Create a Walls element schedule and add the required wall instance and type fields. (correct answer)
Explanation: When a question asks about tracking individual building elements with their instance properties, you need to match the schedule type to the granularity of data required. The key distinction in Revit is between schedules that report elements versus schedules that report materials within elements. A Walls element schedule (option D) does exactly what this scenario demands: it generates one row per wall instance and exposes instance parameters like Base Constraint and Length, plus type parameters like the wall type name. You can also add the built-in Area parameter to capture total wall surface area. This is the standard, purpose-built tool for this task. Option A falls apart immediately because a Rooms schedule reports room geometry and occupancy data — not wall instances. You cannot reliably derive individual wall lengths or areas from room-level fields, and there's no direct wall instance row to work with. Option B is the classic trap here. A Wall Material Takeoff does include wall-related data, but it breaks each wall into separate rows for every material layer (paint, substrate, insulation, etc.). This is precisely the "separate records for constituent materials" the manager wants to avoid. Grouping by host wall type reduces clutter but doesn't collapse the records into one row per wall instance. Option C is a distractor that conflates category filtering with schedule type selection. A Multi-Category schedule can include walls, but filtering by "wall materials" still pulls material-level data, not clean per-instance wall records. Study tip: On Revit exam questions, if the requirement is one row per element, reach for the matching element schedule (Walls, Floors, Doors, etc.) — Material Takeoffs are for layer-level quantity extraction.

Question 5

A plumbing fixture schedule must retain one row per fixture. Fixtures should be grouped by Level, with each level name displayed once above its group and a blank separator between consecutive level groups.

Which Sorting/Grouping setup best meets these requirements?

  1. Sort by Level, select Blank line only, and keep Itemize every instance selected.
  2. Sort by Level, select Footer and Grand totals, and clear Itemize every instance.
  3. Sort by Family and Type, select Header, hide Level, and clear Itemize every instance.
  4. Sort by Level, select Header and Blank line, and keep Itemize every instance selected. (correct answer)
Explanation: When configuring a schedule's Sorting/Grouping settings in Revit, you need to think about three independent controls working together: the sort field (what organizes the rows), header/footer/blank line options (how groups are visually separated), and Itemize every instance (whether individual rows appear at all). The requirements here are clear: one row per fixture (so instances must be itemized), grouped by Level with the level name shown once above each group (that's a Header), and a blank line between consecutive groups (that's a Blank line). Answer D delivers exactly this — sorting by Level with both Header and Blank line selected, while keeping Itemize every instance active so each fixture retains its individual row. Looking at the distractors: A gets the sort field and Itemize setting right, but selecting only Blank line means no level name appears above each group — you'd see separating gaps without any label identifying which level you're reading. B introduces Footer and Grand totals, which are count/summary tools, and critically clears Itemize every instance, collapsing the schedule so individual fixture rows disappear entirely — the opposite of what the requirement demands. C sorts by Family and Type instead of Level, which reorganizes the data around fixture categories rather than building levels, and clearing Itemize every instance again removes individual rows; hiding the Level column doesn't substitute for proper level grouping. A useful rule of thumb: Header = label above a group, Blank line = visual gap between groups, Itemize every instance = individual rows visible. Whenever a question mentions "retain one row per fixture," that's your signal that Itemize every instance must stay checked.

Question 6

A window schedule contains six instances. Type A has two windows in the East Wing and one in the West Wing. Type B has one window in the East Wing and two in the West Wing. The schedule is filtered for Wing equal to East, sorted by Type, displays Count, and has Itemize every instance cleared.

What rows will the schedule display after the filter and grouping are applied?

  1. One Type A row with a count of three and one Type B row with a count of three
  2. Two Type A rows and one Type B row, with each row showing a count of one
  3. One Type A row with a count of two and one Type B row with a count of one (correct answer)
  4. One East Wing row with a count of three and one West Wing row with a count of three
Explanation: When working with Revit schedules, you need to track three independent settings: filters (which rows appear), itemization (how rows are grouped), and Count (what number is displayed). Apply each layer in sequence. Start with the filter: "Wing equals East" removes all West Wing instances. That leaves two Type A windows and one Type B window — three total instances, but split by type. Now apply itemization. Because Itemize every instance is cleared, Revit collapses matching types into a single row per type rather than showing one row per window. So you get exactly two rows: one for Type A and one for Type B. The Count field then reflects how many instances were grouped into each row — two for Type A (both East Wing instances) and one for Type B (the single East Wing instance). That's option C, the correct answer. A is wrong because it reports counts of three for both types, which would only be accurate if no filter were applied — three is the total across both wings for each type, not just East Wing. B is wrong because it describes the behavior when Itemize every instance is enabled. Each instance would appear as its own row with a count of one, producing two Type A rows and one Type B row — but the question states itemization is cleared. D is wrong because schedules filtered by Wing don't produce Wing-based summary rows. The sort and grouping key here is Type, not Wing. Study tip: In Revit schedule questions, always separate the filter (what survives), itemization (how many rows), and Count (what the number reflects) — they're easy to conflate under pressure.

Question 7

An equipment schedule must list every equipment instance and show a subtotal of Cost at the end of each Level group. A project-wide grand total is not required.

Which combination of settings will produce the required level subtotals while preserving instance rows?

  1. Sort by Level, enable a footer with totals for that group, format Cost to calculate totals, and keep itemization enabled. (correct answer)
  2. Sort by Cost, enable grand totals, hide the Level field, and clear itemization for the schedule.
  3. Filter by Level, enable a header for each group, format Cost as currency, and keep itemization enabled.
  4. Sort by Level, enable blank lines between groups, format Cost to calculate totals, and clear itemization.
Explanation: Whenever you see a Revit schedule question involving grouped subtotals, think through four independent settings: sorting/grouping, footer configuration, field formatting, and itemization. Each plays a distinct role, and the question will often mix correct and incorrect components across the distractors. To produce subtotals at the end of each Level group while still showing individual rows, you need all four pieces working together. First, sorting by Level creates the groups. Second, enabling a footer with totals on that sort field tells Revit to insert a summary row after each group ends. Third, formatting the Cost field to calculate totals tells Revit what to sum in that footer. Fourth, keeping itemization enabled ensures individual equipment rows remain visible — without it, you'd see only the summary rows, losing the instance-level detail the schedule requires. That's option A, and it satisfies every condition in the scenario. Option B fails on multiple fronts: sorting by Cost doesn't create Level groups, clearing itemization hides individual rows, and grand totals aren't even required by the scenario. Option C confuses filtering with grouping — filtering by Level would limit which records appear rather than organizing them into subtotaled groups, and a header doesn't produce a subtotal; a footer does. Option D is tempting because it correctly sorts by Level and formats Cost for totals, but clearing itemization collapses each group down to just its summary row, removing the individual equipment instances the schedule must preserve. A useful rule of thumb: footers produce subtotals; headers do not. Memorize that distinction, and always confirm that itemization matches whether individual rows are required.

Question 8

A door schedule should include only doors that are at least 900 mm900\text{ mm} wide and have a fire rating of at least 60 minutes60\text{ minutes}. Doors meeting only one condition must be excluded.

Which filter setup satisfies the requirement?

  1. Create a Width filter for at least 900 mm900\text{ mm} and a Fire Rating filter for at least 60 minutes60\text{ minutes}. (correct answer)
  2. Create only a Width filter for at least 900 mm900\text{ mm}, then sort the schedule by Fire Rating.
  3. Create a Width filter for at least 900 mm900\text{ mm} and a Fire Rating filter for less than 60 minutes60\text{ minutes}.
  4. Create one text filter that searches a combined Width and Fire Rating field for both required values.
Explanation: When working with Revit schedules, filters let you control exactly which elements appear based on their properties. The key concept here is AND logic: when you apply multiple filters in Revit, a door must satisfy every filter simultaneously to appear in the schedule. This is precisely what the passage requires — both conditions must be met. Answer A is correct because it creates two independent filters: one requiring Width ≥900 mm\geq 900\text{ mm} and another requiring Fire Rating ≥60 minutes\geq 60\text{ minutes}. Revit applies these together, so only doors passing both tests are included. Doors meeting just one condition are automatically excluded — exactly what the passage demands. Answer B fails because sorting by Fire Rating doesn't filter anything — it only reorders rows. All doors wider than 900 mm900\text{ mm} still appear regardless of their fire rating, so doors with insufficient ratings remain visible in the schedule. Answer C is a logical trap. A Fire Rating filter set to less than 60 minutes60\text{ minutes} would actually include under-rated doors and exclude the compliant ones — the exact opposite of the requirement. This reversal is a classic filter-direction mistake. Answer D is incorrect because Revit doesn't offer a combined multi-property text field for Width and Fire Rating. These are separate, typed parameters. You cannot write a single text query that simultaneously evaluates a numeric width and a numeric fire rating across two distinct fields. As a study tip, whenever a Revit question mentions "must meet all conditions," think multiple filters with AND logic — not sorting, not a single filter, and never inverted conditions.

Question 9

A door schedule currently displays one row for every door instance. The project manager wants one row for each door type, with a quantity showing how many instances of that type occur in the project. Individual door marks are not required.

Which schedule configuration will produce the requested result?

  1. Add Family and Type and Count, sort by Family and Type, and clear Itemize every instance. (correct answer)
  2. Add Family and Type and Mark, sort by Mark, and keep Itemize every instance selected.
  3. Add Type Mark and Count, filter Count greater than one, and keep Itemize every instance selected.
  4. Add Family and Type and Count, sort by Count, and select Itemize every instance.
Explanation: When working with Revit schedules, you'll often need to toggle between seeing every individual instance of an element versus a summarized view by type. This question tests exactly that concept — understanding how the "Itemize every instance" checkbox and the Count field work together. To consolidate a schedule so that each row represents a door type rather than a door instance, you need two things: a field that identifies the type (Family and Type), and the Count field to tally how many instances belong to each type. Most critically, you must uncheck "Itemize every instance" — this is the switch that tells Revit to collapse duplicate rows into a single summarized row. Sorting by Family and Type keeps the list organized alphabetically by type name. That's exactly what A does, making it the correct answer. B is wrong because it keeps "Itemize every instance" selected, meaning every door still gets its own row — no consolidation occurs. Adding Mark just identifies individual doors, which the project manager explicitly doesn't need. C is wrong for the same core reason: keeping "Itemize every instance" selected prevents row consolidation. The Count filter is also redundant and doesn't address the underlying problem. D is wrong because it selects "Itemize every instance," which is the opposite of what you want. Even though it includes Count and Family and Type, checking that box will expand each type back into individual rows, defeating the purpose entirely. A good rule of thumb: whenever a question asks for a type-based summary with quantities, your first instinct should be to find the answer that unchecks "Itemize every instance."

Question 10

A multi-category schedule must list mechanical equipment and electrical equipment together and include a custom Asset ID field. Each family currently contains an ordinary family parameter named Asset ID, but that field is unavailable when the multi-category schedule is created.

What change will most reliably make Asset ID schedulable across both categories?

  1. Create a shared Asset ID parameter, apply or bind it to both categories, and add that shared parameter as a schedule field. (correct answer)
  2. Rename each ordinary family parameter identically, reload the families, and add the built-in Type Comments field.
  3. Create separate single-category schedules, rename both schedule columns Asset ID, and combine them by sorting on Category.
  4. Create a calculated text field named Asset ID in the multi-category schedule and enter each equipment identifier manually.
Explanation: Whenever you see a question about scheduling across multiple categories in Revit, the core concept being tested is parameter visibility and shareability. Revit's multi-category schedule can only display parameters that are recognized universally across family categories — and ordinary family parameters simply don't qualify. Ordinary family parameters live inside individual families and are invisible to schedules that span multiple categories. The solution is a shared parameter: a parameter defined in an external shared parameter file (.txt), which gives it a unique GUID that Revit recognizes consistently across any family or category. When you create a shared parameter, load it into both your mechanical and electrical families (or bind it as a project parameter to both categories), Revit can surface it as a single, unified column in a multi-category schedule. That's exactly what option A describes, making it the correct answer. Option B fails because simply giving two ordinary parameters the same name doesn't make them the same parameter to Revit — they still lack the shared GUID, so the multi-category schedule still won't see them. Renaming to "Type Comments" just piggybacks on an unrelated built-in field rather than solving the real problem. Option C sidesteps the scheduling system entirely; separate single-category schedules can't be merged into one true multi-category schedule, and column renaming doesn't create shared data. Option D is impractical and error-prone — a calculated value field can't pull actual family parameter data, meaning you'd be entering every Asset ID manually with no live link to the model. Study tip: On any Revit exam question involving cross-category scheduling, think "shared parameter first." If a field needs to appear in a multi-category schedule, a shared parameter is almost always the answer.