Bid leveling subcontractor quotes: a GC’s guide
The low bid is rarely the complete bid. How to normalize every quote against your IFC scope and price the gaps before they come back as change orders.
Read the guide → PlaybookSubmittal log management: stop reviews stalling the job
Real submittal cycles average ~32 days against 10–14 day spec windows. Where the time goes and how to pull it back.
Read the guide → Closeout & disputesConstruction dispute documentation: the evidence packet
The average U.S. dispute is worth $60.1M and takes a year. What a defensible evidence packet contains and how to assemble it from the record you already have.
Read the guide → DataHow many freight invoices have errors?
Errors show up in up to 10% of freight bills, and a thorough audit recovers 2–5% of transport spend. The audit data and how to catch errors before payment.
Read the data → DataHow much time do teams lose hunting policy & SOP answers?
About 1.8 hours per employee per day goes to searching for internal information. What that costs and how a cited answer layer claws it back.
Read the data → DataWhat does an RFI really cost in 2026?
~$1,080 to answer the average RFI, ~9.7 days to turn it around — and where that money actually goes (hint: the search, not the decision).
Read the guide → PlaybookHow to cut RFI turnaround from 10 days to 1
A five-step playbook to collapse the answer loop without cutting diligence — centralize revisions, cite by default, and put an answer layer in front of the documents.
Read the guide → Field guideSpec vs. drawing conflict — which one governs?
There's no universal rule. Here's how order-of-precedence clauses actually work, why a field decision should never silently pick, and how to catch conflicts early.
Read the guide → Free toolWhich document governs? — order-of-precedence checker
Pick your contract family (AIA, CCDC, ConsensusDocs, EJCDC) and the kind of conflict, and see the general order of precedence — plus why the safe move is almost never to just pick one.
Open the checker → ChecklistConstruction document software: a buyer's checklist
23 questions to ask any vendor before you sign — grounding, citations, revision-awareness, conflict handling, data isolation, and the traps to avoid.
Open the checklist → Field guideThe hidden cost of building from a superseded revision
Outdated-set rework is one of the most expensive mistakes on a job — and it hides inside change orders and delay. Why it happens and how to stop it.
Read the guide → ExplainerRFI vs. submittal vs. change order
Three documents, three jobs. What each one is, when to use which, and the one bottleneck they all share.
Read the map → Closeout & disputesHow to build a defensible project record
Disputes are won by who can prove they were right. Build a dated, cited record as you go — so the evidence exists before you need it.
Read the guide → AI, responsiblyAI for construction documents: what's safe, what isn't
Generic AI will confidently invent a panel rating. Here's the line between safe and unsafe AI on a jobsite — and the pattern that keeps you on the right side.
Read the guide → Plain-language guideCan AI read construction drawings?
Yes — but only a cited, revision-aware answer is safe to act on. How it works, where it fails, and the three checks that separate a real answer from a confident guess.
Read the guide → Plain-language guideIs there a Bluebeam alternative for answering questions about your drawings?
Bluebeam owns markup and takeoffs. Getting a cited, revision-aware answer across your whole document set is a different job — how the two compare, and where each one fits.
Read the guide → Plain-language guideIs it safe to use AI on construction documents?
It can be — with the right tool. The two real risks (your data leaking, and made-up answers) and the five checks to run before you upload a single drawing set.
Read the guide → Where it fitsProcore, Buildertrend & the missing answer layer
Your system of record stores and routes documents well — it still can't answer the question inside them. Where a grounded answer layer fits alongside it.
Read the guide → ChecklistThe construction closeout package checklist
O&Ms, warranties, as-builts, attic stock, approvals — the full list. Print it and collect as you go instead of chasing closeout for months.
Open the checklist → Plain-language guideWhat is an RFI in construction?
The formal question that resolves gaps and conflicts in the documents — when to send one, what it costs, a clean format, and how to cut the pile down.
Read the guide → LogísticaDetention vs. demurrage — and disputing the charges
Two clocks, two charges, and invoices that are wrong often enough to matter. How your own rate agreement and gate records win the dispute.
Read the guide → Live proofReal answers, timed and cited — including the one it refused to guess
Unedited production answers: a dimension cited in 56 seconds, and an honest "the documents don't say" on a fire-rating question. Judge for yourself.
See the proof → First principlesWhat a "cited answer" means — and why it matters
"It's fine" gets challenged at the wall. "Per E-2.1, Rev 3, detail 4" doesn't. Why the citation is the whole ballgame on a jobsite.
Read the guide → Protect your marginChange-order scope creep: catch it early
Scope creep leaks in through small COs and vague answers. How to catch it in the documents before it eats your margin.
Read the guide → CompareIntelMS vs a generic AI chatbot vs the manual way
Three ways to answer a document question. Only one cites its source, reads the latest revision, and refuses to guess on the dangerous calls.
See the comparison → Caso de éxitoA live electrical scope — real cited answers
How IntelMS was proven on a live electrical scope, with real questions answered from the project's own drawings and specs.
Lee el caso de éxito →See what one RFI is costing your job
Two-minute calculator. Your numbers, your annual figure — then a real cited answer from a live project.
Open the RFI cost calculator →