HurdWorksAI
← All Projects
AI-assisted and rules-based construction automation

From change order proposal to approved project updates in fewer steps.

Review proposals and backup, redline rejected scope, reconcile pricing and prepare validated updates to your construction management systems.

Discuss a Similar Project See Redline Demo ↓
CHANGE ORDER PROPOSAL · DEMONSTRATIONCO-017
Riverton Office RenovationFictional change proposal · Northline Mechanical

Scope & Pricing Review

Additional mechanical ductwork$8,250.00
Temporary duct insulationNOT ACCEPTED$1,245.67
Additional hangers and supports$2,851.11
Add Alternate 1 · Fire damper supports ACCEPTED+$475.50
Original total$12,346.78
Revised base$11,101.11
Accepted Add Alternate 1+$475.50
Revised proposal$11,576.61
Rounded amount for review$11,577
Review instructionsReconcile valuesPrepare project fields

Example: “Strike item 3, accept Add Alternate 1.” Fictional values, subject to human approval.

AI + non-AI automationProposal redliningConnected project systemsOperational intelligence
INTERACTIVE FICTIONAL WORKFLOW

Watch a change order proposal get redlined.

Try the sample instruction. It rejects item 3, accepts Add Alternate 1, recalculates the amount and maps the result to a sample Change Event. Everything shown uses fictional data.

Change Order Proposal ReviewFictional project · Interactive walkthrough
HUMAN REVIEW REQUIRED
SOURCE-CONSISTENT REVIEW

Change Order Proposal

Project: Riverton Office Renovation CO-017

ORIGINAL / SUBMITTED
Fictional change order proposal line items and their submitted values
Item / scope descriptionQtyAmount
1. Supply and install additional ductwork1 LS$8,250.00
2. Additional hangers and supports1 LS$2,851.11
3. Temporary duct insulation per RFI-023NOT ACCEPTED1 LS$1,245.67
Add Alternate 1. Fire damper support modifications ACCEPTEDOPTIONAL · NOT SELECTED1 LS$475.50
Original base proposal$12,346.78
Less rejected item 3−$1,245.67
Revised base scope$11,101.11
Plus accepted Add Alternate 1+$475.50
Revised proposal (before rounding)$11,576.61
Rounded to nearest whole dollar$11,577
Item 3 is not accepted and Add Alternate 1 is included. The $11,576.61 revised proposal rounds to $11,577.

Fictional illustration of document review and project-field preparation. Changes to any connected platform, approvals, and electronic signatures require authorized access and human approval.

OVERVIEW

Built around how the work actually happens.

Reviewing construction change order proposals means tracking PDFs, vendor backup, financial decisions and information that must be reentered in project management software.

A connected workflow uses AI where interpreting documents or instructions helps, and deterministic rules for calculations, data mapping and repeatable actions. The project team can give instructions such as “strike item 3, accept Add Alternate 1.” The application preserves the source proposal, redlines excluded work, reconciles supported totals and prepares approved change event and change order fields.

Where a platform provides supported API access and the customer authorizes it, a HurdWorks workflow can retrieve vendors, commitments and project codes, populate eligible Procore or similar software fields, and verify approved updates through readback. People retain authority over scope, pricing and approvals.

Your data is valuable, so put it to work. Structured records can also support reporting about recurring scope gaps and pricing patterns by subcontractor, project manager, job type and trade. Which analyses can be produced depends on the evidence and data an organization captures.

WHAT IT DOES

More useful work, with fewer manual steps.

Practical tools, clear outputs, and people in control of the important decisions.

01

Review proposals and backup

Read change order proposal PDFs, supporting backup and project instructions with source traceability.

02

Extract scope, pricing and alternates

Identify vendors, scope descriptions, priced items, excluded work and Add Alternates for review.

03

Apply plain-English instructions

Direct a reviewable change by saying “strike item 3, accept Add Alternate 1.”

04

Redline rejected proposal items

Mark unaccepted work directly on a redlined copy while preserving the original.

05

Reconcile approved financial values

Remove supported exclusions, add approved alternates and round final amounts when appropriate.

06

Populate connected project-system fields

Prepare authorized vendors, commitments, budget codes and Change Event data in the receiving system.

07

Choose AI or rules-based automation

Use AI for interpretation where useful and predictable automation for validation, math and supported API tasks.

08

Preserve human decisions and evidence

Keep source review, financial authority, approvals and integration verification separate and traceable.

09

Turn change data into operational insight

Create a basis for finding repeated scope gaps by subcontractor, PM, project type and trade.

WORKFLOW

How the pieces fit together.

Every important decision stays visible and reviewable.

  1. 01

    Submit the change order proposal

    Upload the proposal, supporting backup and any review instructions.

  2. 02

    Read and confirm source information

    Extract scope, vendor, price and Add Alternate details, then verify them against originals.

  3. 03

    Give clear review instructions

    Mark item 3 for rejection and Add Alternate 1 for acceptance.

  4. 04

    Redline and reconcile

    Strike rejected scope, include accepted alternates and calculate a reviewed final amount.

  5. 05

    Prepare connected system records

    Map authorized values to Change Events, commitments, cost codes and other supported fields.

  6. 06

    Confirm updates and reuse the data

    Verify eligible API writes with readback, and preserve the approved records for operational analysis.

DELIVERABLES & OUTCOMES

Useful outputs. Clearer next steps.

  • Redlined proposal copies with visible rejected items and accepted alternates.
  • Reconciled financial totals and editable change order descriptions.
  • Project-specific Change Event data prepared for supported system integrations.
  • Reusable review records to help track common scope gaps and decision patterns.

Relevant systems and document types: Procore Open API where supported · Other authorized business APIs · Source proposal and backup PDFs · Reviewed financial records

Fictional example only. Direct platform updates, signature routing and analytics require supported APIs, client authorization and appropriate review controls.

HURDWORKS AI

Have a process like this in your business?

You don't need to know which automation or AI tool to ask for. Start with the work you want to improve.

Talk About Your Workflow