Skip to main content

Docs · Workflow

Plan-to-bid playbook

The 9-step pipeline, walked at the level a senior estimator cares about. What each step does, what to review, what to override, and where the data ends up in the audit packet.

Apply for the PilotAll docs
Back to docs

  1. 01

    Intake

    Drop the plan set, addendums, and spec book. We classify each document by trade, division, and revision; you confirm the classification on the Workspace tab.

  2. 02

    Plan review

    Every sheet and spec section becomes a structured scope of work. Each claim ties back to its source page + paragraph.

  3. 03

    Quantity takeoff

    Per-trade symbol library + schedule parser produces editable line items with bidirectional source links. Low-confidence lines land in the review queue.

  4. 04

    Resource schedule

    Crew composition, equipment hours, durations — generated from the takeoff with org-level overrides honored.

  5. 05

    Direct cost

    Material + labor + equipment loaded against your cost database; RSMeans fallback for missing SKUs. Org-level pricing wins over RSMeans whenever you've set it.

  6. 06

    Indirect / general conditions

    Project-aware general-conditions template — pulled from past jobs of the same project class, editable per project.

  7. 07

    Validation

    Compliance checks: signed boilerplate, bond requirements, certification list, addendum-acknowledgment count. Flags surface as a checklist before you ship.

  8. 08

    Risk envelope

    Monte Carlo distribution over the bid total based on per-line variance. You see 10/50/90 percentiles; markup discussion gets evidence.

  9. 09

    Markup + peer review

    Markup waterfall by trade and overhead bucket; AI peer reviewer grades the bid, flags scope gaps and pricing anomalies.

Confidence gating

  • Each step has its own confidence threshold (configurable per project)
  • Below the threshold, the run pauses on the review queue
  • At or above the threshold, the run advances
  • Confirmed lines are pinned (`reviewed_by_user=true`); re-extraction can't overwrite them
  • Rejected lines train the recognizer's next bid as a hard-negative
  • Bulk-confirm at, say, 0.95 if you've seen the project class before

Related

Read these next.

Next move

Want help on a real bid? Schedule a live review.

Schedule a live reviewContact support
Plan-to-bid playbook — OmniTakeoff Docs