Division 31: Earthwork for Software & Platforms

How software & platforms use MasterFormat Division 31 – Earthwork for specifications, coordination, and project documentation. Licensed through CSI Dynamic Standards.

Software & Platforms engage with MasterFormat Division 31 – Earthwork throughout the project lifecycle. Division 31 covers site earthwork—clearing, grading, excavation, fill, soil stabilization, and erosion control that prepare the ground for construction. For software & platforms, Division 31 is where most commonly embedded standard.

How Software & Platforms Use Division 31 – Earthwork

Most commonly embedded standard—used for search/filter/autocomplete, spec outlines, WBS generation, cost code structures, and any UI that organizes data by divisions/sections. Division 31 is one of the divisions that software & platforms encounter most frequently in practice. The sections within Division 31 define the products, execution methods, and quality standards that software & platforms must reference, review, or author.

Key sections within Division 31 include: - 31 10 00 – Site Clearing - 31 20 00 – Earth Moving - 31 23 00 – Excavation and Fill - 31 25 00 – Erosion and Sedimentation Controls - 31 30 00 – Earthwork Methods

These sections shape how software & platforms display csi divisions/sections/titles in the ui, or let users search, filter, or autocomplete by csi data. When section numbers are outdated or inconsistent, the downstream impact on software & platforms is immediate: stale classification data in production databases.

Division 31 in the Software & Platforms Workflow

Platforms that store, process, display, generate, or learn from CSI numbers, titles, classifications, or mappings in their UI, backend, or services. Within this scope, Division 31 plays a specific role:

  1. Documentation — Software & Platforms display csi divisions/sections/titles in the ui, or let users search, filter, or autocomplete by csi data. Division 31 sections must be correctly numbered and titled in every document that references them.
  2. Coordination — Division 31 scope intersects with other divisions on every project. Software & Platforms need consistent classification to coordinate earthwork work with adjacent trades and disciplines.
  3. Quality — train or prompt ai features to produce or validate csi classifications.

Pain Points Software & Platforms Face with Division 31

  • Stale classification data in production databases — When Division 31 section references are affected by stale classification data in production databases, the result is rework, RFIs, or coordination failures that software & platforms must resolve.
  • Users encountering outdated section numbers — When Division 31 section references are affected by users encountering outdated section numbers, the result is rework, RFIs, or coordination failures that software & platforms must resolve.
  • Manual updates when new editions are released — When Division 31 section references are affected by manual updates when new editions are released, the result is rework, RFIs, or coordination failures that software & platforms must resolve.
  • Licensing ambiguity for embedded CSI data — When Division 31 section references are affected by licensing ambiguity for embedded CSI data, the result is rework, RFIs, or coordination failures that software & platforms must resolve.

These issues compound across projects. A single incorrect Division 31 section number in a team's template can propagate across every project that uses that template.

Division 31 Cross-References for Software & Platforms

UniFormat: Division 31 maps to UniFormat G (Sitework)—the site preparation work that precedes building construction.

OmniClass: OmniClass Table 22 (Work Results) includes earthwork results; Table 13 (Spaces by Function) covers site spaces.

Understanding these connections helps software & platforms maintain consistency when Division 31 work touches UniFormat elements or OmniClass classifications in their deliverables.

Why Software & Platforms Need Current Division 31 Data

CSI Dynamic Standards includes Division 31 as part of a connected, edition-aware system—licensed through The Construction Standard. For software & platforms, this means always-current section numbers and titles for Division 31, governed cross-references to UniFormat and OmniClass, and edition tracking that prevents referencing obsolete classifications in software & platforms deliverables.

COMMON QUESTIONS
Software & Platforms use Division 31 – Earthwork when display csi divisions/sections/titles in the ui, or let users search, filter, or autocomplete by csi data. Division 31 sections define the products, execution methods, and quality standards for earthwork work that software & platforms must incorporate into their deliverables and workflows.
The most referenced Division 31 sections for software & platforms include 31 10 00, 31 20 00, 31 23 00. The specific sections vary by project type, but software & platforms typically engage with Division 31 during store activities.
Division 31 maps to UniFormat G (Sitework)—the site preparation work that precedes building construction. For software & platforms, these connections ensure Division 31 references in specifications align with element classifications in cost models and BIM deliverables.
CSI Dynamic Standards—licensed through The Construction Standard—provides software & platforms with always-current Division 31 section numbers, edition-aware data, and governed cross-references to UniFormat and OmniClass. This prevents the classification errors that cause RFIs, scope disputes, and coordination failures.

Ready to Get Started?

CSI Dynamic Standards includes MasterFormat, UniFormat, and OmniClass as a connected, edition-aware system. The Construction Standard provides licensed access—built for the speed of your work.

Get startedView packages