Estimating

The job pressure

Estimates and budgets diverge the moment someone edits one without the other.

All packages

On the job

Construction estimating software fails when the bid number and the job budget are two different files. EstiLumina keeps hierarchical estimate lines — CSI or cost code — on the same job that received takeoff quantities.

Price with org catalog items and assemblies, review totals with your team, then lock the baseline when the number is firm. That lock is what Job Run uses before RFQ and award, so winning the job does not start from a rebuilt spreadsheet.

Teammates can work the same estimate without silent overwrites. The handoff into budgeting is a continuation of the same spine, not a copy-paste night.

How it works

1. 1

   Build or receive hierarchical estimate lines from takeoff push.

2. 2

   Price with catalog items, assemblies, and cost types.

3. 3

   Review totals, then lock the baseline when the number is firm.

4. 4

   Locked estimate becomes the job budget spine for winning the job through RFQ and award.

What you get

• Hierarchical estimate structure by CSI / cost code
• Assemblies and catalog unit costs in one place
• Lock baseline so job cost stays honest
• See teammates in the estimate — edits merge without overwriting each other
• Hands off cleanly into budget and RFQ

Why teams subscribe

• One hierarchical number from takeoff through lock
• Catalog pricing stays on the same estimate lines
• Locked baseline feeds budget before you win the job

Honest boundaries

• Not a standalone bid spreadsheet that never becomes job cost.
• Not a claim that every regional form set ships prebuilt.
• Not a claim that the /estimating worksheet is the same hierarchical lock as the job Estimate tab.