Construction · Document intake & extraction

Construction bid package

An invitation to bid arrives. Its requirements are pulled out with their sources, a conflict in the addendum goes to the estimator, and the bid calendar and forms checklist are prepared.

Workflow demonstration · fictional data
  1. 1Package received
  2. 2Requirements extracted
  3. Estimator confirms
  4. 4Calendar & checklist
Invitation to bidMarrowfield Civic Annex · pp. 1–3

Sealed bids will be received until Nov 14, 2:00 PM.

A pre-bid job walk will be held on Oct 30 at 10:00 AM. Attendance is mandatory.

Each bid shall be accompanied by a bid bond of ten percent (10%) of the total bid.

Questions must be submitted in writing by Nov 5.

Submit with bid: bid form, subcontractor list, addenda acknowledgment.

Addendum 1: The pre-bid job walk is optional; attendance is recommended.

Fictional document for this demonstration.

Ready

An invitation to bid arrives. Its requirements are pulled out with their sources, a conflict in the addendum goes to the estimator, and the bid calendar and forms checklist are prepared.

Press Run the workflow to follow the document through each step. It will stop when a person needs to decide.

What this demonstrates

  • Requirements pulled from a long document, each linked to the text it came from.
  • A conflict between the invitation and an addendum caught before it reaches the calendar.
  • Deadlines and a forms checklist prepared from a single confirmation.

Where a person stays in control

The estimator confirms the requirements and resolves the conflict. Invitations to subcontractors are drafts until someone sends them.

In a real workflow

In practice, a workflow like this starts when a bid package reaches a shared inbox or folder, and writes to the calendar and project tools your team already uses.

Start a discovery

What is your business still doing manually?

Tell us about one process that takes too much of your team’s time. Michael personally reviews every discovery request.