Abstract

Construction estimation often breaks down due to redundant data entry, outdated price references, and fragmented document handling. Darwin introduces a modular framework combining reusable cost blocks, dynamic price lists, and collaborative workflows. The result is rapid, precise, and auditable estimations that scale across teams and projects.

1. The Core Idea: Eliminating Redundancy

Traditional workflows force estimators to repeatedly define elements, retype supplier prices, and attach documents in separate systems. Darwin resolves this by:

  • Defining construction knowledge once (modules).
  • Anchoring estimates to time-stamped price lists.
  • Managing documents directly inside each project context.

2. Modules as Knowledge Blocks

Modules capture the complete cost structure of an element:

  • Materials (quantity × price)
  • Labor (hours × rate)
  • Expenses (transport, insurance, overheads)

Modules are reusable across projects. Once validated, they become the company's "cost DNA"—applied instantly to new estimations with only price updates.

3. Price Lists as Temporal Anchors

Darwin separates logic (modules) from market conditions (prices).

  • Price Lists store material, labor, and logistics values at a given moment.
  • Projects can be recalculated with new lists without redefining modules.

This ensures historical estimates remain reproducible while future ones reflect current conditions.

4. Design Integration as Input

Darwin can parse IFC BIM files to extract elements and map them into modules. This acts as a fast input channel into the cost engine—reducing manual entry but still relying on the core principles: modules, price lists, and collaborative validation.

5. Estimation Formula

[Formula details to be added]

6. Collaboration as a First-Class Citizen

Darwin is not a single-user tool. Teams can:

  • Draft an estimation and request a price reviewer to update or validate costs.
  • Assign roles such as approvers, reviewers, and contributors for controlled workflows.
  • Track modifications with time-stamped histories.

Collaboration ensures estimations are not just technically correct but also organizationally accountable.

7. Projects as Organized Repositories

Every estimation lives inside a Project container. Projects can store:

  • Estimations and revisions
  • IFC design files
  • Supplier and client documents
  • Contracts, drawings, and correspondence

This makes Darwin a structured document repository, ensuring all knowledge is preserved and accessible in context, rather than scattered across emails or drives.

Conclusion

Darwin reframes estimation as a scientific, collaborative process. By unifying reusable modules, dynamic price lists, auditable formulas, and project-based document repositories, Darwin enables teams to produce precise budgets quickly, avoid redundant work, and maintain transparency across stakeholders. Its IFC integration provides an optional accelerator, but the foundation remains a robust cost engine and a collaborative knowledge system.