Project Folder Structure Standards

11. Project Folder Structure Standards

11.1 File Naming Standard

Use a consistent file naming convention for all models, exports, drawings, and coordination files.

11.1.1 Revit Model File Naming

Revit model files must use the following naming pattern unless the project BIM Execution Plan defines an approved exception:

Pattern: <ProjectNumber>_<Client>_<ProjectName>_<ProjectCityCounty>_<RevitVersion2Digit><DisciplineAbbreviation>.rvt

Token definitions:

Token

<ProjectNumber>

Description

S3 project number

Token

<Client>

Description

Client name or approved short client name

Token

<ProjectName>

Description

Approved project name

Token

<ProjectCityCounty>

Description

Project city or county. Use the project location naming approved for the project.

Token

<RevitVersion2Digit>

Description

Two-digit Revit version year, such as 24, 25, or 26

Token

<DisciplineAbbreviation>

Description

Approved discipline abbreviation, such as A, S, M, P, E, FP, or other approved project discipline code

Rules:

• Use underscores between major name fields.

• Do not use spaces in Revit model filenames.

• Keep client and project name values consistent across all discipline models.

• Use the same two-digit Revit version for all models created in the same Revit project version.

• Do not rename active cloud workshared models without BIM manager approval.

Example:

Value: 24001_S3Design_YogaJoint_Braintree_26A.rvt

11.1.2 Export and Coordination File Naming

For exports, coordination files, and non-Revit deliverables, use the following general pattern unless the BIM Execution Plan defines a more specific project standard:

Value: ProjectNumber-Originator-Discipline-Zone-Level-Type-Description-Revision

Example:

Value: 24001-DTC-ARC-A-L01-NWC-Architecture-R01.nwc

11.1.3 S3 Content Naming Convention

Rule Number 1

Be consistent.

Consistency is the primary naming rule. Names must be predictable, readable, and structured the same way across families, types, parameters, reference planes, files, and supporting BIM content.

Prefix

All new S3 standard content names must begin with:

Value: S3

S3 indicates that the item has been developed as part of the new S3 standard and differentiates it from older content.

Macro-to-Micro Structure

Names must progress from general to specific, also known as macro to micro.

This structure helps users understand what the item is and what it does at a glance.

Example structure:

Value: S3_Category_Item_Subtype_Descriptor

Separators

Use underscores (_) to separate hierarchy levels.

Underscores help with parsing, sorting, and organizing files and content consistently across projects.

Abbreviations

Abbreviations are preferred to be all caps, but all caps are not required in every case.

Example:

Value: S3.AOR.License.No.

CamelCase

Use CamelCase by capitalizing the first letter of each word for readability.

Example:

Value: SemiRecessed

Spaces

Spaces are not allowed in names except when writing feet and inches.

For all non-dimensional names, use CamelCase instead of spaces.

Dimension rules:

• Use spaces only for feet-and-inches formatting.

• Do not use decimal units in names.

• Use fractional units only.

• Use inches only if the dimension is less than 12" or 1' 0".

• If one value in a multi-value name is less than 12", still use feet-and-fractional-inch formatting so units remain consistent in the name.

Correct and incorrect examples:

Correct

2' 8"

Incorrect

2'8"

Correct

2' 8"_0' 8"

Incorrect

2' 8"_8"

Correct

1 1/2"

Incorrect

11/2"

Correct

F_Door_2' 8"_6' 8"

Incorrect

F_Door_2'8"_6'8"

Correct

F_Door_2' 8"_6' 8 1/2"

Incorrect

F_Door_2'8"_6'81/2"

All other names must have no spaces.

Scales

When family or type names include scales, add the scale factor as a prefix so scale values sort in a usable order.

Required scale format:

Value: ScaleFactor_FractionScale"

Correct and incorrect examples:

Correct

008_1 1/2"

Incorrect

1 1/2"

Underscores

Use underscores only as hierarchy separators or intentional placeholders.

Dashes

Do not use dashes.

Correct and incorrect examples:

Correct

BiPass

Incorrect

Bi-Pass

Correct

SemiRecessed

Incorrect

