08 71 00 Door Hardware
"Conduit at Door D103 is work of Division 28."
"Provide an electric strike, fail secure, at Door D101."
"Power supply for Door D103 is by others."
Pre-bid scope risk review
Catch the scope nobody priced — before the bid goes in.
Blueprint cross-checks electronic-security specifications and project manuals for scope gaps, conflicting requirements and unclear responsibility, then shows the rule, evidence and source behind every finding.
Source-backed findings Deterministic rules Human-verifiable
Current pilot focus: Access Control · Division 08 ↔ Division 28 · California Public/K-12
High
Scope gap
SB-022
Each division assigns the rough-in to the other
At opening D103, Division 08 assigns the rough-in to Division 28 and Division 28 assigns it back to Division 08. Each section has moved the work to the other side of the boundary, so no section carries it.
Extracted evidence
Conduit at Door D103 is work of Division 28. Project manual, section 08 71 00, page 5
Conduit at Door D103 is furnished under Division 08. Project manual, section 28 13 00, page 9
- Opening
- D103, rough-in at the Division 08 / Division 28 seam
- Authority
- CSI MasterFormat Division 08 and Division 28 boundary. AIA A201 General Conditions 1.2.1, the contract documents are complementary.
- Pre-bid action
- File an RFI quoting both sentences side by side and asking which division carries the work. Quote both. Asking with only one attached invites the answer that it is obviously yours.
- Confidence
- 0.90, the minimum of the two extracted statements
Rule trace
- seam_determinable = true
- each_division_assigns_to_the_other = true
- SB-022 raised SEAM_CIRCULAR_ASSIGNMENT, priority 10
- conflict_group opening_division_seam, won over SB-021
Live output from the division_seam fixture in the repository. Not a mockup.
The risk register
Full demo
Five findings from one seam. Open any of them.
This is the whole register from a package where the door hardware section and the access control section were both read. Select a row to see the evidence behind it.
| Risk | Target | Rule | Source | Recommended action | Review |
|---|---|---|---|---|---|
| High | D101 locking device | SB-020 | 08 71 00 p4 28 13 00 p8 |
RFI to delete one of the two requirements | no |
| High | D103 rough-in | SB-022 | 08 71 00 p5 28 13 00 p9 |
RFI quoting both sentences side by side | no |
| High | D104 power | SB-023 | 08 71 00 p3 28 13 00 p7 |
RFI asking which division carries the item | yes |
| Medium | D103 power | SB-024 | 08 71 00 p6 | Read the cited sections by hand before relying on this seam | no |
| Medium | D102 locking device | SB-021 | 08 71 00 p5 28 13 00 p9 |
Confirm which division carries it and price it once | no |
Finding
Division 08 (section 08 71 00) and Division 28 (section 28 13 00) both specify the locking device at opening D101, and they do not require the same thing. Division 08 requires an electric strike, fail secure. Division 28 requires an electrified mortise lockset.
Evidence
Provide an electric strike, fail secure, at Door D101. 08 71 00, page 4
Provide an electrified mortise lockset at Door D101. 28 13 00, page 8
Why it matters
Only one device gets installed, so one of the two sections is unmet the day the door is hung, and which one is unmet is decided by whoever ordered first rather than by the design. An electrified lockset and an electric strike do not share a frame prep.
Confidence
0.93 · review_required false · category DOCUMENT_CONTRADICTION
Finding
At opening D103, Division 08 assigns the rough-in to Division 28 and Division 28 assigns it back to Division 08. Each section has moved the work to the other side of the boundary, so no section carries it.
Evidence
Conduit at Door D103 is work of Division 28. 08 71 00, page 5
Conduit at Door D103 is furnished under Division 08. 28 13 00, page 9
Why it matters
At bid time nobody prices it, because each estimator reads their own section and correctly concludes it is not theirs. After award the two sentences are still there, which is why this is worth an RFI and not a phone call. The answer has to change a document.
Confidence
0.90 · review_required false · category SCOPE_GAP
Finding
Neither Division 08 (section 08 71 00) nor Division 28 (section 28 13 00) specifies the power at opening D104, and no other division is named for it. Both sections were read.
Evidence
SECTION 08 71 00 - DOOR HARDWARE page 3, read in full
SECTION 28 13 00 - ACCESS CONTROL page 7, read in full
Why it matters
Nobody has priced the item, so at award it is a change order or it is absorbed by whichever trade is standing closest to the opening when the gap is found, which in practice is the one already pulling cable.
Confidence
0.55 · review_required true · category SCOPE_GAP
This is the most inferential rule in the family. It is flagged for human review rather than presented as settled, because it argues from silence.
Finding
The power at opening D103 cannot be placed on either side of the boundary, because the only statement covering this work moves it to a party the documents do not name, so no division can be shown to carry it.
Evidence
Power supply for Door D103 is by others. 08 71 00, page 6
Why it matters
This is not the same finding as neither division specifying the work. Neither is a conclusion reached after reading both sections. Undetermined is the admission that the sentence covering this work moves it to a party the documents decline to name. Reporting the second as the first would be a confident output where the honest output is a flag.
Confidence
0.86 · review_required false · category SCOPE_GAP
Finding
Division 08 (section 08 71 00) and Division 28 (section 28 13 00) both carry the locking device at opening D102, and they do not disagree about what it is. Two trades are priced for one item.
Evidence
Provide an electric strike, fail secure, at Door D102. 08 71 00, page 5
Provide an electric strike (fail-secure) at Door D102 and connect it to the access control system. 28 13 00, page 9
Why it matters
Nothing about this looks wrong on either sheet. Both sections are correct in isolation and both estimators price the device, so either the owner pays for two of them or, more often, one bidder assumes the other trade has it, deletes it, and is the low bidder for the wrong reason.
Confidence
0.91 · review_required false · category SCOPE_GAP
The problem
The expensive mistake usually isn't hidden.
Division 08
Division 28
The expensive mistake usually isn't hidden.
It's between two documents.
Built for the seam between the door and the security system.
Access control scope is distributed across the architectural door schedule, the Division 08 hardware specification, the Division 28 security specification, the general notes, the addenda and the equipment schedules. Each document is internally consistent. The gap lives in the space between them, and closing that space by hand is the work that gets cut when the bid is due Thursday.
Division 08
"Conduit at Door D103 is work of Division 28."
Opening
D103 rough-in
Division 28
"Conduit at Door D103 is furnished under Division 08."
Blueprint
Circular assignment. Neither section carries the rough-in. Rule SB-022. Issue an RFI before bid.
28 13 00 Access Control
"Conduit at Door D103 is furnished under Division 08."
"Provide an electrified mortise lockset at Door D101."
No statement covers power at D104.
Four rules fire on this package: SB-020, SB-022, SB-023 and SB-024. Each names one opening, one aspect of it, and the sentences that put it there.
Assigned to both
Two sections carry the same device at the same opening. One estimator deletes it assuming the other has it. Both assumed correctly about their own section.
Assigned to neither
Each section moves the work across the boundary, or neither mentions it. Nobody prices it, and the sentences are still there after award.
Assigned differently
Both sections specify the device and they specify different devices. An electrified lockset and an electric strike do not share a frame prep.
MS
Who is building this
Built from the problems that appear between the drawing, the BOM and the field.
Blueprint Risk Engine is built by Muhammad Sizar, who holds a PMP from the Project Management Institute. The rules in it come from direct exposure to electronic physical security work: access control implementations, bill of materials review, project management and project finance, field coordination, and the specific kind of trouble that starts when the door schedule, the hardware specification and the security specification stop agreeing before construction begins.
The design decisions are recorded rather than assumed. The reason a model is not allowed to produce a number, and the reason a disagreement between two readings emits nothing at all, are written down in the repository, dated, and open to argument.
How it works
Three stages, and only one of them involves a model.
Stage 01
Read the package
Blueprint extracts structured evidence from the project documents and keeps a record of where every piece came from: document, section, page, and the exact sentence. Provenance is captured at extraction, not reconstructed later.
Stage 02
Cross-check the scope
Published deterministic rules compare requirements, responsibilities and known interfaces across documents. The rules are JSON, version controlled, and readable before you buy anything.
Stage 03
Review the risk register
The estimator gets ranked findings, each with the rule that fired, the evidence that triggered it, the source location, the rationale, and a recommended pre-bid action.
AI reads. Rules decide. You approve.
A model is permitted to read, and permitted to do nothing else: extract text, classify a statement, transcribe a schedule row, locate a device on a sheet, match one document's language to another's. A model may never compute a quantity, assign a part number, produce a risk score or determine compliance. Those are decided by deterministic rules in version controlled files, so the same documents produce the same register every time and any finding traces back to the rule and the sentence that caused it. The boundary is enforced by a test that walks the import graph and fails the build if a model client is reachable from the scoring code.
Why it pays to look early
Turn potential change-order conversations into pre-bid questions.
The same ambiguity costs a different amount depending on when you find it. Before the bid it is an email. After award it is a negotiation with a party who can point at their contract and be right.
Blueprint's job is to put items in front of an estimator while every option is still open: qualify the bid, issue an RFI, carry an allowance, get vendor pricing, write an exclusion, or decide the risk is acceptable and price it deliberately.
Before bid
An RFI
The design team answers in writing. The answer changes a document, and the document is what the contract is built on.
At bid
A qualification
You carry it, exclude it, or allowance it on purpose. Whichever you choose, you chose it and you can defend it.
After award
A negotiation
The scope is unpriced and the other party has a section that says it is yours. This is the conversation the earlier two are meant to prevent.
Security
Your bid documents are not marketing data. Treat them accordingly.
A bid package is a competitor's cost structure, an owner's vulnerabilities and a school's door schedule in one file. Blueprint is built so that the sensitive part of the work has the shortest possible path.
Your documents, in detailThe engine runs locally
Ingest, rule evaluation, validation and report generation are a command line program that runs on your machine. No document is uploaded for any of it.
Model calls are disclosed
Where a model is used for reading, the run says so, names the vendor, and cannot suppress that disclosure. There is no flag that turns it off.
No key is stored on a server
If you connect your own model account, that key stays in your browser. The database schema has no column for it, and a test fails the build if one appears.
Transparency
Don't trust a black box. Inspect the rules.
Most software in this category asks you to believe a number. Blueprint publishes the checks, the gaps, the build state and the measurement method. What we publish is measured. What isn't measured is labeled accordingly.
01
What Blueprint does not detect
Published rules
Every check the engine performs, with conditions, rationale and cited authority.
02Limitations
What Blueprint does not detect, stated plainly and kept current.
03Build status
What is implemented, what is partial, and what is not built at all.
04Benchmark
The measurement method, published before any result exists so the method cannot be chosen after seeing the numbers.
Pilot program
Run Blueprint against a real bid.
Blueprint is being validated against real packages, with real estimators, before it is sold as a finished product. A limited number of electronic security contractors and estimators are being taken on as design partners.
Step 01
Request a review
Tell us the project type and rough package size. No documents at this stage.
Step 02
Confirm the fit
We agree whether the package is in scope and how the documents will be handled.
Step 03
Run the package
Blueprint reads it and produces the register, with every finding sourced.
Step 04
Tell us what was wrong
Which findings were useful, which were noise, and what it missed. That feedback is the point of the pilot.
Find it while it's still an RFI.
Run Blueprint against your next electronic security bid package and see what deserves another look before submission.