The partition types call lighter studs than the structural wall schedule requires for the same full-height walls.
The construction set for a retail store fit-out in a shopping center was read for scope gaps, owner decisions and cost risk, and the architectural framing, fixture anchorage and rooftop equipment sheets describe different walls, racks and units from the structural and mechanical sheets.
Retail store framing and anchorage
Architectural, structural, mechanical, electrical, plumbing, fire protection, security and technology drawings for a retail store fit-out in a shopping center, with the responsibility schedule and trade specifications bound into the set, read against one another for scope, consistency and value engineering.
What the review compared
The review read the full construction set for a retail store fit-out in a shopping center: architectural, structural, mechanical, electrical, plumbing, fire protection, security and technology sheets, with the responsibility schedule and the trade specifications bound into the drawings. Its instructions asked for unresolved owner decisions, scope gaps, cross-discipline conflicts and cost or value-engineering risks. Code checking was not enabled.
Where the architectural and structural sheets part ways
The framing is drawn twice. The partition types call lighter studs and a different head connection from the structural wall schedule, the ceiling suspension and its seismic bracing differ between the architectural and structural details, and an architectural seismic sheet is older than the rest of the set. The fixture and rack anchorage was designed for a layout and rack height the store no longer uses. On the roof, a note calls for a new unit the mechanical sheets do not include, the roof plan shows a unit no other trade accounts for, and one unit’s breaker exceeds its own scheduled maximum protection.
What to verify next
The architect and structural engineer should settle one stud, head and ceiling design and align the anchorage tags with the current fixture and rack selections. The mechanical and electrical engineers should confirm how many rooftop units serve the store and size each circuit to its unit. Every example is a question for the design team before pricing.
12 selected examples from the review
Twelve distinct findings, summarized for professional verification.
Partition studs lighter than the structure
The partition types call lighter stud gauges than the structural wall schedule.
Why it matters: Bids from the partition types would carry undersized studs.
What to check: Match the types to the structural schedule.
Architectural · StructuralDoor taller than its framed opening
A new door is scheduled taller than the opening its structural header detail allows.
Why it matters: The header would need redesign after the door is ordered.
What to check: Revise the opening or the door height.
Structural · ArchitecturalRooftop unit breaker above its rating
A unit’s breaker and fuses exceed the maximum overcurrent protection its schedule gives.
Why it matters: Protection or wire may change after nameplates are checked.
What to check: Size the circuit to the unit data.
Electrical · MechanicalRacks taller than their anchorage
Specified stockroom racks are taller than the anchorage detail the structural plan assigns.
Why it matters: The anchorage would not cover the racks bought.
What to check: Check the detail or select shorter racks.
Structural · ArchitecturalTwo head connections for one wall
The architectural head detail assumes joists and open deck; structural uses a deflection track.
Why it matters: Every full-height wall invites a question.
What to check: Point the types to the structural head.
Architectural · StructuralCeiling suspension drawn two ways
Architectural details call rod-and-channel hangers and one grid; structural calls wire and another.
Why it matters: Bids may carry a system the bracing does not cover.
What to check: Pick one system and align both.
Architectural · StructuralSeismic detail sheet out of date
An architectural seismic sheet cites missing sheets and lighter splay wires than structural.
Why it matters: Bracing could follow the outdated detail.
What to check: Reissue the sheet or withdraw it.
Architectural · StructuralTrade bracing criteria disagree
Four trade specifications give different risk categories from the structural design data.
Why it matters: Bracing may be designed to the wrong category.
What to check: Refer every trade to the structural values.
Structural · Fire Protection · Electrical · PlumbingFixture anchors follow an old layout
Anchor tags match neither the count nor the positions on the fixture plan.
Why it matters: Anchors and inspection would follow a superseded layout.
What to check: Retag anchorage to the current plan.
Structural · ArchitecturalNew rooftop unit called, not designed
A roof note calls a new unit and opening; mechanical sheets keep the existing units.
Why it matters: Bidders may carry or exclude a large roof scope.
What to check: Delete the note or design the unit.
Mechanical · ArchitecturalFour units on the roof, three designed
The roof plan shows four existing units; mechanical and electrical sheets account for three.
Why it matters: The fourth unit’s controls and power are unknown.
What to check: State what it serves; number units consistently.
Mechanical · ElectricalPlastic waste pipe allowed and banned
Some plumbing notes ban plastic waste pipe; others allow it below the slab.
Why it matters: Bidders may price different pipe and joints.
What to check: Choose one material and align the notes.
PlumbingReview 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.
Coordination and completeness within the set
This review checked the documents against one another. No code check was enabled.
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 coordination and completeness
Compare the documents and identify missing or conflicting information.
- 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 and completeness 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.
Was a code check included?
No code check was enabled for this review. It covered coordination and completeness within the set. Code checking is available: Groundbook reads the building codes that governments publish online and uses licensed codes only where a license allows it. You can upload a copy you’re licensed to use.
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.