Building a BIM practice deliberately, one decision at a time

What a BIM practice is

Many firms "use Revit" without having a BIM practice. The difference is intent. A practice has a clear reason for working this way, people responsible for the standard, a consistent way of starting and running projects, and a habit of learning from each project. Without those, results depend on whoever happens to be on the project.

A practice does not need to be large. In a small firm it may be a single standards owner, a short written guide, a template, a library and a quarterly review. What matters is that it is deliberate.

Start with purpose

Write down why the firm is investing in BIM. Typical reasons include:

• More consistent drawings with fewer coordination errors.
• Meeting client or contract requirements for models and data.
• Better design coordination with consultants.
• Reducing repetitive drafting so time goes to design and detailing.
• Keeping knowledge in the firm's standards rather than in individuals.

Choose the two or three reasons that matter most. They decide priorities: a firm driven by client requirements invests early in delivery planning and data, while a firm driven by drawing quality invests early in templates and details.

Assess where you are

Before planning, take an honest inventory:

• People: who is confident in Revit, who is learning, who has not started?
• Standards: is there a template? A written guide? Does anyone own them?
• Content: which families and details exist, and how good are they?
• Projects: which recent projects went well or badly, and why?
• Legacy: how large is the CAD detail library, and how much of it is still used?
• Tools and hardware: are workstations, versions and file locations consistent?

Record what you do not know as unknown. A good assessment leads to a short list of priorities, not a long list of problems.

Assign ownership

Every part of the practice needs an owner with time to do the work:

• Practice lead: sets direction and priorities, reports to firm leadership.
• Standards owner: template, guide, library and change control. In a small firm this may be the same person as the practice lead.
• Project BIM coordinators: model health, exchanges and execution plans on each project.
• Content contributors: people who build and review families and details.

Write the responsibilities down and plan the time. Ownership without time quietly becomes nobody's job.

Build the standard in layers

The standard is the practice's backbone. Build it in the order that delivers value soonest:

1. A firm template with your graphics, title blocks and core view templates.
2. A short written guide covering file setup, naming, worksharing and sheet standards.
3. A starter library of the families and details used on most projects.
4. Mapping between legacy CAD standards and Revit types, for migration and reuse.
5. Delivery templates: execution plan, exchange checklists and export settings.

The guides on BIM standards for small firms, naming conventions and view template strategy cover these layers in more detail.

Prove changes with pilots

Large changes, such as a new template, a new add-in or a new detailing approach, should be piloted before they become standard. A good pilot is small and bounded:

• A defined scope: one project, one stage, or one set of details.
• Written success criteria agreed before starting.
• An effort cap and a stop condition.
• A short review with a recorded decision: adopt, adapt, extend or stop.

Pilots protect live projects and create evidence. They also make it easier to say no to ideas that do not work, without blame.

Use evidence, not impressions

Practices improve when decisions rest on observation. Useful evidence is usually simple:

• Health check results across projects, compared over time. See model health checks.
• Recurring issues from drawing reviews and coordination.
• Logged time for specific tasks, before and after a change, on comparable work.
• Short project close-out reviews: what helped, what got in the way.

Keep evidence honest. Do not turn estimates into claimed savings, and do not compare results across very different projects. If you cannot measure something well, describe it qualitatively and say so.

Governance and change control

As the standard grows, changes need a simple process:

• Anyone can propose a change, with a reason and an example.
• The standards owner reviews proposals on a regular cycle.
• Approved changes are versioned, tested in a sample project and announced.
• Live projects decide whether to adopt changes mid-stage; new projects start with the current version.

Governance should be light. The goal is predictability, not bureaucracy. A one-page change log is often enough.

Choosing tools

Add-ins and other tools can help a practice, but only when they serve a priority and fit the standard. Evaluate them with written criteria, on test data, with a recorded decision; the add-in evaluation checklist describes how. Prefer tools that use your existing types, show what they will do before doing it, and leave native results that remain editable without the tool.

For example, if migrating a large CAD detail library is a priority, a mapping-based converter may help. Nova Codex is a Revit 2025 add-in that converts DXF details into native drafting views using your existing line styles, text types and filled region types, with a preview of entity counts and skips. Its coverage is limited and listed openly on its page, which is exactly the kind of information a practice needs to decide whether it fits.

Keep knowledge in the firm

One of the quieter benefits of a deliberate practice is that knowledge stops living only in individual heads. In many firms, the person who knows why a particular detail is drawn a certain way, or which wall type to use for a specific condition, is the only record of that decision. When they leave or retire, the knowledge leaves too.

A practice captures that knowledge in places other people can find:

• Types with clear names and descriptions, so the right choice is obvious in the type selector.
• Reviewed details in the library, each with a short note on where it applies and where it does not.
• A written guide that explains the reasoning behind important rules, not only the rules themselves.
• Project close-out notes that record lessons in a searchable form.

Invite experienced staff to contribute directly. Reviewing migrated details, writing a paragraph about a tricky condition, or explaining a convention in a lunchtime session is often the most valuable work they can do for the practice.

Talking about BIM with clients

Clients increasingly ask about BIM, sometimes with specific requirements and sometimes in general terms. A practice helps you answer honestly. Describe what you actually deliver, for example coordinated models at agreed stages, with defined levels of development and agreed exchange formats, rather than broad promises. Where a client has information requirements, respond with an execution plan that states what you will and will not provide. Clear, modest commitments that you meet build more trust than ambitious ones that slip.

A realistic first-year sequence

Timing varies greatly with firm size and workload. A firm under heavy project pressure may need to stretch this sequence; that is better than skipping the pilot and review steps.

Common mistakes

• Buying software before defining purpose.
• Writing a large standard nobody reads.
• Assigning ownership without time.
• Skipping pilots and rolling changes out to every project at once.
• Claiming savings without evidence.
• Treating the practice as a project that ends, instead of a habit that continues.

Planning resources

If you want structured help planning, Nova is preparing strategy packs covering readiness, priorities and adoption planning, and a free startup roadmap preview. They are drafts, and purchasing is not yet enabled. The guides on this site are free and can be used on their own.

Practice checklist

• Purpose written, with two or three priorities.
• Honest assessment of people, standards, content and projects.
• Owners named with time allocated.
• Standard built in layers, starting with the template.
• Pilots with criteria, effort caps and recorded decisions.
• Evidence gathered honestly and reviewed regularly.
• Light governance with versioned changes.
• Tools evaluated against priorities and standards.