Why should I use an .rte file instead of creating a rvt project template?

[Anonymous]

My company is in the process of creating a template to use as a starting point for all of our projects.  I am one of the lead persons responsible for creating this file.  We are currently using a .rte file, but I have not been able to figure out the benefits of doing this .vs just creating a .rvt project template file.  The latter would allow multiple people to work in the template (we have electrical and mechanical) as well as set up worksets within the template.  The intent is to not necessarily drive what worksets are used, but reduce the number of items required during project setup.  Any thoughts on this topic would be greatly appreciated.

[ToanDN · Accepted solution]

The only benefits of an RTE (that I found) are make it less exposed to accidentally modified and that one fancy dialog when you start a new project. 

I don't use it but a RVT template project and Save As.

[robert.klempau · Accepted solution]

Hello @Anonymous,

I set up Revit Template files for many companies.

The difference between creating a .tre file or a Revit project file lays in wetter you want to define standard Worksets for all your new project or not.

As you may know, you can't store Worksets in a .rte file.

So I advise companies always to start new projects using a Revit template project .rvt with Worksets.

They store a read-only Revit template project file in a central location from where they start the new project they open this file and detach it from central and save it to the project location.

The Revit template file or template project file stores your company standard.

So it does not matter which method you use as long as you take care of your company standard.

One of the most important standard settings for MEP projects is the correct set up of all your Pipe- and Duct systems, View template, and View Types.

Users like to change the visibility Graphic Overrides of views what mostly ends up in incorrect output on construction documents. 

Learn users to use View Types with View Templates connected.

Learn them also to work with the temporary View Properties method.

If they mess up View templates you always can use the Transfer Project Standards to correct the View Templates.

Hope this information is helpful for you to create your company standard.

Please see my articles below that can help you to create your standards:

Turn all Level and Grids off in linked models in your entire project

Filtering sections in Views based of the Sub-Discipline

[dcaiW26XZ]

@robert.klempau Hi Robert, do you have a copy of the two articles you linked in your comment? The links seem to be dead.

[Tom_Kunsman]

I think working with a template is slightly easier, especially if you have new(er) users to Revit. I always like to encourage new users to start a blank project with the company template and start "playing" around in the program to trya nd get more comfortable with the interface and any special set up in the Project Browser. 

When starting a new project you will have to detach from central the project based template, relinguish elements, and save into a new location. With a template file you can create your worksets from beginning, or even automate that step with Python and pyRevit.