Semi-Recessed

Family Name Examples

Examples:

• S3_PlumbingFixtures_Sink_Undermount_Single

• S3_PlumbingFixtures_Sink_Undermount_Double

Family Type Name Examples

Examples:

• S3_Default

• S3_SemiRecessed_LifeSafety_Top

Family Parameter Name Examples

Examples:

• S3_Length

• S3_Bowl_Interior_Length

Reference Plane Name Examples

Examples:

• S3_Center_Left.Right

• S3_Drain_Center_Front.Back

11.1.4 Revit View Naming

View names must be clear, consistent, and coordinated with sheet presentation.

Linked Views

All linked views must use the following suffix in the Revit view name:

Value: _Linked View

Required format:

Pattern: <ViewName>_Linked View

Example:

Value: FirstFloorPlan_Linked View

Rules:

• The suffix is required in the Revit view name for linked views.

• The sheet Title on Sheet must not include the _Linked View suffix.

• Linked view naming must remain consistent across all disciplines using linked views.

11.1.5 Revit Family Type and File Naming

Family type and family file naming must follow the S3 naming rules in Section 11.1.3.

Family type example:

Value: S3_2' 10"_6' 8"_Metal_180MIN

Recommended family file/type naming structure:

Pattern: S3_<RevitCategory>_<SearchKeyword>_<SecondaryDescription>_<Size>_<HostType>_<MasterSpecSectionName>_<DivisionSection6Digits>

Alternate readable structure:

Pattern: S3_<NounKeyword>_<Size>_<HostType>_<MasterSpecSectionName>_<DivisionSection6Digits>_<SecondaryDescription>

Examples:

Examples:

• S3_SpecialtyEquipment_FireExtinguisher_Cabinet_Wall_104400

• S3_FireExtinguisherCabinet_Wall_FireProtectionSpecialties_104400

Host type values:

• None

• Wall

• Floor

• Roof

• Level

• Face

• Line

• Ceiling

• System

• Adaptive

• CurtainPanel

Rules:

• Use S3_ as the prefix.

• Use CamelCase for search keywords and descriptive names.

• Do not use spaces except in dimensional values.

• Use the six-digit division section number when available.

• Manufacturer, client, or brand references may be used as secondary descriptions when they help users identify the content.

• Family names, type names, and file names should be searchable by Revit category, noun / keyword, host type, and specification section where applicable.

11.2 Default Project Startup Folder

New project folders should be created from the default project startup folder when the project is using the network project drive workflow.

Path Type

Staff-facing mapped path

Location

P:\00000 - Project Start-up Folder

Path Type

Server UNC path

Location

\\192.168.1.99\projects\00000 - Project Start-up Folder

Use the mapped path in project team instructions. Use the UNC path only for technical reference, troubleshooting, or Cinch IT coordination.

Current folder template:

Template compliance note:

• The current observed startup folder contains legacy locations for keynotes, title blocks, Revit families, and Revit materials.

• Those legacy locations are not approved production storage locations under the current standards in Sections 10, 11, and 12.

• If the startup folder is copied before the template is formally updated, the project startup team must follow the current policy sections over the legacy folder names.

11.3 General Folder Rules

• Work in progress files remain in discipline-controlled locations.

• Shared files must be suitable for use by other disciplines.

• Published files must match milestone or formal issue requirements.

• Archived files must not be modified.

• Coordination files must be traceable to model issue dates.

• Project directories must not be used as uncontrolled storage locations for managed BIM content.

11.4 Removed Directories

The following legacy directories are removed from the project folder standard.

11.4.1 Extras Folder

The following folder is removed:

Folder / file path: 01_Architectural/02_Extras

11.4.2 Title Blocks Folder

Title block folders are removed from all Revit drawing directories.

11.5 Folder Structure Direction

Project folder structures are being reduced where Forma Data Management now provides the controlled source of truth.

The following local or network structures should not be recreated unless specifically approved:

• Duplicate keynote folders

• External title block folders

• Revit family storage folders inside project directories

• Revit material storage folders inside project directories

• Redundant drawing/documentation folders when Forma Data Management is the controlled document location