At my previous employer, I was tasked with creating a template library for each jurisdiction that our projects were located. When I was done, on every project, these templates had to be copied into a project template library and modified multiple times to meet particular circumstances. As such, even with standard templates, it seemed nothing was truly standard.
I would suggest a solid, consistent naming convention for points, components, parametric labels, styles and anything else you can think of. And then some basic examples of how you can control some aspects of a template using these items with an admonishment about maintaining these standards. Point out that these naming conventions exist so that using these will not be a unique learning experience on every project. And that with them, anyone, from any project, can step in to any other project and immediately know why a template is behaving a certain way and how to adjust it if necessary.
You are aware that you can plot the templates to a drawing, right? It's in a right click menu, as I recall.
