BidTriage

How it works

Every source in.One ranked queue out.

BidTriage does not replace the portals your team already uses. It reads across them, pulls in email traffic, collapses duplicates, processes the documents behind the invitation, checks them against your signals (the rules you set for what makes a job worth pursuing) and gives the estimator one place to decide.

The loop

Seven steps. One record.

From the invitation landing in a portal to the addendum that moves the bid date two weeks later, every step writes to the same opportunity record; your source systems are never modified.

  1. Ingest

    Every invitation enters one workspace: ConstructConnect, BuildingConnected, and the shared estimator inbox. Each record keeps its source.

  2. Collapse duplicates

    The same job arrives through several GCs, portals, and email. Related records are grouped so the estimator works the opportunity once, without losing where each invitation came from.

  3. Process the package

    The invitation is only the cover sheet. The available supporting documents are captured, their text extracted, and the package indexed, so your signals can be checked against what is actually inside the job.

  4. Apply your signals

    Your signals run against every document BidTriage pulls from an invitation, on your live bid flow, not a sandbox. Each one is tested against your firm's own past bid packages before it runs live.

  1. Show the evidence

    A recommendation without evidence is not useful. Every flag names what triggered it and cites its source, and the estimator can open the matching text.

  2. Decide

    Pursue, watch, or decline. BidTriage organizes the evidence and the priority; the estimator makes the call, and every decision becomes part of the firm's record.

  3. Stay ahead

    Addenda, deadline changes, and new documents keep arriving after the first call. The same opportunity record is where the team tracks them.

What a signal can express

  • Geography
  • Project type
  • Scope fit
  • Excluded work
  • GC preference
  • Labor requirements
  • Specification language
  • Record-level fields

Signals are built with the firm and tested against your own past bid packages before they go live, so you see what a signal catches first. Rules age and documents vary, so some recommendations will be wrong. When one is, the estimator overrides the verdict and the signal behind it gets adjusted.

Document processing, measured

94–99%
Measured document extraction coverage across the sources running in production today, varying by source.
1,925 pages
One package captured and ready in under two minutes.

A package can mean hundreds or thousands of pages of drawings, specifications, addenda, and supporting documents. Why not 100%? Some pages arrive as scanned drawings or images with no readable text. When BidTriage can’t read something, it says so instead of guessing.

Example

What an estimator sees.

The score is the summary, not the argument. Underneath it are the reasons the rules fired and the sentences they fired on, so the estimator can inspect every signal before accepting or changing the recommendation.

Central Library Renovation · Austin, TX

Bid dateJun 12, 2025 · 2:00 PM CDTInvited byConstructConnect

Triage score91/100

Top reasons

  • Core renovation scope matches the firm's rules
  • GC is one the firm actively pursues
  • Labor requirements align with current criteria

Evidence

  • Work includes interior demolition and full MEP replacement across all floors.

    Specs 23 31 00
    p. 12
  • Prevailing wage applies to all trades.

    Specs 00 72 13
    p. 4
  • Bid due by 2:00 PM CDT on June 12, 2025.

    Invitation
    p. 1
Verdict
PursueWatchDecline

Illustrative example. The project, the GC, and the document references are composite, not a live customer record.

Trust and data handling

What BidTriage does not touch.

The triage layer sits beside the systems your team already works in. It leaves your source records and your bids untouched, and the final call stays with your estimator.

  • Read-only on your sources.

    Read-only by design: your portals and inbox are never modified.

  • Your workspace stays yours.

    Bid data belongs to the customer workspace and is not pooled across firms.

  • Every flag cites its source.

    You can always open the document and the matching text behind a recommendation.

  • Human judgment stays human.

    The system ranks and explains. Your estimator decides.

Getting started

How onboarding works.

Setup is measured in weeks, not months, and nothing about your current process changes until you decide it should.

  1. Connect your sources

    You keep your own ConstructConnect and BuildingConnected subscriptions: your accounts, your data. A dedicated bids inbox works best for email flow, and a Chrome extension does the document capturing.

  2. Seed your signals

    Bring a handful of past bids, the good and the bad. Your signals are built with you and tested against your own documents before they run on live traffic.

  3. Weekly working calls

    A standing session while the system tunes to your flow. You flag what's wrong or missing; it gets fixed fast.

  4. A 30-day run-alongside trial

    BidTriage runs next to your current process for the first 30 days. If it isn't earning its keep, walk away.

The estimator does not need to read three hundred invitations to find the ten worth pursuing. BidTriage does that reading first.

See it on your own intake

Walk the queue with us.

Bring your sources and your criteria. We will walk the intake, the rules, and the evidence behind a live recommendation, end to end.

hello@bidtriage.com