MasterFormat Division 35 – Waterway and Marine Construction in Idaho

Idaho's Regulatory Environment and Division 35

Idaho follows the International Building Code (IBC) as its primary model code, with construction classification requirements that align with national standards. Snow load requirements, seismic considerations in southern Idaho, and energy code compliance in a heating-dominant climate shape specification requirements across the state.

While Division 35 may not be among Idaho's highest-volume divisions overall, every project involving waterway and marine construction work requires current, accurate classification to prevent specification errors.

Cold climate construction demands rigorous attention to thermal envelope performance, insulation specifications, and freeze-thaw considerations in concrete and masonry work. For Division 35 work specifically, these climate conditions influence product selections, performance criteria, and execution requirements across the key specification sections.

Moderate seismic considerations influence structural specifications and require familiarity with seismic design categories that affect multiple MasterFormat divisions.

Key Division 35 Sections for Idaho Projects

This division includes waterway and marine signaling, dredging, dams, levees, ports, harbors, navigation locks, coastal construction, and underwater construction.

Representative sections within Division 35 that Idaho construction teams reference include: - 35 20 00 – Waterway and Marine Construction and Equipment - 35 30 00 – Coastal Construction - 35 40 00 – Waterway Construction and Equipment - 35 50 00 – Marine Construction and Equipment - 35 70 00 – Dam Construction and Equipment

Idaho is one of the fastest-growing construction markets in the Mountain West, driven by technology industry migration, population growth, and commercial development in the Boise metro and beyond. Within this market context, Division 35 work appears across the full range of Idaho's project types—from the state's largest commercial and institutional projects to residential and infrastructure work.

Division 35 and Idaho's Key MasterFormat Divisions

Idaho's construction market heavily references Divisions 03, 07, 23 across its project pipeline. Division 35 coordinates with these divisions on every multi-trade project. When section numbers across divisions are inconsistent, coordination failures—RFIs, scope gaps, submittal delays—compound across the entire project team.

Keeping Division 35 Current Across Idaho

Construction teams working across Idaho should treat Division 35 as governed project data. Specification masters, estimating templates, submittal logs, and closeout checklists all need the same current section references. When a team copies a prior project without validating the edition, stale Division 35 labels can move into bid packages, RFIs, and owner turnover documents.

The practical control is to review Division 35 references before issue, preserve section numbers through construction administration, and keep the connection to UniFormat and OmniClass intact where the work affects budgets, models, or facility records.

Cross-Standard Connections for Idaho Projects

UniFormat:Division 35 extends UniFormat into marine and waterway infrastructure—specialized construction entities beyond typical building scope.

OmniClass:OmniClass Table 11 (Construction Entities) classifies marine and waterway facilities as built environment entities.

On Idaho construction projects, these cross-standard connections create coordination demands across specification packages. Teams that maintain governed crosswalks between Division 35 and UniFormat and OmniClass ensure classification consistency from early design through facility lifecycle.

CSI Dynamic Standards for Division 35 in Idaho

CSI Dynamic Standards includes Division 35 as part of a connected, edition-aware classification system—licensed through The Construction Standard. For construction teams in Idaho, this means always-current Division 35 section numbers and titles, governed cross-references to UniFormat and OmniClass, and edition tracking that prevents referencing obsolete classifications in idaho project documentation.