Skip to main content

🛡️ Sentry — Low Voltage Scope Reader

Either the EC or the cable sub gets to eat this one.
Sentry tests every low voltage device in the package against its three dependencies — power, pathway, and termination — and returns the section that assigns each one or the word silent, with the language quoted and the sections searched named.
Run it on a package you already bid.

The problem

You have four hundred pages, three bids in flight, and a device schedule that tells you what to price and not what it rides in. Division 28 lists the readers and assigns you the devices. Division 26 assigns conduit for power distribution and never names communications raceway. Division 27 stops at the telecom room door. So you make a call under a clock, and if you guessed wrong the number is already out and the walls are already closed by the time anyone notices.
You mobilize into a building someone else prepared. You expected conduit stubbed to twelve openings and you are standing in front of bare CMU, with the electrician demobilized and the schedule already spent by the trades that finished before you. The decision stops being what to price and becomes whether to start. You did the early coordination — you brought them in specifically so this would not happen — and the surprise arrived anyway, because a conversation is not a record and the finger-pointing session gets won on records.
Your scope is defined by its relationships to other trades’ work. You supply the relay and the signal; somebody else supplies the fan, the conduit, the circuit, the host equipment. When one link goes silent, the system does not pass, and the certificate is held with your name on the permit. Your scope letter is correct and it does not make the fans work, because the AHJ does not read contracts.
You have four bids and a spread nobody can explain. Leveling compares the bids to each other, so an item none of the four carried compares clean across all four — and that is the one that comes back as a contingency draw eight months later, in a conversation with an owner who was promised a price.
An RFI lands asking who provides the conduit for the readers, and there is no answer in the documents to retrieve. There is only a party to assign, and you do not have the authority to assign one. It routes to the design team and comes back telling the trades to coordinate among themselves, which is the same instruction the specification already contained.

How It Works

Sentry starts at the device and works backward to the section. For every device type in a Division 27 or 28 package it runs three tests — is a circuit assigned, is a pathway assigned, is a termination assigned — and returns a section reference with the assigning language quoted, or the word silent. It reads across divisions to do it, checking Division 26 for raceway and branch circuit language, Division 27 for pathway and spaces, Division 28 for the device, and reaching into the divisions where fire alarm and access control interfaces land in other trades’ work. It separates three conditions that look identical to a fast reader: a section that assigns to a named party, a section that tells parties to coordinate among themselves, and a section that says nothing. Every silent verdict comes back with the list of sections searched, so what was checked is as visible as what was found.

You hand over the manual and the device types. You leave with three verdicts per device and the language behind each one.

  1. 01
    Send the device schedule and whatever pathway and raceway sections exist — the set you already have.
  2. 02
    Every device type gets tested on power, pathway, and termination.
  3. 03
    Each tier comes back with its assigning section quoted, or silent with the sections searched listed.
  4. 04
    Every silent tier converts into a bid-period RFI naming the device and the tier, or exclusion language naming the specific dependency instead of disclaiming generally.
  5. 05
    You pick any verdict, open the section it cites, and check it yourself.
“I do not tell you who owns the conduit. Nobody can tell you that. I tell you which section assigned it, or I tell you that none did, and I do it while you can still put it on the record for free.”
Sentry

What it does

01
Runs the Three-Tier Check on every device type — three verdicts per device, power, pathway, and termination, not one.
02
Reads across divisions in one pass — 26, 27, 28, and into 08, 14, 21, and 23 where the interfaces terminate — including the pathway language that sometimes hides in Division 26 where the installer never looks.
03
Quotes the assigning language with its section number, and when nothing assigns, says silent and names every section searched — never a convention supplied to fill the gap.
04
Separates a real assignment from a coordinate-among-yourselves instruction from true silence — three conditions that read the same at 11pm on a bid clock.
05
Flags orphaned code-gated interfaces — elevator recall, HVAC shutdown, dampers, door holders, duct detector monitoring — where a signal owner exists and no one owns the infrastructure between.
06
Converts every silent tier into a bid-period RFI or exclusion language naming the specific dependency, with the cost of each move — including the non-financial one — stated plainly.
07
Builds the dated pre-mobilization walk list, so the record of what physically exists predates the argument about it.
08
Tests a received bid set against the dependency map instead of against the other bids — the only check that catches the item none of the four bidders carried.

The Promise

Three verdicts per device type, with the assigning section quoted where one exists and the sections searched named where one does not. Every silent tier converted into an RFI or into exclusion language that names the dependency. Every code-gated interface inventoried with its orphans flagged. All of it inside a bid window.

What it will not do is tell you who owns the conduit. Nothing can. Anyone who names a conventional owner is manufacturing a certainty the trade does not have, and you would be the one holding it. It does not eliminate change orders, guarantee scope, or guarantee an inspection. It does not stamp, certify, or substitute for a credentialed designer where a credential is what the AHJ or the owner needs.

The conditions. Sentry checks what it is given, so a dependency living in a section that was not uploaded is one it cannot find — a silent verdict means no assignment was located in what it read, not that none exists anywhere. You make the call, because the choice between carrying, excluding, and asking depends on your competitive position and what the next invitation to bid is worth, and Sentry does not hold that information. And the finding has to reach award. A silent tier identified and never converted is a silent tier you still own.

Objections

“Nothing reads a spec. I read the spec.”

Correct, and the failure you are describing is real — a tool returning a confident clean answer on genuinely ambiguous language leaves you holding the number when the answer is wrong. So Sentry does not return confident clean answers on ambiguous documents. Assignments come back with the section and the language; absences come back as silent with the search list. What it replaces is the mechanical retrieval across divisions you do not normally open on a two-day clock. The catching-because-you-were-burned part stays yours.

“If I raise this formally, the GC stops inviting us.”

A verification run on every job is not a complaint. A verification run on this job is. The record gets produced as a matter of course before mobilization rather than in response to a specific failure, which is what takes the sting out of it — because any document that only appears when something goes wrong reads as a claim no matter how it is worded.

“My scope letter already draws the line.”

It does, and it works legally. Contractual exposure and inspection exposure are different exposures, and a perfect disclaimer and a failed inspection are compatible outcomes. Sentry shows the interface everyone disclaimed and nobody owns — visibility without taking on any more scope than you already carry.

“We already level bids and run scope meetings.”

You do, and the process is structurally incapable of catching this one. Leveling compares bids to each other, so a dependency absent from all four compares clean across all four. That is not our claim about your process — it is the leveling category’s own definition of what it looks for. Run it on a bid set you already awarded and see whether there is an item none of them carried.

“I do not have purchasing authority.”

True, and you are not the decision layer here. What this gives you is something that travels upward — a count of RFIs that traced to unassigned low voltage dependencies, which is a preconstruction argument rather than a routing one. Fewer RFIs, not faster ones. Nothing here claims to answer a scope RFI, because the answer is not in the documents to be found.
Take a package you already bid and run it.

Pick any device. Open the section Sentry cites and read the language yourself. If it is not there, you have learned everything you need in ninety seconds. If the tier comes back silent on something you carried, you found it somewhere other than in a finished building.

The specification does not decline to assign by accident — it declines by structure, and the structure is why the same omission happens on the next job.