Bid / no-bid intelligence · Divisions 26 · 27 · 28
Four days to decide. Three hundred pages of Division 26.
RFiQ reads the whole bid package — spec book and E-series drawings — pulls your Division 26/27/28 scope, checks the GC and the developer against your own win history, and hands back a verdict you can argue with.
Specs and drawings, not just the spec book
Grounded in your win history
Every factor shown, every call overridable
Design partners are onboarding now. No spam, no pricing pitch.
Package · 412 pp · 38 E-sheets4 min 11 s
92
GO
Chase it. Scope fits what you self-perform.
Long-lead equipment · weeks to site
Switchgear30
Panelboards16
Lighting control10
BID 11 AUGAWARD ~12 SEPENERGIZE 4 MAY
!Switchgear lands three weeks past the energize milestone. Owner-direct, so it isn’t your money — but it is your sequence, and the GC will ask you to absorb it.
Why
014-of-11 with this GC’s Southeast office — above your book average.
02Div 26 scope is 91% self-perform work; no gear you sub out.
03Switchgear is owner-direct — 30 weeks out. Schedule risk sits with the GC, not you.
The problem
Electrical scope doesn’t live in one place. Neither does the risk.
Split across three divisions
Power in 26, communications in 27, safety in 28 — and half of what you’ll be held to is drawn on the E-series, not written in the book.
Estimators are the constraint
Every hour spent pricing a job you were never going to win is an hour stolen from a job you could have taken.
Gear decides the schedule
Switchgear on a 30-week lead, an ODP list you find in an addendum, and a GC who assumes you absorbed it. By then you’ve already bid.
A missed line item on the E-series is a change order you don’t get.
Chasing a loser burns estimating hours you can count. Missing a feeder run, a lighting control panel or an owner-furnished unit is a number you eat at closeout. Both compound, quarter after quarter.
How it works
Spec book in. E-series in. Verdict out.
01
Drop the package in
Project manual and the drawing set, however your GC sent them. Big PDFs are the normal case, not the exception.
Project manualE-series drawingsAddenda
02
RFiQ reads all of it
Divisions 26, 27 and 28 located across specs and sheets, pulled into structured line items you can click back to the source page.
Div 26 · 27 · 28Page-level citationsReview flags
03
You get a verdict, and the argument behind it
GO, CAUTION or NO-GO with every factor exposed. Disagree and override — that override trains your next verdict.
GO / CAUTION / NO-GOFactor breakdownOverride logged
DAY ONENo history in the system yet? Upload your past bids as a spreadsheet and RFiQ starts from “you’re 4-of-11 with that GC’s Southeast office” instead of “first time”.
Inside the verdict
Every line traced back to a page and a sheet.
Scope, extracted
Located across the spec book and the drawings, line by line, with the page it came from.
26 05 19Low-voltage conductors & cablesp. 118
26 24 16Panelboards — 12 branchp. 141
26 51 00Interior lightingp. 166
27 15 00Horizontal cablingp. 204
28 31 00Fire detection & alarmp. 231
Built for recall — flagged for review, never silently dropped.
Who you’re bidding to
GC and developer resolved to the regional office — because one office is not the other.
General contractor4/11
Regional GC · Southeast office
11 bids · 4 wins · last won 8 months ago
Developer0/0
First time on your book
No history · payment terms unproven
Engineer of record6
Seen on 6 prior packages
Specs run tight; few addenda
Signals off the drawings
The things that quietly swing labor value and margin, read straight off the E-series.
Drawing stageIFB
Square footage142,000
OFCI items3 found
ODP equipmentSwitchgear
Stage matters: an IFB set and a DD set are not the same bet, and RFiQ says so.
RFiQ decides whether to bid. It is not a takeoff tool, not an invitation aggregator, and not a contract-risk reviewer — it hands off to the ones you already use.
Your data
Your bid history is the asset. We treat it that way.
We don’t train on your data
Your packages and your bid history are used to answer your questions. They never become someone else’s model or someone else’s benchmark.
One org, one wall
Every document, scope item and win record is scoped to your organisation. There is no cross-customer pool, aggregate or otherwise.
Documents on your terms
Set how long packages are kept after a verdict. Delete a project and its extractions go with it.
Every verdict is auditable
Who ran it, what it said, what changed, who overrode it and why — kept as a record you can pull, not a log we hide.
Access you control
SSO and per-seat roles, so the estimator, the chief and the owner see what their job requires and nothing more.
No silent changes
When scoring criteria change, the change is recorded against the verdicts it affects. Old calls stay explainable.
Ask before you bid.
We’re taking on a small number of subcontractors as design partners. You bring real packages and real bid history; we bring the verdict engine and move fast on what you tell us is wrong.