BIM standards for small firms: start small, write it down, keep it alive

Why small firms need a different approach

Published BIM standards and large-firm manuals are valuable references, but they are written for organizations with dedicated BIM teams, many offices and many concurrent projects. A small firm copying one wholesale usually ends up with a document nobody reads and a template nobody trusts.

Small firms have real advantages. Decisions can be made quickly. Everyone can be trained in a single session. The template can be changed in an afternoon. A right-sized standard uses those advantages: it is short, practical and changes when the work changes.

What a standard actually is

For a small firm, a BIM standard has three parts:

1. The project template. This is the standard in executable form: line styles, text types, filled region types, view templates, title blocks, schedules and common families. If it is in the template, people use it without thinking.
2. A short written guide. A few pages explaining the decisions the template cannot enforce: naming, file locations, how to start a project, how to handle CAD content, what to check before issue.
3. A library. Approved families and details that the template does not carry, with a clear approval state.

Everything else, such as detailed procedures and project-specific requirements, can wait until there is a real need for it.

The first ten decisions to write down

If you write nothing else, write these:

1. Where files live. Folder structure for projects, the template and the library.
2. How projects start. Which template to use and the first setup steps, such as levels, coordinates and title block information.
3. Naming. Files, views, sheets, families and types. See the naming conventions guide.
4. Graphic standards. Line weights, line styles, text types and fills, embedded in the template.
5. View templates. Which templates exist and when to use them. See the view template strategy guide.
6. CAD content. When to link, import or convert, and what is not allowed in production models.
7. Families. Where approved families come from and how new ones are approved.
8. Worksharing. If you use it: workset names, synchronization habits and local file practice.
9. Before issue. A short checklist covering health, naming, sheets and exports.
10. Who decides. The name or role of the person who owns the standard and approves changes.

Each decision can be a paragraph or a short table. Together they may fit on a handful of pages.

Put the standard in the template

Written rules that the template contradicts are ignored. Rules embedded in the template are followed automatically. Whenever possible, express a decision in the template rather than in prose:

• Delete or rename default types that conflict with your standard, so people cannot pick the wrong one.
• Set view templates as defaults for new views.
• Include standard schedules, legends and sheets so projects start complete.
• Load a small set of approved, commonly used families.
• Add shared parameters your schedules and tags need.

Keep the template lean. Every additional family and view increases file size and maintenance. If something is used on only a few projects, it belongs in the library rather than the template.

Ownership in a small team

In a small firm, the standards owner is usually someone with another full-time role: a project architect, a senior technologist or a principal. That is workable if the role is explicit and time is protected.

• Name the owner. One person approves changes, even if many contribute ideas.
• Protect time. A small, regular allocation, for example a fixed slot each month, does more than occasional bursts.
• Collect feedback continuously. A shared list where anyone can note a problem or suggestion.
• Release changes deliberately. Batch template changes into versions with a short note, rather than editing the template whenever someone asks.

Handling CAD legacy content

Many small firms have years of CAD details and standards. Decide early how that content enters Revit, because uncontrolled imports and explodes are a leading cause of template drift. A simple rule set might be:

• Consultant and manufacturer CAD files are linked for reference, not imported into production models.
• Firm details move into Revit through a defined process, with review, rather than ad hoc on projects.
• Exploding CAD in production models is avoided unless the result is checked and cleaned.

The migration roadmap and layer mapping guide describe how to move details deliberately. For firms with many similar 2D details, a mapping-based converter such as Codex can create native drafting views that use the template's own line styles, text types and filled region types.

Training and onboarding

A standard only works if people know it. In a small firm, training can be informal but should be deliberate:

• Walk every new hire through the template and written guide in their first week.
• Hold a short session whenever a new template version is released.
• Pair less experienced users with someone who knows the standard on their first Revit project.
• Keep a page of good and bad examples from real, anonymized projects.

Growing the standard

Add structure when a real problem appears, not in anticipation. Signs that it is time to add something:

• The same question is asked repeatedly. Write the answer down.
• The same correction appears in multiple reviews. Change the template or add a check.
• A new project type or client requirement does not fit. Add a variant or a project-specific appendix.
• The firm grows past the point where everyone can be trained in one room. Formalize ownership and change control.

Equally, remove things that are not used. A short standard that is followed is better than a long one that is not.

Knowing whether it works

You do not need elaborate metrics. Ask a few questions at the end of each project: Did the team use the template unchanged, or work around it? Which parts of the standard were questioned? What did reviewers keep correcting? Were there problems at exchange or issue that the standard should have prevented? The answers are your change list for the next version.

Sharing standards with consultants and collaborators

Small firms rarely work alone. Structural engineers, MEP consultants and specialist designers exchange models and drawings with you, and each has its own standard. You do not need to impose yours on them, but you do need to agree on the points where the standards meet:

• Shared coordinates and levels, so linked models line up without manual adjustment.
• File naming for exchanged models, so everyone can tell which discipline, building and version a file represents.
• Exchange format and frequency, for example native models at agreed milestones or IFC at specific stages.
• Who models what, particularly for elements at the boundary between disciplines, such as structural walls or ceiling-mounted services.

Record these agreements in a short project-level document or a BIM execution plan. Keep a reusable version in your standard so you do not have to rewrite it for every project.

Checking that the standard is followed

A standard that is never checked drifts. A light-touch check at each stage, reviewing a sample of sheets, views and type names against the guide, is usually enough in a small firm. Treat departures as information: sometimes the project is wrong, and sometimes the standard is missing something the project needed. Either way, the check tells you where to act.

Common mistakes

• Copying a large firm's manual wholesale.
• Writing rules the template does not support.
• A template built around one project and never revisited.
• No named owner, so changes happen ad hoc on live projects.
• Allowing uncontrolled CAD imports and explodes.
• Treating the standard as finished.

Getting help with the thinking

Most of what a small firm needs is clear decisions and someone to own them. The Nova Foundation strategy pack is designed for owner-led studios and teams starting to formalize BIM: a readiness assessment, priorities and a 90-day plan. The free startup roadmap preview describes a lighter starting point. Both are self-guided planning resources, not consulting or certification.

Small firm standard checklist

• Template that embeds graphics, view templates and common content.
• Short written guide covering the ten first decisions.
• Library with an approval state.
• Named owner with protected time.
• Feedback list and versioned releases.
• CAD legacy rules.
• Onboarding walkthrough.
• End-of-project review feeding the next version.