Modules — Your Cost DNA

A Module is the most powerful concept in Darwin.
It represents a reusable piece of construction knowledge — a complete definition of how something is built.

Modules allow organizations to stop rewriting the same line items and instead build a consistent, traceable, and scalable cost structure.

If projects are the containers of knowledge, modules are the knowledge itself.

1. What a Module Represents

A module describes a construction assembly such as:

a masonry wall
a concrete slab
a steel beam
a gypsum partition
a façade panel
a door or window system

Each module contains:

Materials (type, quantity, unit)
Labor (trades, hours, production rates)
Expenses (indirects, logistics, handling)
Classification tags (UniFormat, MasterFormat, IFC context)
Documentation (notes, drawings, specs)

A module is not a “line item.”
It is a complete building block that can be reused across projects.

2. Why Modules Matter

Modules solve several long-standing problems in traditional estimating:

Consistency

Everyone uses the same logic for the same assembly.

Speed

No more rewriting takeoffs and resource lists from scratch.

Scalability

Organizations can maintain deep libraries of construction knowledge.

Traceability

Each module becomes a stable reference point across the lifecycle of estimating.

Adaptability

Modules stay constant; prices change through the price list.

This separation of logic and cost is one of Darwin’s core principles.

3. How Modules Interact With Price Lists

Modules contain logic, not prices.

For example:

Module: Masonry Wall 20cm

1.05 m² of blocks
0.25 hours of mason labor
0.10 hours of helper labor
1.0 m² of plaster (optional)
0.02 m³ of mortar
Indirects such as scaffolding or handling

The price list determines:

cost of blocks
hourly rates of labor
cost of mortar
cost of logistics or expenses

This means:

change the price list → the estimate updates
revise the module → every project uses the corrected logic

This is the foundation of consistent, intelligent estimating.

4. Creating a Module

To create a new module:

Go to Catalog → Modules.
Click New Module.
Enter a name and classification (UniFormat recommended).
Add materials, labor, and expenses.
(Optional) Add documentation or notes.
Save the module.

Screenshot placeholder:
Add here: Module creation screen

A module can be edited at any time, and changes apply to future estimations.

5. Composite Modules

A Composite Module groups several modules into a larger assembly.

Examples:

Exterior Wall System
- insulation module
- masonry module
- plaster module
- waterproofing module
Foundation System
- footing module
- rebar module
- concrete module

Composites allow teams to conceptualize complex systems without losing granularity.

6. Using Modules in Estimations

When you create an estimation:

mapped IFC elements bring modules automatically
you may add modules manually
quantities flow from the IFC or from manual input
the price list calculates costs

Modules ensure that every project speaks the same “cost language.”

7. Versioning and Evolution

Modules evolve over time as:

production rates improve
design standards change
materials change
new suppliers appear
lessons are learned from previous jobs

Darwin allows organizations to refine their module library continuously, strengthening their cost DNA.

8. Best Practices for Building Modules

Use clear naming conventions

Include size, type, or specification.

Keep modules focused

Each module should represent a specific assembly, not a vague system.

Document assumptions

Add notes or specs so others understand the logic.

Avoid embedding prices

Let the price list handle cost values.

Review modules periodically

A strong module library is a strategic asset.

9. Next Steps

Explore the rest of the Catalog:

➡️ Materials
➡️ Labor
➡️ Categories

Or continue learning about project workflows:

➡️ Create Your First Estimation