All docs

Goals

What Struction is built to do, and the two ideas everything hangs on: the scope of work, and the drawings and specifications that fund every assumption in it.

Updated 2 minApplies to: MapFeedback →

What preconstruction is, to Struction

Preconstruction is the work of defining every scope of work needed to deliver a project's contract documents. Margin and win rate follow how completely and accurately those scopes are defined — quantities included. Struction is built to help you define every scope more precisely and completely, whatever the timeline.

Two ideas carry the whole product:

  • The scope of work — the core unit of every bid.
  • The drawings and specifications — the requirements that fund every assumption in a scope.

Struction assumes the architect and engineers have broken the project's requirements into disciplines, and that your job is to define the scopes that fulfill them. So it produces a first draft of those scopes, then flags the risks, RFIs and gaps that come with them.

A project's Trade Map: every discipline as a cluster of sheets and spec sections, with the scopes of work Struction drafted from them underneath.
A project's Trade Map: every discipline as a cluster of sheets and spec sections, with the scopes of work Struction drafted from them underneath.

What you get from a project

  • Scopes of Work — trade-by-trade bid forms, every item pointing back to the page it came from.
  • Issues — RFIs, risks and scope gaps to resolve before bid day.
  • Quantities — measurements taken off the drawings to back your pricing.

Today Struction helps with five jobs: discovery (understanding a new project), scope creation, RFI creation, risk resolution and quantity takeoff.

Five things to remember

  1. Your documents are here.
  2. Your scopes come from your drawings and specs.
  3. Every output has a source.
  4. And every source is connected.
  5. Chat is your partner. Anything you can do by clicking, you can also ask chat to do.

Tip — Senior and junior estimators use Struction the same way; the difference is scope of responsibility, not workflow. A junior estimator might own one discipline, a senior estimator the whole map — and you work on the same map, with assignments, comments and a record of who changed what.

Was this page useful?Stuck? help@struction.com