Template vs Project for project start up

[david_peterson]

Our firm is in the process of re-creating something and making some major updates (we haven't touched our templates in like 3yrs).
While trying to figure out what to change the question came up as to should we use a .rvt file vs a .rte file for project start ups.
RVT files give you the option to have worksets already set up for you. But outside of that I'm not sure if there's any other real advantage.
What's the Augi Nation got to say?

[KoryCox]

Aren't workswets going to be different per project?

I think the biggest advantage of using .rte files is that there is little danger of someone starting a project in the template, where if a .rvt is being used a user could accidently start a project within the template.

[david_peterson]

That's kind of my major concern. However we've negated that by locking down our content folders.

[etboards17]

We use .rvt because we want worksharing enabled upon startup.
For us, worksets are different per project, but only depending on size. For small projects, worksets consist of workset1, Misc.Ref., Shared Levels and Grids, and Linked Models by discipline. For larger projects we might break the model up my building mass: Bldg1, Bldg2, plus the previously listed worksets. So, starting with a workshared model is advantageous to help users stick to Best Practices and Naming Conventions.

[mburke.54112]

We also use a .rvt file for our template because we want the worksharing enabled. We use the same worksets for all our projects & it's easier for us to delete the project specific ones we don't need than to create all of them.

[Duncan Lithgow]

I humbly advocate using rvt files. For all the reasons mentioned but also because it means I can set up placeholder links (see http://malleristicrevitation.blogspot.dk/2011/03/creating-revit-template.html) in their own worksets with views setup to do QA of what is on which workset. Settings all of that up once in every file is a pain. But then my experience is from a small number of projects with nearly identical setups.