Skip to main content

πŸ”Œ Volt β€” Electrical Scope Reader

I bid the project on 17 May. The Scope of Work is dated 18 May.
Volt reads the whole project manual β€” all of it, not just Division 26 β€” and returns every place another division hands work to electrical, with the section, the sentence, and what the sentence leaves undefined.
Run it on a book you already bid.

The Problem

You priced what you could see. The mechanical schedule said the units come furnished with disconnect. It did not say integral, it did not say who mounts it, and there was nothing in Division 26 to tell you either way.

The cut sheets showed up later. Now there are five sidewall exhaust fans at 480 volt three phase, two smaller exhaust fans, and four motorized louvers that were not in what you priced. The PM says they were in the Scope of Work. The Scope of Work is dated the day after you bid.

Or it is the model number. The heat strip configuration determined an additional tap, the electrical schedule did not carry that information, and you ate the Polaris lugs across quite a few units. There was no dispute and no one to bill. You found out at closeout, by yourself.

The remedy you adopted afterward was to look up every model in the schedule. That works on a quiet week. It is the first thing to go when there are eight packages due.

The Stakes

What happens if this stays the way it is

Short term, you absorb it. The fragment was technically in the bid documents, which makes the GC a bystander rather than an adversary, and there is no one to bill.

Longer term, your exclusion list keeps growing β€” and it only ever defends the border you can already see. The fragments that cost you are the ones you never read and therefore never excluded.

The part that does not reverse: once you sign, the documents govern. If the units are in the bid documents, too bad for the person who missed it. That is not a vendor’s framing. That is the community’s own verdict on itself.

Who this is for

The estimator bidding a blank sheet
You get the electrical set and the fragments live everywhere else β€” the mechanical connection notes, the kitchen equipment schedule, the elevator disconnect, the temporary power paragraph in Division 01. You meet them at takeoff, before any leverage exists, and usually with no second reader.
The senior estimator who reads everything
You already cross-reference the mechanical schedules. Your problem is not discovery β€” it is that the spec is a contract document whether it is good, bad, contradictory or incomplete, and the omission risk transfers to you at signature. Reading more does not close that. Naming the sentence in the exclusion does.
The GC estimator leveling four bids
The low number is well under the next one and the room wants to take it. What is actually in front of you is a fire alarm rough-in that lives in Division 28, quietly dropped. The spread presents as a price; its cause is a document location.
The project engineer watching gear release
The HVAC contractor got 480 volt units approved and you ran 208 volt circuits per the electrical drawings. Nobody told you. The chiller went from 400 to 500 tons in an addendum you did not catch. The schedules are authored by a different discipline on a different revision cycle, so no amount of diligence inside your own model keeps them aligned.
The PM standing in the field fight
The unit is landed, the disconnect is set, and nobody carried the final connection β€” or everybody thought somebody else did. You are converting a scope argument into a change order with the crew standing by, over a boundary that was written ambiguously at bid and never nailed down.

How It Works

  1. 01
    Give it the whole book. The full project manual, not the electrical set. That is the only setup there is β€” no per-project configuration, no template to build first.
  2. 02
    It comes back with a list. Fragments, each with its division, its section number, and the sentence, ordered by what it will cost rather than by where it appears in the book.
  3. 03
    Check the sections it names. Open the ones you want to verify. Every finding carries its citation precisely so you can audit it instead of trusting it. An uncited finding is not delivered as a finding.
  4. 04
    Carry it or exclude it. Each fragment comes with the language for either side. You make the call, it goes in the scope letter.
β€œThe note on the mechanical schedule says the units are furnished with disconnect β€” it does not say who mounts it, and that silence is where the money goes. Carry it or exclude it, but do not leave it alone, because silence resolves against whoever signed. Here is the language for either side, sheet and note number attached β€” your call which one goes in.”
Volt

What it does

01

It reads every division, not just yours.

Division 23 connection notes, Division 22 heat trace, Division 21 fire pump, Division 14 elevator disconnects and shunt trip, Division 11 kitchen and foodservice, Division 12 motorized shades, Division 01 temporary power. Each fragment comes back with its section number and the sentence it came from.
02

It finds the assignment no matter how the sentence is phrased.

By electrical, by Division 26, by EC, wired by others, furnished by mechanical, coordinate with electrical contractor. Including on scanned sheets that return nothing at all to a text search.
03

It sorts each fragment into furnish, install, connect, or coordinate β€” and names what the fragment leaves undefined.

The schedule note that assigns final connection without defining connection. The note silent on whether the disconnect is integral.
04

It turns each fragment into carry-or-exclude language with the citation attached.

One line per fragment, the wording for either side, the sheet and note number in it.
05

It records what you priced against.

Which documents, which dates, which fragment language. So a Scope of Work dated the day after your bid is demonstrably outside what you priced.

What it does not do: it does not price. It produces no labor unit and no bid number β€” you set the number, the same as you do now. It does not decide the responsibility split; it names the ambiguity, cites it, and hands the call back to you. And it cannot read a document you were not given. If a fragment exists in no issued document at bid time, it is outside what any reader can catch, and Volt says so instead of filling the gap.

The Promise

What you can expect, and what has to be true

Volt returns every place outside Division 26 where the book hands work to electrical, with the section and the sentence. It reconciles a panel schedule against the mechanical, plumbing and equipment schedules and names the mismatches. It diffs revisions and reports which referenced equipment moved. It produces carry-or-exclude language you can lift into a scope letter, and a record of what a number was priced against.

The conditions: you have to give it the full manual, not just your set. It handles scanned and image-based sheets. It cannot catch a fragment that exists in no issued document at bid time β€” and the worst case in the record is exactly that, a governing document nobody had. You still make the pricing decision.

There is no customer catch to show you and no return figure to quote, because this is new and nobody has a year of results with it yet. What exists is the record of what this problem costs when nobody runs the cross-check, and the fact that the cross-check itself is not sold by anyone. That is why the first step is your book instead of our case study.

Objections, answered

β€œThe tool prices what I put in it. My problem is what I never found.”

That is an accurate read, and it is why this is not an estimating platform. Accubid, ConEst, McCormick, the spreadsheet β€” all of them price what is entered. The fragment never entered because it was never found, or never delivered. Volt works on the reading side of that line and stops there; it hands off to whatever you price with. Run it against a manual you know and watch where it looks.

β€œThat is way too detail oriented for the size of jobs I bid.”

There is no per-project setup to justify. The input is the manual you already have and the output is a list. The honest test is not a feature walkthrough on a flagship project β€” it is a run against a small book, inside the time you actually have in a bid week.

β€œIt was in the documents. That is on me, and no tool changes that.”

The documents did contain it. What did not happen is coverage β€” the equipment schedules and the other divisions are a document class nobody at a shop your size is assigned to read end to end. Looking up every model on every unit on every bid is not a discipline problem. It is arithmetic on a bid calendar, and it fails on the crowded week.

β€œCanned numbers will make me high and I will lose work.”

Volt does not produce numbers. No labor units, no pricing database, no material catalog β€” it tells you what is in the book and you price it your way. What it changes is that carrying, excluding, or walking becomes a decision you made rather than one that happened to you.
Stop finding out at closeout.

Run it on a book you already bid. If it does not return the fragment that got you, you have lost an hour and learned something for free.

Your scope is in the book. It is just not in your division.