Skip to main content

🔐 Strike — Door and Opening Specification Reader

One bad line in a repeating set hits every opening.
Strike reads your door and hardware specification before the number is committed and tells you where the hardware sets, the door schedule, and the code notes disagree, with the page behind every finding.
No rollout. Bring a package you already know.

Who this is for

Door and hardware estimator
One bad line in a set that repeats hits every opening carrying it. The schedule says one thing, the life-safety plan says another, the number is due tonight, and a miss after award comes out of my margin.
GC project engineer
I own twenty trades and doors is the one that slips. I sent the clarification three times and the wrong-voltage strikes showed up in the frames anyway. Nobody owns the line between Division 8 and Division 28.
Distributor submittal detailer
It came back revise and resubmit, and nothing is ordered. My drawings are fine. What bounced was a field the reviewer scans first, and the weatherstrip fighting the closer that nobody saw until I was ordering.
Senior hardware estimator
I have been pricing openings thirty years and I am faster with a pen. Every system we bought cost us a year and gave us back a spreadsheet. Show me what it does on a job I already priced.
GC preconstruction estimator
Two door quotes, eighty thousand apart, and I cannot tell you why. One carried the exit devices and one did not, and neither said so. Whatever both of them left out comes back as a change order.

How It Works

You hand Strike the specification sections as issued, the door schedule, and the life-safety plan, plus the jurisdiction if you know it. It reads the hardware sets against the schedule and the code notes, checks every rated opening against its listing, and finds the sentence that assigns each electrified lock’s power and prep. You get each disagreement named with the section behind it, what the manual leaves unassigned, and what Strike could not determine, stated plainly.

IN

The manual as issued

Specification sections, door schedule, and life-safety plan as written, not a summary, plus the jurisdiction if you know it.
READ

Three documents, one opening

Sets against schedule against code notes. Rated openings checked against their listing. The boundary sentence for every electrified lock.
OUT

Findings you can check

Each disagreement named with its section, what the manual leaves unassigned, and what Strike could not determine, stated plainly.

Example format — these cards show the shape of a finding, not a real result.

Door Schedule, Opening 114 / Hardware Set 07

Flagged

The schedule shows Opening 114 as a 90-minute rated pair. Set 07 lists no coordinator. Either the schedule or the set is wrong.
Door Schedule, Sheet A-601
Section 08 71 00, Part 1.4.B

Found

Power supplies for electric latch retraction are assigned to Division 08 in this paragraph, with door prep and power transfers in the same sentence.
Spec page 08 71 00-3
Section 08 71 00, Part 2.6 / Opening 102

Could not determine

Delayed egress on Opening 102 turns on a local amendment this read cannot verify. Name the authority having jurisdiction to resolve it.
Spec page 08 71 00-9
“The label is the product, and NFPA 80 forbids the field repair. That is why I check the rating column before I look at a single component.”
Strike

What it does

01

Reconciles sets, schedule, and code notes

Names every disagreement visible in the documents you provide, before you price, and flags where the paper may not match the building.
02

Checks rated openings against the listing

Every component on a rated opening is checked against its listing constraint, including the ones the schedule never mentions.
03

Finds the electrified boundary sentence

Locates who furnishes, installs, preps, and powers each electrified lock in 08 71 00, and names what the manual leaves unassigned.
04

Shows its work, declines when unsure

Every determination carries its section, listing, code reference, or function code. Unverified local amendments are marked unverified, not resolved.
05

Writes allowance and exclusion language

Per-leaf allowance and exclusion language where the bid allows a qualification. On a public or fully responsive bid, it frames the pre-bid question instead.
06

Checks each set for conflicts

Component against component, function against door type, prep against frame: the weatherstrip fighting the closer, named before ordering.
07

Runs the submittal completeness pass

Rating and hardware match, UL 10C references, double-door lines, finish codes. What the reviewer scans first, reported as missing rather than filled.
08

States what a complete package contains

A standard for this specification, so you see what every quote left out, not only where two quotes differ.

The Promise

Strike names every disagreement visible in the documents you provide, shows the section behind each one, and flags where the paper may not match the building. It does not promise a caught error or a saved change order. Nobody in this trade has documented prevention, Strike included. It does not verify installed compliance or decide who pays. It works when you bring the sections as issued, the schedule, and the jurisdiction, at bid, while a fix is still a redline.

Objections

“We already bought a system that was supposed to do this. It sat there.”

This is not a platform decision. There is no implementation, no migration, and nothing to move into. Run it on a bid you already priced. It costs no bid-season hours, and you see whether it reaches your answer.

“It cannot read the local amendments, and that is where the risk is.”

Right, and it says so. Where adoption or amendment status cannot be verified, Strike marks it unresolved instead of defaulting to the model code, and names where each requirement lives, including outside the submittal section.

“Does it find conflicts between products, or just lay them out?”

Have it show you on a real set: the coordinator against the closer, the weatherstrip against the hardware, the double-door lines. It reads and reports. It does not sync into your system or hold a copy of anything.

“I am faster with a pen.”

Probably true, and nobody is asking you to put it down. Run Strike alongside your paper on a job you already priced. If it does not reach your answer by a path you would follow, the pen was right.

“Sub pricing is never comparable. No software fixes that.”

Agreed. Strike does not compare the quotes. It states what a complete package must contain for this specification, so you see what every quote left out, not only where they differ from each other.
Run it on a package you already priced

Bring a job you know cold. Within an afternoon you will know whether Strike reaches your answer by a path you respect.

No rollout, no migration, nothing to sync.
One bad line in a set that repeats hits every opening carrying it. I catch it while it is still one line.