Conventional automationWorkflow guide · not independently tested

Build shared conceptual estimates in a precon estimating platform

Precon estimating platforms let teams build and update conceptual estimates collaboratively.

Estimator · Construction · ediphi

Content updated · Tool links listed below; vendor features and pricing change, so confirm with the vendor

Short answer

Precon estimating platforms let teams build and update conceptual estimates collaboratively. Start here: set up your cost codes and unit cost library. Keep a person in the loop: Unit costs need local market checks.

The problem

Build conceptual estimates the whole precon team can work in. This is a common, time-consuming task for a estimator.

What this workflow does

Precon estimating platforms let teams build and update conceptual estimates collaboratively.

How it works: Rules or specialist software perform the task. No AI agent is required.

Your checkpoint: Unit costs need local market checks.

Before you start

  • Access to the named tool; confirm license, version and cost with the vendor.
  • A small, non-confidential sample to try the workflow on first.
  • A qualified person to review the output before it is used.

Tools and access

Follow the steps

  1. Set up your cost codes and unit cost library.
  2. Build the estimate from the conceptual design.
  3. Track changes as the design develops.
  4. Export a summary for the owner.

Try a small example

Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet.

Sample input

Fill in the bracketed [fields] in the text below with your project data.

Manual setup checklist

Write an estimate assumptions and exclusions list for a conceptual estimate of a [building type] from these notes: [paste notes]

Expected output

Not published yet. Treat any output as a draft and check it against the source documents.

Check the result

  • Every value, citation or quantity traces back to a source document.
  • Missing information is marked as missing, not filled in.

Limits and recovery

  • Unit costs need local market checks.
  • Check your organization’s data policy before sharing project files with third-party tools.

Stop or switch when: The source cannot be verified, permissions are missing, or the result contains unsupported facts.

Frequently asked questions

How do I build shared conceptual estimates in a precon estimating platform?

Set up your cost codes and unit cost library. Build the estimate from the conceptual design. Track changes as the design develops. The full step list is above.

Does this use an AI agent or regular software?

It is labeled Conventional automation: Rules or specialist software perform the task. No AI agent is required.

What tools do I need?

ediphi. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first.

Can I use the output without checking it?

No. Unit costs need local market checks.

Has this workflow been tested?

Workflow guide · not independently tested. It is written from vendor documentation and practitioner use.

Evidence and maintenance

Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.

Know what does the work.

Agent executes
An AI agent calls connected tools to carry out bounded actions. You set permissions and review the result.
AI assists
AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
Conventional automation
Rules or specialist software perform the task. No AI agent is required.