Managing Project Files — Open, save, and manage project files (RVT) and templates (RTE)

Historical Context & Motivation

Before Building Information Modeling (BIM) reshaped the architecture and design professions, practitioners relied on collections of separate two-dimensional drawings — plans, sections, elevations, and detail sheets — stored as individual CAD files with no inherent relationship to one another. A change in a floor plan required manual updates across dozens of corresponding sheets, an error-prone workflow that consumed hours of production time. Autodesk recognized that unifying every drawing, schedule, and three-dimensional view inside a single, intelligent database would eliminate redundancy and dramatically reduce coordination errors. That insight became the conceptual seed for Revit, a parametric building modeler whose file management conventions — the RVT project file and the RTE template file — remain central to every professional workflow today.

The transition from a folder full of disconnected DWG files to a single parametric project database was not merely a technical upgrade; it was a philosophical shift in how designers think about representation and documentation. For Visual Arts students accustomed to layered Photoshop or Illustrator files, the Revit model is analogous to a single living canvas in which every layer automatically redraws itself whenever the underlying geometry changes. The fundamental question this lesson addresses is: how do you create, open, save, back up, and template that living canvas so that your design intent is always protected and your studio workflow remains fluid?

Core Principles & Definitions

Understanding Revit's file ecosystem begins with a handful of foundational concepts that govern every interaction you will have with the software. Unlike raster-based applications where a file is essentially a pixel grid, a Revit file is a relational database containing three-dimensional geometry, metadata, view definitions, annotations, and rendering settings — all tightly interlinked. The five principles below form the conceptual scaffolding upon which every practical operation in this lesson rests.

Visual Explanation — The Revit File Ecosystem

The visual above illustrates the core relationships you will navigate daily. Notice that the RTE template is a one-time input: once a project has been created from it, the template and the project file are independent entities. Changes to the template after project creation do not retroactively alter the project, much as a printed photograph does not change when you adjust the Lightroom preset that was used to develop it. The backup folder, on the other hand, grows automatically with every save — a safety net you configure rather than manually create. Finally, linked files allow disciplinary isolation: the structural engineer's model remains a separate RVT, reducing file size and preventing cross-discipline interference while still appearing in coordinated views.

How It Works — File Operations in Depth

Creating a New Project

Every Revit session begins with either opening an existing RVT file or creating a new project. To start fresh, navigate to File → New → Project. A dialog box presents two critical choices. First, you select a template file (.rte) — the pre-loaded starting condition — or you can choose "None" for a truly blank slate, though this is rarely advisable because you would lose all pre-configured view templates, title blocks, and loaded families. Second, you decide whether the new file is a Project or a Project Template. Choosing "Project" produces an .rvt file; choosing "Project Template" produces an .rte file. This distinction is pivotal because it determines the file extension and the way Revit treats the file in future workflows.

Opening Existing Files

The File → Open → Project command opens the standard file browser filtered to .rvt and .rte extensions. However, Revit also exposes several important options at the bottom of the Open dialog. The Audit checkbox instructs Revit to scan the file for database corruption and attempt repairs — a practice recommended after unexpected crashes. The Detach from Central option is essential when opening a workshared file that you do not want to synchronize back; it creates an independent copy, which is invaluable when you need to experiment without affecting the live collaborative model. The Create New Local option generates a local working copy linked to the central file, the standard procedure for joining a collaborative project.

Saving Strategies

Revit offers three distinct save operations. Save (Ctrl + S) writes the current state to the existing file path and simultaneously creates an incremental backup copy in the project's backup folder. Save As allows you to specify a new file name or location, effectively forking the project — useful for milestone snapshots like "SchematicDesign_v3.rvt." Within the Save As dialog, the Options button reveals settings for the maximum number of backups (default is 20) and a checkbox to make the saved file the new central model if worksharing is enabled. The third operation, Synchronize with Central (SWC), is exclusive to workshared projects: it pushes your local edits to the central file and pulls others' changes into your local copy, resolving ownership conflicts in the process.

Detailed Breakdown — Revit File Types & Extensions

While the RVT and RTE formats are the primary focus of everyday project management, Revit's ecosystem includes several additional file types that interact with and support the core project file. Understanding the full cast of extensions prevents confusion when navigating project folders and helps you recognize which files are safe to move, rename, or delete.

A critical nuance for Visual Arts students coming from Adobe workflows: Revit does not use a separate "assets" folder the way After Effects references footage or InDesign references linked images. Everything — textures, materials, family geometry, even rendered appearances — lives inside the RVT file. This is why Revit files can balloon to several hundred megabytes or even gigabytes on large projects. The upside is portability: you can hand someone a single RVT file and they have the complete model. The downside is that file management discipline — regular purging of unused families, diligent template maintenance, and strategic use of linked files — becomes essential to keep performance acceptable.

Worked Example — Setting Up a New Studio Project from Template

Imagine you are beginning a semester-long studio project for a small gallery pavilion. Your instructor has provided a custom RTE template containing the school's title block, a curated set of wall and floor families, and view templates tuned for presentation-quality drawings. Walk through the following steps to establish, save, and protect your working file.

Strengths, Limitations & Comparisons

No file management system is without trade-offs. Revit's single-file database architecture offers compelling advantages but also introduces constraints that become especially apparent when compared to the workflows Visual Arts students already know from Adobe Creative Cloud or Rhino/Grasshopper ecosystems. The table below maps these strengths and limitations so you can anticipate pain points and develop mitigation strategies early.

Connection to Advanced Workflows

The fundamentals of opening, saving, and templating Revit files are the gateway to more sophisticated project management strategies used in professional practice. As studios scale from individual student projects to multi-discipline, multi-firm collaborations, the same file management principles extend into cloud-based environments, automated model-checking pipelines, and interoperability frameworks. The table below maps the concepts you have learned in this lesson to their advanced counterparts.

As you progress through your Visual Arts curriculum and begin collaborating with engineering or construction management students, you will find that the file management habits you build now — consistent naming conventions, disciplined backup routines, and mindful template configuration — translate directly into the BIM Execution Planning frameworks that govern professional practice. The technical vocabulary evolves, but the underlying logic of preserving design intent within a structured, version-aware file system remains constant.

Practice Problems

Lesson Summary