Using Reference Details with AVAIL
Reference Details in AVAIL allow teams to capture and reuse detail information from existing Revit projects without treating every detail as a static, standardized library asset.
Overview
With AVAIL, Publishers can harvest the reusable 2D information from Detail Views so users can discover, reference, and transfer it into another Revit project.
This creates an opportunity to build a broader reference library from successful project work. Instead of recreating a detail from scratch or manually searching through previous projects, users can find relevant examples in AVAIL and use them as a starting point for a new project.
Reference Details are intended to be references, not necessarily project-ready standards. A detail created for one project may need to be reviewed and modified before it is appropriate for another.
How Reference Details Work in AVAIL
AVAIL has traditionally supported harvesting and reusing Drafting Views from Revit. Reference Details extend this workflow to Detail Views, including live section cuts containing 2D drafting information.
When a Detail View is harvested, AVAIL captures the transferable 2D elements associated with the detail. The Reference Detail can then be indexed in AVAIL alongside other content and made available for reuse.
AVAIL also identifies the 2D components used to create the detail and displays them as Related Content. This provides additional context about the resources associated with the original detail.
When bringing a Reference Detail into Revit, users can choose how they want to use the information:
Option 1: Create a Drafting View
Use the Reference Detail to create a new Drafting View in the destination project.
This is useful when the information does not need to remain associated with live model geometry and the goal is to reuse the 2D detail as a starting point.
Option 2: Load into an Existing Detail View
If you have created a new Detail View or section in the destination project, the 2D information from the Reference Detail can be transferred into that view.
AVAIL transfers the 2D information it can from the original detail. If the source and destination views use different scales, AVAIL may display a warning so the destination view can be adjusted appropriately.
Use Related Content for Additional Context
Review the Related Content associated with a Reference Detail before using it.
Related Content can help identify the 2D components associated with the original detail and provide additional context for how it was constructed.
Where your organization maintains approved versions of those components in AVAIL, consider whether the current approved content should replace older project-specific resources.
Preserve the Reason Behind the Detail
A detail is more useful when users understand why it was created—not just what it looks like.
When possible, supplement Reference Details with contextual information explaining important considerations, limitations, or decisions associated with the detail. This may include AVAIL Notes, Related Content, supporting documentation, or links to other resources.
For example, context might explain:
- Why a particular assembly was selected
- Conditions where the detail should or should not be used
- Required project-specific modifications
- Lessons learned from the original project
- Relevant firm standards or documentation
Preserving this context helps turn a Reference Detail from a graphical example into reusable institutional knowledge.