The storefront glazing, the barricade and the fire alarm system are each assigned to two different parties in the same bid set.
The bid set for a retail store remodel in a shopping mall was checked for scope gaps, overlaps and pricing information before bids, and several major packages have two owners while structural supports the architecture relies on are not designed.
Mall store bid set scope
A bid set of architectural, structural, mechanical, electrical, plumbing and fire protection drawings for a retail store remodel in a shopping mall, with the responsibility schedule, specification sheets and energy compliance forms, read against one another and the code sections the review cited.
What the review compared
The review read the bid set for a retail store remodel in a shopping mall: architectural, structural, mechanical, electrical, plumbing and fire protection sheets, the responsibility schedule, specification sheets and the energy compliance forms. Its instructions asked for scope gaps and overlaps, conflicting pricing requirements, addenda and revision consistency, and the information needed for pricing and purchasing, without inventing costs, quantities or lead times. Code checking was enabled.
Where bids would not level
Several large packages have two owners. The storefront glazing, the storefront barricade, the fire alarm system and the HVAC disconnects are each assigned to different parties on different sheets, so bidders can carry them twice or not at all. Elsewhere, the architecture relies on structure that is not designed: a steel lintel at a bulkhead cut, a support for chandeliers heavier than the detail they point to, an air handler missing from the support plan, and hanger notes written for bar joists under a concrete plank floor. The mechanical energy compliance form bound into the set reports that it does not comply.
What to verify next
The owner and architect should assign every package once on the responsibility schedule and align the trade notes before bids are due. The structural engineer should design the lintel, the chandelier and air handler supports and a plank anchor detail. Examples that cite a requirement follow the documents and code sections the review cited; every example is a question for the design team.
12 selected examples from the review
Twelve distinct findings, summarized for professional verification.
Storefront glazing has two buyers
Schedule rows give storefront glazing, mullions and trim to both the contractor and the owner’s vendor.
Why it matters: Bids may carry it twice or not at all.
What to check: Name one furnisher and installer.
ArchitecturalBarricade built by two parties
The schedule gives the storefront barricade to the owner; general notes give it to the contractor.
Why it matters: It may be priced twice or by no one.
What to check: Name one party to build and remove it.
ArchitecturalFire alarm assigned to two contractors
Electrical notes give the fire alarm system to the electrical contractor and to the mall’s contractor.
Why it matters: The work may be carried twice or missed.
What to check: Name one party for design through testing.
Electrical · Fire ProtectionBulkhead lintel never designed
A section calls a new steel lintel at a bulkhead cut; no structural sheet sizes it.
Why it matters: The lintel cannot be priced or fabricated.
What to check: Size and detail it before bids.
Architectural · StructuralChandeliers heavier than their support
Two chandeliers are tagged to a support rated below their weight; their own detail is unfinished.
Why it matters: Their support cannot be priced or installed.
What to check: Issue a support detail for that weight.
Architectural · StructuralMain panel breaker rated two ways
The scope and the riser give different ratings for the landlord breaker feeding the main panel.
Why it matters: Whether it must be upsized, and by whom, is unclear.
What to check: State the rating and any change.
ElectricalDisconnects assigned to different trades
Condensing unit, air handler and fan disconnects have different installers on different sheets.
Why it matters: Electrical and mechanical bids cannot be leveled.
What to check: Name one party per disconnect.
Mechanical · ElectricalSupport plan misses an air handler
The structural support plan omits one scheduled air handler and labels another unit twice.
Why it matters: Its hangers and bracing are outside the structural scope.
What to check: Add the unit and fix the labels.
Structural · MechanicalHangers written for joists over plank
Hanger and fixture support notes assume bar joists; the floor above is concrete plank.
Why it matters: Each trade may price its own support method.
What to check: Issue a plank anchor detail.
Mechanical · Electrical · StructuralEnergy form reports noncompliance
The bid set’s mechanical energy compliance form reports two condensing units below the minimum efficiency.
Why it matters: Units or the form may change after award.
What to check: Select complying units or correct the form.
MechanicalAir handler without outdoor air
One air handler is scheduled for outdoor air, but the plan shows no duct or damper.
Why it matters: The duct and damper are outside every bid.
What to check: Draw the duct or revise the schedule.
MechanicalWindow trim kept and removed
Demolition keeps the decorative window trim; storefront notes and the scope remove and re-install it.
Why it matters: Bidders cannot tell what to price.
What to check: State one treatment and align the notes.
ArchitecturalReview scope and priorities
The review organized the questions by severity, discipline, and source context so the responsible designers could investigate them.
Architectural, Structural, Mechanical, Electrical, Plumbing, and Fire Protection
Check the findings with the responsible discipline designers.
High, Medium, and Low priorities
Selected examples retain their assigned priority.
Drawing coordination and code checking
Code checking was enabled alongside the review of plans, schedules, details, and notes.
Findings connected to their source context
Groundbook links each finding to the sheets it came from so the responsible designer can confirm or dismiss it.
Potential impacts describe the issue type. They are not verified outcomes from this project.
Follow the information across the complete set
Groundbook reads the documents you upload and reports where they disagree, where a reference does not resolve, and where a required value is absent.
See how a full set is reviewed or how interfaces are coordinated.
- 1Map the complete set
Identify sheets, disciplines, details, schedules, and notes.
- 2Connect repeated information
Follow tags, references, and requirements wherever they reappear.
- 3Check drawings and code references
Read the detected code references alongside the drawing evidence.
- 4Return findings for verification
Organize potential issues by severity, discipline, and supporting context.
Questions for professional verification
The output supports the responsible designers as they review the source documents and decide what needs to change.
What this result means
- Groundbook surfaced potential issues for professional review.
- Severity helps prioritize which questions to investigate.
- The findings describe coordination, completeness, and code-reference questions in the uploaded set.
- Each finding includes source context for verification.
What it does not mean
- Every potential finding is a confirmed error or violation.
- The project was unsafe, unbuildable, or ultimately noncompliant.
- Groundbook replaced the responsible professionals or authority.
- A correction was made, or any cost or delay was avoided.
About this review
Is this a real review?
Based on a Groundbook review completed in November 2026. Findings are summarized.
Are these findings confirmed defects?
No. Each one is a potential issue for the responsible designer to verify against the source documents. Groundbook reports what the documents say and where they disagree. It does not make design decisions, certify compliance, or replace the authority having jurisdiction.
How long did the review take?
Turnaround runs from 20 minutes to 24 hours depending on project size.
Which codes were checked?
Code checking was enabled for this review. Groundbook detects the codes a set references, reads the codes and amendments that governments publish online, and uses licensed codes only where a license allows it.
Can I see a full report?
Yes. The sample plan review report shows all 79 findings from one review of a drawing set and its specifications, with the cited excerpts.
Continue from the case study
Explore the source-linked examples in the sample plan review report, or browse every published case study.
Give the next drawing set a connected first pass
Upload the project, choose the checks that matter, and receive structured potential findings with source context.