Every office eventually hits the point where "we'll just clean it up on the next project" stops working, because the inconsistency has compounded across a dozen live jobs. Building a real office template once, properly, pays for itself within the first two or three projects. Here's the build order I actually follow.
1. Start from a clean base, not last year's messy project file
Starting a template from an old project file, even a "good" one, drags in years of unused families, orphaned line styles, and one-off settings nobody remembers the reason for. Start from Autodesk's default template and add deliberately, rather than starting from a cluttered file and trying to subtract.
2. Define your shared parameter file first
This needs to exist before you build a single family or schedule, because every data field you want consistent across projects depends on it (see our breakdown of shared vs project vs global parameters). Retrofitting shared parameters into an existing template later means touching every family that uses the equivalent project parameter.
3. Build view templates before individual views
View templates control graphic overrides, visibility/graphics settings, and scale consistently across every view of that type. Set up your core set first — Floor Plan, Reflected Ceiling Plan, Section, Elevation, 3D — with consistent line weights, fill patterns, and annotation crop visibility. Every new view created later should inherit from these, not be manually formatted one at a time.
4. Load only the families you'll actually standardize on
A bloated template with hundreds of rarely used families slows every project that starts from it. Curate a core library — common door/window/furniture types your office actually uses repeatedly — and keep specialty or one-off families out of the template, loaded per-project instead.
5. Build your sheet and title block standards
| Standard | What to fix in the template |
|---|---|
| Title block | Office logo, project info fields, revision table format |
| Sheet naming convention | Consistent numbering scheme (e.g., discipline-level-type) |
| Drawing list/index | A schedule auto-populated from sheet parameters, not manually maintained |
6. Set up your core schedules as templates too
Door, window, room, and area schedules built once with correct filtering, sorting, and the right shared parameters included will save every future project team from rebuilding them from scratch — and more importantly, ensure schedules are comparable across projects for office-wide reporting.
7. Document the template itself
A template with no accompanying short standards document just becomes "the thing we inherited and don't fully understand" within a year or two of staff turnover. A one-page reference — what's included, why certain settings were chosen, who to ask for changes — keeps the template maintainable rather than something people quietly work around.
Why this matters more than it seems
A consistent office template is one of the quiet differentiators between firms that can scale BIM delivery across many projects and ones where every project feels like starting over. It's also exactly the kind of standards thinking that ISO 19650-aligned delivery expects at an organizational level, not just a project level.
Template and standards setup is part of the process training in our Apex plan, alongside ISO 19650 literacy. Full curriculum on the Programs page.
