Construction
12 workflows—pursuit and proposals, estimating, procurement and contracts, field operations, scheduling, safety, finance, and compliance.
Workflows from general contractors, specialty trades, and construction managers. Each one starts with a document the office already produces—a spec book, a drawing set, a certified payroll report—and ends with a person signing off.
Chasing the work
-
Go or no-go before anyone reads three hundred pages
How it works
ProblemA public solicitation runs hundreds of pages across a base document and nine amendments, and the details that kill a pursuit hide in the appendices. Someone reads all of it, summarizes it verbally, and the call gets made on feel under deadline pressure.
- Starts fromThe solicitation and every one of its amendments
- You getA scored go/no-go workbook, with a page citation behind every score
- Signed byThe pursuit committee, which overrides any score and makes the call
What AI doesReads the solicitation and every amendment, scores the firm’s own go/no-go factors with a page citation behind each score, finds comparable past projects, and writes a scoring workbook with a tier and an estimated pursuit effort.
What you needThe solicitation document and all amendments; attachment and evaluation-criteria exhibits; your past pursuit portfolio and win-loss history; client relationship history and current pipeline.
-
Every RFP requirement mapped, and checked back at the end
How it works
ProblemOne person retypes every submission requirement into a spreadsheet, assigns owners and backs a schedule out from the due date. Before submittal someone cross-checks the whole proposal by hand, and missing a single requirement can disqualify the bid.
- Starts fromThe RFP and its submission instructions
- You getA requirements matrix with an owner on every line, and a compliance check of the finished proposal
- Signed byThe marketing lead, who certifies compliance before the proposal ships
What AI doesPulls every requirement with its page limit, maps it to a response section and an owner, hands each author a starter file carrying that section’s requirements and the past content it found, then checks the finished proposal back against the list and marks each item answered, partial or missing.
What you needThe RFP, its amendments, and submission instructions; evaluation criteria and page limits; past submitted proposals and the content library; the pursuit team roster and availability.
Pricing and contracts
-
Material lists straight off the drawing set
How it works
ProblemSomeone reads the set fixture by fixture, scaling runs and counting fittings into a spreadsheet. Every ordering and pricing mistake downstream starts with that count.
- Starts fromThe drawing set and equipment schedules you already produce
- You getA quantity list—item, tag, size, material, and count—in your estimating format
- Signed byThe estimator, who owns the number that goes in the bid
What AI doesReads the drawings, riser diagrams, and equipment schedules and produces a quantity list—item, tag, size, material, and count—in the format the estimator already prices from, marking anything it cannot read for field verification instead of guessing.
What you needDrawing sets, riser diagrams, and process diagrams; fixture and equipment schedules; handwritten field takeoff notes; your own takeoff or estimate template; historical job cost by cost code.
-
Trade scope packages out of the spec book
How it works
ProblemScoping one trade means reading a thousand-page spec book and hundreds of sheets by hand. What gets missed—sealants, a permit, who pulls the wire—becomes an argument in the field.
- Starts fromThe spec book and the drawing set
- You getYour own scope sheet, filled in, with every requirement cited to a spec section and sheet number
- Signed byThe procurement lead, who resolves every unowned and double-owned section
What AI doesIndexes the spec book and drawing set, finds the pages that matter for one trade, and fills the firm’s own scope sheet with each requirement cited back to a spec section and sheet number—flagging sections no trade owns and sections two trades both claim.
What you needThe full specification book, organized by division; the drawing set; your master scope sheet template; the planned list of trade packages; the signed subcontract and its exclusion list, where one exists.
-
Subcontracts read against your own risk checklist
How it works
ProblemLender consent and assignment agreements run pages of dense language, and one missed clause can bind you to keep working after the general contractor defaults, or quietly waive lien rights. A signed subcontract will name spec sections as your scope while an exclusion list carves work back out—and nobody reconciles the two before signing.
- Starts fromThe subcontract, its exhibits and the exclusion list
- You getEach risky clause quoted and rated, sorted into accept, negotiate or escalate, with counter-language drafted in your house style
- Signed byThe owner and the attorney, who decide what to redline and whether to sign
What AI doesRuns each document against a written checklist of risk categories specific to the trade, quotes the actual clause, rates the exposure high, medium or low, and sorts every term against the firm’s own written acceptable ranges. Read alongside the spec book it produces a scope table: what you own, what is excluded, what the spec assigns to others, and the contradictions to get in writing before signing.
What you needThe subcontract with its exhibits and exclusion list; lender consent and assignment agreements; the prime contract where available; the full specification book; a written guardrails document of acceptable ranges and previously accepted language.
Running the job
-
The submittal register, built from the specs
How it works
ProblemAt project start an engineer walks every spec section hunting for submittal requirements and types them into a register. About a week of work, and anything missed surfaces months later as a late submittal.
- Starts fromThe spec book and the schedule’s install dates
- You getA register with each item’s section reference, type and required-by date, and the long-lead items flagged
- Signed byThe project engineer, who performs the review of record and stamps the submittal
What AI doesWalks every spec division, pulls each required submittal with its section reference and type, works the required-by date back from the install date in the schedule, flags long-lead items, and reports any section where it found nothing.
What you needThe full specification book and any amendments; the project schedule install dates; subcontract scope assignments; submittal packages and product data; referenced material test standards.
-
The three-week look-ahead, off the handwritten board
How it works
ProblemA superintendent crosses off work and pencils dates onto a printed template, then someone types it all up again for the subcontractor meeting.
- Starts fromThe marked-up template, or a photograph of the planning board
- You getThe updated look-ahead, the meeting agenda and a sign-in sheet, with critical-path and weather-sensitive work called out
- Signed byThe superintendent, who confirms activities, crews, and dates before the pack goes out
What AI doesReads the marked-up template or a photograph of the planning board alongside the schedule export, and produces the updated look-ahead, the meeting agenda and a sign-in sheet, with critical-path activities and weather-sensitive work called out.
What you needThe scanned handwritten look-ahead template or a photo of the planning board; the critical-path schedule export; subcontractor meeting notes; zone and floor plans.
-
Daily field logs turned into the weekly owner report
How it works
ProblemSuperintendents type weather, crews, tasks, and photos into the project system every day—then someone re-types the same week into a template, drags the photos across, resizes them, and rewrites the narrative from memory. And every superintendent emails a separate spreadsheet that someone copies into a master sheet every Monday.
- Starts fromThe week’s daily logs and site photos
- You getThe owner report drafted into your standard template—progress, issues with what is being done about each, and the look-ahead
- Signed byThe project manager, who edits the draft and decides what actually goes to the owner
What AI doesTakes the week’s daily logs and photos and drafts the owner report into the standard template, marking anything it could not find so a person fills the gap. It also lets a foreman dictate the whole daily entry once from a phone—project, date, trade, crew size, work completed, open questions, and near misses—and merges the weekly spreadsheets into one sheet with the source noted on every row.
What you needDaily logs entered by superintendents; site photos; the previous week’s report and the blank template; weekly work-report spreadsheets from each superintendent.
-
The safety paperwork that gates a job start
How it works
ProblemNo work starts until the hazard analysis clears five sets of hands, which can take a month. Status lives only in how someone renamed the file.
- Starts fromThe subcontractor’s draft hazard analysis and the project brief
- You getA pre-filled cover sheet, the draft read against the hazards past reviews have rejected, and a status view readable from a phone on site
- Signed byThe safety lead, who accepts every hazard analysis personally—it is a liability decision, so it is never automated
What AI doesPre-fills the cover sheet from project records, reads the subcontractor’s draft against the hazards and permits past reviews have rejected, and shows what is sitting at which stage and what is past its review window, readable from a phone on site.
What you needThe subcontractor’s draft hazard analysis and cover sheet; certification and competent-person documents plus the daily crew list; the company safety manual and the general contractor’s requirements; a project brief naming the site, trades, and hazards; prior accepted analyses and rejection history.
-
What moved in this month’s schedule
How it works
ProblemA schedule update arrives and nobody can say precisely what moved. When the owner asks why the completion date slipped, the answer comes from memory. Writing the formal monthly narrative runs two to three hours on a heavy project, and reformatting the raw period-comparison export alone takes an hour or more.
- Starts fromThe current and prior schedule exports
- You getA movement report—activities added and deleted, date and logic changes, milestone slips, and the chain behind the slip—plus your narrative’s data-driven sections
- Signed byThe scheduler, who writes the judgment sections and decides whether a trend warrants escalation
What AI doesCompares two schedule exports and reports activities added and deleted, duration and date shifts, logic and status changes, milestone slips, and the net movement of the completion date, with the chain behind the slip. From a single export it also calculates schedule performance, a compression index and a quality grade against recognized scheduling standards, and produces the milestone table, the longest path and the revision list in the firm’s own long or short form.
What you needCurrent and prior schedule exports; the baseline schedule and contract milestones; your narrative template and the prior month’s narrative.
Billing and closing out
-
The monthly card statement, split and coded
How it works
ProblemOne consolidated card statement covering dozens of cardholders gets split by hand, a coding request emailed to each person, late responders chased, then every returned receipt matched back to a transaction and re-sorted into statement order. On top of that, cost codes have to be checked and sales tax treatment verified state by state.
- Starts fromThe consolidated monthly statement and the cardholder roster
- You getOne coding packet per cardholder, the chase emails drafted, receipts matched to transactions, and an exception report with a confidence score on each line
- Signed byThe cost accountant, who works the exception queue—nothing posts to the accounting system without a person releasing it
What AI doesSplits the statement into one coding packet per cardholder, drafts each request email with the right attachment and due date, tracks who has not replied and sends reminders, then matches returned receipts to transactions on vendor, date, and amount within tolerance. It checks cost codes and per-state tax treatment and hands back an exception report with a confidence score on each transaction.
What you needThe consolidated monthly card statement; the cardholder roster and email rules; returned receipts and coding responses; the valid cost code list and state tax rules.
-
Certified payroll checked against the wage determination
How it works
ProblemEvery week a compliance team hand-reads roughly five hundred pages of subcontractor payroll, checking each worker’s classification, rate and fringe against the wage determination for that job.
- Starts fromThe weekly certified payroll documents and the job’s wage determination
- You getAn audit workbook with every underpayment written up, classification by classification
- Signed byA compliance auditor, who decides what is a real violation—the signed workbook is the record
What AI doesReads each page—including the non-standard formats subcontractors send—matches every classification to the right line on the wage determination, recomputes the required rate including fringe, and writes each underpayment into an audit workbook.
What you needWeekly certified payroll documents from subcontractors; the wage determination rate table for the job; the pay-period and subcontractor list per job.